http://wiki.openstreetmap.org/wiki/Mkgmap/help/Tags rework?
I am going a bit through the wiki and try to update pages and remove stuff that might irritate. The page http://wiki.openstreetmap.org/wiki/Mkgmap/help/Tags is a first try to document the tags that are used by mkgmap and that are created by mkgmap and can be used within the style system. The page is incomplete and at a first glance it is not easy understandable. At least a short introduction is missing. Is anybody there who wants to start a rework of this page? Thanks! WanMil
Am 20.12.2012 22:42, schrieb WanMil:
I am going a bit through the wiki and try to update pages and remove stuff that might irritate.
The page http://wiki.openstreetmap.org/wiki/Mkgmap/help/Tags is a first try to document the tags that are used by mkgmap and that are created by mkgmap and can be used within the style system.
The page is incomplete and at a first glance it is not easy understandable. At least a short introduction is missing.
Is anybody there who wants to start a rework of this page? I could do so, but I need someone, who adds all the Tags, which are used in mkgmap. Intro and explanation of the tags can I do.
Henning
I could do so, but I need someone, who adds all the Tags, which are used in mkgmap. Intro and explanation of the tags can I do.
Henning
What tags do you need? I think we have two groups: Those that are hard coded in *.java code and those that are coded in the style files. If you want a merged list of both hard coded and the default style files, see attached file. If created it with a simple patch that prints out all tag keys used in OSMHandler. Maybe that helps already? Gerd
Am 21.12.2012 09:28, schrieb Gerd Petermann:
I could do so, but I need someone, who adds all the Tags, which are used in mkgmap. Intro and explanation of the tags can I do.
Henning
What tags do you need? I think we have two groups: Those that are hard coded in *.java code and those that are coded in the style files. If you want a merged list of both hard coded and the default style files, see attached file. If created it with a simple patch that prints out all tag keys used in OSMHandler. Maybe that helps already I think the page is explaining the hardcoded tags. So I need only them. But I try to get them out of your list.
Henning
Henning Scholland wrote
I think the page is explaining the hardcoded tags. So I need only them. But I try to get them out of your list.
Wait a bit, I found out that the list also depends on the options, for example mkgmap:line2poi is missing. A year ago I created a list of all hard coded tags, I try to find it .. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/http-wiki-openstreetmap-org-wiki-Mkgmap-help-... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Am 21.12.2012 09:39, schrieb GerdP:
Henning Scholland wrote
I think the page is explaining the hardcoded tags. So I need only them. But I try to get them out of your list. Wait a bit, I found out that the list also depends on the options, for example mkgmap:line2poi is missing.
A year ago I created a list of all hard coded tags, I try to find it .. mkgmap:line2poi, :area2poi and line2poitype I got from my style-file.
Some questions: I have something like: mkgmap:postal_code!=* & mkgmap:postcode=* { set mkgmap:postal_code='${mkgmap:postcode}' } in my style. What is the difference between postal_code and postcode? Are mkgmap:ref, :gtype, :boundary_name, :phone only used by default style or are them hard coded? Are other tags without mkgmap: hard coded. oneway, toll, access and maxspeed are hard coded afaik. Are there more? Henning
Am 21.12.2012 09:39, schrieb GerdP:
Henning Scholland wrote
I think the page is explaining the hardcoded tags. So I need only them. But I try to get them out of your list. Wait a bit, I found out that the list also depends on the options, for example mkgmap:line2poi is missing.
A year ago I created a list of all hard coded tags, I try to find it .. mkgmap:line2poi, :area2poi and line2poitype I got from my style-file.
Some questions:
I have something like: mkgmap:postal_code!=* & mkgmap:postcode=* { set mkgmap:postal_code='${mkgmap:postcode}' } in my style. What is the difference between postal_code and postcode?
The location hook sets mkgmap:postcode (if --bounds is used). The StyledConverter looks for a tag mkgmap:postal_code So, if I got that right, the style should evaluate mkgmap:postcode and than set mkgmap:postal_code.
Are mkgmap:ref, :gtype, :boundary_name, :phone only used by default style or are them hard coded?
It's hard to say. Even if you find the string mkgmap:xxx in the java sources, it is not sure that this part of the program will ever be executed.
Are other tags without mkgmap: hard coded. oneway, toll, access and maxspeed are hard coded afaik. Are there more?
yes, a lot of normal tags are used when eg. a cycle way is created. I think most of the tags listed in hardcoded.tags.txt will be used somewhere. For more details, one has to search the java sources for the string constant and try to understand what's happening. Gerd
GerdP wrote
Henning Scholland wrote
I think the page is explaining the hardcoded tags. So I need only them. But I try to get them out of your list. Wait a bit, I found out that the list also depends on the options, for example mkgmap:line2poi is missing.
A year ago I created a list of all hard coded tags, I try to find it ..
Gerd
Attached is the list. It may not be 100% up to date. I created that when I tried to change all hard coded tags to constats. hardcoded.tags.txt <http://gis.19327.n5.nabble.com/file/n5741334/hardcoded.tags.txt> Gerd -- View this message in context: http://gis.19327.n5.nabble.com/http-wiki-openstreetmap-org-wiki-Mkgmap-help-... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Am 21.12.2012 09:59, schrieb GerdP:
GerdP wrote
Henning Scholland wrote
I think the page is explaining the hardcoded tags. So I need only them. But I try to get them out of your list. Wait a bit, I found out that the list also depends on the options, for example mkgmap:line2poi is missing.
A year ago I created a list of all hard coded tags, I try to find it ..
Gerd Attached is the list. It may not be 100% up to date. I created that when I tried to change all hard coded tags to constats. Thanks Gerd! I added a few of them. Some I don't know, so I left them out. Maybe others could take a look at it.
Henning
I could do so, but I need someone, who adds all the Tags, which are used in mkgmap. Intro and explanation of the tags can I do.
Henning
Thanks! I'll have a look on it and try to find and add more mkgmap special tags. I wonder if it would be better not to use a table but a small chapter for each tag or tag group. This could also contain an example how to use the tag. For instance when I read the description for toll the second column points out that it affects "routing - avoid options". My first dumb idea was: Okay, it affects routing but which options should I avoid? So maybe it is better to have some more text and examples? The naming of mkgmap:postal_code and mkgmap:postcode was my bad idea. It's very irritating. I don't mind changing that. Any better suggestion? WanMil
Am 21.12.2012 13:28, schrieb WanMil:
I could do so, but I need someone, who adds all the Tags, which are used in mkgmap. Intro and explanation of the tags can I do.
Henning Thanks!
I'll have a look on it and try to find and add more mkgmap special tags.
I wonder if it would be better not to use a table but a small chapter for each tag or tag group. This could also contain an example how to use the tag. This would be the next step. I think first we should collect all needed tags and maybe think about them (useful or not?). If they will be removed in a couple of versions, them we don't need to explain them.
For example: except=*. It is used in turn-restriction. I think this is a part which should be reworked, because actual you can't handle this part in style-file. Henning
Am 21.12.2012 13:28, schrieb WanMil:
I could do so, but I need someone, who adds all the Tags, which are used in mkgmap. Intro and explanation of the tags can I do.
Henning Thanks!
I'll have a look on it and try to find and add more mkgmap special tags.
I wonder if it would be better not to use a table but a small chapter for each tag or tag group. This could also contain an example how to use the tag. This would be the next step. I think first we should collect all needed tags and maybe think about them (useful or not?). If they will be removed in a couple of versions, them we don't need to explain them.
For example: except=*. It is used in turn-restriction. I think this is a part which should be reworked, because actual you can't handle this part in style-file.
Henning
I agree! Doing it step by step makes it easier :-) WanMil
I'll have a look on it and try to find and add more mkgmap special tags.
I've started looking through the source code for mkgmap special tags. Here is a first list. There are some additional tags for the marine styles: mkgmap:xt-depth mkgmap:xt-height mkgmap:xt-style mkgmap:xt-colour mkgmap:xt-type mkgmap:xt-light mkgmap:xt-period mkgmap:xt-racon mkgmap:xt-height-above-foundation mkgmap:xt-height-above-datum mkgmap:xt-leading-angle mkgmap:xt-note mkgmap:xt-int-desig mkgmap:xt-local-desig mkgmap:xt-facilities Fortunately they seem to be quite well documented: http://www.mkgmap.org.uk/websvn/filedetails.php?repname=mkgmap&path=%2Ftrunk... When using --generate-sea=close-gaps=N the way that is created by mkgmap to close gaps in the coastline is tagged with natural=mkgmap:coastline-gap mkgmap:mp_created values: true (false is not set) The multipolygon algorithm tags all polygons created by the mp algorithm with this tag. This is used internally by the add-pois-to-areas function but could also be used in the style file. Anyhow I don't know why... mkgmap:osmid values: the OSM id of the node All exit nodes (highway=motorway_junction and highway=services are tagged with this tag. This is used internally by mkgmap but could also be used in the style file. mkgmap:way-has-pois values: true (false is not set) All highway=* ways are tagged with true when one of its nodes has tags. This is used by the StyledConverter to use tags from these nodes to set/modify road speed etc. Can be used in the style file but I don't know why... mkgmap:dead-end-check values: true/false This flag defines if a oneway road should be checked for a dead end. These dead ends are reported by mkgmap (only if --report-dead-ends is set?). The style may set this flag to avoid this check on some roads (e.g. highway=construction). mkgmap:frig_roundabout This tag is set by mkgmap on all roundabouts if the undocumented option --frig-roundabouts=<double> is set. It has something to do with routing instructions on roundabouts. But I don't understand that after a short look on it. The option frig-roundabouts is not documented. Can it be removed? mkgmap:synthesised values: true (false is not set) This is set on cycle ways created by mkgmap to realize a cycle way lane on a street. The tag is used to ignore these ways on some checks (dead-end, roundabout flares etc.) Some tags are mkgmap internal, so they are set by mkgmap, are used internally by mkgmap and should not or cannot be used in the style: mkgmap:stylefilter values: polyline, polygon Determines that the element is processed by the line or polygon style only mkgmap:tagsincomplete values: true (false is not set) Determines that some of the multipolygons tags are not loaded from the OSM file because the style doesn't use them. This is used internally by the MP algorithm to decide if the tags should be taken from the MP or from its outer ways. mkgmap:removetags values: a ; separated list of tag names (mkgmap:ALL=all tags) The given tags must be removed before the style is applied. This is used by the mulitpolygon algorithm to remove duplicate taggings on ways and the relation. This list is not complete. I will continue later... WanMil
participants (4)
-
Gerd Petermann -
GerdP
-
Henning Scholland -
WanMil