On jeudi 28 février 2013, Cruz Enrique Borges Hernandez wrote: > Well these fixme are put because they need local survey.
What you mean is that you don't require that the importer corrects the fixmes before the upload ? And that it should be corrected on the long run ? Then I'd say most of the highway in OSM could have a : fixme=please specify the width of this highway but we don't do it ;-) > I mean, for example, we know there is a parking space, but we did not have > enoght information to know if it is public or private. Then you don't need a fixme, but a QA tool to list the parking spaces currently in OSM not yet having a access=private/public Noone will forget to remove the fixme if the correction is done because it is determined by the new added access tag. (See pieren's comment about osmose) > So what will you suggest? The only options that came to my mind are: > > + Do not import these features. It depends how your community welcome the information in osm "here is a parking space, but we don't know yet if that is public or private" > + Put all the fixme in a extra file named FIXME-DO-NOT-UPLOAD-OR-A KITTEN_WILL_DIE.osm That could be valid if your import chain is meant to be : "Correct all the fixmes before the upload, or don't upload" but I guess that isn't the case ? However, if your goal is this, then I understand the fixmes are just a "JOSM enlightening trick" to be removed before the upload, then your import tool chain becomes different and yes you can provide un-uploadable osm files (maybe with positive ids in it + version=1) that people need to send back to moderators who check for no fixme in it and re-convert to uploadable form. But that is more complex. -- sly, DWG member since 11/2012 Coordinateur du groupe [ga] http://wiki.openstreetmap.org/wiki/User:Sletuffe _______________________________________________ Imports mailing list [email protected] http://lists.openstreetmap.org/listinfo/imports
