3 ms·
More appropriately no one seems to know who is routing them to null island. You can't deal with this type of data for very long before you run into the case wh
by yaur 10y ago
More appropriately no one seems to know who is routing them to null island.
You can't deal with this type of data for very long before you run into the case where you (or someone who processed the data before you got it) messed up and you end up with 0,0 coordinates.
- jrkatz 10y agoI see a lot of geocoding at work and one of the real mysteries is that null island is a fair few miles around. 0,0 isn't good enough for some people; 0.00001,0.00002, etc always have to get involved. Reliably catching that variant of the "Actually, I think your address is wrong" error needs a null island at least 50 miles across. If I had to guess, there's a UI somewhere that allows people to drag a pin to the exact right location when it isn't close enough, and feeds that back into a geocoding database. They can only drag for so long across the Atlantic before they give up.
- yaur 10y agoI believe that anything between (1,1) and (-1,-1) is safe to kill if you are are only dealing with land based coordinates.
- Johnny555 10y agoThe distance between 0.00002,0.00002 and -0.00002,-0.00002 is only 0.006290km (or around 20 feet).
- Symbiote 10y agoConverting coordinates between different coordinate systems could give these figures. I should probably add a check for this in my work, I think it only checks for null in WGS84 at present...