logo separator

[mkgmap-dev] how to deal with "Attention: Tile contains both drive-on-left (303) and drive-on-right roads" ?

From Alexis Huxley alexishuxley at gmail.com on Wed Jul 10 15:58:07 BST 2019

Hi, I'm using mkgmap r4287 and trying to process continent files from
geofabrik, e.g.  http://download.geofabrik.de/asia-latest.osm.pbf.

For about the last six months (today included) I have 
"drive-on-left-and-drive-on-right" errors for either Africa or Asia:

I call splitter like this:

	java -Xmx380000M -jar splitter.jar --max-threads=40 --mapid=38610001 --search-limit=1000000 /u/ahux/tmp-dir/as/asia-latest.osm.pbf

The splitter output looks okay, though I note it ends:

	Number of MapFailedExceptions: 1
	Number of ExitExceptions: 0

and then I call mkgmap like this:

	java -Xmx380000M -jar mkgmap.jar --code-page=1252 --latin1 --route --remove-short-arcs --road-name-pois --add-pois-to-areas --index --location-autofill=bounds --tdbfile --max-jobs=40 --mapname=38610001 --country-abbr=AS --country-name="Asia" --family-id=598 --family-name="OSM_AS" --overview-mapname=as --series-name="OSM Asia (2019 07)" --description="OSM_AS" --generate-sea=multipolygon --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 /u/ahux/tmp-dir/as/3861*.osm.pbf

and get a *lot* of these:

	SEVERE (StyledConverter): /u/ahux/tmp-dir/as/38610086.osm.pbf: Attention: Tile contains both drive-on-left (71473) and drive-on-right roads (51)

and a few other assorted messages like:

	SEVERE (MapFailedException): /u/ahux/tmp-dir/as/38610555.osm.pbf: (thrown in RoadDef.writeRgnOffsets()) Overflow of the NET1. The tile (/u/ahux/tmp-dir/as/38610555.osm.pbf) must be split so that there are fewer roads in it
	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&zoom=17) via node is not a routing node

How should I respond to these messages? I mean: can I use mkgmap's
output anyway? Or should I try to get upstream data fixed in OSM? (if
yes: how can I turn these error messages into a location?) Or should
I modify my calls to mkgmap or splitter?

Oh, also another small question: is there any convention/rule/list
for '--mapname=NNNNNNNN' or '--family-id=NNN' numbers, or should just
make them up? (which what I'm currently doing).

Can anybody offer any advice? Many thanks!


More information about the mkgmap-dev mailing list