Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[Andrzej Popowski]

Hi Teemu,

> Looks like 0x10f__ types are not working on polygons despite both IMG
> and TYP being seemingly fine with them.

Types 0x10f__ are called "customizable area", they should work correctly 
but are invisible without graphics in TYP file. And don't forget about 
draw order for each area.


--
Best regards,
Andrzej
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[Teemu Peltonen]

Hi,

unfortunately I didn't have time or ability to test the patch. Seems 
like problems are solved when I changed POI types 
(https://github.com/pailakka/mtk2garmin/commit/4b3969d726e7b3e36eaa4f0fb8323a744a6c33cf). 



Looks like 0x10f__ types are not working on polygons despite both IMG 
and TYP being seemingly fine with them.


-Teemu

16.11.2016, 17:38, Gerd Petermann kirjoitti:

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


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

http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


___
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-tp5885434p5885635.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.
___
mkgmap-dev mailing list


mkgmap-dev@.org

http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


___
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-tp5885434p5885999.html
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



___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[rheinskipper1000]

My first test look really promising. All the draw order problems for fairway on 
river Rhine in the Mainz/Wiesbaden area are gone. It looks very beautiful now:

https://mega.nz/#!dFE1QIKK!BfIobp0WApKJtGdthwWvDt8IzNluZSwOaixW7PnmvJk


However I still found one spot where the fairway is still not visible:

https://mega.nz/#!IM1FjK6R!Q0pDo43Qu8alan4Qrk4QCGsQtTyoQg7eWQx5cLs_EU8

But this should not be a mkgmap issue because same problem also exists in 
openseamap online map. I will investigate further and keep you informed.

Thank you so much for this great improvement. It is a huge step for the 
openseamap project because it is pre-condition for rendering crowdsourced water 
depth as different shades of blue. There are 7 different predefined extended 
types for water depth which all have same built in draw order. Now chances are 
good that they can be controlled.



And sorry for mixing LEVEL and RESOLUTION. I used LEVEL but my style is based 
on default style which uses RESOLUTION.


Von: Ticker Berkin
Gesendet: Mittwoch, 16. November 2016 17:05
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

Hi

Not quite, you should have something like:

seamark:type=fairway {name 'fairway'; set mkgmap:drawLevel=60 }
[0x10306 level 2]
waterway=riverbank { set mkgmap:drawLevel=02 } [0x10302 resolution 18]

but you only need one of the mkgmap:drawLevel for the fairway to be
written after/overwrite the riverbank. Which you use depends on what
you want the behaviour to be with other polygons sharing the same area.

Also, slightly confusing to have level and resolution in the same
style.

And the wrong thread.

Regards
Ticker
___
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

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[Ticker Berkin]

Hi

Not quite, you should have something like:

seamark:type=fairway {name 'fairway'; set mkgmap:drawLevel=60 }
[0x10306 level 2]
waterway=riverbank { set mkgmap:drawLevel=02 } [0x10302 resolution 18]

but you only need one of the mkgmap:drawLevel for the fairway to be
written after/overwrite the riverbank. Which you use depends on what
you want the behaviour to be with other polygons sharing the same area.

Also, slightly confusing to have level and resolution in the same
style.

And the wrong thread.

Regards
Ticker
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[rheinskipper1000]

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
>>>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>>>>
>>>> ___
>>>> 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-tp5885434p5885635.html
>>> Sent from the Mkgmap Development mailing list archive at Nabble.com.
>>> ___
>>> mkgmap-dev mailing list
>>> 

>> mkgmap-dev@.org

>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>> 
>> 
>> ___
>> 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-tp5885434p5885999.html
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

___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[Gerd Petermann]

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
>   
> 
> 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
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
 ___
 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-tp5885434p5885635.html
>>> Sent from the Mkgmap Development mailing list archive at Nabble.com.
>>> ___
>>> mkgmap-dev mailing list
>>> 

>> mkgmap-dev@.org

>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>> 
>> 
>> ___
>> 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-tp5885434p5885999.html
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

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[Gerd Petermann]

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
  

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
 http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

>>> ___
>>> 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-tp5885434p5885635.html
>> Sent from the Mkgmap Development mailing list archive at Nabble.com.
>> ___
>> mkgmap-dev mailing list
>> 

> mkgmap-dev@.org

>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> 
> 
> ___
> 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-tp5885434p5885745.html
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

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[Andrzej Popowski]

Hi,

there are points 0x1001 in img and it looks correctly in BaseCamp. If I 
compile mp with mkgmap, then points 0x1001 becomes 0x1000 but map still 
works in BaseCamp.


--
Best regards,
Andrzej
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[Teemu Peltonen]

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

http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


___
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-tp5885434p5885635.html
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



___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[Gerd Petermann]

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

>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
> 
> ___
> 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-tp5885434p5885635.html
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

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[Teemu P]

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

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[Andrzej Popowski]

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@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[Gerd Petermann]

Hi Teemu,

I do not yet know why but it seems that it causes problems when you use type
0x1001 in the points file.
Either this type is not allowed or mkgmap does something wrong when it
encodes it for  the img format.

Gerd


Teemu Peltonen wrote
> Hi,
> 
> I have been creating Garmin map from Finnish national topographic 
> database and lately I updated the process to use mkgmap to convert OSM 
> PBF files to Garmin IMG. I have encountered a problem with Garmin PC 
> software showing blank tiles 
> (http://kartat.hylly.org/mkgmap/mkgmap2.png) and digging further i 
> discovered that there are extra points in IMG files on those tiles 
> http://kartat.hylly.org/mkgmap/mkgmap1.png. These points does not exist 
> in the source data (http://kartat.hylly.org/mkgmap/M431_osm.osm.pbf and 
> http://kartat.hylly.org/mkgmap/mkgmap3.png) nor are those Garmin types 
> referenced in any way in style files 
> (https://github.com/pailakka/mtk2garmin/tree/master/mtk2garmin_style).
> 
> Do you have any idea what I might be doing wrong, or any pointers which 
> way to look in mkgmap source is this happens to be some kind of bug in 
> mkgmap?
> 
> Best regards,
> 
> Teemu Peltonen
> 
> ___
> 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-tp5885434p5885615.html
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

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[Teemu Peltonen]

7.11.2016, 20:59, nwillink kirjoitti:

This is not a mkgmap error but clearly points to a type number Basecamp
objects to.
  


Perhaps your 0x30 in lines?



--
View this message in context: 
http://gis.19327.n8.nabble.com/Spurious-points-Basecamp-blank-tiles-tp5885434p5885528.html
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


0x30 types were problematic, but I tested that these artifacts are 
created without 0x30 lines. It looks like artifacts appear after I merge 
original OSM data to pbf files. Original custom pbf files converted from 
National Topographic Database GML has node/way/relations ids starting 
from 50. Merged OSM data naturally has much smaller ids. I'm 
thinking this could have something to do with this problem.



-Teemu

___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

[nwillink]

This is not a mkgmap error but clearly points to a type number Basecamp
objects to.
 

Perhaps your 0x30 in lines?



--
View this message in context: 
http://gis.19327.n8.nabble.com/Spurious-points-Basecamp-blank-tiles-tp5885434p5885528.html
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

[mkgmap-dev] Spurious points & Basecamp blank tiles

[Teemu Peltonen]

Hi,

I have been creating Garmin map from Finnish national topographic 
database and lately I updated the process to use mkgmap to convert OSM 
PBF files to Garmin IMG. I have encountered a problem with Garmin PC 
software showing blank tiles 
(http://kartat.hylly.org/mkgmap/mkgmap2.png) and digging further i 
discovered that there are extra points in IMG files on those tiles 
http://kartat.hylly.org/mkgmap/mkgmap1.png. These points does not exist 
in the source data (http://kartat.hylly.org/mkgmap/M431_osm.osm.pbf and 
http://kartat.hylly.org/mkgmap/mkgmap3.png) nor are those Garmin types 
referenced in any way in style files 
(https://github.com/pailakka/mtk2garmin/tree/master/mtk2garmin_style).


Do you have any idea what I might be doing wrong, or any pointers which 
way to look in mkgmap source is this happens to be some kind of bug in 
mkgmap?


Best regards,

Teemu Peltonen

___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev