Hi Ticker,
yes, with the current implemation the barrier doesn't change the access
attributes of the way(s). The data structure in IMG format is very similar to
that of restriction relations with type "no_*" in OSM, it allows to define that
certain vehicles (transport modes) are not allowed to
Hi Gerd
I haven't been able to understand the routing data structures and logic
but it looks like barrier=* is using some similar methods to
mkgmap:throughroute=no, which is applied to a road and changes the
routing nodes at either end.
In the case of a barrier between two roads, then couldn't th
Hi Ticker,
The problem with this kind of tagging is that it is not obvious for which way
the access restriction is meant. In your example both ways have the same tags
which allow bicycles, the default style interprets the barrier=kissing_gate as
a bicycle=no.
No idea if the tagging makes sense
Hi Gerd
Another case where I get similar errors is when there is a barrier that
imposes a restriction that is on the join of 2 ways (quite a common and
sensible thing to do):
WARN: uk.me.parabola.mkgmap.osmstyle.StyledConverter 74210002.osm.pbf:
Access restriction in POI node
http://www.openstr
Hi Alexis,
turned out I was wrong. The messages which I referred to should contain the
string "internal error". Your case was in fact simply wrong data.
With r4288 the message was improved:
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4288
Gerd
___
Version mkgmap-r4288 was committed by gerd on Thu, 01 Aug 2019
Improve log message when route restriction when via node is not a routing node.
(Change severity to Warning, add hint that the restriction is ignored)
There are two possible reasons for this:
- the restriction can be wrong, e.g. contai
Hi Alexis,
thanks, that will help.
Gerd
Von: mkgmap-dev im Auftrag von Alexis
Huxley
Gesendet: Donnerstag, 1. August 2019 13:18
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] how to deal with "Attention: Tile contains both
drive-on-left (30
Hi Gerd,
Ticker wrote:
> > I forgot to answer one of your previous questions fully:
> >>SEVERE (RestrictionRelation): /u/ahux/tmp-
> >> dir/as/38610173.osm.pbf: Turn restriction (no_straight_on)
> >> http://www.openstreetmap.org/relation/9335098 (at
> >> http://www.openstreetmap.org/?ml
Ticker Berkin wrote
> I forgot to answer one of your previous questions fully:
>>SEVERE (RestrictionRelation): /u/ahux/tmp-
>> dir/as/38610173.osm.pbf: Turn restriction (no_straight_on)
>> http://www.openstreetmap.org/relation/9335098 (at
>> http://www.openstreetmap.org/?mlat=-6.405884&ml
