To help with this, a group of folks (including me) started OpenAddresses (https://openaddresses.io/ and https://github.com/openaddresses/openaddresses/) with the goal of finding every open address dataset in the world. We produce a zip file with 100M's of addresses that several of the APIs mentioned in this thread use as a major part of their dataset. We've been going for well over 10 years now, but it would be great to have more eyes looking for more address sources. Check us out!
http://federalgovernmentzipcodes.us/free-zipcode-database-Pr...
Deleted Comment
Why does the USPS need a moat? It's not a private, profit-seeking enterprise
https://www.uspsoig.gov/focus-areas/did-you-know/postal-serv...
The USPS knows about deliverable addresses but won't give that information to the federal government because then it'd be public domain and they would lose several of their primary data moats (Zipcodes, addresses, delivery routes, for example). The Census has very complete knowledge of every address, but won't give it up because it's illegal (see Title 13 of the US Code). There is an ongoing attempt by the DOT to collect a National Address Database (https://www.transportation.gov/gis/national-address-database) by collecting information from the address assigning authorities (usually county governments), but it's incomplete and unlikely to ever be complete because of holdout/underfunded local governments.
There are several address datasets that are private (Google has a fairly complete one, FedEx/UPS probably have the most complete, TomTom, CostQuest, etc.). I started https://openaddresses.io/ to try and collect them (NAD is based off this idea) into an open-licensed dataset.
The broadband companies have records that say "this address is connected to this network, which could theoretically have this service level", but (a) they won't/can't tell you where they think the address is and (b) won't spend the time to match their address string format with the government's address because both are private data.
Finally, without the address -> location data, even if we could get broadband providers to tell us what service is available at each address, we couldn't put that service level on a map because we don't know where the address is.
----
The Markup published some work in 2022 where they used OpenAddresses to use ISP's own tools to gather per-address service offerings and put them on a map. This is what the FCC's broadband map should be doing, but can't for the above (and political) reasons: https://themarkup.org/show-your-work/2022/10/19/how-we-uncov...
- Hybrid does exactly what you're looking for: http://maps.stamen.com/toner-hybrid/#12/37.7706/-122.3782
But they also break that down into labels and lines:
- Labels: http://maps.stamen.com/toner-labels/#12/37.7706/-122.3782
- Lines: http://maps.stamen.com/toner-lines/#12/37.7706/-122.3782
Their Terrain style has a similar separation:
- Lines: http://maps.stamen.com/terrain-lines/#12/37.7706/-122.3782
- Labels: http://maps.stamen.com/terrain-labels/#12/37.7706/-122.3782
- Background: http://maps.stamen.com/terrain-background/#12/37.7706/-122.3...
Somehow that manages to surprise and confuse me almost every day. In desktop operating systems, and, I belive, in iOS, there is no need for such thing? Opening a PDF from a mail application usually just opens the PDF viewer as its own application, or it is embedded in some nice way that does not make the entire mail app suddenly look like a PDF viewer app instead.
Unfortunately they can probably never fix that because app lifecycle and intents are connected to everything and a good fix for this would probably break everything.
I wonder what experience made this feel more awkward for you (and conversely, why it feels more natural for me). What a weird/complex world we live in!