Re: [mkgmap-dev] side effects add-pois-to-lines
I use the add-poi-to-lines option only in a few cases (yet), and I don't use it
on every node either, but only in the middle of a road segment
(mkgmap:line2poitype=mid).
One example is on lines tagged with route=ferry opening_hours=*
http://www.openstreetmap.org/browse/way/40326852
route=ferry opening_hours=* mkgmap:line2poitype=mid {name '${name}
(${opening_hours})' | 'operating ${opening_hours}' } [0x6406 resolution 24]
This is a screenshot of my map:
http://img836.imageshack.us/img836/5582/ferryroute.jpg
Before add-poi-to-lines was introduced I used an extra line to render
opening_hours, but the disadvantage is that you often cannot see this info on
the GPS (it displays the streetname only, or in this case where there is no
streetname, it shows the bike route relation name). Other cases that you can
use this are for example incline, smoothness, tracktype, access tags etc.
Greg wrote:
Can you explain when you want to have a POI for every node in a way? It
seems the area-POI code makes one POI for the closed way, and this is
different. (Not trying to be difficult; I really don't get it.)
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] side effects add-pois-to-lines
Minko ligfiet...@online.nl writes:
Greg wrote:
Can you explain when you want to have a POI for every node in a way? It
seems the area-POI code makes one POI for the closed way, and this is
different. (Not trying to be difficult; I really don't get it.)
I use the add-poi-to-lines option only in a few cases (yet), and I
don't use it on every node either, but only in the middle of a road
segment (mkgmap:line2poitype=mid).
One example is on lines tagged with route=ferry opening_hours=*
http://www.openstreetmap.org/browse/way/40326852
route=ferry opening_hours=* mkgmap:line2poitype=mid {name '${name}
(${opening_hours})' | 'operating ${opening_hours}' } [0x6406
resolution 24]
This is a screenshot of my map:
http://img836.imageshack.us/img836/5582/ferryroute.jpg
Before add-poi-to-lines was introduced I used an extra line to render
opening_hours, but the disadvantage is that you often cannot see this
info on the GPS (it displays the streetname only, or in this case
where there is no streetname, it shows the bike route relation
name). Other cases that you can use this are for example incline,
smoothness, tracktype, access tags etc.
Thanks. I understand why you want to create one POI from a linear
feature. I still don't understand why it would make sense to make a POI
per node. What I'm getting at is that perhaps the line2poi code should
somehow default to making only one synthetic point POI. I have the
impression it didn't, and you were posting code to work around that.
pgpE64aiwvJil.pgp
Description: PGP signature
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] side effects add-pois-to-lines
Greg Troxel schrieb am 27.11.2011 17:12:
I still don't understand why it would make sense to make a POI
per node. What I'm getting at is that perhaps the line2poi code should
somehow default to making only one synthetic point POI.
Below is an example from my points-style, where I generate icons for incline
values set to a line, similar to the highway=incline POIs. Perhaps it would be
enough, to generate a single icon for each way marked with incline=*, but by
generating the icons for all nodes of the way, it is better visible, where the
inlcine starts and where it ends.
Gruss
Torsten
highway=incline
[0x4009 resolution 24 continue]
highway=incline_steep
[0x400a resolution 24 continue]
highway=* mkgmap:line2poitype=* mkmap_incline_type!=done incline ~
'^-?[0-9].*' {set mkmap_incline_type=numeric}
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?[2-9][0-9].*' incline ~ '.*%' {set name=20%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?19.*' incline ~ '.*%' {set name=19%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?18.*' incline ~ '.*%' {set name=18%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?17.*' incline ~ '.*%' {set name=17%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?16.*' incline ~ '.*%' {set name=16%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?15.*' incline ~ '.*%' {set name=15%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?14.*' incline ~ '.*%' {set name=14%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?13.*' incline ~ '.*%' {set name=13%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?12.*' incline ~ '.*%' {set name=12%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?11.*' incline ~ '.*%' {set name=11%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?10.*' incline ~ '.*%' {set name=10%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?9.*' incline ~ '.*%' {set name=9%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?8.*' incline ~ '.*%' {set name=8%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?7.*' incline ~ '.*%' {set name=7%; set ref=; set
mkmap_incline_type=done} [0x4009 resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?6.*' incline ~ '.*%' {set name=6%; set ref=; set
mkmap_incline_type=done} [0x4009 resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?5.*' incline ~ '.*%' {set name=5%; set ref=; set
mkmap_incline_type=done} [0x4009 resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?4.*' incline ~ '.*%' {set name=4%; set ref=; set
mkmap_incline_type=done} [0x4009 resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?3.*' incline ~ '.*%' {set name=3%; set ref=; set
mkmap_incline_type=done} [0x4009 resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?[2-9][0-9].*' incline ~ '.*°' {set name=20%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?19.*' incline ~ '.*°' {set name=20%; set ref=; set
mkmap_incline_type=done} [0x400a resolution 24 continue with_actions]
highway=* mkgmap:line2poitype=* mkmap_incline_type=numeric incline ~
'^-?18.*' incline ~ '.*°' {set name=20%; set ref=; set
mkmap_incline_type=done}
Re: [mkgmap-dev] side effects add-pois-to-lines
Moin,
Felix Hartmann schrieb am 17.11.2011 19:35:
There are only very very few cases where I
can see this option having any sense for me, so I would have to use
quite a lot of
mkgmap:line2poi!=true
statements.
Actually you do not need so many statements like this, since you can combine
them and delete the main-tag via an action rule. So e.g. if you know, that you
do not want any natural POIs based on lines, you could add a rule like
natural=* mkgmap:line2poi=true {set natural=}
Surely it would be more straight forward, if could could positively mark the
lines (or areas) in the style for the POI generation, but in the end you can
achieve the same results with both. So I am quite satisfied with the actual
implementation.
Gruss
Torsten
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] side effects add-pois-to-lines
Greg, leisure=track sport=cycling is certainly not a bug in OSM, but I dont want a sport icon on every node of this road. What I like is displaying a few relevant poi-to-line icons like bad surfaced roads, ferry schedules etc. on my map. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] side effects add-pois-to-lines
Am 26.11.2011 15:51, schrieb Greg Troxel: Example of unwanted pois on a line element: leisure=track sport=cycling http://www.openstreetmap.org/browse/way/41176449 BTW, there is a highway=service, too. Think that's not right. -- PGP Schlüssel: 311D1055 http://keyserver.pgp.com ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] side effects add-pois-to-lines
Can you explain when you want to have a POI for every node in a way? It seems the area-POI code makes one POI for the closed way, and this is different. (Not trying to be difficult; I really don't get it.) pgpXp0TYKSrBh.pgp Description: PGP signature ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] side effects add-pois-to-lines
I would support that change. There are only very very few cases where I
can see this option having any sense for me, so I would have to use
quite a lot of
mkgmap:line2poi!=true
statements. Also I think in general I would only like these additional
POI for the POI search on my Garmin, maybe never actually visible. Hence
mkgmap:line2poi=true requirement would be better.
On 14.11.2011 17:12, Minko wrote:
If this option is enabled, there are unwanted side effects.
For instance if someone accidently tagged a highway with barrier=gate, every
node on this highway gets a gate symbol.
If I want to change this behaviour I have to put on almost every poi line the
statement mkgmap:line2poi!=true
Is it possible to turn this around? That if I DO want to see this poi, I put
mkgmap:line2poi=true in the rule?
Something like this:
route=ferry opening_hours=* mkgmap:line2poi=true
mkgmap:line2poitype=mid {name '${name} (${opening_hours})' | 'operating
${opening_hours}' } [0x6406 resolution 24]
___
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
Re: [mkgmap-dev] side effects add-pois-to-lines
At the moment I have no good idea how to achieve that.
I can tag all POIs not created by the line2poi algorithm with
mkgmap:line2poi=false but that probably doesn't help you.
Any ideas?
WanMil
I would support that change. There are only very very few cases where I
can see this option having any sense for me, so I would have to use
quite a lot of
mkgmap:line2poi!=true
statements. Also I think in general I would only like these additional
POI for the POI search on my Garmin, maybe never actually visible. Hence
mkgmap:line2poi=true requirement would be better.
On 14.11.2011 17:12, Minko wrote:
If this option is enabled, there are unwanted side effects.
For instance if someone accidently tagged a highway with barrier=gate, every
node on this highway gets a gate symbol.
If I want to change this behaviour I have to put on almost every poi line
the statement mkgmap:line2poi!=true
Is it possible to turn this around? That if I DO want to see this poi, I
put mkgmap:line2poi=true in the rule?
Something like this:
route=ferry opening_hours=* mkgmap:line2poi=true
mkgmap:line2poitype=mid {name '${name} (${opening_hours})' | 'operating
${opening_hours}' } [0x6406 resolution 24]
___
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
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] side effects add-pois-to-lines
well as it seems to be performance related, would it be then possible to
have a new file (e.g. linepois) where such definitions go into?
Otherwise I think it's still okay, one just needs to take care with all
POI keys that are waterway; highway;barrier and so on and tag them
with mkgmap:line2poi!=true.
On 17.11.2011 20:21, WanMil wrote:
At the moment I have no good idea how to achieve that.
I can tag all POIs not created by the line2poi algorithm with
mkgmap:line2poi=false but that probably doesn't help you.
Any ideas?
WanMil
I would support that change. There are only very very few cases where I
can see this option having any sense for me, so I would have to use
quite a lot of
mkgmap:line2poi!=true
statements. Also I think in general I would only like these additional
POI for the POI search on my Garmin, maybe never actually visible. Hence
mkgmap:line2poi=true requirement would be better.
On 14.11.2011 17:12, Minko wrote:
If this option is enabled, there are unwanted side effects.
For instance if someone accidently tagged a highway with
barrier=gate, every node on this highway gets a gate symbol.
If I want to change this behaviour I have to put on almost every poi
line the statement mkgmap:line2poi!=true
Is it possible to turn this around? That if I DO want to see this
poi, I put mkgmap:line2poi=true in the rule?
Something like this:
route=ferry opening_hours=* mkgmap:line2poi=true
mkgmap:line2poitype=mid {name '${name} (${opening_hours})' |
'operating ${opening_hours}' } [0x6406 resolution 24]
___
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
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] side effects add-pois-to-lines
If this option is enabled, there are unwanted side effects.
For instance if someone accidently tagged a highway with barrier=gate, every
node on this highway gets a gate symbol.
If I want to change this behaviour I have to put on almost every poi line the
statement mkgmap:line2poi!=true
Is it possible to turn this around? That if I DO want to see this poi, I put
mkgmap:line2poi=true in the rule?
Something like this:
route=ferry opening_hours=* mkgmap:line2poi=true mkgmap:line2poitype=mid
{name '${name} (${opening_hours})' | 'operating ${opening_hours}' } [0x6406
resolution 24]
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
