It's interesting that this feels awkward to you, because when apps don't function this way it feels broken and odd to me. When I tap a PDF attachment in an email I expect the back button to go back to the email I was just viewing, not the list of PDFs on my phone. If I wanted to view all the PDFs on my device, I would start at the PDF viewer and tap into PDFs from there.
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!
I kind of agree and see what you mean, but what I described happen often that I forget where I came from and have no idea that the PDF I read was opened from some other app.
It's part of what I mentioned in another comment, that BACK button can feel random. "Did I open this PDF from within the PDF viewer or from some other app? What app?" Instead of the BACK button having a predictable, known, function, it depends on some hidden state.
I love seeing all the great comments in here about the different APIs and the features they do and don't offer, but I want to point out that the underlying data for addresses is incredibly hard to find. The reason the commercial geocoding providers won't let you store their data is because they're worried you'll store enough data to build your own geocoder.
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!
It boils down to the fact that the United States does not have (public domain) knowledge of every address in the country.
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...
> It boils down to the fact that the United States does not have (public domain) knowledge of every address in the country.
i suspect licensing problems but this sounds too absurd to be true. as you said, there are multiple companies that have said dataset, at least one is under goverment control, saying nothing of the biggest defense/intelligence complex in the world which probably has coordinates of every address on the planet.
> 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
Why does the USPS need a moat? It's not a private, profit-seeking enterprise
A major political party and several large corporations are opposed to increasing federal funds to the post office. Unless you can spin it as national defense, notable federal funding for any group is unlikely.
"Education is key to every aspect of national defense, and broadband maps are a critical element of seeing that our future soldiers, laborers, and engineers have the resources they need in order to be the best and brightest -- on the battlefield, in the factory, and in the office designing the next generation of war machine."
The other major political party likes its make work program for its voter base, so it’s unlikely to accept a one time payment vs guarantees of organizational stability.
You...are aware that the US military is a rural welfare program, right? It's designed to suck in skilless, poorly educated rural (and to a lesser degree, urban) young men...and to employ adults making munitions, gear, vehicles, and weapons systems.
For example, just about the only reason Susan Collins is still a congressional representative is because she reliably keeps defense spending rolling into the Portsmouth naval shipyard which in turn is fed by a large network of suppliers.
When we did "Remote Encoding" for the USPS one of the early common "modes" was asking for Zipcode + 4 + Last 2 of House Number. The administrators explained that this 11 digit number was enough to uniquely identify most deliverable addresses "boxes" in the United States.
I like BAG. It is a shame that our WOZ-waarde (municipal home valuation) isn't a similar centralised system but that every municipality does their own thing. Similar for zoning, charge points and traffic signage / traffic data.
> 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
I don't know if it's still the case, but ISP's tools for address offerings were unreliable enough that realtors have suggested getting an install estimate in writing if the seller didn't have broadband.
No major ISP will give you an install commitment in writing.
I wouldn't buy a house based on a mere estimate of the availability of something this critical.
It's a gigantic clusterfuck.
The realtors know they can't fix this, but they can't exactly let it impede the source of their paycheck either. I absolutely would not take advice of any kind on internet access from a realtor.
I don’t know if the following is related, but I find it very strange that title insurance is necessary. I would assume that both municipal and state governments would know exactly who owns what piece of property/natural resource rights/air rights/other property-related right at the click of a button.
> I don’t know if the following is related, but I find it very strange that title insurance is necessary. I would assume that both municipal and state governments would know exactly who owns what piece of property/natural resource rights/air rights/other property-related right at the click of a button.
They only need to know well enough to send a tax bill. If someone is paying property taxes, that's good enough for the municipality. It's not good enough when people start suing each other, at which point the municipality very much does not want to own the liability for any mistakes.
Consider the simple situation in which Alice sells property to Bob, without revealing (intentionally or mistakenly) that Carol has a lien against the property. If Carol comes to collect and Alice cannot pay, then Carol now also has a claim to the property.
Things get even more complicated with fraud. Lets say that Eve manages to fraudulently record a transfer from Alice to Eve, and then sells the property to Bob. Bob has not committed fraud, but Alice also should own it. In systems in which the government registry is indefeasible, then Bob owns it; Alice may recover money (see above why municipalities don't want to be liable), but not the property (had Eve been caught before selling the property then the fraud would have invalidated her claim, but Bob hasn't committed any fraud).
Of course they know. They also wisely refuse to accept responsibility for the reprecussions of being wrong.
This is the whole point of title insurance. You aren't paying for the answer. You're paying somebody to accept massive liability if the answer is wrong.
There is something called the "Torrens Title System" where the government does accept some part of this liability, subject to a huge raft of weird terms and conditions that the legislature can change unilaterally after the fact. It has only been successful in countries lacking constitutional limits on eminent domain, since in those places landowners are already subject to legislative whims anyways:
It has been a flop in every US jurisdiction that has tried it.
When given a choice between transferring responsibility to somebody who can be sued (states can't) and gives you a contract, vs someone who can't and won't, it turns out people prefer the former.
I like the part where we're expected to just believe these agencies/departments aren't sharing and circulating address data internally, simply because they say they aren't. As if they've never misled and outright lied to the public thousands of documented times in the past.
Interestingly, it wasn't the Obama administration that tried to build the high speed rail. It was the Republican governor of Wisconsin (Tommy Thompson) that pushed for it. Scott Walker used it as a wedge to split the electorate and win the election. Wisconsin Public Radio did a great podcast about it here: https://www.wpr.org/derailed/wisconsins-high-speed-rail-saga...
OSM editors are prevented from using Google Maps because OSM prefers that we have explicit permission to use data sources. Since we don't have explicit permission to use Google Maps, we can't use it.
Separately, Google Maps has a terms of use that prevent reuse of Google Maps data. You agree to those terms when visiting Google Maps or using Google Maps API.
You wouldn't be breaking copyright law when copying from Google Maps to OSM, you'd be breaking the terms of use contract with Google and community Norma expectations in OSM.
> You agree to those terms when visiting Google Maps or using Google Maps API.
Those terms are not even presented on the screen when visiting Google Maps. And even if they were, I didn't sign anything or agree to anything. It is ridiculous if those terms are legally binding. Because then I will make a site and make you pay $1 for every page viewed.
> And even if they were, I didn't sign anything or agree to anything. It is ridiculous if those terms are legally binding.
Contracts don't need to be signed to be valid (when was the last time you signed a contract with an online shop). And if you don't agree to the terms, then you're using the site without permission and can be sued for damages. But the exact amount to pay can't just be any made-up number.
Similarly, if you walk into a shop, take an apple and eat it; then when the shopkeeper demands a million dollars, you can refuse to agree. Then the shopkeeper is free to sue you for destroying his property and you will be ordered to compensate him, although probably not for the full amount.
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!