nycbuildings
nycbuildings copied to clipboard
osmlab
Infrequent duplicate address nodes
Looks like this area was redeveloped at this is old data that's still in the address DB.
Hi Ian, are you saying this because the building has two addresses or because of some other data?
I said that because the buildings all appear to be similar and none of the others have an entrance facing north. StreetView confirms my suspicion that there is no entrance on the north side of the building.
This is a going to be an especially hard one to fix during validation as we we can't really use google street view to correct this.
I think we need to punt on this as we have no way of verifying the address on the ground. Many of these instances are gone now as we're not importing range addresses anymore.
Many of these instances are gone now as we're not importing range addresses anymore.
How many are we talking about? I don't think that leaving incorrect data in OSM (ie punting) is an acceptable solution.
We can drop a note in places where we suspect that a given address is not correct. Not sure what else we can do.
The solution, I think, will depend on the frequency. The title of this issue is "infrequent duplicate address nodes", but I don't know what that means. Is it one? ten? a hundred? a thousand? ten thousand?...
If it's one, sure, put a note up there. If it's 10,000 (which would still fall under the definition of infrequent- representing 1% of all addresses, then notes aren't a good fit. So let's tailor the solution to the problem- but I don't think that knowingly putting incorrect data in OSM is a good solution.