Rick Root wrote: > Actually, I did a limitation by longitude as well, because at the equator, > the fudge factor is the same (approximatley 69 miles per degree)... > everything in the US is less than that but I figured what the heck. So I > draw the box on both lat and long, knowing that the longitude will actually > encompass MORE than the area I'm looking for... the getDistance() function > actually does the work of exact distances anyway. As long as the "box" is > bigger than necessary, it's all good. > > I was thinking it might actually be wise to use a range factor GREATER than > 1/69 ... like 2/69...giving the latitude some wiggle room. > > But thinking about the math involved as to *WHY* I'd do that makes *MY* head > hurt! > >
What calculation did you use to limit the longitude?...if you are using the same one as latitude, I'm not understanding... Let's take a latitude around the center of our home state of NC...35 degrees... At 35 a degree of longitude is approx 57 miles long (per http://www.csgnetwork.com/degreelenllavcalc.html) 1 degree longitude/57 miles = .017544 1 degree latitude/69.172 miles = .014457 ..014457 < .017544 so you would be limiting too much of the longitude if you are only using the .014457 number. Are you doing something different? Or do I have it all wrong? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:268884 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
