postal code

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert Latest commit thisisaaronland Update README.md May 7, 2025 586600f · May 7, 2025 History 93 Commits Open commit details 93 Commits bin bin Create postalregions ( Fix compile.py for Python 3 Create postalregion placetype") 33 ) Fix compile.py for Python 3 Create postalregion placetype") Mar 1, 2024 data data Create postalregions ( Fix compile.py for Python 3 Create postalregion placetype") 33 ) Fix compile.py for Python 3 Create postalregion placetype") Mar 1, 2024 images images update diagram Oct 29, 2018 placetypes placetypes Create postalregions ( Fix compile.py for Python 3 Create postalregion placetype") 33 ) Fix compile.py for Python 3 Create postalregion placetype") Mar 1, 2024 .gitignore .gitignore Add DS Store to gitignore Jun 4, 2018 CONTRIBUTING.md CONTRIBUTING.md add docs; update Makefile May 18, 2016 LICENSE.md LICENSE.md add docs; update Makefile May 18, 2016 Makefile Makefile add docs; update Makefile May 18, 2016 README.md README.md Update README.md May 7, 2025 View all files For any hierarchy of place types we have identified three “roles” that any one of those place types can fall into. That doesn't mean there can't be others (roles or place types) only that these are the ones we've identified as a good place to start. These are, well, common across any hierarchy for any place in Who's On First. This part is important: It means that at some point every single record shares at least one or more common ancestors (for example a country or a continent or occasionally just the Earth). That doesn't preclude very specific additions to the hierarchy for a given location only that those additions need to fit within a common hierarchy shared across all locations. The blue boxes are common placetypes, the green ones common optional and the yellow ones are optional . Things like universities or office complexes and airports . Something something something, Burning Man and other annual events. This needs a better - that is more abstract - name. Like "region" instead of state, province, whatever... but for counties. Basically places that issue passports, notwithstanding the details (like empires which actually issue the passports...). In some areas country and dependency are used interchangeably. Custom placetypes are provided as a convenience for projects producing data that live outside of the "core" Who's On First (WOF) data repositories as a way to allow those records to have a well-known WOF placetype. This ensures that these projects can continue to use the WOF-related tooling, some of which enforces strict validation on things like placetypes. It's not a sub-region of a country but rather dependent on a parent country for defence, passport control, subsidies, etc. In some areas country and dependency are used interchangeably. Places that one or more parties claim as their own. As of this writing all disputed places are parented only by the country (and higher) IDs of the claimants. This isn't to say there aren't more granular hierarchies to be applied to these place only that we are starting with the simple stuff first. Or "sovereignty" but really... empire. For example the Meta United States that contains both the US and Puerto Rico. In many countries, the lowest level of government. They contain one or more localities (or "populated places") which themselves have no authority. Often but not exclusively found in Europe. In some areas locality and localadmin are used interchangeably. Towns and cities, independent of size or population. Things with neighbourhoods, basically. In some areas locality and localadmin are used interchangeably. Like "BoCoCa" which in WOE is a neighbourhood that parents another... neighbourhood. Economic geography areas that are usually an