Comment by kaikai | Hacker News Reader

Comment by kaikai | Hacker News Reader

Parent Full thread

I work on geocoding, so I have a ridiculous stash of these saved up for a talk some day. Here's a couple:

- Place names are listed smallest feature to largest feature (address, city, state, etc)

- There is one name (per language) for every place, and everyone agrees on it

- Place names will start with an alphabetic character (see: 's-Heer Arendskerke)

- Addresses start with a number, for each building

- Addresses include a number for each building

- Address exist for each building

- On streets with addresses, the addresses will be in order of location on street

- Speaking of streets: all streets have names

- Every country's place hierarchy is roughly similar, or at least has a similar number of layers

- A city can not contain other cities

- Zipcodes have defined areas

- Zipcodes are areas

- Zipcodes are stationary areas

Here's some that are more Arg! Programming!:

- People will search for features in the language in their phone settings

- Two similar names separated by punctuation are likely to be synonyms (lookin' at you, Helena-West Helena)

- Governments use consistent projections

- Governments use consistent file formats (thanks for the SOSI, Norway) (no but really y'all make great maps, thank you)

I could go on. Even though there's a ton of inconsistencies and frustrating moments, it really is a joy to learn about the world through its idiosyncrasies.

(edited for formatting)

> - Every country's place hierarchy is roughly similar, or at least has a similar number of layers

It was always fun seeing packages arrive in Singapore with an address ending in "Singapore, Singapore, SINGAPORE" since every international shipping company assumes that city, state/prefecture, country are all different and required.

Ideally address input would just be one multiline text field, but unfortunately users are just too unreliable to be left to their own devices like that...

Yeah! It's also hard to distinguish programmatically when this is a good response: New York, New York, is expected, while Hong Kong, Hong Kong makes a lot less sense.

There's a fun street in West Hartford: "Boulevard". Everyone abbreviates it to Blvd, of course. They didn't use it as a descriptor, it's the name.

https://www.google.com/maps/place/1500+Boulevard,+West+Hartf...

  - Zipcodes have defined areas
  - Zipcodes are areas
  - Zipcodes are stationary areas

Can you elaborate on these? I always assumed (thankfully not for any professional purposes) there was indeed an area assigned to each zip code.

Military zipcodes often do not have a defined area - as military units are mobile. The zipcode may direct mail to varying actual physical places.

Certain extremely high-traffic entities (e.g., government agencies) may also receive their own zipcodes - and mail directed at them may go to different places. Private places (see: Empire State Building, 10118) may also receive their own zipcodes which, while representing a physical building, defies the usual "defined boundary" zipcode definition.

It's worth noting that the zip-for-building case is very common, most cities with skyscrapers have a few with their own zip.

It still definitely counts as an edge case though, in the sense that if the building were torn down or foreclosed I don't think its block would still warrant its own code

Indeed, and it's important to remember that skyscraper-zipcodes create holes in otherwise regular polygons, which is often not accounted for when storing shapes of zipcodes.

Lots of edge cases abound when using zipcodes, especially zipcodes in a spatial context.

> It still definitely counts as an edge case though, in the sense that if the building were torn down or foreclosed I don't think its block would still warrant its own code

For example, the World Trade Center's zip code was retired after the 9/11 attacks.

https://en.wikipedia.org/wiki/10048_(ZIP_code)

In Singapore, every building of a reasonable size has its own zip code

Zipcodes in the United States are postal routes, which aren't really polygons like cities. We can make an approximation, but that's not how they're defined. In some countries, point postcodes are common. We just spent a bunch of time on postcodes in Great Britain, which commonly only have a few addresses in each one. Even in the Unites States, some universities or other large institutions will have a "postcode" which is a single address. The US military also assigns postcodes to ships, which tend to move a bit more than your average building.

As others have mentioned, zip codes might not have any geometry at all (point zips), and they are frequently updated/changed. In addition, zips do not follow standard constraints that other defined region types do. For instance, counties are entirely contained by their parent state, but that is not the case for zip codes, as they frequently cross county and state borders.

My understanding: Zipcodes are postal routes. We just typically visualize them as the box containing those routes.

USPS maintains them as lists of addresses (with some sort of relationship to delivery routes). A new address will be assigned a zip code based on convenience.

So at a given moment you can generalize those lists into areas, but the way they are defined, there isn't a real boundary, just a line that happens to separate the addresses with different postcodes.

Bangalore, a large city in Southern India, is probably the world leader in the proportion of layers that have embedded numbers. Here's an example:

ICICI BANK LTD, 273, 15TH CROSS, 20TH MAIN, JP NAGAR 5TH PHASE, BANGALORE - 560078

I happen to be in Bangalore right now and literally no one uses addresses. Everything is landmark based.

Reply on news.ycombinator.com