On 12/06/2014, John Baker <[email protected]> wrote: > 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.
Note that this kind of postprocessing cannot replace the gardening changesets. For the simple reason that if gardening, which is expected to include a manual review step, can make mistakes, there's no way a fully-automated script will do a better job. You can argue that the script's mistakes didn't impact the db, but really for that kind of corrections you just shouldn't attempt postprocessing at all. But postprocessing does have valid usecases, complementary to gardening : * One is the *=yes/true/1 case, which would be too much bother to fix in the db so we postprocess instead. * Another is changing, say, landuse=forest to natural=wood because *for my usecase* they're the same. In this case you cannot do this in the db, since there is a semantic difference. _______________________________________________ talk mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk
