Why does splitter remove (only) the created_by tag?
Hi all, I've noticed that splitter silently removes the "created_by" tag since version 8. I don't see a good reason for that, on the other hand we may also implement a filter to remove more tags. JOSM has a hardcoded list of tags which are silently removed when you edit an object. The JOSM source file OsmPrimitive.java contains this list: "created_by", "converted_by", "geobase:datasetName", "geobase:uuid", "KSJ2:ADS", "KSJ2:ARE", "KSJ2:AdminArea", "KSJ2:COP_label", "KSJ2:DFD", "KSJ2:INT", "KSJ2:INT_label", "KSJ2:LOC", "KSJ2:LPN", "KSJ2:OPC", "KSJ2:PubFacAdmin", "KSJ2:RAC", "KSJ2:RAC_label", "KSJ2:RIC", "KSJ2:RIN", "KSJ2:WSC", "KSJ2:coordinate", "KSJ2:curve_id", "KSJ2:curve_type", "KSJ2:filename", "KSJ2:lake_id", "KSJ2:lat", "KSJ2:long", "KSJ2:river_id", "odbl", "odbl:note", "SK53_bulk:load", "sub_sea:type", "tiger:source", "tiger:separated", "tiger:tlid", "tiger:upload_uuid", "yh:LINE_NAME", "yh:LINE_NUM", "yh:STRUCTURE", "yh:TOTYUMONO", "yh:TYPE", "yh:WIDTH", "yh:WIDTH_RANK" Do you think that splitter should contain such a filter for tags? I think it would be easy to add an option which would read a file with those tags or use a given one. Gerd
El 06/12/16 a las 14:32, Gerd Petermann escribió:
Hi all,
I've noticed that splitter silently removes the "created_by" tag since version 8.
I don't see a good reason for that, on the other hand we may also
implement a filter to remove more tags.
JOSM has a hardcoded list of tags which are silently removed when you edit an object.
The JOSM source file OsmPrimitive.java contains this list:
"created_by", "converted_by", "geobase:datasetName", "geobase:uuid", "KSJ2:ADS", "KSJ2:ARE", "KSJ2:AdminArea", "KSJ2:COP_label", "KSJ2:DFD", "KSJ2:INT", "KSJ2:INT_label", "KSJ2:LOC", "KSJ2:LPN", "KSJ2:OPC", "KSJ2:PubFacAdmin", "KSJ2:RAC", "KSJ2:RAC_label", "KSJ2:RIC", "KSJ2:RIN", "KSJ2:WSC", "KSJ2:coordinate", "KSJ2:curve_id", "KSJ2:curve_type", "KSJ2:filename", "KSJ2:lake_id", "KSJ2:lat", "KSJ2:long", "KSJ2:river_id", "odbl", "odbl:note", "SK53_bulk:load", "sub_sea:type", "tiger:source", "tiger:separated", "tiger:tlid", "tiger:upload_uuid", "yh:LINE_NAME", "yh:LINE_NUM", "yh:STRUCTURE", "yh:TOTYUMONO", "yh:TYPE", "yh:WIDTH", "yh:WIDTH_RANK"
Do you think that splitter should contain such a filter for tags? I think it would be easy
to add an option which would read a file with those tags or use a given one.
Gerd
I guess if splitter filters such useless tags or some more, output tiles would be smaller and mkgmap processing time would be shorter. If so, +1 for adding such filter.
The output tiles would be a bit smaller, but I don't think that mkgmap would be significantly faster as it ignores all tags which are not used in the style or somewhere in the java code. Might be different with xml format. Gerd ________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es> Gesendet: Dienstag, 6. Dezember 2016 15:14:15 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Why does splitter remove (only) the created_by tag? El 06/12/16 a las 14:32, Gerd Petermann escribió:
Hi all,
I've noticed that splitter silently removes the "created_by" tag since version 8.
I don't see a good reason for that, on the other hand we may also
implement a filter to remove more tags.
JOSM has a hardcoded list of tags which are silently removed when you edit an object.
The JOSM source file OsmPrimitive.java contains this list:
"created_by", "converted_by", "geobase:datasetName", "geobase:uuid", "KSJ2:ADS", "KSJ2:ARE", "KSJ2:AdminArea", "KSJ2:COP_label", "KSJ2:DFD", "KSJ2:INT", "KSJ2:INT_label", "KSJ2:LOC", "KSJ2:LPN", "KSJ2:OPC", "KSJ2:PubFacAdmin", "KSJ2:RAC", "KSJ2:RAC_label", "KSJ2:RIC", "KSJ2:RIN", "KSJ2:WSC", "KSJ2:coordinate", "KSJ2:curve_id", "KSJ2:curve_type", "KSJ2:filename", "KSJ2:lake_id", "KSJ2:lat", "KSJ2:long", "KSJ2:river_id", "odbl", "odbl:note", "SK53_bulk:load", "sub_sea:type", "tiger:source", "tiger:separated", "tiger:tlid", "tiger:upload_uuid", "yh:LINE_NAME", "yh:LINE_NUM", "yh:STRUCTURE", "yh:TOTYUMONO", "yh:TYPE", "yh:WIDTH", "yh:WIDTH_RANK"
Do you think that splitter should contain such a filter for tags? I think it would be easy
to add an option which would read a file with those tags or use a given one.
Gerd
I guess if splitter filters such useless tags or some more, output tiles would be smaller and mkgmap processing time would be shorter. If so, +1 for adding such filter. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (2)
-
Carlos Dávila -
Gerd Petermann