Hi Steve,
I'd like to change the code for the --link-pois-to-ways option
so that POI with access restrictions (e.g. barriers or gates)
are converted to route restrictions instead of short way segments with
limited access as this doesn't represent the real meaning
of the POI.
My problem: Current
Thanks Wanmil, I'll do some tests.
In the default access style of the branch I found one error:
highway=cycleway { add bicycle=yes; add access=no }
Correction:
highway=cycleway { add bicycle=yes; add foot=yes; add access=no }
___
mkgmap-dev
On Fri, Dec 20, Minko wrote:
Thanks Wanmil, I'll do some tests.
In the default access style of the branch I found one error:
highway=cycleway { add bicycle=yes; add access=no }
Correction:
highway=cycleway { add bicycle=yes; add foot=yes; add access=no }
That's wrong.
From OSM:
A few more additions:
highway=steps { add foot=yes; add access=no }
highway=bridleway { add foot=yes; add access=no }
About access on bridleways i'm not sure.
In the UK cyclists are allowed but in the NL's only pedestrians.
The default rule is no
On Fri, Dec 20, Minko wrote:
A few more additions:
highway=steps { add foot=yes; add access=no }
highway=bridleway { add foot=yes; add access=no }
About access on bridleways i'm not sure.
In the UK cyclists are allowed but in the NL's only
Thanks Wanmil, I'll do some tests.
In the default access style of the branch I found one error:
highway=cycleway { add bicycle=yes; add access=no }
Correction:
highway=cycleway { add bicycle=yes; add foot=yes; add access=no }
Hi Minko,
it's discussable which variant is correct. And
Ok, there is no access restriction for horses in the Garmin img format.
But you are right
highway=bridleway { add foot=yes; add access=no }
should be
highway=bridleway { add access=no }
I will change that.
What about highway=steps? I think the rule is
If you look at the traffic rules you might be right Thorsten.
Pedestrians may only use cycleways if there are no adjacent footways.
In general on OSM sidewalks are not mapped very frequently so I would suggest
to set access default on yes.
Unless mkgmap can detect if there are sidewalks/footways
Wanmil wrote
But you are right
highway=bridleway { add foot=yes; add access=no }
should be
highway=bridleway { add access=no }
I will change that.
No, I meant the opposite. It is already set to no which means unroutable.
What about highway=steps? I think the rule is fine?
WanMil
No,
Am 20.12.2013 10:52, schrieb Minko:
If you look at the traffic rules you might be right Thorsten.
Pedestrians may only use cycleways if there are no adjacent footways.
In general on OSM sidewalks are not mapped very frequently so I would suggest
to set access default on yes.
Unless mkgmap
Hi Chris,
Ok, I read in the cycleways wiki that it is strongly adviced that foot=yes
should be tagged on cycleways that are open for pedestrians, didnt know this.
Hi,
the default access rules are listed here:
http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access-Restrictions
Wanmil wrote
But you are right
highway=bridleway { add foot=yes; add access=no }
should be
highway=bridleway { add access=no }
I will change that.
No, I meant the opposite. It is already set to no which means unroutable.
What about highway=steps? I think the rule is fine?
WanMil
No, I
Hi,
okay, I think I understand now better.
mkgmap r2889 writes all route restrictions
so that they prohibit pedestrians and emergency vehicles.
RouteRestriction contains this:
HEADER = 0x004005;
If I change that to
0x004605
(as the wiki suggests) routing is allowed for pedestrians and
On 12/20/13 10:20 AM, GerdP wrote:
Hi,
okay, I think I understand now better.
mkgmap r2889 writes all route restrictions
so that they prohibit pedestrians and emergency vehicles.
RouteRestriction contains this:
HEADER = 0x004005;
If I change that to
0x004605
(as the wiki suggests)
Hi Richard,
please check: mkgmap treats except=psv like execpt=bus, and I think that's
correct.
Gerd
Date: Fri, 20 Dec 2013 10:47:25 -0500
From: rwe...@averillpark.net
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Route Restrictions
On 12/20/13 10:20 AM, GerdP wrote:
Hi,
Hi Wanmill,
I tried to compile maps with mkgmap-r2889. Now the first issue is fixed.
Probably due to the fix of the shapes which do net have the same first and
last point.
Many thanks.
Marek
2013/10/22 WanMil wmgc...@web.de
Hi Marek,
I compiled Slovakia with logging enabled and the
Hi Steve,
did you find some time to fix the case sensitiveness problem?
Many thanks
Marek
2013/10/24 Steve Ratcliffe st...@parabola.me.uk
On 24/10/13 01:18, Andrzej Popowski wrote:
There is a list of names shortened to 4-characters, isn't it simplified
list for search?
Yes, but that
Hi Wanmil,
I have done a few tests with your debug function.
It didnt report all roads in the log file, but the ones that were logged gave a
good insight of the routing bits that were on and off.
I added two rules to the end of the default branch line style to see what will
happen:
Hi Wanmil,
I have done a few tests with your debug function.
It didnt report all roads in the log file, but the ones that were logged gave a
good insight of the routing bits that were on and off.
I added two rules to the end of the default branch line style to see what will
happen:
Hi all,
I have added documentation for new actions and tags evaluated by the
mergeroads branch. So from my point of view I am ready to merge it back.
The documentation already seems to be online
(http://www.mkgmap.org.uk/doc/pdf/style-manual.pdf).
I will merge to trunk on Sunday if noone
20 matches
Mail list logo
