search

atorger / nvdb2osm

The Unlicense
9 stars 2 forks source link

Parking has some questionable values #41

Closed matthiasfeist closed 2 years ago

matthiasfeist commented 2 years ago

Hi. I am currently importing around this area: https://www.openstreetmap.org/#map=18/64.10740/16.17430 and I noticed that NVDB also has some data on parking spaces. However the capacity and the operator values are clearly bullshit 😆 So I was wondering if you think this is a systemic issue, if the data is wrong or interpreted in the wrong way, or if the best way would be to omit these tags. See here:

Screenshot 2022-01-03 at 16 57 39
atorger commented 2 years ago

I have not looked in many places but at least in some it has been correct :-). Almost all large public parkings are already mapped with more detail than NVDB provides though, so usually I dump that info. I think the interpretation is correct, but NVDB may not that well updated. I would guess that it is best on the parkings which has operator=trafikverket

NVDB provide all information only in one node, while the OSM mapping is usually spread out over several nodes and/or geometry.

matthiasfeist commented 2 years ago

ok. maybe my issue was an isolated incident then :)