|
Re: Ringmap problem solved. |
Hi Roger: I briefly glanced at the program section posted below earlier. My first impression was that there may not be enough "condition handling" and had decided to look it over more carefully later (when I had more time). It looks like you have nailed it down. Good going. I would suggest that you add a routine to identify where groups of ring regions overlap "heavily". This may allow various earthquake hunters / (contestants) to narrow their picks more quickly (assuming they subscribe to the FFA concept as implemented). One way to do this is to "save" (in arrays or files) the ring lat/longs and then just do distance checks between points. Anything within range "X" (TBD km) could be considered an overlap region for further consideration(s). This could be printed to an output file or maybe a red box icon (or something) could be added to these overlap sections on the map. Yes...I may do a beta check for you when I get a chance. Are still at the same web-site ? .02 p.s. ( Just maybe a discovery of sorts awaits somebody here ...eh ) ?
Follow Ups: ● Re: Ringmap problem solved. - Roger Hunter 15:08:44 - 4/1/2002 (14463) (2) ● EQ Christmas Trees == multiple ringmaps geometry? - 2cents 22:42:07 - 4/1/2002 (14486) (0) ● Re: Ringmap problem solved. - michael 16:20:37 - 4/1/2002 (14464) (1) ● seismicity added anyway - Roger Hunter 16:56:42 - 4/1/2002 (14467) (0) ● Re: Ringmap problem solved. - michael 14:47:05 - 4/1/2002 (14460) (1) ● Re: Ringmap problem solved. - 2cents 22:49:53 - 4/1/2002 (14487) (1) ● Re: Ringmap problem solved. - Roger Hunter 04:41:29 - 4/2/2002 (14494) (1) ● Re: Ringmap problem solved. - 2cents 08:41:40 - 4/2/2002 (14498) (0) ● Re: Ringmap problem solved. - Roger Hunter 14:20:43 - 4/1/2002 (14458) (0) |
|