This error was caused in my syle file, where I handled place=locality the same as villages: (place=locality | place=village) & mkgmap:area2poi!=true [0x0b00 resolution 21-20 continue] (place=locality | place=village) & mkgmap:area2poi!=true [0x0600 resolution 22-22 continue] (place=locality | place=village) & mkgmap:area2poi!=true [0x0400 resolution 23] The strange thing is when I render locality the same as hamlets, there is no crash when Mapsource tries to write an index. (place=neighbourhood | place=hamlet | place=locality) & mkgmap:area2poi!=true [0x0b00 resolution 22-22 continue] (place=neighbourhood | place=hamlet | place=locality) & mkgmap:area2poi!=true [0x0800 resolution 23] I also downloaded the problematic tile, with only the nodes place=locality http://www.overpass-api.de/api/xapi?node[bbox=-2.724609,41.835938,-1.142578,42.978516][place=locality][@meta] Holy crap! This tile alone contains 23.537 nodes with place=locality!! No wonder the index crashes, I better don't render this item at all or at least make it not findable in the index.... One question remains, why does this particular tile has an impact on the whole country set? If I choose another tile (no matter where) and want to send to the GPS from Mapsource, it also crashes.

I have detected the tile that makes the index crash. http://osm.pleiades.uni-wuppertal.de/garmin/openfietsmap_lite/15-10-2012/634... If I send this tile to the GPS, Mapsource crashes instantly: MDR_TRIM_ADDR.CXX-347-6.16.3.0

Maybe someone can find the bug in this file?

...

I have isolated the file which gives an error message "point number too big" http://mijndev.openstreetmap.nl/~ligfietser/test/63440791.zip

However, this one didnt cause the problem with writing an index. So I have to search in the other tiles (but still like to know what "point number too big" means) ;-)

Thanks Steve, I've decided to use a Garmin category for place=locality that will not be indexed. Downloaded Spain with only place=locality, it won't open in JOSM so I think it is better not put it in the index at all ;-) Any idea what the warning message "point number too big" means? It is displayed when generating an index file on this img: http://mijndev.openstreetmap.nl/~ligfietser/test/OFM_Lite/63440791.zip The map looks ok without any crashes, just wondering what this message means.

In Denmark all(?) addresses have been imported, something we are considering in the NLD's too since the National Address database is public domain. Maybe this causes those warnings?

On 22/10/12 12:34, Minko wrote:

Thanks Steve, I've decided to use a Garmin category for place=locality that will not be indexed. Downloaded Spain with only place=locality, it won't open in JOSM so I think it is better not put it in the index at all ;-)

Any idea what the warning message "point number too big" means?

It means that there is more than 256 points in a single subdivision. You can't have this in the index, so any such points are just not included and the messages is printed. However, mkgmap is supposed to ensure that all subdivisions have less points than that. So I would expect a previous 'Area too small to split' message when compiling the tile. I see the Henning's reply that he does in fact get that message. The index should be fine, apart from possibly missing a few entries. In your particular file the affected points are all swimming pools without a name, so would not be in the index anyway. ..Steve

I'm having a similar problem as recently reported by Minko with my Central America map [1]: as soon as I click on any tile to select it on MapSource or MapInstall, the program crashes. The problem doesn't seem to be related with my stile tough, as removing the line "place=locality [0x2800 resolution 24]" from my points style file doesn't help neither does using default stile. I have used a predefined areas.list but also splitter calculated tiles, with max-nodes from 500000 to 1600000 with no success. The estrange thing is that gmapsupp.img generated with mkgmap [2] seems to work fine on device, as least on my limited tests. The only unusual information I have found in the log is some 450 lines of type: no precompiled boundary information available for raster tile X-Y My commands: java -Xmx1500M -jar splitter.jar --overlap=3000 --split-file=$pais.list --geonames-file=cities15000_$ABR.zip --mapid=551${FID}001 $pais.osm.pbf java -Xmx2000m -ea -Dlog.config=logging.properties -jar mkgmap.jar --output-dir=../mapas/$pais --bounds=bounds --precomp-sea=sea --max-jobs --route --latin1 --code-page=1252 --area-name=$MAPA --family-name="OpenStreetMap $MAPA" --family-id=1$FID --product-id=1 --series-name="OSM-$MAPA" --overview-mapname=$ABR-1${FID} --overview-mapnumber=551${FID}000 --index --road-name-pois=0x640a --ignore-maxspeeds --remove-short-arcs --merge-lines --add-pois-to-areas --adjust-turn-headings --report-similar-arcs --link-pois-to-ways --location-autofill=is_in --drive-on-right --check-roundabouts --check-roundabout-flares --license-file=license_ODbL.txt --copyright-message="OpenStreetMap contributors, ODbL. See: http://www.openstreetmap.org/copyright" --style=mio -c $pais.args @Minko: what garmin code are you using now for place=locality? [1] http://mapas.alternativaslibres.es/OpenStreetMap_Central-America.exe [2] http://mapas.alternativaslibres.es/gmapsupp_Central-America.zip

Hi Minko, please post the OSM data file together with your mkgmap options. The img file does not help when searching for problems and/or error messages in the mkgmap chain. Thanks! WanMil

I have isolated the file which gives an error message "point number too big" http://mijndev.openstreetmap.nl/~ligfietser/test/63440791.zip

However, this one didnt cause the problem with writing an index. So I have to search in the other tiles (but still like to know what "point number too big" means) ;-) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev