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

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

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

Alexis Huxley
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!

Alexis
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Reply | Threaded
Open this post in threaded view
|

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

Ticker Berkin
Hi Alexis

On Wed, 2019-07-10 at 16:58 +0200, Alexis Huxley wrote:

> 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

Wouldn't default value (auto) for max-threads be better
Maybe you need --max-nodes={some value lower than 1600000 to fix the
road problem later}

>
> The splitter output looks okay, though I note it ends:
>
> Number of MapFailedExceptions: 1

you should check out this error

> 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

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


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

I'd expect this from asia & africa; there are a mix of driving sides

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

you need to experiment with splitter max-nodes to fix this

> 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

Mostly can be ignored. Sometimes these are wrong in OSM, but often they
express a more complicated situation than can be expressed in the
garmin routing format.
>
> 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).

Generally make up the first 4 digits, then append 0001 as splitter -
-mapid and it will generate the --mapname in the template file.
I use the same 4 digits as the --family-id

> Can anybody offer any advice? Many thanks!
>
> Alexis

Hope this helps
Ticker

> _______________________________________________
> mkgmap-dev mailing list
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Reply | Threaded
Open this post in threaded view
|

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

Alexis Huxley
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.)

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.

Thanks again!

Alexis

[*] - second to last entry at https://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Download#Worldwide
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Reply | Threaded
Open this post in threaded view
|

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

Ticker Berkin
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
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Reply | Threaded
Open this post in threaded view
|

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

Gerd Petermann
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&mlon=106.829270&zoom=17)
>> via node is not a routing node
>
> This particular case is just rubbish OSM data

Sorry for the late response, was on my bike for a while...
Whenever this message appears it means that there is a severe error in
mkgmap. The code contains a lot of logic to detect invalid route relations
and ignore them, those relations who produce such a message passed these
tests and were later corrupted by one of the many routines which try to
optimize the data before the img data is written.

@Ticker: If you have sample data that allows to reproduce the problem please
post a link.

Gerd



--
Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Reply | Threaded
Open this post in threaded view
|

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

Alexis Huxley
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&zoom=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=17) 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
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Reply | Threaded
Open this post in threaded view
|

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

Gerd Petermann
Hi Alexis,

thanks, that will help.

Gerd

________________________________________
Von: mkgmap-dev <[hidden email]> im Auftrag von Alexis Huxley <[hidden email]>
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&zoom=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=17) 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
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Reply | Threaded
Open this post in threaded view
|

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

Gerd Petermann
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

________________________________________
Von: mkgmap-dev <[hidden email]> im Auftrag von Gerd Petermann <[hidden email]>
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 <[hidden email]> im Auftrag von Alexis Huxley <[hidden email]>
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&zoom=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=17) 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
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Reply | Threaded
Open this post in threaded view
|

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

Ticker Berkin
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=4288
>
> Gerd
>
> ________________________________________
> Von: mkgmap-dev <[hidden email]> im Auftrag
> von Gerd Petermann <[hidden email]>
> 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 <[hidden email]> im Auftrag
> von Alexis Huxley <[hidden email]>
> 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=17)
> 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
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Reply | Threaded
Open this post in threaded view
|

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

Gerd Petermann
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 <[hidden email]> im Auftrag von Ticker Berkin <[hidden email]>
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=4288
>
> Gerd
>
> ________________________________________
> Von: mkgmap-dev <[hidden email]> im Auftrag
> von Gerd Petermann <[hidden email]>
> 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 <[hidden email]> im Auftrag
> von Alexis Huxley <[hidden email]>
> 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=17)
> 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
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Reply | Threaded
Open this post in threaded view
|

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

Ticker Berkin
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 <[hidden email]> im Auftrag
> von Ticker Berkin <[hidden email]>
> 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 <[hidden email]> im Auftrag
> > von Gerd Petermann <[hidden email]>
> > 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 <[hidden email]> im Auftrag
> > von Alexis Huxley <[hidden email]>
> > 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
> > [hidden email]
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> > _______________________________________________
> > mkgmap-dev mailing list
> > [hidden email]
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> > _______________________________________________
> > mkgmap-dev mailing list
> > [hidden email]
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Reply | Threaded
Open this post in threaded view
|

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

Gerd Petermann
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 travel through a node coming from arc a1 going to arc a2 (also more with more arcs and via nodes).
The code checks if the barrier really restricts anything, if not, it is ignored.

I don't understand the last paragraph. I thought this is handled well in inc/access?

Gerd

________________________________________
Von: mkgmap-dev <[hidden email]> im Auftrag von Ticker Berkin <[hidden email]>
Gesendet: Donnerstag, 1. August 2019 21:00
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

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 <[hidden email]> im Auftrag
> von Ticker Berkin <[hidden email]>
> 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 <[hidden email]> im Auftrag
> > von Gerd Petermann <[hidden email]>
> > 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 <[hidden email]> im Auftrag
> > von Alexis Huxley <[hidden email]>
> > 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
> > [hidden email]
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> > _______________________________________________
> > mkgmap-dev mailing list
> > [hidden email]
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> > _______________________________________________
> > mkgmap-dev mailing list
> > [hidden email]
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Reply | Threaded
Open this post in threaded view
|

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

Ticker Berkin
Hi Gerd

I'll have another go at understanding the routing / restrictions
structures and code.

Concerning default/inc/access[_country]: it has quite a few problems
and I use my own version that fixes most of them.

Maybe this should become a new thread - it's getting a bit off the
topic of mkgmap warnings...

Ticker

On Thu, 2019-08-01 at 19:26 +0000, Gerd Petermann wrote:

> 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 travel through a node coming from arc a1 going to arc
> a2 (also more with more arcs and via nodes).
> The code checks if the barrier really restricts anything, if not, it
> is ignored.
>
> I don't understand the last paragraph. I thought this is handled well
> in inc/access?
>
> Gerd
>
> ________________________________________
> Von: mkgmap-dev <[hidden email]> im Auftrag
> von Ticker Berkin <[hidden email]>
> Gesendet: Donnerstag, 1. August 2019 21:00
> 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
>
> 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 <[hidden email]> im Auftrag
> > von Ticker Berkin <[hidden email]>
> > 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=4
> > > 28
> > > 8
> > >
> > > Gerd
> > >
> > > ________________________________________
> > > Von: mkgmap-dev <[hidden email]> im
> > > Auftrag
> > > von Gerd Petermann <[hidden email]>
> > > 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 <[hidden email]> im
> > > Auftrag
> > > von Alexis Huxley <[hidden email]>
> > > 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.82927
> > > > > > 0&;
> > > > > > 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
> > > [hidden email]
> > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> > > _______________________________________________
> > > mkgmap-dev mailing list
> > > [hidden email]
> > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> > > _______________________________________________
> > > mkgmap-dev mailing list
> > > [hidden email]
> > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> > _______________________________________________
> > mkgmap-dev mailing list
> > [hidden email]
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> > _______________________________________________
> > mkgmap-dev mailing list
> > [hidden email]
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> [hidden email]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[hidden email]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev