Test if POI is part of a line
I read through the old poi-tagged-v3.patch is_in()function for point on line discussion - but what I want is actually different and should be much easier? Could there be a solution to check if a point is a single point vs if it is part of a open/closed line? Why? I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line. Especially for gates most are just useless clutter because they are tagged on private houses and similar. If there was a way to delete afterwards/or create only in first place those points that are part of a line would be good, best would be if they are only shown if part of a routable line (so after the lines stye-file is processed). -- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
Hi Felix, my first thought was that --add-poi-to-lines is all that you need, but maybe I've missed something? One problem with your suggested solution is that the current implementation in mkgmap processes (tagged) nodes before lines. I can't remember exactly why but a change probably causes side effects. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com> Gesendet: Freitag, 7. Oktober 2022 23:12 An: Development list for mkgmap Betreff: [mkgmap-dev] Test if POI is part of a line I read through the old poi-tagged-v3.patch is_in()function for point on line discussion - but what I want is actually different and should be much easier? Could there be a solution to check if a point is a single point vs if it is part of a open/closed line? Why? I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line. Especially for gates most are just useless clutter because they are tagged on private houses and similar. If there was a way to delete afterwards/or create only in first place those points that are part of a line would be good, best would be if they are only shown if part of a routable line (so after the lines stye-file is processed). -- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
Hi Gerd, No --*add-poi-to-lines* creates points from a line that has certain tags. What I try to achieve is actually to remove points that are NOT part of a line / or part of a line that is not rendered in the map. There is no reason to show a gate if you don't have a line/road.So essentially for me there is no sense to show a gate for me if it is not part of a routable line. However points created by add-pois-to-lines are also not what I want - because it would show the gate in an incorrect position. So the clutch of using *--link-pois-to-ways * to get the access tags onto the line - then never show an actual barrier=gate/highway=gate but only show one created by the *--add-poi-to-line* command? The logical solution is to really only show a gate where it is tagged, but only if the map is creating a routable line for it and remove all other barrier=* / highway=gate / entrance=yes POI. If this is too much work to implement - then drop it. But as far as I understand right now there is no good solution by mkgmap for this. The same would be for traffic lights - if you remove a road because your map does not show private roads - but a private road has a traffic light - this traffic light should not be in the map either. And yes I know the dilemma - we need points to be looked at pre lines for --link-pois-to-ways to work, but for some other things we would need to look at them later again. So this would need to be some kind of seond_finalize rules in the points file that is executed after the lines file - and removes points from the map again. It's not a big problem - but right now this really makes it inconvenient to put gates into your map - as 75% of gates are just cluttering up the map without providing any information to the user (except if you want to create a cataster type of map showing everything). Leaving gates out completely on the other hand makes it very hard to show for example with parks where people can enter and where not. As very often there are service entries to parks not open to public - so these are the main ones that we want to show in a map. On Mon, 10 Oct 2022 at 08:35, Gerd Petermann < gpetermann_muenchen@hotmail.com> wrote:
Hi Felix,
my first thought was that --add-poi-to-lines is all that you need, but maybe I've missed something?
One problem with your suggested solution is that the current implementation in mkgmap processes (tagged) nodes before lines. I can't remember exactly why but a change probably causes side effects.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com> Gesendet: Freitag, 7. Oktober 2022 23:12 An: Development list for mkgmap Betreff: [mkgmap-dev] Test if POI is part of a line
I read through the old poi-tagged-v3.patch
is_in()function for point on line discussion - but what I want is actually different and should be much easier?
Could there be a solution to check if a point is a single point vs if it is part of a open/closed line? Why?
I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line. Especially for gates most are just useless clutter because they are tagged on private houses and similar.
If there was a way to delete afterwards/or create only in first place those points that are part of a line would be good, best would be if they are only shown if part of a routable line (so after the lines stye-file is processed).
-- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
Also I don't like using --link-pois-to-ways to put an access=private onto a road - and then remove this road. Because in the case of a park - the footways/pathes on both sides of the gate do exist. So an access=private does not actually apply to the road. So it's correct to show the road, and show the gate that is blocking the road. I think this is better that deleting that road because of the gate. On Mon, 10 Oct 2022 at 11:47, Felix Hartmann <extremecarver@gmail.com> wrote:
Hi Gerd,
No --*add-poi-to-lines* creates points from a line that has certain tags. What I try to achieve is actually to remove points that are NOT part of a line / or part of a line that is not rendered in the map. There is no reason to show a gate if you don't have a line/road.So essentially for me there is no sense to show a gate for me if it is not part of a routable line. However points created by add-pois-to-lines are also not what I want - because it would show the gate in an incorrect position.
So the clutch of using *--link-pois-to-ways * to get the access tags onto the line - then never show an actual barrier=gate/highway=gate but only show one created by the *--add-poi-to-line* command? The logical solution is to really only show a gate where it is tagged, but only if the map is creating a routable line for it and remove all other barrier=* / highway=gate / entrance=yes POI.
If this is too much work to implement - then drop it. But as far as I understand right now there is no good solution by mkgmap for this. The same would be for traffic lights - if you remove a road because your map does not show private roads - but a private road has a traffic light - this traffic light should not be in the map either. And yes I know the dilemma - we need points to be looked at pre lines for --link-pois-to-ways to work, but for some other things we would need to look at them later again. So this would need to be some kind of seond_finalize rules in the points file that is executed after the lines file - and removes points from the map again. It's not a big problem - but right now this really makes it inconvenient to put gates into your map - as 75% of gates are just cluttering up the map without providing any information to the user (except if you want to create a cataster type of map showing everything). Leaving gates out completely on the other hand makes it very hard to show for example with parks where people can enter and where not. As very often there are service entries to parks not open to public - so these are the main ones that we want to show in a map.
On Mon, 10 Oct 2022 at 08:35, Gerd Petermann < gpetermann_muenchen@hotmail.com> wrote:
Hi Felix,
my first thought was that --add-poi-to-lines is all that you need, but maybe I've missed something?
One problem with your suggested solution is that the current implementation in mkgmap processes (tagged) nodes before lines. I can't remember exactly why but a change probably causes side effects.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com> Gesendet: Freitag, 7. Oktober 2022 23:12 An: Development list for mkgmap Betreff: [mkgmap-dev] Test if POI is part of a line
I read through the old poi-tagged-v3.patch
is_in()function for point on line discussion - but what I want is actually different and should be much easier?
Could there be a solution to check if a point is a single point vs if it is part of a open/closed line? Why?
I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line. Especially for gates most are just useless clutter because they are tagged on private houses and similar.
If there was a way to delete afterwards/or create only in first place those points that are part of a line would be good, best would be if they are only shown if part of a routable line (so after the lines stye-file is processed).
-- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
-- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
Hi Felix, the current implementation of the link-pois-to-ways doesn't transfer the access tag(s) to the way. It just creates a route restriction which tells Garmin that it must not route the given vehicles through the barrier. Older implementations created a short stub close to the barrier node. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com> Gesendet: Montag, 10. Oktober 2022 12:13 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Test if POI is part of a line Also I don't like using --link-pois-to-ways to put an access=private onto a road - and then remove this road. Because in the case of a park - the footways/pathes on both sides of the gate do exist. So an access=private does not actually apply to the road. So it's correct to show the road, and show the gate that is blocking the road. I think this is better that deleting that road because of the gate. On Mon, 10 Oct 2022 at 11:47, Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com>> wrote: Hi Gerd, No --add-poi-to-lines creates points from a line that has certain tags. What I try to achieve is actually to remove points that are NOT part of a line / or part of a line that is not rendered in the map. There is no reason to show a gate if you don't have a line/road.So essentially for me there is no sense to show a gate for me if it is not part of a routable line. However points created by add-pois-to-lines are also not what I want - because it would show the gate in an incorrect position. So the clutch of using --link-pois-to-ways to get the access tags onto the line - then never show an actual barrier=gate/highway=gate but only show one created by the --add-poi-to-line command? The logical solution is to really only show a gate where it is tagged, but only if the map is creating a routable line for it and remove all other barrier=* / highway=gate / entrance=yes POI. If this is too much work to implement - then drop it. But as far as I understand right now there is no good solution by mkgmap for this. The same would be for traffic lights - if you remove a road because your map does not show private roads - but a private road has a traffic light - this traffic light should not be in the map either. And yes I know the dilemma - we need points to be looked at pre lines for --link-pois-to-ways to work, but for some other things we would need to look at them later again. So this would need to be some kind of seond_finalize rules in the points file that is executed after the lines file - and removes points from the map again. It's not a big problem - but right now this really makes it inconvenient to put gates into your map - as 75% of gates are just cluttering up the map without providing any information to the user (except if you want to create a cataster type of map showing everything). Leaving gates out completely on the other hand makes it very hard to show for example with parks where people can enter and where not. As very often there are service entries to parks not open to public - so these are the main ones that we want to show in a map. On Mon, 10 Oct 2022 at 08:35, Gerd Petermann <gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>> wrote: Hi Felix, my first thought was that --add-poi-to-lines is all that you need, but maybe I've missed something? One problem with your suggested solution is that the current implementation in mkgmap processes (tagged) nodes before lines. I can't remember exactly why but a change probably causes side effects. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag von Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com>> Gesendet: Freitag, 7. Oktober 2022 23:12 An: Development list for mkgmap Betreff: [mkgmap-dev] Test if POI is part of a line I read through the old poi-tagged-v3.patch is_in()function for point on line discussion - but what I want is actually different and should be much easier? Could there be a solution to check if a point is a single point vs if it is part of a open/closed line? Why? I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line. Especially for gates most are just useless clutter because they are tagged on private houses and similar. If there was a way to delete afterwards/or create only in first place those points that are part of a line would be good, best would be if they are only shown if part of a routable line (so after the lines stye-file is processed). -- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org -- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
Hi Gerd, I also have a - similar? - issue implementing poi2line. I cannot Add or Delete poi2line nodes. Perhaps (as you said): "One problem with your suggested solution is that the current implementation in mkgmap processes (tagged) nodes before lines". In 'lines' this is working OK: access:conditional = 'no @ sunset-sunrise' { delete access:conditional } access:conditional = 'no @ sunset - sunrise' { delete access:conditional } access:conditional = 'no @ (sunset-sunrise)' { delete access:conditional } access:conditional = 'no @ (sunset - sunrise)' { delete access:conditional } opening_hours = '24/7' { delete opening_hours } opening_hours = '(24/7)' { delete opening_hours } and 50 more lines of script because these tags are useless and/or polluting the map and/or default and/or needless. IMO! But once I add 'omsid()=...' to mkgmap it doesn't work anymore to remove line2poi. highway=unclassified & osmid()=912437951 {delete smoothness; delete opening_hours} In next example I delete all tags (don't want to render this highway), highway is deleted (not rendered) but line2poi is still rendered. highway=cycleway & osmid()=1011546906 {deletealltags} I also cannot ADD a line2poi tag: highway=unclassified & osmid()=176775241 {set opening_hours="may be closed during sport events"} I want to add private tags (line2poi), IMO tags, subjective tags, 'necessary' tags (IMO) that are not allowed on OSM (f.i.: bicycle=dismount, scenic=yes, which are only 'allowed' if a (traffic)sign is 'on the ground' to confirm dismount/scenic). AnkEric -----Original Message----- From: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> On Behalf Of Gerd Petermann Sent: maandag 10 oktober 2022 12:49 To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk> Subject: Re: [mkgmap-dev] Test if POI is part of a line Hi Felix, the current implementation of the link-pois-to-ways doesn't transfer the access tag(s) to the way. It just creates a route restriction which tells Garmin that it must not route the given vehicles through the barrier. Older implementations created a short stub close to the barrier node. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com> Gesendet: Montag, 10. Oktober 2022 12:13 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Test if POI is part of a line Also I don't like using --link-pois-to-ways to put an access=private onto a road - and then remove this road. Because in the case of a park - the footways/pathes on both sides of the gate do exist. So an access=private does not actually apply to the road. So it's correct to show the road, and show the gate that is blocking the road. I think this is better that deleting that road because of the gate. On Mon, 10 Oct 2022 at 11:47, Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com>> wrote: Hi Gerd, No --add-poi-to-lines creates points from a line that has certain tags. What I try to achieve is actually to remove points that are NOT part of a line / or part of a line that is not rendered in the map. There is no reason to show a gate if you don't have a line/road.So essentially for me there is no sense to show a gate for me if it is not part of a routable line. However points created by add-pois-to-lines are also not what I want - because it would show the gate in an incorrect position. So the clutch of using --link-pois-to-ways to get the access tags onto the line - then never show an actual barrier=gate/highway=gate but only show one created by the --add-poi-to-line command? The logical solution is to really only show a gate where it is tagged, but only if the map is creating a routable line for it and remove all other barrier=* / highway=gate / entrance=yes POI. If this is too much work to implement - then drop it. But as far as I understand right now there is no good solution by mkgmap for this. The same would be for traffic lights - if you remove a road because your map does not show private roads - but a private road has a traffic light - this traffic light should not be in the map either. And yes I know the dilemma - we need points to be looked at pre lines for --link-pois-to-ways to work, but for some other things we would need to look at them later again. So this would need to be some kind of seond_finalize rules in the points file that is executed after the lines file - and removes points from the map again. It's not a big problem - but right now this really makes it inconvenient to put gates into your map - as 75% of gates are just cluttering up the map without providing any information to the user (except if you want to create a cataster type of map showing everything). Leaving gates out completely on the other hand makes it very ha rd to show for example with parks where people can enter and where not. As very often there are service entries to parks not open to public - so these are the main ones that we want to show in a map. On Mon, 10 Oct 2022 at 08:35, Gerd Petermann <gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>> wrote: Hi Felix, my first thought was that --add-poi-to-lines is all that you need, but maybe I've missed something? One problem with your suggested solution is that the current implementation in mkgmap processes (tagged) nodes before lines. I can't remember exactly why but a change probably causes side effects. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag von Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com>> Gesendet: Freitag, 7. Oktober 2022 23:12 An: Development list for mkgmap Betreff: [mkgmap-dev] Test if POI is part of a line I read through the old poi-tagged-v3.patch is_in()function for point on line discussion - but what I want is actually different and should be much easier? Could there be a solution to check if a point is a single point vs if it is part of a open/closed line? Why? I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line. Especially for gates most are just useless clutter because they are tagged on private houses and similar. If there was a way to delete afterwards/or create only in first place those points that are part of a line would be good, best would be if they are only shown if part of a routable line (so after the lines stye-file is processed). -- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org -- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Eric, the option --add-pois-to-lines is operates on the nodes of the ways before any style rules were executed. So, whatever you do in the lines rules has no effect on the generated points. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von ankeric.osm@gmail.com <ankeric.osm@gmail.com> Gesendet: Montag, 10. Oktober 2022 12:59 An: 'Development list for mkgmap' Betreff: Re: [mkgmap-dev] Test if POI is part of a line Hi Gerd, I also have a - similar? - issue implementing poi2line. I cannot Add or Delete poi2line nodes. Perhaps (as you said): "One problem with your suggested solution is that the current implementation in mkgmap processes (tagged) nodes before lines". In 'lines' this is working OK: access:conditional = 'no @ sunset-sunrise' { delete access:conditional } access:conditional = 'no @ sunset - sunrise' { delete access:conditional } access:conditional = 'no @ (sunset-sunrise)' { delete access:conditional } access:conditional = 'no @ (sunset - sunrise)' { delete access:conditional } opening_hours = '24/7' { delete opening_hours } opening_hours = '(24/7)' { delete opening_hours } and 50 more lines of script because these tags are useless and/or polluting the map and/or default and/or needless. IMO! But once I add 'omsid()=...' to mkgmap it doesn't work anymore to remove line2poi. highway=unclassified & osmid()=912437951 {delete smoothness; delete opening_hours} In next example I delete all tags (don't want to render this highway), highway is deleted (not rendered) but line2poi is still rendered. highway=cycleway & osmid()=1011546906 {deletealltags} I also cannot ADD a line2poi tag: highway=unclassified & osmid()=176775241 {set opening_hours="may be closed during sport events"} I want to add private tags (line2poi), IMO tags, subjective tags, 'necessary' tags (IMO) that are not allowed on OSM (f.i.: bicycle=dismount, scenic=yes, which are only 'allowed' if a (traffic)sign is 'on the ground' to confirm dismount/scenic). AnkEric -----Original Message----- From: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> On Behalf Of Gerd Petermann Sent: maandag 10 oktober 2022 12:49 To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk> Subject: Re: [mkgmap-dev] Test if POI is part of a line Hi Felix, the current implementation of the link-pois-to-ways doesn't transfer the access tag(s) to the way. It just creates a route restriction which tells Garmin that it must not route the given vehicles through the barrier. Older implementations created a short stub close to the barrier node. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com> Gesendet: Montag, 10. Oktober 2022 12:13 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Test if POI is part of a line Also I don't like using --link-pois-to-ways to put an access=private onto a road - and then remove this road. Because in the case of a park - the footways/pathes on both sides of the gate do exist. So an access=private does not actually apply to the road. So it's correct to show the road, and show the gate that is blocking the road. I think this is better that deleting that road because of the gate. On Mon, 10 Oct 2022 at 11:47, Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com>> wrote: Hi Gerd, No --add-poi-to-lines creates points from a line that has certain tags. What I try to achieve is actually to remove points that are NOT part of a line / or part of a line that is not rendered in the map. There is no reason to show a gate if you don't have a line/road.So essentially for me there is no sense to show a gate for me if it is not part of a routable line. However points created by add-pois-to-lines are also not what I want - because it would show the gate in an incorrect position. So the clutch of using --link-pois-to-ways to get the access tags onto the line - then never show an actual barrier=gate/highway=gate but only show one created by the --add-poi-to-line command? The logical solution is to really only show a gate where it is tagged, but only if the map is creating a routable line for it and remove all other barrier=* / highway=gate / entrance=yes POI. If this is too much work to implement - then drop it. But as far as I understand right now there is no good solution by mkgmap for this. The same would be for traffic lights - if you remove a road because your map does not show private roads - but a private road has a traffic light - this traffic light should not be in the map either. And yes I know the dilemma - we need points to be looked at pre lines for --link-pois-to-ways to work, but for some other things we would need to look at them later again. So this would need to be some kind of seond_finalize rules in the points file that is executed after the lines file - and removes points from the map again. It's not a big problem - but right now this really makes it inconvenient to put gates into your map - as 75% of gates are just cluttering up the map without providing any information to the user (except if you want to create a cataster type of map showing everything). Leaving gates out completely on the other hand makes it very ha rd to show for example with parks where people can enter and where not. As very often there are service entries to parks not open to public - so these are the main ones that we want to show in a map. On Mon, 10 Oct 2022 at 08:35, Gerd Petermann <gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>> wrote: Hi Felix, my first thought was that --add-poi-to-lines is all that you need, but maybe I've missed something? One problem with your suggested solution is that the current implementation in mkgmap processes (tagged) nodes before lines. I can't remember exactly why but a change probably causes side effects. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag von Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com>> Gesendet: Freitag, 7. Oktober 2022 23:12 An: Development list for mkgmap Betreff: [mkgmap-dev] Test if POI is part of a line I read through the old poi-tagged-v3.patch is_in()function for point on line discussion - but what I want is actually different and should be much easier? Could there be a solution to check if a point is a single point vs if it is part of a open/closed line? Why? I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line. Especially for gates most are just useless clutter because they are tagged on private houses and similar. If there was a way to delete afterwards/or create only in first place those points that are part of a line would be good, best would be if they are only shown if part of a routable line (so after the lines stye-file is processed). -- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org -- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Ah okay thanks for the clarification - well okay then those ways are not removed - except if they already have themselves an access=private on them. However I cannot check this from the points file - so I will put useless gate symbols into the map - as there is no way to check whether or not it is attached to a routable line. On Mon, 10 Oct 2022 at 12:48, Gerd Petermann < gpetermann_muenchen@hotmail.com> wrote:
Hi Felix,
the current implementation of the link-pois-to-ways doesn't transfer the access tag(s) to the way. It just creates a route restriction which tells Garmin that it must not route the given vehicles through the barrier. Older implementations created a short stub close to the barrier node.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com> Gesendet: Montag, 10. Oktober 2022 12:13 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Test if POI is part of a line
Also I don't like using --link-pois-to-ways to put an access=private onto a road - and then remove this road. Because in the case of a park - the footways/pathes on both sides of the gate do exist. So an access=private does not actually apply to the road. So it's correct to show the road, and show the gate that is blocking the road. I think this is better that deleting that road because of the gate.
On Mon, 10 Oct 2022 at 11:47, Felix Hartmann <extremecarver@gmail.com <mailto:extremecarver@gmail.com>> wrote: Hi Gerd,
No --add-poi-to-lines creates points from a line that has certain tags. What I try to achieve is actually to remove points that are NOT part of a line / or part of a line that is not rendered in the map. There is no reason to show a gate if you don't have a line/road.So essentially for me there is no sense to show a gate for me if it is not part of a routable line. However points created by add-pois-to-lines are also not what I want - because it would show the gate in an incorrect position.
So the clutch of using --link-pois-to-ways to get the access tags onto the line - then never show an actual barrier=gate/highway=gate but only show one created by the --add-poi-to-line command? The logical solution is to really only show a gate where it is tagged, but only if the map is creating a routable line for it and remove all other barrier=* / highway=gate / entrance=yes POI.
If this is too much work to implement - then drop it. But as far as I understand right now there is no good solution by mkgmap for this. The same would be for traffic lights - if you remove a road because your map does not show private roads - but a private road has a traffic light - this traffic light should not be in the map either. And yes I know the dilemma - we need points to be looked at pre lines for --link-pois-to-ways to work, but for some other things we would need to look at them later again. So this would need to be some kind of seond_finalize rules in the points file that is executed after the lines file - and removes points from the map again. It's not a big problem - but right now this really makes it inconvenient to put gates into your map - as 75% of gates are just cluttering up the map without providing any information to the user (except if you want to create a cataster type of map showing everything). Leaving gates out completely on the other hand makes it very ha rd to show for example with parks where people can enter and where not. As very often there are service entries to parks not open to public - so these are the main ones that we want to show in a map.
On Mon, 10 Oct 2022 at 08:35, Gerd Petermann < gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>> wrote: Hi Felix,
my first thought was that --add-poi-to-lines is all that you need, but maybe I've missed something?
One problem with your suggested solution is that the current implementation in mkgmap processes (tagged) nodes before lines. I can't remember exactly why but a change probably causes side effects.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto: mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag von Felix Hartmann < extremecarver@gmail.com<mailto:extremecarver@gmail.com>> Gesendet: Freitag, 7. Oktober 2022 23:12 An: Development list for mkgmap Betreff: [mkgmap-dev] Test if POI is part of a line
I read through the old poi-tagged-v3.patch
is_in()function for point on line discussion - but what I want is actually different and should be much easier?
Could there be a solution to check if a point is a single point vs if it is part of a open/closed line? Why?
I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line. Especially for gates most are just useless clutter because they are tagged on private houses and similar.
If there was a way to delete afterwards/or create only in first place those points that are part of a line would be good, best would be if they are only shown if part of a routable line (so after the lines stye-file is processed).
-- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
-- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
Hey, I'm new here (Hello!), so please be patient if I'm missing points ;-) @ Felix
/...so I will put useless [] symbols into the map - as there is no way to check whether or not it //*is*//attached to a routable line./
But couldn't you check whether the line the point is attached to later on /*would*/ become a routable line? Basically, because the points inherit all tags from the lines when using --add-poi-to-lines, by running through the same decision tree that (later on) is used in the lines file already in the points file? Optimally from some clever include file to avoid redundancy? @ Gerd
/mkgmap:line2poi=true & highway=* & mkgmap:from-node:barrier=gate [...]/
Why is "mkgmap:line2poi=true" required? Shouldn't only acting on /mkgmap:from-node:barrier=gate/ in conjunction with the lines tag suffice here? Cheers another Felix
On Mon, Oct 10, 2022 at 09:39:11PM +0200, Felix Herwegh wrote:
Hey,
I'm new here (Hello!), so please be patient if I'm missing points ;-)
@ Felix
/...so I will put useless [] symbols into the map - as there is no way to check whether or not it //*is*//attached to a routable line./
But couldn't you check whether the line the point is attached to later on /*would*/ become a routable line? Basically, because the points inherit all
I have mapped gates in a fence/wall which are not on routable lines. These are very important if you are to find your way out of an enclosure or field. I am thinking of just such a place on a rugged hillside where the location of the gate can not be seen until quite close. I want my OSM/garmin map to show me this sort of thing. ael
On Mon, 10 Oct 2022 at 22:05, ael <witwall3@disroot.org> wrote:
On Mon, Oct 10, 2022 at 09:39:11PM +0200, Felix Herwegh wrote:
I have mapped gates in a fence/wall which are not on routable lines. These are very important if you are to find your way out of an enclosure or field. I am thinking of just such a place on a rugged hillside where the location of the gate can not be seen until quite close.
Are you sure this is correct tagging? I think this would merit a highway=path - maybe with low visibility (key visibility)
I want my OSM/garmin map to show me this sort of thing.
I'm not proposing this for the default style - any style is different and everyone wants to filter different things. We cannot show even half of the data that is inside OSM without ending up with a useless map - so every map needs to filter according to it's use case. Most maps don't even show barrier=gate / highway=gate in first place.
ael
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
On Mon, Oct 10, 2022 at 10:51:07PM +0200, Felix Hartmann wrote:
On Mon, 10 Oct 2022 at 22:05, ael <witwall3@disroot.org> wrote:
On Mon, Oct 10, 2022 at 09:39:11PM +0200, Felix Herwegh wrote:
I have mapped gates in a fence/wall which are not on routable lines. These are very important if you are to find your way out of an enclosure or field. I am thinking of just such a place on a rugged hillside where the location of the gate can not be seen until quite close.
Are you sure this is correct tagging? I think this would merit a highway=path - maybe with low visibility (key visibility)
Yes. There was no path: just an open field - well an enclosed area of hillside with walls and fencing to retain livestock. I entered it expecting to be able to cross and exit somewhere on the far boundary, but found myself trapped inside. It took a little while to find my way back to the gate. So no sensible path at all. Unless one invented a tiny path just crossing the boundary. It seems entirely legitimate: very similar to "entrance" on a building. After that I also recorded the location of gates through walls and fences in the area, although I think in most of those cases there were footways that I also mapped. But not always. ael
Hi (another) Felix, yes, you can omit the clause mkgmap:line2poi=true. I've only added this check to make clearer that the rule only works with the --add-pois-to-lines option. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Herwegh <mlmmduk@herwegh.de> Gesendet: Montag, 10. Oktober 2022 21:39 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Test if POI is part of a line Hey, I'm new here (Hello!), so please be patient if I'm missing points ;-) @ Felix
...so I will put useless [] symbols into the map - as there is no way to check whether or not it is attached to a routable line.
But couldn't you check whether the line the point is attached to later on would become a routable line? Basically, because the points inherit all tags from the lines when using --add-poi-to-lines, by running through the same decision tree that (later on) is used in the lines file already in the points file? Optimally from some clever include file to avoid redundancy? @ Gerd
mkgmap:line2poi=true & highway=* & mkgmap:from-node:barrier=gate [...]
Why is "mkgmap:line2poi=true" required? Shouldn't only acting on mkgmap:from-node:barrier=gate in conjunction with the lines tag suffice here? Cheers another Felix
Hi Felix, please check the docu for special tag mkgmap:from-node:attname . I think this allows to filter a barrier node which on a highway. A rule in points like this should work with option --add-pois-to-line: mkgmap:line2poi=true & highway=* & mkgmap:from-node:barrier=gate [...] I didn't try it but this should only render the generated points from ways with highway=* and a tag barrier=gate on the node. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com> Gesendet: Montag, 10. Oktober 2022 11:47 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Test if POI is part of a line Hi Gerd, No --add-poi-to-lines creates points from a line that has certain tags. What I try to achieve is actually to remove points that are NOT part of a line / or part of a line that is not rendered in the map. There is no reason to show a gate if you don't have a line/road.So essentially for me there is no sense to show a gate for me if it is not part of a routable line. However points created by add-pois-to-lines are also not what I want - because it would show the gate in an incorrect position. So the clutch of using --link-pois-to-ways to get the access tags onto the line - then never show an actual barrier=gate/highway=gate but only show one created by the --add-poi-to-line command? The logical solution is to really only show a gate where it is tagged, but only if the map is creating a routable line for it and remove all other barrier=* / highway=gate / entrance=yes POI. If this is too much work to implement - then drop it. But as far as I understand right now there is no good solution by mkgmap for this. The same would be for traffic lights - if you remove a road because your map does not show private roads - but a private road has a traffic light - this traffic light should not be in the map either. And yes I know the dilemma - we need points to be looked at pre lines for --link-pois-to-ways to work, but for some other things we would need to look at them later again. So this would need to be some kind of seond_finalize rules in the points file that is executed after the lines file - and removes points from the map again. It's not a big problem - but right now this really makes it inconvenient to put gates into your map - as 75% of gates are just cluttering up the map without providing any information to the user (except if you want to create a cataster type of map showing everything). Leaving gates out completely on the other hand makes it very hard to show for example with parks where people can enter and where not. As very often there are service entries to parks not open to public - so these are the main ones that we want to show in a map. On Mon, 10 Oct 2022 at 08:35, Gerd Petermann <gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>> wrote: Hi Felix, my first thought was that --add-poi-to-lines is all that you need, but maybe I've missed something? One problem with your suggested solution is that the current implementation in mkgmap processes (tagged) nodes before lines. I can't remember exactly why but a change probably causes side effects. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag von Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com>> Gesendet: Freitag, 7. Oktober 2022 23:12 An: Development list for mkgmap Betreff: [mkgmap-dev] Test if POI is part of a line I read through the old poi-tagged-v3.patch is_in()function for point on line discussion - but what I want is actually different and should be much easier? Could there be a solution to check if a point is a single point vs if it is part of a open/closed line? Why? I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line. Especially for gates most are just useless clutter because they are tagged on private houses and similar. If there was a way to delete afterwards/or create only in first place those points that are part of a line would be good, best would be if they are only shown if part of a routable line (so after the lines stye-file is processed). -- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
*mkgmap:line2poi=true & highway=* & mkgmap:from-node:barrier=gate [...]* --- I will give this a try. Is this implemented in the main branch? I thought this tag was related to patch poi-tagged-v3.patch and never accepted. I had not fully understood how it worked however. Will try this out and see if it can work (then if it works, instead of higwhay=* insert the list of conditions that delete a road) On Mon, 10 Oct 2022 at 14:45, Gerd Petermann < gpetermann_muenchen@hotmail.com> wrote:
Hi Felix,
please check the docu for special tag mkgmap:from-node:attname . I think this allows to filter a barrier node which on a highway. A rule in points like this should work with option --add-pois-to-line:
mkgmap:line2poi=true & highway=* & mkgmap:from-node:barrier=gate [...]
I didn't try it but this should only render the generated points from ways with highway=* and a tag barrier=gate on the node.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com> Gesendet: Montag, 10. Oktober 2022 11:47 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Test if POI is part of a line
Hi Gerd,
No --add-poi-to-lines creates points from a line that has certain tags. What I try to achieve is actually to remove points that are NOT part of a line / or part of a line that is not rendered in the map. There is no reason to show a gate if you don't have a line/road.So essentially for me there is no sense to show a gate for me if it is not part of a routable line. However points created by add-pois-to-lines are also not what I want - because it would show the gate in an incorrect position.
So the clutch of using --link-pois-to-ways to get the access tags onto the line - then never show an actual barrier=gate/highway=gate but only show one created by the --add-poi-to-line command? The logical solution is to really only show a gate where it is tagged, but only if the map is creating a routable line for it and remove all other barrier=* / highway=gate / entrance=yes POI.
If this is too much work to implement - then drop it. But as far as I understand right now there is no good solution by mkgmap for this. The same would be for traffic lights - if you remove a road because your map does not show private roads - but a private road has a traffic light - this traffic light should not be in the map either. And yes I know the dilemma - we need points to be looked at pre lines for --link-pois-to-ways to work, but for some other things we would need to look at them later again. So this would need to be some kind of seond_finalize rules in the points file that is executed after the lines file - and removes points from the map again. It's not a big problem - but right now this really makes it inconvenient to put gates into your map - as 75% of gates are just cluttering up the map without providing any information to the user (except if you want to create a cataster type of map showing everything). Leaving gates out completely on the other hand makes it very ha rd to show for example with parks where people can enter and where not. As very often there are service entries to parks not open to public - so these are the main ones that we want to show in a map.
On Mon, 10 Oct 2022 at 08:35, Gerd Petermann < gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>> wrote: Hi Felix,
my first thought was that --add-poi-to-lines is all that you need, but maybe I've missed something?
One problem with your suggested solution is that the current implementation in mkgmap processes (tagged) nodes before lines. I can't remember exactly why but a change probably causes side effects.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto: mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag von Felix Hartmann < extremecarver@gmail.com<mailto:extremecarver@gmail.com>> Gesendet: Freitag, 7. Oktober 2022 23:12 An: Development list for mkgmap Betreff: [mkgmap-dev] Test if POI is part of a line
I read through the old poi-tagged-v3.patch
is_in()function for point on line discussion - but what I want is actually different and should be much easier?
Could there be a solution to check if a point is a single point vs if it is part of a open/closed line? Why?
I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line. Especially for gates most are just useless clutter because they are tagged on private houses and similar.
If there was a way to delete afterwards/or create only in first place those points that are part of a line would be good, best would be if they are only shown if part of a routable line (so after the lines stye-file is processed).
-- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Felix Hartman - Outdoormaps LTD - Openmtbmap.org & VeloMap.org
I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line.
Since I try to declutter my maps as best as possible I too had "remove non-relevant gates" on my to do list and followed up on that today. Accounting for points mapped on or between ways and access restrictions optionally stemming from point and/or way I was able, to already thin out my gates significantly. The include file is just "re-used" from my lines processing. /# NoAccess gates on relevant highways// //# only works w/ mkgmap option --add-pois-to-lines// //if (mkgmap:from-node:barrier ~ '.*(gate)' & highway=*) then// //# gate on highway// // include "../inc/RaceSurf"; // // # tagging of (preselected) elements w/ hgh:surface=(Race|noRace)// // # depending on quality in regard to race (and gravel) bike use// //// // if (hgh:surface=Race) then // // (mkgmap:from-node:access ~ 'no|private// // & !(mkgmap:from-node:bicycle ~ 'yes|permissive') ...//) // # relevant access restricted by point// // |// // (access ~ 'no|private' // // & !(bicycle ~ 'yes|permissive') ...//) // # relevant access restricted by road segment// //[...]// //end // //end/ But I was not able, to solve the probably most interesting situation: If a (gate) point is part of two (or more) consecutive ways, it is processed multiple times from --add-pois-to-lines, but one would need the tags of all ways involved at the same time to make the final decision on whether or not to render this point. (That is -for starters-, if not at least two ways were deemed interesting, the gate might not be rendered although from one way alone, it would). Is there a concept, allowing to do that? The only idea I came up with would be, to use the mkgmap:line2poitype tag to flag these POIs somehow and finally delete all, if not at least 2 of those where placed at the exact same location. Somewhat similar to deleting identical POIs at the same location as documented for the nearby-poi-rules. In the latter case (>2), delete all but one... Cheers, Felix
Hi Felix, I do understand that one would want to avoid rendering gates which are not on highways, but I don't understand why you care about the effect on routing. That's a completely different story and I think mkgmap handles this very well with the --link-pois-to-ways option. Or maybe you mean something else? A barrier node should never be connected to more than one way, else it is a mapping error and mkgmap reports this in the log (if enabled). It should be a rare case and thus I see no need to add lots of logic to avoid the rendering. The corresponding nodes should be fixed in OSM. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Herwegh <mlmmduk@herwegh.de> Gesendet: Samstag, 15. Oktober 2022 18:36 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Test if POI is part of a line
I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line.
Since I try to declutter my maps as best as possible I too had "remove non-relevant gates" on my to do list and followed up on that today. Accounting for points mapped on or between ways and access restrictions optionally stemming from point and/or way I was able, to already thin out my gates significantly. The include file is just "re-used" from my lines processing. # NoAccess gates on relevant highways # only works w/ mkgmap option --add-pois-to-lines if (mkgmap:from-node:barrier ~ '.*(gate)' & highway=*) then # gate on highway include "../inc/RaceSurf"; # tagging of (preselected) elements w/ hgh:surface=(Race|noRace) # depending on quality in regard to race (and gravel) bike use if (hgh:surface=Race) then (mkgmap:from-node:access ~ 'no|private & !(mkgmap:from-node:bicycle ~ 'yes|permissive') ...) # relevant access restricted by point | (access ~ 'no|private' & !(bicycle ~ 'yes|permissive') ...) # relevant access restricted by road segment [...] end end But I was not able, to solve the probably most interesting situation: If a (gate) point is part of two (or more) consecutive ways, it is processed multiple times from --add-pois-to-lines, but one would need the tags of all ways involved at the same time to make the final decision on whether or not to render this point. (That is -for starters-, if not at least two ways were deemed interesting, the gate might not be rendered although from one way alone, it would). Is there a concept, allowing to do that? The only idea I came up with would be, to use the mkgmap:line2poitype tag to flag these POIs somehow and finally delete all, if not at least 2 of those where placed at the exact same location. Somewhat similar to deleting identical POIs at the same location as documented for the nearby-poi-rules. In the latter case (>2), delete all but one... Cheers, Felix
Hi Gerd, the quote ("best routable") was from Felix Hartmanns opening post. I just try to render my maps as focussed and decluttered as possible for keeping a bike rolling without loosing too much attention on the map while not using routing. But as far as I understand I see similarities in identifying objects to omit. In my question I was addressing situations similar to the example from the Wikis barrier=gate section <https://wiki.openstreetmap.org/wiki/Tag:barrier%3Dgate> (either with or without an additional barrier=fence or the like crossing), a barrier node being part of two ways hence being processed from both by --add-pois-to-lines. /Based on the location below, the gate node should be the end of a way. A new way starts with the gate node and it should have the access set to private if the access is restricted. / /x------x------O++++x++++x / * /|x|//= node// / * /|O|//= node with barrier=gate/ * /|------|//default way/ * /|+++++|//way with access=private/ For example /Punkt: 17848298// // Datensatz: 230db4cd// // ...// // Merkmale: // // "access"="private"// // "barrier"="gate"// // Koordinaten: 54.1016042, 11.5995597// // ...// // Teil von: // // Linie: Dünenstraße (3629239)// // Linie: 546855848// // Linie: 81154811/ Hence, having a gate between a bad track (later on not rendered due to quality, already filtered from the RaceSurf include) and an acces=no road (later on not rendered for just that) could have rendered an isolated gate from the latter road segment. That's where I took the problematic turn, trying to make a decision on all possible ways connecting a gate, instead of more consequently filtering all roads before having points derived from them in the first place. So another RelevantRoads include file for dual use in points and lines it will be. But: For my sample above, the gate then still will be rendered from the "Dünenstraße", although not needed, since "Dünenstraße" will just end there in my map because neither of lines 546855848 or 81154811 will be rendered. Honestly, I was additionally flirting with trying to use different icons for gates with and without a barrier line (fence), since those without and on suitable roads occasionally could just void nice shortcuts for a bike... :-)
I see no need to add lots of logic...
Sorry, that was not my intention. I'm still searching my way into OSM and mkgmap and only wanted to make shure, not to miss an existing concept as more than once before. I should better have omitted that raw idea of mine, thought it might help understand my train of thought. Cheers, Felix ------------------------------------------------------------------------ *From:* Gerd Petermann [mailto:gpetermann_muenchen@hotmail.com] *Sent:* Sunday, October 16, 2022 at 10:35 AM *To:* Development list for mkgmap *Subject:* [mkgmap-dev] Test if POI is part of a line
Hi Felix,
I do understand that one would want to avoid rendering gates which are not on highways, but I don't understand why you care about the effect on routing. That's a completely different story and I think mkgmap handles this very well with the --link-pois-to-ways option. Or maybe you mean something else?
A barrier node should never be connected to more than one way, else it is a mapping error and mkgmap reports this in the log (if enabled). It should be a rare case and thus I see no need to add lots of logic to avoid the rendering. The corresponding nodes should be fixed in OSM.
Gerd
________________________________________ Von: mkgmap-dev<mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Herwegh<mlmmduk@herwegh.de> Gesendet: Samstag, 15. Oktober 2022 18:36 An:mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Test if POI is part of a line
I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line. Since I try to declutter my maps as best as possible I too had "remove non-relevant gates" on my to do list and followed up on that today. Accounting for points mapped on or between ways and access restrictions optionally stemming from point and/or way I was able, to already thin out my gates significantly. The include file is just "re-used" from my lines processing.
# NoAccess gates on relevant highways # only works w/ mkgmap option --add-pois-to-lines if (mkgmap:from-node:barrier ~ '.*(gate)' & highway=*) then # gate on highway include "../inc/RaceSurf"; # tagging of (preselected) elements w/ hgh:surface=(Race|noRace) # depending on quality in regard to race (and gravel) bike use
if (hgh:surface=Race) then (mkgmap:from-node:access ~ 'no|private & !(mkgmap:from-node:bicycle ~ 'yes|permissive') ...) # relevant access restricted by point | (access ~ 'no|private' & !(bicycle ~ 'yes|permissive') ...) # relevant access restricted by road segment [...] end end
But I was not able, to solve the probably most interesting situation: If a (gate) point is part of two (or more) consecutive ways, it is processed multiple times from --add-pois-to-lines, but one would need the tags of all ways involved at the same time to make the final decision on whether or not to render this point. (That is -for starters-, if not at least two ways were deemed interesting, the gate might not be rendered although from one way alone, it would).
Is there a concept, allowing to do that?
The only idea I came up with would be, to use the mkgmap:line2poitype tag to flag these POIs somehow and finally delete all, if not at least 2 of those where placed at the exact same location. Somewhat similar to deleting identical POIs at the same location as documented for the nearby-poi-rules. In the latter case (>2), delete all but one...
Cheers, Felix _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Not sure which Felix you meant. For me it was not about that poi influencing the routing, but the opposite. If mkgmap created a reputable line only then display the gate. E.g. if excluded using semi-connected marker, then also remove the gate. Typical scenario a highway=path entering a residence garden and the highway=gate tag on the path. What I want are gates for say a public garden or theme park, or similar. On Sun, 16 Oct 2022, 23:18 Felix Herwegh <mlmmduk@herwegh.de> wrote:
Hi Gerd,
the quote ("best routable") was from Felix Hartmanns opening post. I just try to render my maps as focussed and decluttered as possible for keeping a bike rolling without loosing too much attention on the map while not using routing. But as far as I understand I see similarities in identifying objects to omit.
In my question I was addressing situations similar to the example from the Wikis barrier=gate section <https://wiki.openstreetmap.org/wiki/Tag:barrier%3Dgate> (either with or without an additional barrier=fence or the like crossing), a barrier node being part of two ways hence being processed from both by --add-pois-to-lines.
*Based on the location below, the gate node should be the end of a way. A new way starts with the gate node and it should have the access set to private if the access is restricted. *
*x------x------O++++x++++x *
- *x** = node* - *O** = node with barrier=gate* - *------** default way* - *+++++** way with access=private*
For example
*Punkt: 17848298* * Datensatz: 230db4cd* * ...* * Merkmale: * * "access"="private"* * "barrier"="gate"* * Koordinaten: 54.1016042, 11.5995597* * ...* * Teil von: * * Linie: Dünenstraße (3629239)* * Linie: 546855848* * Linie: 81154811*
Hence, having a gate between a bad track (later on not rendered due to quality, already filtered from the RaceSurf include) and an acces=no road (later on not rendered for just that) could have rendered an isolated gate from the latter road segment. That's where I took the problematic turn, trying to make a decision on all possible ways connecting a gate, instead of more consequently filtering all roads before having points derived from them in the first place. So another RelevantRoads include file for dual use in points and lines it will be.
But: For my sample above, the gate then still will be rendered from the "Dünenstraße", although not needed, since "Dünenstraße" will just end there in my map because neither of lines 546855848 or 81154811 will be rendered. Honestly, I was additionally flirting with trying to use different icons for gates with and without a barrier line (fence), since those without and on suitable roads occasionally could just void nice shortcuts for a bike... :-)
I see no need to add lots of logic...
Sorry, that was not my intention. I'm still searching my way into OSM and mkgmap and only wanted to make shure, not to miss an existing concept as more than once before. I should better have omitted that raw idea of mine, thought it might help understand my train of thought.
Cheers, Felix ------------------------------ *From:* Gerd Petermann [mailto:gpetermann_muenchen@hotmail.com <gpetermann_muenchen@hotmail.com>] *Sent:* Sunday, October 16, 2022 at 10:35 AM *To:* Development list for mkgmap *Subject:* [mkgmap-dev] Test if POI is part of a line
Hi Felix,
I do understand that one would want to avoid rendering gates which are not on highways, but I don't understand why you care about the effect on routing. That's a completely different story and I think mkgmap handles this very well with the --link-pois-to-ways option. Or maybe you mean something else?
A barrier node should never be connected to more than one way, else it is a mapping error and mkgmap reports this in the log (if enabled). It should be a rare case and thus I see no need to add lots of logic to avoid the rendering. The corresponding nodes should be fixed in OSM.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Herwegh <mlmmduk@herwegh.de> <mlmmduk@herwegh.de> Gesendet: Samstag, 15. Oktober 2022 18:36 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Test if POI is part of a line
I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line.
Since I try to declutter my maps as best as possible I too had "remove non-relevant gates" on my to do list and followed up on that today. Accounting for points mapped on or between ways and access restrictions optionally stemming from point and/or way I was able, to already thin out my gates significantly. The include file is just "re-used" from my lines processing.
# NoAccess gates on relevant highways # only works w/ mkgmap option --add-pois-to-lines if (mkgmap:from-node:barrier ~ '.*(gate)' & highway=*) then # gate on highway include "../inc/RaceSurf"; # tagging of (preselected) elements w/ hgh:surface=(Race|noRace) # depending on quality in regard to race (and gravel) bike use
if (hgh:surface=Race) then (mkgmap:from-node:access ~ 'no|private & !(mkgmap:from-node:bicycle ~ 'yes|permissive') ...) # relevant access restricted by point | (access ~ 'no|private' & !(bicycle ~ 'yes|permissive') ...) # relevant access restricted by road segment [...] end end
But I was not able, to solve the probably most interesting situation: If a (gate) point is part of two (or more) consecutive ways, it is processed multiple times from --add-pois-to-lines, but one would need the tags of all ways involved at the same time to make the final decision on whether or not to render this point. (That is -for starters-, if not at least two ways were deemed interesting, the gate might not be rendered although from one way alone, it would).
Is there a concept, allowing to do that?
The only idea I came up with would be, to use the mkgmap:line2poitype tag to flag these POIs somehow and finally delete all, if not at least 2 of those where placed at the exact same location. Somewhat similar to deleting identical POIs at the same location as documented for the nearby-poi-rules. In the latter case (>2), delete all but one...
Cheers, Felix _______________________________________________ mkgmap-dev mailing listmkgmap-dev@lists.mkgmap.org.ukhttps://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I won't be able to test anything the next 2 weeks however. Traveling in Nepal.... On Tue, 1 Nov 2022, 15:29 Felix Hartmann <extremecarver@gmail.com> wrote:
Not sure which Felix you meant. For me it was not about that poi influencing the routing, but the opposite. If mkgmap created a reputable line only then display the gate.
E.g. if excluded using semi-connected marker, then also remove the gate. Typical scenario a highway=path entering a residence garden and the highway=gate tag on the path. What I want are gates for say a public garden or theme park, or similar.
On Sun, 16 Oct 2022, 23:18 Felix Herwegh <mlmmduk@herwegh.de> wrote:
Hi Gerd,
the quote ("best routable") was from Felix Hartmanns opening post. I just try to render my maps as focussed and decluttered as possible for keeping a bike rolling without loosing too much attention on the map while not using routing. But as far as I understand I see similarities in identifying objects to omit.
In my question I was addressing situations similar to the example from the Wikis barrier=gate section <https://wiki.openstreetmap.org/wiki/Tag:barrier%3Dgate> (either with or without an additional barrier=fence or the like crossing), a barrier node being part of two ways hence being processed from both by --add-pois-to-lines.
*Based on the location below, the gate node should be the end of a way. A new way starts with the gate node and it should have the access set to private if the access is restricted. *
*x------x------O++++x++++x *
- *x** = node* - *O** = node with barrier=gate* - *------** default way* - *+++++** way with access=private*
For example
*Punkt: 17848298* * Datensatz: 230db4cd* * ...* * Merkmale: * * "access"="private"* * "barrier"="gate"* * Koordinaten: 54.1016042, 11.5995597* * ...* * Teil von: * * Linie: Dünenstraße (3629239)* * Linie: 546855848* * Linie: 81154811*
Hence, having a gate between a bad track (later on not rendered due to quality, already filtered from the RaceSurf include) and an acces=no road (later on not rendered for just that) could have rendered an isolated gate from the latter road segment. That's where I took the problematic turn, trying to make a decision on all possible ways connecting a gate, instead of more consequently filtering all roads before having points derived from them in the first place. So another RelevantRoads include file for dual use in points and lines it will be.
But: For my sample above, the gate then still will be rendered from the "Dünenstraße", although not needed, since "Dünenstraße" will just end there in my map because neither of lines 546855848 or 81154811 will be rendered. Honestly, I was additionally flirting with trying to use different icons for gates with and without a barrier line (fence), since those without and on suitable roads occasionally could just void nice shortcuts for a bike... :-)
I see no need to add lots of logic...
Sorry, that was not my intention. I'm still searching my way into OSM and mkgmap and only wanted to make shure, not to miss an existing concept as more than once before. I should better have omitted that raw idea of mine, thought it might help understand my train of thought.
Cheers, Felix ------------------------------ *From:* Gerd Petermann [mailto:gpetermann_muenchen@hotmail.com <gpetermann_muenchen@hotmail.com>] *Sent:* Sunday, October 16, 2022 at 10:35 AM *To:* Development list for mkgmap *Subject:* [mkgmap-dev] Test if POI is part of a line
Hi Felix,
I do understand that one would want to avoid rendering gates which are not on highways, but I don't understand why you care about the effect on routing. That's a completely different story and I think mkgmap handles this very well with the --link-pois-to-ways option. Or maybe you mean something else?
A barrier node should never be connected to more than one way, else it is a mapping error and mkgmap reports this in the log (if enabled). It should be a rare case and thus I see no need to add lots of logic to avoid the rendering. The corresponding nodes should be fixed in OSM.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Herwegh <mlmmduk@herwegh.de> <mlmmduk@herwegh.de> Gesendet: Samstag, 15. Oktober 2022 18:36 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Test if POI is part of a line
I would only like to display barrier/highway=gate point icons if they are part of a (best routable) line.
Since I try to declutter my maps as best as possible I too had "remove non-relevant gates" on my to do list and followed up on that today. Accounting for points mapped on or between ways and access restrictions optionally stemming from point and/or way I was able, to already thin out my gates significantly. The include file is just "re-used" from my lines processing.
# NoAccess gates on relevant highways # only works w/ mkgmap option --add-pois-to-lines if (mkgmap:from-node:barrier ~ '.*(gate)' & highway=*) then # gate on highway include "../inc/RaceSurf"; # tagging of (preselected) elements w/ hgh:surface=(Race|noRace) # depending on quality in regard to race (and gravel) bike use
if (hgh:surface=Race) then (mkgmap:from-node:access ~ 'no|private & !(mkgmap:from-node:bicycle ~ 'yes|permissive') ...) # relevant access restricted by point | (access ~ 'no|private' & !(bicycle ~ 'yes|permissive') ...) # relevant access restricted by road segment [...] end end
But I was not able, to solve the probably most interesting situation: If a (gate) point is part of two (or more) consecutive ways, it is processed multiple times from --add-pois-to-lines, but one would need the tags of all ways involved at the same time to make the final decision on whether or not to render this point. (That is -for starters-, if not at least two ways were deemed interesting, the gate might not be rendered although from one way alone, it would).
Is there a concept, allowing to do that?
The only idea I came up with would be, to use the mkgmap:line2poitype tag to flag these POIs somehow and finally delete all, if not at least 2 of those where placed at the exact same location. Somewhat similar to deleting identical POIs at the same location as documented for the nearby-poi-rules. In the latter case (>2), delete all but one...
Cheers, Felix _______________________________________________ mkgmap-dev mailing listmkgmap-dev@lists.mkgmap.org.ukhttps://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (5)
-
ael -
ankeric.osm＠gmail.com -
Felix Hartmann -
Felix Herwegh -
Gerd Petermann