[mkgmap-dev] POI (point) resolution problem

Wed Feb 17 10:15:46 GMT 2016

Hi Alexandre,

okay, thanks for the info.

Gerd

________________________________
Von: mkgmap-dev-bounces at lists.mkgmap.org.uk <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Alexandre Loss <alexandre.loss at gmail.com>
Gesendet: Mittwoch, 17. Februar 2016 10:27
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] POI (point) resolution problem

Hi Gerd,

I'm slow to answer you because I'm unable to reproduce the problem with the cGPSmapper. I mean that I'm getting the same behavior (problem) in resolution of Hospitals and Police in maps compiled with mkgmap e cgpsmapper. Which leads me to believe that Thorsten was right in saying that this behavior was normal. Perhaps it is I who hadn't  seen that cGPSmapper behaved this way before.

So I thank you and Thorsten for your attention and if someday I can replicate the problem I return it.

Regards,

Alexandre

2016-02-15 4:15 GMT-02:00 Gerd Petermann <GPetermann_muenchen at hotmail.com<mailto:GPetermann_muenchen at hotmail.com>>:

Hi Alexandre,

okay, I was able to reproduce the problem, but I think that mkgmap writes correct data,

GPSMapEdit seems to confirm this. Please post a link to the files produced with cGPSmapper

and the sources for it. Maybe there is a bit flag that controls this behaviour.

Gerd

________________________________
Von: mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk> <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk>> im Auftrag von Alexandre Loss <alexandre.loss at gmail.com<mailto:alexandre.loss at gmail.com>>
Gesendet: Sonntag, 14. Februar 2016 23:09
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] POI (point) resolution problem

Hi Gerd,

I done the 2xCtrl-G and the problem persist.

Recapping, I tested with default style to make sure to use the standard.
If you need examples, you can test with aeroway=airport (0x2f04) that  is one type of POI that works as expected (resolution is reflected in the img); and amenity=police (0x3001) which is one where change resolution in points file doesn't have any effect.

Alexandre

2016-02-14 19:06 GMT-02:00 Gerd Petermann <GPetermann_muenchen at hotmail.com<mailto:GPetermann_muenchen at hotmail.com>>:

Hi ALexandre,

okay, I'll try to reproduce the problem with the default style.

Did you make sure that you press 2xCtrl+G to flush the cache

in Mapsource after changing the map ?

Gerd

________________________________
Von: mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk> <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk>> im Auftrag von Alexandre Loss <alexandre.loss at gmail.com<mailto:alexandre.loss at gmail.com>>
Gesendet: Sonntag, 14. Februar 2016 22:00

An: Development list for mkgmap
Cc: Tracksource Adm Tec
Betreff: Re: [mkgmap-dev] POI (point) resolution problem

Hi Gerd,

I reported a problem where I was changing the resolution of a POI of type amenity:police in the style file point, and this change wasn't been reflected in the img file produced by mkgmap (it wasn't being shown in the expected zoom level).

Then Thorsten answered me that this is the normal behavior because some kind of Garmin code for POI are shown in fixed resolution or following specific rules depending of the device or software where the img map is installed. So, this means that don't care what resolution I configure in point, it will be ignored.

So, in my last mail I was saying that I disagree with Thorsten position, because when I was using cgpsmapper, I was able to change the resolution of these POI and they were correctly shown in Mapsource and many devices. I mean, if cgpsmapper was able the generate img files respecting the configured resolution, then probably, the fact of points configuration be ignored should be a mkgmap fault instead of a hardware/software environment rule.

Thanks,

Alexandre

2016-02-14 16:03 GMT-02:00 Gerd Petermann <GPetermann_muenchen at hotmail.com<mailto:GPetermann_muenchen at hotmail.com>>:

Hi Alexandre,

not sure what you mean here. Do you say that mkgmap produces wrong output

or do you miss an option that cGPSmapper provides?

Gerd

________________________________
Von: mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk> <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk>> im Auftrag von Alexandre Loss <alexandre.loss at gmail.com<mailto:alexandre.loss at gmail.com>>
Gesendet: Sonntag, 14. Februar 2016 13:39
An: Development list for mkgmap
Cc: Tracksource Adm Tec
Betreff: Re: [mkgmap-dev] POI (point) resolution problem

Hi Thorsten,

I beg to differ, but I still think this resolution problem is a deficiency in mkgmap because in cGPSmapper we got more control and freedom in the resolution setting of POIs, regardless of device or software.

Thanks.

Alexandre

---------- Forwarded message ----------
From: Thorsten Kukuk <kukuk at suse.de<mailto:kukuk at suse.de>>
Date: 2016-02-12 10:02 GMT-02:00
Subject: Re: [mkgmap-dev] POI (point) resolution problem
To: mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>

Hi,

On Fri, Feb 12, Alexandre Loss wrote:

> Hi guys,
>
> I have noticed that the resolution set in the styles' point file is not
> considered for some types of POI.
> I'm not sure if this behavior is my fault or a mkgmap bug and therefore I
> ask your help.

The resolution of POIs depend on the device/software you use to display
the map, not on the map itself. It's hardcoded in the devices and software.
You could only try to use another POI number.

  Thorsten

--
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20160217/38235014/attachment-0001.html>