Roland, > > Please go to taginfo > https://taginfo.openstreetmap.org/ > choose "highway" there, browse through the values and tell me which of > the values you would like to change. >
Post processing that you spoke is about process the bad data into a readable form after the fact. It is used when you do not know what state the data is in and fixing the bad data. Potentially this could be anything. Also the data has already been fixed by the mech edits/gardening that has been done before and is done on a regular basis. I know I have done residential typos in the past. So many for this example might not occur still however for post processing you need to consider that they might and do happen. In theory if the data is perfect to begin with there is no need for any post processing. But searching on taginfo highlight the potential in-correctness of the data. There are currently 1049 values for highway. I could reverse your point and say are all of these 1049 values correct? For example is this correct? highway = "Bandar Road" https://taginfo.openstreetmap.org/tags/highway=Bandar%20Road#overview which is here: http://www.openstreetmap.org/#map=16/16.5072/80.6299 Now how do we fix that with any form of mechanical editing? Do I follow all the rules? wait a few weeks for a consensus on the import mailing list? Now I could seeing that just fix it to name = "Bandar Road" highway = unclassified (I could at aerial imagery and guess the correct type) The point of this type of gardening is to fix errors like this and make a better map. Some people are happy to leave that there until a local mapper fixes it as it will ruin the local community if I fix. They will be threats or actual blocks/bans etc if any fixes this that has no local knowledge and does this in a mechanical way. Even using in conjunction with aerial imagery may not be ok. > Couldn't this be even worse than applying those changes directly in > the database? >The postprocessing refers to the final data consumer, not the map on >osm.org. The map on osm.org is specifically designed for giving mappers >feedback. Therefore, it has no such postprocessing and will never have. The map at osm.org does have post processing to varying degrees most of it simple stuff (it is a bridge if it is true, yes or 1) and is a data consumer just as much as anyone else. Creating maps is probably the greatest data consumer use of openstreetmap data. The map is designed for various reasons (and that changes over time) one of them is mappers feedback. Post processing is a balance of doing everything and there is an overhead. Not much ignoring the case of something like that some might remove whitespace around a tag but beyond that there is very little most of time the solution is fixing the data. Thank you for your ongoing discussion.
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
