
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 this be the routing node that imposes restrictions between the 2 ways. I'm not really suggesting making any changes; I don't how it all works and I have never noticed a problem with the current implementation: 1/ I can't see that it matters if the restrictions are applied to both roads (presumably up to the next junction/routing node). 2/ I only ever use pedestrian or car navigation and most of the barriers are stiles/kissing-gates on footpaths with bicycle=no. 3/ For the UK, cycling is not allowed on footpaths. Other thoughts: If the barrier doesn't impose additional restrictions over the most restrictive of the 2 ways, then no action is needed anyway. If the routing node support the idea of restricting through-routing based on the transport mode, it would be really useful to have access to this from the style. I've been trying to come up with a tolerable solution for cases where there is a foot/cycleway right-of-way along on a highway=service with that also has something like motor_vehicle=destination. Regards Ticker On Thu, 2019-08-01 at 16:30 +0000, Gerd Petermann wrote:
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 for that particular place?
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Donnerstag, 1. August 2019 18:15 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] how to deal with "Attention: Tile contains both drive-on-left (303) and drive-on-right roads" ?
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.openstreetmap.org/node/1043237463 affects routing on multiple ways
Ticker
On Thu, 2019-08-01 at 12:29 +0000, Gerd Petermann wrote:
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=428 8
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <gpetermann_muenchen@hotmail.com> Gesendet: Donnerstag, 1. August 2019 13:23 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] how to deal with "Attention: Tile contains both drive-on-left (303) and drive-on-right roads" ?
Hi Alexis,
thanks, that will help.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Alexis Huxley <alexishuxley@gmail.com> 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 (303) and drive-on-right roads" ?
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/?mlat=-6.405884&mlon=106.829270& zo om=17) via node is not a routing node
Gerd wrote:
Whenever this message appears it means that there is a severe error in mkgmap.
@Ticker: If you have sample data that allows to reproduce the problem please post a link.
Geofabrik's daily 'asia-latest.osm.pbf' has this problem. I just re -downloaded from http://download.geofabrik.de/asia-latest.osm.pbf to verify the problem is still there, which it is. In case it helps, the checksum of the asia-latest.osm.pbf I just tested is:
$ md5sum download-cache-dir/asia-latest.osm.pbf bae4ea71f6b48366cb21c2cdf5ceda20 download-cache-dir/asia -latest.osm.pbf $
Besides the numerous 'Tile contains both drive-on-left and drive-on -right' messages, which is what I originally posted about, and which Ticker has already explained are not really errors, these are the other errors:
$ grep SEVERE *.log | grep -v 'Tile contains both drive-on -left' SEVERE (RestrictionRelation): 59890171.osm.pbf: Turn restriction (only_straight_on) http://www.openstreetmap.org/relation/9335096 (at http://www.openstreetmap.org/?mlat=-6.442483&mlon=106.830079&zoom=1 7) via node is not a routing node SEVERE (MapFailedException): 59890543.osm.pbf: (thrown in RoadDef.writeRgnOffsets()) Overflow of the NET1. The tile (59890543.osm.pbf) must be split so that there are fewer roads in it SEVERE (MapFailedException): 59890570.osm.pbf: (thrown in RoadDef.writeRgnOffsets()) Overflow of the NET1. The tile (59890570.osm.pbf) must be split so that there are fewer roads in it $
For the 'Overflow' ones, Ticker already advised me how to split the tiles up a bit more.
Regading the 'Turn restriction', I've copied the specific tile 59890171.osm.pbf to https://datashare.rzg.mpg.de/s/RHEzSLYhNNkPbfb?path=%2Ftmp.
My splitter and mkgmap command line arguments are:
java -Xmx380000M -jar splitter.jar --mapid=59890001 - -search -limit=1000000 /u/ahux/tmp-dir/as/asia-latest.osm.pbf java -Xmx380000M -jar mkgmap.jar --code-page=1252 --latin1 - -route --remove-short-arcs --add-pois-to-areas --index --location -autofill=is_in,nearest --tdbfile --mapname=59890001 --family -id=5989 --family-name="OSM_AS" --overview-mapname=as --series-name="OSM Asia (2019 08)" --description="OSM_AS" --bounds=/u/ahux/tmp -dir/as/bounds -latest.zip --precomp-sea=/u/ahux/tmp-dir/as/sea-latest.zip --style -file=/u/ahux/tmp-dir/as/mkgmap/distrib/mkgmap -r4287/examples/styles/default -c template.args
and I'm using:
$ ls -l ../../download-cache-dir/*.zip -rw-r--r-- 2 ahux rzs 1090392991 Aug 1 10:36 ../../download -cache-dir/bounds-latest.zip -rw-r--r-- 1 ahux rzs 3401612 Aug 1 11:45 ../../download -cache-dir/mkgmap-r4287.zip -rw-r--r-- 2 ahux rzs 224903148 Aug 1 10:36 ../../download -cache-dir/sea-latest.zip -rw-r--r-- 1 ahux rzs 1569564 Aug 1 11:45 ../../download -cache-dir/splitter-r592.zip $
Hope that helps you to help us! :-) Thanks!
Alexis _______________________________________________ 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 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