[Imports] [Talk-es] [Cat2Osm2] Tool for exporting Spanish Cadastre data in OSM suitable format

Cruz Enrique Borges Hernandez cruz.borges at deusto.es
Thu Feb 28 20:10:53 UTC 2013


Well these fixme are put because they need local survey. 
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.

So what will you suggest? The only options that came to my mind are:

+ Do not import these features.
+ Put a fair guess.
+ Put the most general tag we are sure it is correct.
+ Put all the fixme in a extra file named FIXME-DO-NOT-UPLOAD-OR-A KITTEN_WILL_DIE.osm
   with  an incorrect geometry (or something like that) to avoid the upload.

> Hi,
> 
> > Moreover, the tool puts a fixme in those places
> > because with the data provided it is not possible to distinguish between the
> > different types of garages (private or public) and the local mapper (who 
> > know the place) has decided that this is the best tag for them. 
> 
> Just like Andy said in an other email, I strongly suggest not to add fixme=* 
> or FIXME=* tags
> and I (only) suggest not to add *=fixme or *=fixme values in an automated or 
> semi-automated manner.
> 
> I know it is made to enlight the things to do in JOSM, but it might often end 
> where people will just upload the whole thing, without removing the fixmes 
> here and there.
> 
> And those fixmes will clutter the view of people seaking to repare manually 
> reported errors (in low numbers) where people have (hopefully) carefully 
> wrotten a fixme text for cases they cannot fix and need local survey.
> 
> I have seen people adding mass of fixme because they think the community "will 
> fix it" It only create frustration, make fixme displaying tools less usefull.
> 
> + Andy is again right, most can be detected by QA tools afterward
> 
> 



More information about the Imports mailing list