I have commited changes to the default style so that it should work now.
Of course I couldn't test all combinations but the access file is much
more straight forward (I think so... ;-)
WanMil
> Yep, I have to think about a different workaround for the bug.
>
> I also noticed that the compile tim
Yep the access flags are ok.
I guess like Felix says it always have been like this.
The only solution is making the motorways not routable in a bike specific map.
Too bad we still dont know how the activity routing works in BC and the newer
generation GPS.
> Did you (or if not can you) check th
> Thanks Wanmil,
> Access flags look ok now in gpsmapedit.
>
> Bicycle routing still takes the motorway
> Tested it from city nodes Amersfoort-Apeldoorn
Did you (or if not can you) check the motorways with GPSMapEdit? Is the
flag set that prevents bicycle routing on motorways? In such a case it
Yep, I have to think about a different workaround for the bug.
I also noticed that the compile time for a map seems to be increased
quite a lot. This is not the case when the access file is not included
from the points file.
Some more work to do... :-)
> Here are more examples that are missing
over long distances avoid motorways is not working - it has always been
this way. It shouldn't happen over relatively short distances
On 13.10.2013 13:55, Minko wrote:
> Thanks Wanmil,
> Access flags look ok now in gpsmapedit.
>
> Bicycle routing still takes the motorway
> Tested it from city node
Thanks Wanmil,
Access flags look ok now in gpsmapedit.
Bicycle routing still takes the motorway
Tested it from city nodes Amersfoort-Apeldoorn
The OSM generic routable (osm data 8/10) calculates a route not over motorways
or for cyclists forbidden roads.
However, if I calculate a route between
Here are more examples that are missing in the access rules
public_transport=platform
railway=platform
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
How about access rules for route=ferry?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I think mkgmap is able to distinguish closed areas from lines now.
So maybe the rule with area=yes isnt needed at all?
My point is that polygons like man_made=reinforced_slope and man_made=groine is
rendered now as building,
and it shouldnt be rendered like that (will be rendered as background an
Could there be a fix for this problem that keys also work without
highway=* or other keys from original osm data when they are set via the
style-file itself - or will this bug likely be left unfixed?
On 13.10.2013 11:11, WanMil wrote:
>>> line 11 in the inc\access:
>>>
>>> highway=cycleway {add a
>> line 11 in the inc\access:
>>
>> highway=cycleway {add access = no; add bicycle = yes; add foot = yes}
>
> Oh, I overlooked that. You are right. It seems to be the same bug I
> discussed with Steve:
> http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2013q3/018820.html
>
> I will fix that.
>
> Thank
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 13.10.2013 10:33, schrieb Minko:
> man_made=* & area!=no
I think this is wrong in polygon-file. It should be:
man_made=* & area=* & area!=no
or:
man_made=* & area=yes
In your version above, a man_made-object containing no area-tag is
handled as
Hi,
Can man_made=pier and man_made=bridge added to
# squares and plazas
highway=pedestrian & area=yes [0x17 resolution 22]
man_made=pier | man_made=bridge [0x17 resolution 22]
And man_made=groyne and man_made=reinforced_slope (same thing as breakwater,
used frequently in NL)
are rendered as b
> line 11 in the inc\access:
>
> highway=cycleway {add access = no; add bicycle = yes; add foot = yes}
Oh, I overlooked that. You are right. It seems to be the same bug I
discussed with Steve:
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2013q3/018820.html
I will fix that.
Thanks for reportin
14 matches
Mail list logo
