Is the following syntax correct? seamark:type=fairway {name 'fairway'} { add mkgmap:skipSizeFilter=true; set mkgmap:drawLevel=60 } [0x10306 level 2] waterway=riverbank { add mkgmap:skipSizeFilter=true; set mkgmap:drawLevel=02 } [0x10302 resolution 18] Von: Gerd Petermann Gesendet: Mittwoch, 16. November 2016 16:38 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Spurious points & Basecamp blank tiles Hi all, I did not get any feedback on this patch. I am not sure if it fixes the problem or if it's just a work around. Does anybody expect a problem with it? Gerd Gerd Petermann wrote
Hi Teemu,
Maybe I have a fix for this. We have special code in mkgmap for POI with type >= 0x0100 && type <= 0x1100, they are considered to be cities and those are special. With the attached patch only those with subtype = 0 are: type >= 0x0100 && type <= 0x1100 && (type & 0xff) == 0
This seems to fix the problem, but maybe it is only a workaround. Another observation: The MP file gives a label for each of these 0x1001 POI, the pbf file doesn't.
A binary based on r3701 is here: http://files.mkgmap.org.uk/download/312/mkgmap.jar type_0x1001.patch <http://gis.19327.n8.nabble.com/file/n5885745/type_0x1001.patch>
Gerd Teemu Peltonen wrote
Hi,
http://kartat.hylly.org/mkgmap/M431_cgpsmapper.img is created with cGPSmapper and contains point type 0x1001 (among other rather exotic types) without problems. Polish map file used to generate this file can be found from http://kartat.hylly.org/mkgmap/M431.7z.
It also looks like that these artifacts does not exists when the img is created from a pbf file containing no actual OSM data. Map generated from http://kartat.hylly.org/mkgmap/M431.osm.pbf with the same style definitions works perfectly fine. 0x1001 points are, however missing so they might definitely be part of the problem. The only difference between M431_osm.osm.pbf (from the original post )and M431.osm.pbf is that OSM data is merged to M431_osm.osm.pbf with osmconvert.
-Teemu
9.11.2016, 13:40, Gerd Petermann kirjoitti:
Hi Teemu,
please provide a link to a small map with an 0x1001 type created with cGPSmapper. Maybe we can learn from that.
Gerd
Teemu Peltonen wrote
Hi,
those same types worked with cGPSmapper without a problem. Thank you for this insight, I'll try to change types and see what happens.
-Teemu
On Wed, Nov 9, 2016 at 12:31 PM, Andrzej Popowski < popej@.onet > wrote:
Hi,
I have once created a test map for all possible objects, using cGPSmapper. I have found, that some objects are problematic. I don't remember details, but I think sometimes map doesn't work at all.
My current set of good points exclude 0x1001. Actually I think that for types 0x01xx to 0x11xx only subtype 0 is accepted. And some POI types doesn't work at all, for example 12xx, 13xx, 31xx-3fxx.
I don't know if this is a problem of Garmin devices or cGPSmapper.
-- Best regards, Andrzej
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@.org http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- View this message in context: http://gis.19327.n8.nabble.com/Spurious-points-Basecamp-blank-tiles-tp588543... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n8.nabble.com/Spurious-points-Basecamp-blank-tiles-tp588543... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev