Hi,

okay the normal reason for these error are input files with too many details.
I see them only when I use very high max-nodes values in splitter
or with tiles that contain large areas of sea and the parameter precomp-sea
is used in mkgmap. If you see them in other constellations, please report details
so that we can reproduce them .

Gerd

Date: Sun, 29 Dec 2013 19:59:13 +1000
From: steve.sgalowski@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] FW: SEVERE (MapSplitter) Errors - "Area too small to split at..."

yet when i had that version of mkgmap loaded , it never gave me those areas 
but i do know i get errors in asia ism map.

stephen



On Sun, Dec 29, 2013 at 7:47 PM, Gerd Petermann <gpetermann_muenchen@hotmail.com> wrote:
Sorry, something went wrong...

From: gpetermann_muenchen@hotmail.com
To: geep999@yahoo.co.uk
Subject: RE: [mkgmap-dev] SEVERE (MapSplitter) Errors - "Area too small to split at..."
Date: Sun, 29 Dec 2013 10:44:55 +0100

Hi Peter,

maybe you can try to use a smaller max-nodes value or the precomp-sea parameter for splitter.
If that doesn't help, please provide the splitter.log for further analysis.

Gerd

Date: Sun, 29 Dec 2013 09:12:57 +0000
From: geep999@yahoo.co.uk
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: [mkgmap-dev] SEVERE (MapSplitter) Errors - "Area too small to split at..."

Hi,
I'm getting lots of errors like this with both mkgmap-r2889 and mkgmap-r2651:

SEVERE (MapSplitter): /media/space5/my.osm.stuff.overflow/step4and5/63240021.osm.pbf:
  Area too small to split at http://www.openstreetmap.org/?mlat=51.53796&mlon=-0.10158&zoom=17
  (reduce the density of points, length of lines, etc.)
Can't set city point index for N1P 2NS (too many indexed points in division)
Can't set city point index for N1P 2NR (too many indexed points in division)

However it does run to completion and a gmapsupp.img of a sensible size is created.
The file works on my Garmin eTrex Vista HCx and I can see and navigate to the postcodes.
But some points, e.g. N1P 2NS, are missing, although others nearby, e.g.N1P 2NN, exist.

This has happened since I have been adding postcodes into a map of Great Britain,
using some ideas from this recipe:
http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Postcode_Search_On_Garmin

Anyway - I don't quite know what to do now.
How do I set about reducing the density of points and length of lines?
Is there something I should do prior to running mkgmap e.g. some splitter options
I should change?
Currently I'm just doing:
time splitter \
/media/space5/my.osm.stuff.overflow/step3/great-britain-latest.osm.with.rightsofway.and.postcodes.pbf \
 > splitter.log

time java -Xmx3072M -jar /home/dad/osm.stuff/mkgmap-r2889/mkgmap.jar \
--gmapsupp \
--style-file=/home/dad/osm.stuff/mkgmap-r2651/examples/styles/mydefault/ \
--family-id=4538 \
--max-jobs=2 \
-c /media/space5/my.osm.stuff.overflow/step4and5/template.args \
/home/dad/osm.stuff/own.garmin.images/mydefault.v3.txt

Cheers,
Peter

_______________________________________________ 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