> 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.
Yeah who cares, all those nameless swimming pools in St Tropez ;-)
Thanks Steve for clearing thi
Am 22.10.2012 13:58, schrieb Minko:
> 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?
I checked this. Every problematic tile belongs to Denmark. So
address-no
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 mess
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?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.m
Am 22.10.2012 13:34, schrieb Minko:
> 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 t
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 displ
On 22/10/12 09:07, Minko wrote:
> 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 reso
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 | p
I have detected the tile that makes the index crash.
http://osm.pleiades.uni-wuppertal.de/garmin/openfietsmap_lite/15-10-2012/63440190.img
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 th
