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

Thu Jul 11 14:35:35 BST 2019

Hi Alexis

On Thu, 2019-07-11 at 14:31 +0200, Alexis Huxley wrote:
> Thanks Ticker!
> 
> > > The splitter output looks okay, though I note it ends:
> > > 
> > > 	Number of MapFailedExceptions: 1
> 
> > you should check out this error
> 
> I reworked my wrapper script so splitter and mkgmap save their
> output separately and now I can see that this message was actually 
> from mkgmap, not splitter, and see that this was the cause:
> 
> 	SEVERE (MapFailedException): /u/ahux/tmp
> -dir/as/85120555.osm.pbf: (thrown in RoadDef.writeRgnOffsets())
> Overflow of the NET1. The tile (/u/ahux/tmp-dir/as/85120555.osm.pbf)
> must be split so that there are fewer roads in it
> 
> so I followed your advice:
> 
> > you need to experiment with splitter max-nodes to fix this
> 
> and halved max-nodes to 800000 and Asia now works! 
> 
> I'm processing all continents every three months [*]; is there any 
> disadvantage if I lower max-nodes for *all* continents, rather than
> just the problematic ones? (I'm thinking about my wrapper scripts.)

It's a trade off between the number of tiles and their size; however
fewer, bigger tiles should have an overall map size advantage. So best,
as long as the big tiles don't break anything (ie the NET1 overflow),
to have max-nodes as large as possible, then reduce it a bit (by, say,
10%) if you hit one of these problems. Then, for simplicity, just use
the same value for all your maps.

But beware: changing max-nodes will affect which areas are covered by
each tile, and so it is possible that decreasing it can shift more
items of a particular sort into a tile and break it.

> I'll regenerate the other continents anyway, to check if there
> are any obvious problems and also to see how the execution time
> compares to before. So far my record for Europe is 03:02:31 for
> splitter/mkgmap/zip :-)
> 
> > > 	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
> > 
> > --road-name-pois - probably not needed anymore.
> > --location-autofill=is_in,nearest better (bounds doesn't do
> > anything).
> > --max-jobs is better without a value.
> > --country_name/abbr best removed as you are covering multiple
> > countries.
> > --mapname should be set per tile - see later.
> > --description ditto.
> > --generate-sea remove; you are using --precomp-sea
> > 
> > instead of .../3861*.osm.pbf, use the template file generated by
> > the
> > splitter with -c ..../template.args
> 
> All your suggestions applied. 

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&zoom=17)
> via node is not a routing node

This particular case is just rubbish OSM data

> 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?

There should be no problem using the mkgmap output. Trying to fix these
type of errors is not reasonable for you to do without local knowledge
of the feature being described.

The location (as latitude/longitude) is in the message, also the OSM
feature, so you can just click on the URL in the error message to see
what is going on and where

> Thanks again!
> 
> Alexis

No problem
Ticker

> [*] - second to last entry at
> https://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Download#Worldw
> ide
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev