I posted to the list last April http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2014q2/020800.html and there was no response. It seems that, although the post appeared on the mkgmap web site, most subscribers did not receive it because of the Yahoo! problem http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2014q4/022204.html Therefore I am reposting the message, updated as necessary: I have entered some public transport data into OSM. I have made every effort to enter the data in accordance with the new public transport schema. Some 'old' tags are also present because I started mapping the data before the new schema was approved. For testing purposes I used the extract from Geofabrik of the Languedoc-Roussillon region of France. I used r3433 with the default style and these options: --max-jobs --code-page=1252 --add-pois-to-areas --route --link-pois-to-ways --precomp-sea=sea-20150123211701.zip --generate-sea --index --bounds=bounds_20150129.zip --location-autofill:bounds,is_in,nearest --housenumbers. Looking at the results, I noticed a number of things. (1) Names of railway stations The names of many railway stations appear in the form SNCF: Agde. https://www.openstreetmap.org/way/72614628 This is the result of generic processing of names in the style file inc/name. There are about 3500 railway stations in France and more than half of them are tagged operator=SNCF. I would prefer to see the name in the form Agde SNCF, which was produced by earlier versions of the default style, before the file inc/name was introduced. This is more convenient for searching on a device. (2) Names of bus stops This is an example of the name of a bus stop as it appears in the generated map: Agglo Hérault Méditerranée: (1;2;3;4;5,4,4,3,3)(1;2;3;4;5,4,4,3,3)++ Gare SNCF https://www.openstreetmap.org/node/1424432523 The Garmin software and the device will only display the first part of the string. I used QLandkarte GT to see the complete string. (For legibility, I have used lower case in the strings, although they are in upper case in the generated map.) Earlier versions of the default style produced the result Gare SNCF (1;2;3;4;5,4,4,3,3)+Agglo Hérault Méditerranée, which I prefer. "Gare SNCF" is the name of the bus stop. The earlier version would be essential, to allow you to see the name of the bus stop on a device. What do others think? The solution which I use for my own maps, is as follows. Before line 16 of file inc/name ref=* & (operator!=* & brand!=*) { name '${ref} ${name}' | '${ref}' } insert this line ref=* & (operator!=* & brand!=*) & (highway=bus_stop | railway=tram_stop | railway=halt | railway=station) { name '${name} ${ref}' | '${ref}' } Before line 27 of file inc/name operator=* & brand!=* { insert these 6 lines operator=* & brand!=* & (highway=bus_stop | railway=tram_stop | railway=halt | railway=station) { name '${name} ${ref} ${operator}' | '${name} ${operator}' | '${ref} ${operator}' | '${operator}' } The text 1;2;3;4;5,4,4,3,3 can be changed to 1;2;3;4;5 by using the new not-contained filter as proposed in another thread. The doubling-up of the route_ref and the shelter indicator (+, - or *) is a bug. I will address this in a separate thread. I will leave a further question about public transport for another thread. Adrian
Hi all, I think (1) is still open. I have no idea if the proposed change will also work better for other countries? Gerd
From: ar2988-os@outlook.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Sun, 1 Feb 2015 12:07:53 +0000 Subject: [mkgmap-dev] Public transport
I posted to the list last April http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2014q2/020800.html and there was no response. It seems that, although the post appeared on the mkgmap web site, most subscribers did not receive it because of the Yahoo! problem http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2014q4/022204.html
Therefore I am reposting the message, updated as necessary:
I have entered some public transport data into OSM. I have made every effort to enter the data in accordance with the new public transport schema. Some 'old' tags are also present because I started mapping the data before the new schema was approved. For testing purposes I used the extract from Geofabrik of the Languedoc-Roussillon region of France. I used r3433 with the default style and these options: --max-jobs --code-page=1252 --add-pois-to-areas --route --link-pois-to-ways --precomp-sea=sea-20150123211701.zip --generate-sea --index --bounds=bounds_20150129.zip --location-autofill:bounds,is_in,nearest --housenumbers. Looking at the results, I noticed a number of things.
(1) Names of railway stations
The names of many railway stations appear in the form SNCF: Agde. https://www.openstreetmap.org/way/72614628 This is the result of generic processing of names in the style file inc/name. There are about 3500 railway stations in France and more than half of them are tagged operator=SNCF. I would prefer to see the name in the form Agde SNCF, which was produced by earlier versions of the default style, before the file inc/name was introduced. This is more convenient for searching on a device.
(2) Names of bus stops
This is an example of the name of a bus stop as it appears in the generated map: Agglo Hérault Méditerranée: (1;2;3;4;5,4,4,3,3)(1;2;3;4;5,4,4,3,3)++ Gare SNCF https://www.openstreetmap.org/node/1424432523 The Garmin software and the device will only display the first part of the string. I used QLandkarte GT to see the complete string. (For legibility, I have used lower case in the strings, although they are in upper case in the generated map.)
Earlier versions of the default style produced the result Gare SNCF (1;2;3;4;5,4,4,3,3)+Agglo Hérault Méditerranée, which I prefer. "Gare SNCF" is the name of the bus stop. The earlier version would be essential, to allow you to see the name of the bus stop on a device. What do others think?
The solution which I use for my own maps, is as follows. Before line 16 of file inc/name ref=* & (operator!=* & brand!=*) { name '${ref} ${name}' | '${ref}' } insert this line ref=* & (operator!=* & brand!=*) & (highway=bus_stop | railway=tram_stop | railway=halt | railway=station) { name '${name} ${ref}' | '${ref}' } Before line 27 of file inc/name operator=* & brand!=* { insert these 6 lines operator=* & brand!=* & (highway=bus_stop | railway=tram_stop | railway=halt | railway=station) { name '${name} ${ref} ${operator}' | '${name} ${operator}' | '${ref} ${operator}' | '${operator}' }
The text 1;2;3;4;5,4,4,3,3 can be changed to 1;2;3;4;5 by using the new not-contained filter as proposed in another thread.
The doubling-up of the route_ref and the shelter indicator (+, - or *) is a bug. I will address this in a separate thread.
I will leave a further question about public transport for another thread.
Adrian
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, My proposal is to change the POI labels for railway stations and halts, and bus and tram stops. The name would come first and the operator would come last. This is the reverse of the current situation. I think public_transport=platform should be added to the list of tags in my proposal, for the same reason as it was added to the four rules in the points style. i.e. bus stops tagged according to the new public transport schema would have this tag, and not the tag highway=bus_stop. Adrian
Hi Adrian, okay, if I hear no votes against it I'll commit your proposal next monday. Gerd
From: ar2988-os@outlook.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Wed, 4 Feb 2015 14:17:40 +0000 Subject: Re: [mkgmap-dev] Public transport
Hi Gerd,
My proposal is to change the POI labels for railway stations and halts, and bus and tram stops. The name would come first and the operator would come last. This is the reverse of the current situation.
I think public_transport=platform should be added to the list of tags in my proposal, for the same reason as it was added to the four rules in the points style. i.e. bus stops tagged according to the new public transport schema would have this tag, and not the tag highway=bus_stop.
Adrian
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (2)
-
A drian -
Gerd Petermann