question reg. exits

Hi all, I just noticed that mkgmap treats POI with 0x2000 <= type < 0x2800 special. It looks for the tags exit:to=* and exit:facility=* to add extra information to the POI. This info is shown when you click on an exit in Basecamp, it shows the fields Name, Description, and Overnight Parking. The source was added with r984 in 2009 and it seems nobody noticed that these tags don't exist in OSM anymore (or maybe they were typos)? Or maybe that were meant to be set in the style? Gerd

Hi, On Tue, May 19, Gerd Petermann wrote:
Hi all,
I just noticed that mkgmap treats POI with 0x2000 <= type < 0x2800 special. It looks for the tags exit:to=* and exit:facility=* to add extra information to the POI. This info is shown when you click on an exit in Basecamp, it shows the fields Name, Description, and Overnight Parking.
The source was added with r984 in 2009 and it seems nobody noticed that these tags don't exist in OSM anymore (or maybe they were typos)?
Or maybe that were meant to be set in the style?
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q1/001287.html exit:facility needs to be set by the style, exit:to looks like a proposed OSM tag never introduced. But I admit that I don't really understand the examples in that mail... Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)

That's very interesting. I didn't know about the exit:to tag and apparently nobody else does either because taginfo shows zero occurrences of it. Taginfo also shows 381 uses of exit_to:left and 334 uses of exit_to:right so perhaps that's something to look at also. On Tue, May 19, 2015 at 1:43 AM, Thorsten Kukuk <kukuk@suse.de> wrote:
Hi,
On Tue, May 19, Gerd Petermann wrote:
Hi all,
I just noticed that mkgmap treats POI with 0x2000 <= type < 0x2800 special. It looks for the tags exit:to=* and exit:facility=* to add extra information to the POI. This info is shown when you click on an exit in Basecamp, it shows the fields Name, Description, and Overnight Parking.
The source was added with r984 in 2009 and it seems nobody noticed that these tags don't exist in OSM anymore (or maybe they were typos)?
Or maybe that were meant to be set in the style?
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q1/001287.html
exit:facility needs to be set by the style, exit:to looks like a proposed OSM tag never introduced. But I admit that I don't really understand the examples in that mail...
Thorsten
-- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com

Hi Thorsten, I followed the discussions and it seems that this feature was somehow forgotten, not sure why. I played a bit with the style rules and found that this rule highway=motorway_junction & exit_to=* { set exit:to='${exit_to}'; set exit:facility='3,N,7,blabla'} produces some extra data in the properties of each exit POI. The meaning of the exit:facility stuff is explained in the cgpsmapper manual http://cgpsmapper.com/download/cGPSmapper-UsrMan-v02.5.pdf on page 105 + 106. I was not able to make these exits searchable in MapSource or Basecamp. I assume that we have to set a special bit in one of the headers to make that work. Gerd
Date: Tue, 19 May 2015 10:43:13 +0200 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] question reg. exits
Hi,
On Tue, May 19, Gerd Petermann wrote:
Hi all,
I just noticed that mkgmap treats POI with 0x2000 <= type < 0x2800 special. It looks for the tags exit:to=* and exit:facility=* to add extra information to the POI. This info is shown when you click on an exit in Basecamp, it shows the fields Name, Description, and Overnight Parking.
The source was added with r984 in 2009 and it seems nobody noticed that these tags don't exist in OSM anymore (or maybe they were typos)?
Or maybe that were meant to be set in the style?
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q1/001287.html
exit:facility needs to be set by the style, exit:to looks like a proposed OSM tag never introduced. But I admit that I don't really understand the examples in that mail...
Thorsten
-- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi Gerd, On Wed, May 20, Gerd Petermann wrote:
I played a bit with the style rules and found that this rule highway=motorway_junction & exit_to=* { set exit:to='${exit_to}'; set exit:facility='3,N,7,blabla'}
produces some extra data in the properties of each exit POI.
I played with it yesterday, too, but was not succesful. At least MapSource didn't show this entries. But to be usefull I think we would need a lot of help from mkgmap. For exit:to and exit:facilities. For exit:to we would need the direction (N,S,O,W,...) and for exit:facilities we need to look, what other interesting POI are there.
I was not able to make these exits searchable in MapSource or Basecamp.
Where/how do you search for them? I have: highway=motorway_junction { name '${ref} ${name}' | '${ref}' | '${name}' } highway=motorway_junction [0x2000 level 2] highway=services [0x210f level 2 default_name 'Services'] In my rules and can search for them in MapSource. Only exit:to (my problem here is, if you look how motorway_junction is tagged, that I don't know how to get access to the exit_to/destination tags in the style file. Thorsten
I assume that we have to set a special bit in one of the headers to make that work.
Gerd
Date: Tue, 19 May 2015 10:43:13 +0200 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] question reg. exits
Hi,
On Tue, May 19, Gerd Petermann wrote:
Hi all,
I just noticed that mkgmap treats POI with 0x2000 <= type < 0x2800 special. It looks for the tags exit:to=* and exit:facility=* to add extra information to the POI. This info is shown when you click on an exit in Basecamp, it shows the fields Name, Description, and Overnight Parking.
The source was added with r984 in 2009 and it seems nobody noticed that these tags don't exist in OSM anymore (or maybe they were typos)?
Or maybe that were meant to be set in the style?
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q1/001287.html
exit:facility needs to be set by the style, exit:to looks like a proposed OSM tag never introduced. But I admit that I don't really understand the examples in that mail...
Thorsten
-- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)

On Wed, May 20, Thorsten Kukuk wrote:
Only exit:to (my problem here is, if you look how motorway_junction is tagged, that I don't know how to get access to the exit_to/destination tags in the style file.
More concret with an example: https://www.openstreetmap.org/node/268575608 This node does not have any information about the destination. So we would need the corresponding tags from the way: https://www.openstreetmap.org/way/24710254 This tags could be: destination/exit_to (both are equal, exit_to is used in the US) destination:ref destination:lanes Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)

Hi Thorsten,>
Where/how do you search for them?
I have: highway=motorway_junction { name '${ref} ${name}' | '${ref}' | '${name}' } highway=motorway_junction [0x2000 level 2] highway=services [0x210f level 2 default_name 'Services']
In my rules and can search for them in MapSource.
How ? What category / sub category is it? Gerd

Hi Gerd, On Wed, May 20, Gerd Petermann wrote:
How ? What category / sub category is it?
Ah, you are looking at the menu only. It seems there is no menu entry for it. Since the menu entries are hardcoded in the GPS devices and MapSource, you cannot change that. I don't think there exists some magic flags in the map which changes the menu. I used "search for POI in the near" and "search for all POI". Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)

Hi Thorsten, okay, got the same results. The interesting point here is that the code fills lists in the LBL file, but I don't extra code that would write them to the global index as we do with cities. Anyway, too much work for me, I'll concentrate on the branch for now. Gerd Thorsten Kukuk wrote
Hi Gerd,
On Wed, May 20, Gerd Petermann wrote:
How ? What category / sub category is it?
Ah, you are looking at the menu only. It seems there is no menu entry for it. Since the menu entries are hardcoded in the GPS devices and MapSource, you cannot change that. I don't think there exists some magic flags in the map which changes the menu.
I used "search for POI in the near" and "search for all POI".
Thorsten
-- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/question-reg-exits-tp5845107p5845255.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (4)
-
Dave Swarthout
-
Gerd Petermann
-
GerdP
-
Thorsten Kukuk