Hacker News new | ask | show | jobs
by enticeing 2643 days ago
I think the point is that ringleader.kilt.comedians and since.duplicated.backswing have no relation at all to each other, and don't communicate to the user their spatial relationship. On the other hand, you could infer that 1234 W Something Rd is nearby 1238 W Something Rd.

EDIT: Also, given a set of lat/long coordinates, regardless of the precision, you could infer their spatial relationship as well.

2 comments

Yea, in LL, 1 second of arc at the equator is about 101 feet or 31 meters which means it's pretty easy to figure out relative coordinates, particularly N/S. Even UTM/MGRS is better in this respect.
That UTM/MGRS even exits seems to be lost on most pitching W3W.

For great circles the metric ratio is close to 40000km/360. A simple trick would be converting to 400gon first¹, but even using 111 Km per degree is a useful approximation.

So 0.01 decimal degree difference in latitude is always 1.11km or roughly 1km. All you need to remember is your length of 1 degree longitude at given latitude which is the following basic trigonmetric relation:

0.01deg = cos(lat) * 1.11km

Cheap linear approximation will do well here too. In South to North order: So usually factor down to 0.8 to 0.7 (38 to 48 Miles) if you live anywhere in the continental US. For Europe it's 84km in Rome, 72km in Paris, 69 in London, 67 in Berlin and 56km in Stockholm

And for approximating local distances it's simply those metric deltas with pythagoras, no need for Haversine or even non-spherical earth models here.

The most important relation for anyone who is into earth and the metric system, is that it's 10M meters or 10,000 km from pole to equator per original definition. You dont even need to remember the earth radius, since that's also defined by 4x10,000km/2π historically.

¹It's a shame that the metric revolution stopped short of Gradians, when it comes to full metric convenience here.

https://en.wikipedia.org/wiki/Earth%27s_circumference#Histor...

"you could infer that 1234 W Something Rd is nearby 1238 W Something Rd."

Don't overestimate that. There are nasty exceptions where the street disappears and continues elsewhere without a significant gap in house numbers, especially in cities with a long history.

Don't throw the baby out with the bathwater here. Being able to naively navigate city -> street -> number is incredibly useful, and that it is occasionally broken doesn't make it an undesirable feature.
It's more than occasionally broken, there's billions of people living in spots where it doesn't work.
Billions? You've found navigation by street number to be unreliable in 20+ % of locations?

Either way, it does work for several billion other people.

I haven't personally found it to be the case, but I do know that people in much of the developing world simply don't have/use street addresses like are common in the "West".
Just because you use a system like W3W or even just lat/long for a rural address in a developing country, doesn't really mean you will easily be able to navigate to it. Many rural roads don't have names/numbers and may not even be marked on mapping software. Navigating to these kinds of places takes local knowledge (or at least a GPS, a recent topo map, and careful planning) to get to.
That's why an address consists of more than a street name and a number. It includes town, province/state, postal code, and country. When given two actual complete addresses, it is indeed possible to infer relative distance with reasonable accuracy, exceptions notwithstanding. (And I live near St Paul Minnesota!)

Even granting that your “nasty exceptions” comprise fully half of all complete addresses, that would simply mean that a normal addressing scheme is better than W3W 50% of the time and no worse in all other cases.