date:20180111

Hi Andrzej,

yes, that looks strange. I've added option --show-profiles=1 to yours so that 
MapSource displays height
values even in those areas where hill shading is not working.
For all: The problem is near
N49.19004 E20.07117
Mapsource displays no hill shading at zoom 500m, the wrong area changes when 
you zoom in and out or press 2xStrg+G  to clear the cache.

Not sure if this is a problem in the DEM data or in the hill shading algo.
Will try to find out more tomorrow.

Gerd


Von: mkgmap-dev  im Auftrag von Andrzej 
Popowski 
Gesendet: Donnerstag, 11. Januar 2018 16:50:13
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] HGT - getElevation()

Hi Gerd,

I have uploaded at http://files.mkgmap.org.uk/ data for compilation,
which gives me a map with shading errors. Mkgmap version 4045.

--
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] --gmapi not in parameter list


Hi Henning,

I believe that Garmin uses a formula for these numbers. At least for 
older maps, City Navigator maps are different. It looks like that:


first_mapname = 0x606000 + 2048*family_id
overview_mapname = first_mapname + 2047

I don't think any program looks at overview mapname but GPS doesn't 
accept multiple tiles with the same mapname.


--
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] dem-poly and precomp-sea


Hi Gerd,

DEM shading is displayed only over background object 4B. If you clip 
background, than the effect is like clipping DEM too.


--
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] HGT - getElevation()


Hi Gerd,

I have uploaded at http://files.mkgmap.org.uk/ data for compilation, 
which gives me a map with shading errors. Mkgmap version 4045.


--
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] --gmapi not in parameter list

Hi Henning,

I agree that would be a better default, but I don't want to change it now as 
some scripts might depend on
the current behaviour.

Gerd


Von: mkgmap-dev  im Auftrag von Henning 
Scholland 
Gesendet: Donnerstag, 11. Januar 2018 14:44:00
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] --gmapi not in parameter list

Hi Gerd,
I was mainly confused because 6234 and 1005 both were used. I
would expect if ..number is unset, all files related to overview map are
names 6234.

Maybe --family-id with  in the end is a better default than 6234

Henning

On 11.01.2018 21:25, Gerd Petermann wrote:
> Hi Henning,
>
> yes, I also found this confusing when I added code for to write DEM for 
> overview map.
>
> Gerd
>
> 
> Von: mkgmap-dev  im Auftrag von 
> Henning Scholland 
> Gesendet: Donnerstag, 11. Januar 2018 14:22:24
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] --gmapi not in parameter list
>
> Hi Gerd,
> I'm using only --overview-mapname=%famid%. For 'standard'-img map
> file name is also set to 1005000.img
>
> Will add also ..number. Thanks for the hint.
> Henning
>
> On 11.01.2018 21:06, Gerd Petermann wrote:
>> Hi Henning,
>>
>> I'll add text to the doc and help.
>> You you set --overview-mapnumber ?
>>
>> Gerd
> ___
> 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
>

___
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] option --show-profiles and DEM

Hi Gerd,

Thanks , will keep you posted about any unusual findings.

Nick

On 11/01/2018 14:37, Gerd Petermann wrote:

Hi Nick,

see also
http://gis.19327.n8.nabble.com/r4006-1st-alpha-version-to-write-DEM-data-tp5908584p5908614.html
where I posted my findings.

Gerd

Von: mkgmap-dev im Auftrag von osm@pinns

Gesendet: Donnerstag, 11. Januar 2018 15:30:11
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM

Hi Gerd,

Superb ! Many thanks !

Nick

On 11/01/2018 14:29, Gerd Petermann wrote:

Hi Nick,

you need the program DemDisplay from the display tool, source is here:
https://svn.mkgmap.org.uk/svn/display/trunk
Binary is here:
http://files.mkgmap.org.uk/download/386/display.jar

Usage on a windows machine :
java -cp d:\display\dist\display.jar;d:\mkgmap\dist\mkgmap.jar
test.display.DemDisplay [--verbose] input-file > dem.txt
(adapt the paths, I think on linux you need : instead of ; as a separator)
input-file can be *.DEM or *.IMG containing a dem file.

The values are displayed in the "DEM sector header" as "map units between points
(latitude):" and "map units between points (longitude)"

Gerd

Von: mkgmap-dev im Auftrag von osm@pinns

Gesendet: Donnerstag, 11. Januar 2018 15:16:18
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM

Hi Gerd,

Interesting ; some time ago , you mentioned that you were able to
extract these values from the dem file structure.

Are they set in the headers? If so where so I can check some of the TOPO's

I'm having a problem with my gps64 , not the oregons, where I find its
better to opt for a higher starting distance , ie 6628 for 1''

Nick

On 11/01/2018 14:10, Gerd Petermann wrote:

Hi Nick,

I also wondered why Garmin prefers 3312 while 3314 looks the exacter value.
Found no explanation so far.

Gerd

Von: mkgmap-dev im Auftrag von osm@pinns

Gesendet: Donnerstag, 11. Januar 2018 15:04:32
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM

Hi Gerd

should 3312 logically be 3314 (2^32/(360*3600)) ?

Not that it matters much.

Nick

On 11/01/2018 13:48, Gerd Petermann wrote:

Hi Andreas,

you are right, thanks for the hint. I took those from the transalpin demo map,
but the last two levels are empty.
So, r4045 now says
Example which should work with levels="0:24, 1:22, 2:20, 3:18":
--dem-dists=3312,13248,26512,53024

Gerd

Von: mkgmap-dev im Auftrag von
andreas.schmidt.hetschb...@t-online.de
Gesendet: Donnerstag, 11. Januar 2018 14:38:24
An: Development list for mkgmap
Betreff: [mkgmap-dev] option --show-profiles and DEM

Hi Gerd,

I got a bit confused when I read the doc/example

--dem-dists=number[,number]
If given, the option specifies the resolution(s) or zoom level for the DEM
data. If not given, mkgmap tries to determine a reasonable value based on the
resolution found in the *.hgt files. For PC programs like MapSource or Basecamp
you only need one zoom level, for gps devies you need one for each resolution
given with the --levels option. The actual values are given as distance between
two DEM points. Higher disances mean lower resolution and thus fewer bytes in
the map. Reasonable values for the highest resolution are somewhere between
1648 and 5520, 3312 is often used.
Example which should work with levels="0:24, 1:22, 2:20, 3:18, 4:16":
--dem-dists=3312,13248,26512,53024
This was found in a Garmin Demo map for transalpin data created 2009.

There are only 4 values for –dem-dist ,although there are 5 „Levels“.
This seems to be in contrast to „…for gps devies you need one for each
resolution given with the --levels Option ?

Regards

Andreas

Gesendet von Mail für Windows 10

Von: Henning Scholland
Gesendet: Donnerstag, 11. Januar 2018 12:55
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM

Hi all,

I don't see a reason to have this option at all. It should be set
automatically to 1 if either contour data or DEM is written. If this
data is in the map, you always want to have it and if those are not in
the map, you don't need it. Or am I wrong?

Henning
___
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

Re: [mkgmap-dev] option --show-profiles and DEM

Hi Nick,

see also
http://gis.19327.n8.nabble.com/r4006-1st-alpha-version-to-write-DEM-data-tp5908584p5908614.html
where I posted my findings.

Gerd


Von: mkgmap-dev  im Auftrag von 
osm@pinns 
Gesendet: Donnerstag, 11. Januar 2018 15:30:11
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM

Hi Gerd,

Superb ! Many thanks !

Nick


On 11/01/2018 14:29, Gerd Petermann wrote:
> Hi Nick,
>
> you need the program DemDisplay from the display tool, source is here:
> https://svn.mkgmap.org.uk/svn/display/trunk
> Binary is here:
> http://files.mkgmap.org.uk/download/386/display.jar
>
> Usage on a windows machine :
>   java -cp d:\display\dist\display.jar;d:\mkgmap\dist\mkgmap.jar 
> test.display.DemDisplay [--verbose] input-file > dem.txt
> (adapt the paths, I think on linux you need : instead of ; as a separator)
> input-file can be *.DEM or *.IMG containing a dem file.
>
> The values are displayed in the "DEM sector header" as "map units between 
> points (latitude):"  and "map units between points (longitude)"
>
> Gerd
>
>
> 
> Von: mkgmap-dev  im Auftrag von 
> osm@pinns 
> Gesendet: Donnerstag, 11. Januar 2018 15:16:18
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] option --show-profiles and DEM
>
> Hi Gerd,
>
> Interesting ; some time ago , you mentioned that you were able to
> extract these values from the dem file structure.
>
> Are they set in the headers? If so where so I can check some of the TOPO's
>
> I'm having a problem with my gps64 , not the oregons, where I find its
> better to opt for a higher starting distance , ie 6628 for 1''
>
> Nick
>
>
>
> On 11/01/2018 14:10, Gerd Petermann wrote:
>> Hi Nick,
>>
>> I also wondered why Garmin prefers 3312 while 3314 looks the exacter value.
>> Found no explanation so far.
>>
>> Gerd
>>
>> 
>> Von: mkgmap-dev  im Auftrag von 
>> osm@pinns 
>> Gesendet: Donnerstag, 11. Januar 2018 15:04:32
>> An: mkgmap-dev@lists.mkgmap.org.uk
>> Betreff: Re: [mkgmap-dev] option --show-profiles and DEM
>>
>> Hi Gerd
>>
>> should 3312 logically  be 3314 (2^32/(360*3600))  ?
>>
>> Not that it matters much.
>>
>> r
>>
>> Nick
>>
>>
>> On 11/01/2018 13:48, Gerd Petermann wrote:
>>> Hi Andreas,
>>>
>>> you are right, thanks for the hint. I took those from the transalpin demo 
>>> map, but the last two levels are empty.
>>> So, r4045 now says
>>>Example which should work with levels="0:24, 1:22, 2:20, 3:18":
>>>--dem-dists=3312,13248,26512,53024
>>>
>>> Gerd
>>>
>>> 
>>> Von: mkgmap-dev  im Auftrag von 
>>> andreas.schmidt.hetschb...@t-online.de 
>>> 
>>> Gesendet: Donnerstag, 11. Januar 2018 14:38:24
>>> An: Development list for mkgmap
>>> Betreff: [mkgmap-dev]  option --show-profiles and DEM
>>>
>>> Hi Gerd,
>>>
>>> I got a bit confused when I read  the doc/example
>>>
>>> --dem-dists=number[,number]
>>> If given, the option specifies the resolution(s) or zoom level for the DEM 
>>> data. If not given, mkgmap tries to determine a reasonable value based on 
>>> the resolution found in the *.hgt files. For PC programs like MapSource or 
>>> Basecamp you only need one zoom level, for gps devies you need one for each 
>>> resolution given with the --levels option. The actual values are given as 
>>> distance between two DEM points. Higher disances mean lower resolution and 
>>> thus fewer bytes in the map. Reasonable values for the highest resolution 
>>> are somewhere between 1648 and 5520, 3312 is often used.
>>> Example which should work with levels="0:24, 1:22, 2:20, 3:18, 4:16":
>>> --dem-dists=3312,13248,26512,53024
>>> This was found in a Garmin Demo map for transalpin data created 2009.
>>>
>>> There are only 4 values for –dem-dist ,although there are 5 „Levels“.
>>> This seems to be  in contrast to „…for gps devies you need one for each 
>>> resolution given with the --levels Option ?
>>>
>>> Regards
>>>
>>> Andreas
>>>
>>> Gesendet von Mail für 
>>> Windows 10
>>>
>>> Von: Henning Scholland
>>> Gesendet: Donnerstag, 11. Januar 2018 12:55
>>> An: mkgmap-dev@lists.mkgmap.org.uk
>>> Betreff: Re: [mkgmap-dev] option --show-profiles and DEM
>>>
>>>
>>> Hi all,
>>>
>>> I don't see a reason to have this option at all. It should be set
>>> automatically to 1 if either contour data or DEM is written. If this
>>> data is in the map, you always want to have it and if those are not in
>>> the map, you don't need it. Or am I wrong?
>>>
>>> Henning
>>>

Re: [mkgmap-dev] option --show-profiles and DEM


Hi Gerd,

Superb ! Many thanks !

Nick


On 11/01/2018 14:29, Gerd Petermann wrote:

Hi Nick,

you need the program DemDisplay from the display tool, source is here:
https://svn.mkgmap.org.uk/svn/display/trunk
Binary is here:
http://files.mkgmap.org.uk/download/386/display.jar

Usage on a windows machine :
  java -cp d:\display\dist\display.jar;d:\mkgmap\dist\mkgmap.jar 
test.display.DemDisplay [--verbose] input-file > dem.txt
(adapt the paths, I think on linux you need : instead of ; as a separator)
input-file can be *.DEM or *.IMG containing a dem file.

The values are displayed in the "DEM sector header" as "map units between points 
(latitude):"  and "map units between points (longitude)"

Gerd



Von: mkgmap-dev  im Auftrag von osm@pinns 

Gesendet: Donnerstag, 11. Januar 2018 15:16:18
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM

Hi Gerd,

Interesting ; some time ago , you mentioned that you were able to
extract these values from the dem file structure.

Are they set in the headers? If so where so I can check some of the TOPO's

I'm having a problem with my gps64 , not the oregons, where I find its
better to opt for a higher starting distance , ie 6628 for 1''

Nick



On 11/01/2018 14:10, Gerd Petermann wrote:

Hi Nick,

I also wondered why Garmin prefers 3312 while 3314 looks the exacter value.
Found no explanation so far.

Gerd


Von: mkgmap-dev  im Auftrag von osm@pinns 

Gesendet: Donnerstag, 11. Januar 2018 15:04:32
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM

Hi Gerd

should 3312 logically  be 3314 (2^32/(360*3600))  ?

Not that it matters much.

r

Nick


On 11/01/2018 13:48, Gerd Petermann wrote:

Hi Andreas,

you are right, thanks for the hint. I took those from the transalpin demo map, 
but the last two levels are empty.
So, r4045 now says
   Example which should work with levels="0:24, 1:22, 2:20, 3:18":
   --dem-dists=3312,13248,26512,53024

Gerd


Von: mkgmap-dev  im Auftrag von 
andreas.schmidt.hetschb...@t-online.de 
Gesendet: Donnerstag, 11. Januar 2018 14:38:24
An: Development list for mkgmap
Betreff: [mkgmap-dev]  option --show-profiles and DEM

Hi Gerd,

I got a bit confused when I read  the doc/example

--dem-dists=number[,number]
If given, the option specifies the resolution(s) or zoom level for the DEM 
data. If not given, mkgmap tries to determine a reasonable value based on the 
resolution found in the *.hgt files. For PC programs like MapSource or Basecamp 
you only need one zoom level, for gps devies you need one for each resolution 
given with the --levels option. The actual values are given as distance between 
two DEM points. Higher disances mean lower resolution and thus fewer bytes in 
the map. Reasonable values for the highest resolution are somewhere between 
1648 and 5520, 3312 is often used.
Example which should work with levels="0:24, 1:22, 2:20, 3:18, 4:16":
--dem-dists=3312,13248,26512,53024
This was found in a Garmin Demo map for transalpin data created 2009.

There are only 4 values for –dem-dist ,although there are 5 „Levels“.
This seems to be  in contrast to „…for gps devies you need one for each 
resolution given with the --levels Option ?

Regards

Andreas

Gesendet von Mail für Windows 10

Von: Henning Scholland
Gesendet: Donnerstag, 11. Januar 2018 12:55
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM


Hi all,

I don't see a reason to have this option at all. It should be set
automatically to 1 if either contour data or DEM is written. If this
data is in the map, you always want to have it and if those are not in
the map, you don't need it. Or am I wrong?

Henning
___
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

___
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

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

Re: [mkgmap-dev] option --show-profiles and DEM

Hi Nick,

you need the program DemDisplay from the display tool, source is here:
https://svn.mkgmap.org.uk/svn/display/trunk
Binary is here:
http://files.mkgmap.org.uk/download/386/display.jar

Usage on a windows machine :
 java -cp d:\display\dist\display.jar;d:\mkgmap\dist\mkgmap.jar 
test.display.DemDisplay [--verbose] input-file > dem.txt
(adapt the paths, I think on linux you need : instead of ; as a separator)
input-file can be *.DEM or *.IMG containing a dem file.

The values are displayed in the "DEM sector header" as "map units between 
points (latitude):"  and "map units between points (longitude)"

Gerd



Von: mkgmap-dev  im Auftrag von 
osm@pinns 
Gesendet: Donnerstag, 11. Januar 2018 15:16:18
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM

Hi Gerd,

Interesting ; some time ago , you mentioned that you were able to
extract these values from the dem file structure.

Are they set in the headers? If so where so I can check some of the TOPO's

I'm having a problem with my gps64 , not the oregons, where I find its
better to opt for a higher starting distance , ie 6628 for 1''

Nick



On 11/01/2018 14:10, Gerd Petermann wrote:
> Hi Nick,
>
> I also wondered why Garmin prefers 3312 while 3314 looks the exacter value.
> Found no explanation so far.
>
> Gerd
>
> 
> Von: mkgmap-dev  im Auftrag von 
> osm@pinns 
> Gesendet: Donnerstag, 11. Januar 2018 15:04:32
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] option --show-profiles and DEM
>
> Hi Gerd
>
> should 3312 logically  be 3314 (2^32/(360*3600))  ?
>
> Not that it matters much.
>
> r
>
> Nick
>
>
> On 11/01/2018 13:48, Gerd Petermann wrote:
>> Hi Andreas,
>>
>> you are right, thanks for the hint. I took those from the transalpin demo 
>> map, but the last two levels are empty.
>> So, r4045 now says
>>   Example which should work with levels="0:24, 1:22, 2:20, 3:18":
>>   --dem-dists=3312,13248,26512,53024
>>
>> Gerd
>>
>> 
>> Von: mkgmap-dev  im Auftrag von 
>> andreas.schmidt.hetschb...@t-online.de 
>> 
>> Gesendet: Donnerstag, 11. Januar 2018 14:38:24
>> An: Development list for mkgmap
>> Betreff: [mkgmap-dev]  option --show-profiles and DEM
>>
>> Hi Gerd,
>>
>> I got a bit confused when I read  the doc/example
>>
>> --dem-dists=number[,number]
>> If given, the option specifies the resolution(s) or zoom level for the DEM 
>> data. If not given, mkgmap tries to determine a reasonable value based on 
>> the resolution found in the *.hgt files. For PC programs like MapSource or 
>> Basecamp you only need one zoom level, for gps devies you need one for each 
>> resolution given with the --levels option. The actual values are given as 
>> distance between two DEM points. Higher disances mean lower resolution and 
>> thus fewer bytes in the map. Reasonable values for the highest resolution 
>> are somewhere between 1648 and 5520, 3312 is often used.
>> Example which should work with levels="0:24, 1:22, 2:20, 3:18, 4:16":
>> --dem-dists=3312,13248,26512,53024
>> This was found in a Garmin Demo map for transalpin data created 2009.
>>
>> There are only 4 values for –dem-dist ,although there are 5 „Levels“.
>> This seems to be  in contrast to „…for gps devies you need one for each 
>> resolution given with the --levels Option ?
>>
>> Regards
>>
>> Andreas
>>
>> Gesendet von Mail für 
>> Windows 10
>>
>> Von: Henning Scholland
>> Gesendet: Donnerstag, 11. Januar 2018 12:55
>> An: mkgmap-dev@lists.mkgmap.org.uk
>> Betreff: Re: [mkgmap-dev] option --show-profiles and DEM
>>
>>
>> Hi all,
>>
>> I don't see a reason to have this option at all. It should be set
>> automatically to 1 if either contour data or DEM is written. If this
>> data is in the map, you always want to have it and if those are not in
>> the map, you don't need it. Or am I wrong?
>>
>> Henning
>> ___
>> 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
> ___
> 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] option --show-profiles and DEM


Hi Gerd,

Interesting ; some time ago , you mentioned that you were able to 
extract these values from the dem file structure.


Are they set in the headers? If so where so I can check some of the TOPO's

I'm having a problem with my gps64 , not the oregons, where I find its 
better to opt for a higher starting distance , ie 6628 for 1''


Nick



On 11/01/2018 14:10, Gerd Petermann wrote:

Hi Nick,

I also wondered why Garmin prefers 3312 while 3314 looks the exacter value.
Found no explanation so far.

Gerd


Von: mkgmap-dev  im Auftrag von osm@pinns 

Gesendet: Donnerstag, 11. Januar 2018 15:04:32
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM

Hi Gerd

should 3312 logically  be 3314 (2^32/(360*3600))  ?

Not that it matters much.

r

Nick


On 11/01/2018 13:48, Gerd Petermann wrote:

Hi Andreas,

you are right, thanks for the hint. I took those from the transalpin demo map, 
but the last two levels are empty.
So, r4045 now says
  Example which should work with levels="0:24, 1:22, 2:20, 3:18":
  --dem-dists=3312,13248,26512,53024

Gerd


Von: mkgmap-dev  im Auftrag von 
andreas.schmidt.hetschb...@t-online.de 
Gesendet: Donnerstag, 11. Januar 2018 14:38:24
An: Development list for mkgmap
Betreff: [mkgmap-dev]  option --show-profiles and DEM

Hi Gerd,

I got a bit confused when I read  the doc/example

--dem-dists=number[,number]
If given, the option specifies the resolution(s) or zoom level for the DEM 
data. If not given, mkgmap tries to determine a reasonable value based on the 
resolution found in the *.hgt files. For PC programs like MapSource or Basecamp 
you only need one zoom level, for gps devies you need one for each resolution 
given with the --levels option. The actual values are given as distance between 
two DEM points. Higher disances mean lower resolution and thus fewer bytes in 
the map. Reasonable values for the highest resolution are somewhere between 
1648 and 5520, 3312 is often used.
Example which should work with levels="0:24, 1:22, 2:20, 3:18, 4:16":
--dem-dists=3312,13248,26512,53024
This was found in a Garmin Demo map for transalpin data created 2009.

There are only 4 values for –dem-dist ,although there are 5 „Levels“.
This seems to be  in contrast to „…for gps devies you need one for each 
resolution given with the --levels Option ?

Regards

Andreas

Gesendet von Mail für Windows 10

Von: Henning Scholland
Gesendet: Donnerstag, 11. Januar 2018 12:55
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM


Hi all,

I don't see a reason to have this option at all. It should be set
automatically to 1 if either contour data or DEM is written. If this
data is in the map, you always want to have it and if those are not in
the map, you don't need it. Or am I wrong?

Henning
___
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

___
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


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

Re: [mkgmap-dev] option --show-profiles and DEM

Hi Nick,

I also wondered why Garmin prefers 3312 while 3314 looks the exacter value.
Found no explanation so far.

Gerd


Von: mkgmap-dev  im Auftrag von 
osm@pinns 
Gesendet: Donnerstag, 11. Januar 2018 15:04:32
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM

Hi Gerd

should 3312 logically  be 3314 (2^32/(360*3600))  ?

Not that it matters much.

r

Nick


On 11/01/2018 13:48, Gerd Petermann wrote:
> Hi Andreas,
>
> you are right, thanks for the hint. I took those from the transalpin demo 
> map, but the last two levels are empty.
> So, r4045 now says
>  Example which should work with levels="0:24, 1:22, 2:20, 3:18":
>  --dem-dists=3312,13248,26512,53024
>
> Gerd
>
> 
> Von: mkgmap-dev  im Auftrag von 
> andreas.schmidt.hetschb...@t-online.de 
> 
> Gesendet: Donnerstag, 11. Januar 2018 14:38:24
> An: Development list for mkgmap
> Betreff: [mkgmap-dev]  option --show-profiles and DEM
>
> Hi Gerd,
>
> I got a bit confused when I read  the doc/example
>
> --dem-dists=number[,number]
> If given, the option specifies the resolution(s) or zoom level for the DEM 
> data. If not given, mkgmap tries to determine a reasonable value based on the 
> resolution found in the *.hgt files. For PC programs like MapSource or 
> Basecamp you only need one zoom level, for gps devies you need one for each 
> resolution given with the --levels option. The actual values are given as 
> distance between two DEM points. Higher disances mean lower resolution and 
> thus fewer bytes in the map. Reasonable values for the highest resolution are 
> somewhere between 1648 and 5520, 3312 is often used.
> Example which should work with levels="0:24, 1:22, 2:20, 3:18, 4:16":
> --dem-dists=3312,13248,26512,53024
> This was found in a Garmin Demo map for transalpin data created 2009.
>
> There are only 4 values for –dem-dist ,although there are 5 „Levels“.
> This seems to be  in contrast to „…for gps devies you need one for each 
> resolution given with the --levels Option ?
>
> Regards
>
> Andreas
>
> Gesendet von Mail für Windows 
> 10
>
> Von: Henning Scholland
> Gesendet: Donnerstag, 11. Januar 2018 12:55
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] option --show-profiles and DEM
>
>
> Hi all,
>
> I don't see a reason to have this option at all. It should be set
> automatically to 1 if either contour data or DEM is written. If this
> data is in the map, you always want to have it and if those are not in
> the map, you don't need it. Or am I wrong?
>
> Henning
> ___
> 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

___
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] option --show-profiles and DEM


Hi Gerd

should 3312 logically  be 3314 (2^32/(360*3600))  ?

Not that it matters much.

r

Nick


On 11/01/2018 13:48, Gerd Petermann wrote:

Hi Andreas,

you are right, thanks for the hint. I took those from the transalpin demo map, 
but the last two levels are empty.
So, r4045 now says
 Example which should work with levels="0:24, 1:22, 2:20, 3:18":
 --dem-dists=3312,13248,26512,53024

Gerd


Von: mkgmap-dev  im Auftrag von 
andreas.schmidt.hetschb...@t-online.de 
Gesendet: Donnerstag, 11. Januar 2018 14:38:24
An: Development list for mkgmap
Betreff: [mkgmap-dev]  option --show-profiles and DEM

Hi Gerd,

I got a bit confused when I read  the doc/example

--dem-dists=number[,number]
If given, the option specifies the resolution(s) or zoom level for the DEM 
data. If not given, mkgmap tries to determine a reasonable value based on the 
resolution found in the *.hgt files. For PC programs like MapSource or Basecamp 
you only need one zoom level, for gps devies you need one for each resolution 
given with the --levels option. The actual values are given as distance between 
two DEM points. Higher disances mean lower resolution and thus fewer bytes in 
the map. Reasonable values for the highest resolution are somewhere between 
1648 and 5520, 3312 is often used.
Example which should work with levels="0:24, 1:22, 2:20, 3:18, 4:16":
--dem-dists=3312,13248,26512,53024
This was found in a Garmin Demo map for transalpin data created 2009.

There are only 4 values for –dem-dist ,although there are 5 „Levels“.
This seems to be  in contrast to „…for gps devies you need one for each 
resolution given with the --levels Option ?

Regards

Andreas

Gesendet von Mail für Windows 10

Von: Henning Scholland
Gesendet: Donnerstag, 11. Januar 2018 12:55
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM


Hi all,

I don't see a reason to have this option at all. It should be set
automatically to 1 if either contour data or DEM is written. If this
data is in the map, you always want to have it and if those are not in
the map, you don't need it. Or am I wrong?

Henning
___
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


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

Re: [mkgmap-dev] option --show-profiles and DEM

Hi Andreas,

you are right, thanks for the hint. I took those from the transalpin demo map, 
but the last two levels are empty.
So, r4045 now says
Example which should work with levels="0:24, 1:22, 2:20, 3:18":
--dem-dists=3312,13248,26512,53024

Gerd


Von: mkgmap-dev  im Auftrag von 
andreas.schmidt.hetschb...@t-online.de 
Gesendet: Donnerstag, 11. Januar 2018 14:38:24
An: Development list for mkgmap
Betreff: [mkgmap-dev]  option --show-profiles and DEM

Hi Gerd,

I got a bit confused when I read  the doc/example

--dem-dists=number[,number]
If given, the option specifies the resolution(s) or zoom level for the DEM 
data. If not given, mkgmap tries to determine a reasonable value based on the 
resolution found in the *.hgt files. For PC programs like MapSource or Basecamp 
you only need one zoom level, for gps devies you need one for each resolution 
given with the --levels option. The actual values are given as distance between 
two DEM points. Higher disances mean lower resolution and thus fewer bytes in 
the map. Reasonable values for the highest resolution are somewhere between 
1648 and 5520, 3312 is often used.
Example which should work with levels="0:24, 1:22, 2:20, 3:18, 4:16":
--dem-dists=3312,13248,26512,53024
This was found in a Garmin Demo map for transalpin data created 2009.

There are only 4 values for –dem-dist ,although there are 5 „Levels“.
This seems to be  in contrast to „…for gps devies you need one for each 
resolution given with the --levels Option ?

Regards

Andreas

Gesendet von Mail für Windows 10

Von: Henning Scholland
Gesendet: Donnerstag, 11. Januar 2018 12:55
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM


Hi all,

I don't see a reason to have this option at all. It should be set
automatically to 1 if either contour data or DEM is written. If this
data is in the map, you always want to have it and if those are not in
the map, you don't need it. Or am I wrong?

Henning
___
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

[mkgmap-dev] r4044: changes in doc and help

Hi all,

the discussion about show-profiles got a bit confused, so I've now committed my 
current knowledge.
Please review 
http://www.mkgmap.org.uk/websvn/diff.php?repname=mkgmap=%2Fbranches%2Fdem-tdb%2Fresources%2Fhelp%2Fen%2Foptions=4044=4044

BTW:
I found no problem with a map without DEM and without contour lines created 
with show-profiles=1. The button "Show profile..." is disabled in MapSource and 
Basecamp says 
"The current map does not contain any elevation data on the selected route(s)"
Don't know if the false flag costs time when Mapsource/Basecamp try to find 
data that doesn't exist.

Gerd



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

[mkgmap-dev] option --show-profiles and DEM

2018-01-11 Thread andreas . schmidt . hetschbach

Hi Gerd, I got a bit confused when I read the doc/example --dem-dists=number[,number]If given, the option specifies the resolution(s) or zoom level for the DEM data. If not given, mkgmap tries to determine a reasonable value based on the resolution found in the *.hgt files. For PC programs like MapSource or Basecamp you only need one zoom level, for gps devies you need one for each resolution given with the --levels option. The actual values are given as distance between two DEM points. Higher disances mean lower resolution and thus fewer bytes in the map. Reasonable values for the highest resolution are somewhere between 1648 and 5520, 3312 is often used.Example which should work with levels="0:24, 1:22, 2:20, 3:18, 4:16":--dem-dists=3312,13248,26512,53024This was found in a Garmin Demo map for transalpin data created 2009. There are only 4 values for –dem-dist ,although there are 5 „Levels“. This seems to be in contrast to „…for gps devies you need one for each resolution given with the --levels Option ? Regards Andreas Gesendet von Mail für Windows 10 Von: Henning SchollandGesendet: Donnerstag, 11. Januar 2018 12:55An: mkgmap-dev@lists.mkgmap.org.ukBetreff: Re: [mkgmap-dev] option --show-profiles and DEM Hi all,I don't see a reason to have this option at all. It should be setautomatically to 1 if either contour data or DEM is written. If thisdata is in the map, you always want to have it and if those are not inthe map, you don't need it. Or am I wrong?Henning___mkgmap-dev mailing listmkgmap-dev@lists.mkgmap.org.ukhttp://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] --gmapi not in parameter list

Hi Henning,

yes, I also found this confusing when I added code for to write DEM for 
overview map.

Gerd

Von: mkgmap-dev  im Auftrag von Henning 
Scholland 
Gesendet: Donnerstag, 11. Januar 2018 14:22:24
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] --gmapi not in parameter list

Hi Gerd,
I'm using only --overview-mapname=%famid%. For 'standard'-img map
file name is also set to 1005000.img

Will add also ..number. Thanks for the hint.
Henning

On 11.01.2018 21:06, Gerd Petermann wrote:
> Hi Henning,
>
> I'll add text to the doc and help.
> You you set --overview-mapnumber ?
>
> Gerd
___
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] --gmapi not in parameter list

Hi Gerd,
I'm using only --overview-mapname=%famid%. For 'standard'-img map
file name is also set to 1005000.img

Will add also ..number. Thanks for the hint.
Henning

On 11.01.2018 21:06, Gerd Petermann wrote:
> Hi Henning,
>
> I'll add text to the doc and help.
> You you set --overview-mapnumber ?
>
> Gerd
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] --gmapi not in parameter list

Hi Henning,

I'll add text to the doc and help.
You you set --overview-mapnumber ?

Gerd


Von: mkgmap-dev  im Auftrag von Henning 
Scholland 
Gesendet: Donnerstag, 11. Januar 2018 13:40:24
An: Development list for mkgmap
Betreff: [mkgmap-dev] --gmapi not in parameter list

Hi,

is there a reason for not listing --gmapi in the documentation (at least on 
website)? Description can be simply:

Outputs map in gmap-format.

Btw: In overview map DEM, LBL, RGN and TRE don't follow map-id based file name, 
but using 6234. In my case it should be 1005. NET and NOD and all map 
tiles are fine.

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

Re: [mkgmap-dev] dem-poly and precomp-sea

Hi Gerd,
I like the idea to have somehow a map polygone limiting or extending the
'background'-map (means DEM, sea, background poly). How about --map-polygon?

So if I got it right, this develloping will end in non-rectangle shaped
map tiles?
Henning

On 10.01.2018 16:54, Gerd Petermann wrote:
> Hi all,
>
> I think that the bounding polygon given with option --dem-poly should be also 
> be used in the precomp-sea option,
> so that mkgmap doesn't generate sea polygons outside of the bounding polygon. 
> With the current code a map of e.g.
> scandinavia looks strange, see attached picture.
>
> In a further step I should try to use that polygon also for the background 
> polygon (0x4B) and other data.
> In a final step we might be able to use it for routing data so that you can 
> split maps at left-driving / right-driving boundaries,
> but that needs more thinking.
>
> I've not coded anything yet, but I wonder if the option should be changed 
> from dem-poly to e.g. --polygon-file or --bounding-polygon.
>
> Gerd
>
>
> ___
> 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] option --show-profiles and DEM

2018-01-11 Thread Bernd Weigelt

Am Donnerstag, 11. Januar 2018, 12:55:09 CET schrieb Henning Scholland:
> I don't see a reason to have this option at all. It should be set
> automatically to 1 if either contour data or DEM is written. If this
> data is in the map, you always want to have it and if those are not in
> the map, you don't need it. Or am I wrong?

I think you're right.

I didn't use this option in the past, today enabled it for testing, but in 
mapsource and Basecamp the elevation data are visible.

Bernd

signature.asc
Description: This is a digitally signed message part.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] --gmapi not in parameter list

Hi,

is there a reason for not listing --gmapi in the documentation (at least
on website)? Description can be simply:

Outputs map in gmap-format.

Btw: In overview map DEM, LBL, RGN and TRE don't follow map-id based
file name, but using 6234. In my case it should be 1005. NET and
NOD and all map tiles are fine.

Henning

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

Re: [mkgmap-dev] option --show-profiles and DEM

Also without show-profiles=1 MapSource and BaseCamp don't use DEM for
elevation of waypoints. Basically it's only used for routing and showing
the shades.

Henning

On 11.01.2018 17:52, lig fietser wrote:
>
> --show-profiles=1
>     Sets a flag in tdb file which enables profile calculation in
> MapSource or
>     Basecamp based on contour lines.
>
>
> No, if show-profiles = 1 and DEM data is present, the profile is
> calculated from the DEM data and *not* from the contour lines
>
>
> If DEM data (see "Hill Shading (DEM) options") is available the flag 
> changes the status line to show the height when you hover over an area
> with  valid DEM data.
>
>
> Agree
>
> Maybe add a remark that if show-profiles = 0 and DEM data is present,
> an elevation profile is always  available?
>
>

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

Re: [mkgmap-dev] option --show-profiles and DEM

Hi all,

I don't see a reason to have this option at all. It should be set
automatically to 1 if either contour data or DEM is written. If this
data is in the map, you always want to have it and if those are not in
the map, you don't need it. Or am I wrong?

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

Re: [mkgmap-dev] option --show-profiles and DEM


Hi Gerd,

I think, I have already mentioned it. There are 2 flags written in TDB: 
"enableProfile" and "hasDem". CGPSmapper supports option for profiles, 
but it sets flag "hasDem" for it and surely it works with contours.


Garmin maps usually include contours and DEM together, and then both 
flags are set. I have no access to Garmin map that has only one of this 
features, so I can't tell exact meaning of flags.


Some years ago I tested various maps with DEM and some methods to 
include DEM to free maps. I don't remember what I did, but the 
conclusion is still present in code of GMapTool. It uses reversed 
meaning of flags comparing to mkgmap.


--
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] option --show-profiles and DEM

Sounds good Gerd, plus mention that 0 is default?


Van: mkgmap-dev  namens Gerd Petermann 

Verzonden: donderdag 11 januari 2018 02:07:39
Aan: Development list for mkgmap
Onderwerp: Re: [mkgmap-dev] option --show-profiles and DEM

Next try:
--show-profiles=1
Sets a flag in tdb file. The meaning depends on the availability of DEM
data (see "Hill Shading (DEM) options").
Without DEM data the flag enables profile calculation in MapSource or
Basecamp based on information from contour lines.
If DEM data is available the profile is calculated with that 
information and
the flag only changes the status line to show the height when you hover 
over
an area with valid DEM data.

OK?
Gerd


Von: mkgmap-dev  im Auftrag von lig 
fietser 
Gesendet: Donnerstag, 11. Januar 2018 10:52:29
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM

--show-profiles=1
Sets a flag in tdb file which enables profile calculation in MapSource 
or
Basecamp based on contour lines.


No, if show-profiles = 1 and DEM data is present, the profile is calculated 
from the DEM data and *not* from the contour lines


If DEM data (see "Hill Shading (DEM) options") is available the flag  changes 
the status line to show the height when you hover over an area with  valid DEM 
data.


Agree

Maybe add a remark that if show-profiles = 0 and DEM data is present, an 
elevation profile is always  available?










Van: mkgmap-dev  namens Gerd Petermann 

Verzonden: donderdag 11 januari 2018 01:33:00
Aan: Development list for mkgmap
Onderwerp: Re: [mkgmap-dev] option --show-profiles and DEM

Hi Minko,

thanks for the data. I can confirm now that a profile is shown.
So, I suggest to change the description for the option from
--show-profiles=1
Sets a flag in tdb file which marks set mapset as having contour
lines and allows showing profile in MapSource. Default is 0
which means disabled.
to
--show-profiles=1
Sets a flag in tdb file which enables profile calculation in MapSource 
or
Basecamp based on contour lines.
If DEM data (see "Hill Shading (DEM) options") is available the flag
changes the status line to show the height when you hover over an area 
with
valid DEM data.

OK?
Gerd


___
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] option --show-profiles and DEM

Next try:
--show-profiles=1
Sets a flag in tdb file. The meaning depends on the availability of DEM
data (see "Hill Shading (DEM) options").
Without DEM data the flag enables profile calculation in MapSource or
Basecamp based on information from contour lines.
If DEM data is available the profile is calculated with that 
information and
the flag only changes the status line to show the height when you hover 
over
an area with valid DEM data.

OK?
Gerd


Von: mkgmap-dev  im Auftrag von lig 
fietser 
Gesendet: Donnerstag, 11. Januar 2018 10:52:29
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM

--show-profiles=1
Sets a flag in tdb file which enables profile calculation in MapSource 
or
Basecamp based on contour lines.


No, if show-profiles = 1 and DEM data is present, the profile is calculated 
from the DEM data and *not* from the contour lines


If DEM data (see "Hill Shading (DEM) options") is available the flag  changes 
the status line to show the height when you hover over an area with  valid DEM 
data.


Agree

Maybe add a remark that if show-profiles = 0 and DEM data is present, an 
elevation profile is always  available?










Van: mkgmap-dev  namens Gerd Petermann 

Verzonden: donderdag 11 januari 2018 01:33:00
Aan: Development list for mkgmap
Onderwerp: Re: [mkgmap-dev] option --show-profiles and DEM

Hi Minko,

thanks for the data. I can confirm now that a profile is shown.
So, I suggest to change the description for the option from
--show-profiles=1
Sets a flag in tdb file which marks set mapset as having contour
lines and allows showing profile in MapSource. Default is 0
which means disabled.
to
--show-profiles=1
Sets a flag in tdb file which enables profile calculation in MapSource 
or
Basecamp based on contour lines.
If DEM data (see "Hill Shading (DEM) options") is available the flag
changes the status line to show the height when you hover over an area 
with
valid DEM data.

OK?
Gerd


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

Re: [mkgmap-dev] option --show-profiles and DEM

Hi Minko,

yes, that's another reason why I think that the additional "precision" of DEM 
data in feet doesn't improve anything.
Leave alone bridges and tunnels ;-)
Also the map data is rounded to the 24 bit raster  (~2.3 m) , only DEM uses a 
32 bit raster for the points, so whatever
Mapsource or Basecamp are doing with the information, it is probably also based 
on interpolation.
In my eyes hill shading makes a map nicer and helps to decide where the hills 
are, not much more.

Off Topic:
My experience with height profiles of planned bicycle routes:
When you see a spike in the height profile it may mean that the road goes 
through a tunnel or that you are routed over
a steep highway=path acress the hill because it is much shorter than the way 
around it. Always a good reason to examine
the planned route at that point ;-)

Gerd


Von: mkgmap-dev  im Auftrag von lig 
fietser 
Gesendet: Donnerstag, 11. Januar 2018 10:38:24
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM


With this test map I can also see the difference in the altitude profiles with 
and without DEM (based on 10m contour interval):
 https://postimg.org/gallery/1huzv3m6m/

Please note that the higher accuracy of the DEM profile does not always reflect 
the elevation in reality, the road beds are always smoothing out the micro 
relief and thus leading to a lower elevation gain/loss when riding/walking this 
track.
___
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] option --show-profiles and DEM

--show-profiles=1
Sets a flag in tdb file which enables profile calculation in MapSource 
or
Basecamp based on contour lines.


No, if show-profiles = 1 and DEM data is present, the profile is calculated 
from the DEM data and *not* from the contour lines


If DEM data (see "Hill Shading (DEM) options") is available the flag  changes 
the status line to show the height when you hover over an area with  valid DEM 
data.


Agree

Maybe add a remark that if show-profiles = 0 and DEM data is present, an 
elevation profile is always  available?










Van: mkgmap-dev  namens Gerd Petermann 

Verzonden: donderdag 11 januari 2018 01:33:00
Aan: Development list for mkgmap
Onderwerp: Re: [mkgmap-dev] option --show-profiles and DEM

Hi Minko,

thanks for the data. I can confirm now that a profile is shown.
So, I suggest to change the description for the option from
--show-profiles=1
Sets a flag in tdb file which marks set mapset as having contour
lines and allows showing profile in MapSource. Default is 0
which means disabled.
to
--show-profiles=1
Sets a flag in tdb file which enables profile calculation in MapSource 
or
Basecamp based on contour lines.
If DEM data (see "Hill Shading (DEM) options") is available the flag
changes the status line to show the height when you hover over an area 
with
valid DEM data.

OK?
Gerd


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

Re: [mkgmap-dev] option --show-profiles and DEM


With this test map I can also see the difference in the altitude profiles with 
and without DEM (based on 10m contour interval):
 https://postimg.org/gallery/1huzv3m6m/

Please note that the higher accuracy of the DEM profile does not always reflect 
the elevation in reality, the road beds are always smoothing out the micro 
relief and thus leading to a lower elevation gain/loss when riding/walking this 
track.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] option --show-profiles and DEM

Hi Minko,

thanks for the data. I can confirm now that a profile is shown.
So, I suggest to change the description for the option from
--show-profiles=1
Sets a flag in tdb file which marks set mapset as having contour
lines and allows showing profile in MapSource. Default is 0
which means disabled.
to
--show-profiles=1
Sets a flag in tdb file which enables profile calculation in MapSource 
or
Basecamp based on contour lines.
If DEM data (see "Hill Shading (DEM) options") is available the flag
changes the status line to show the height when you hover over an area 
with
valid DEM data.

OK?
Gerd


Von: mkgmap-dev  im Auftrag von lig 
fietser 
Gesendet: Donnerstag, 11. Januar 2018 10:18:09
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM


Gerd, you can test it with this tile from the Bremen area.
it has contours (10m distance) but no DEM
http://mijndev.openstreetmap.nl/~ligfietser/mkgmap/49000225.o5m

___
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] option --show-profiles and DEM


Gerd, you can test it with this tile from the Bremen area.
it has contours (10m distance) but no DEM
http://mijndev.openstreetmap.nl/~ligfietser/mkgmap/49000225.o5m
  
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] option --show-profiles and DEM

Hi Carlos, and Minko,

thanks for the quick feedback. Seems I've done something wrong. Maybe the 
calculation of the profile depends on the quality or density of the contour 
line data?
I used existing contour data for Bremen, maybe the area is too flat ?
I'll try again with different data.

Gerd


Von: mkgmap-dev  im Auftrag von lig 
fietser 
Gesendet: Donnerstag, 11. Januar 2018 09:46:09
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] option --show-profiles and DEM

I'm sorry Gerd but you are wrong.

When I have a map merged with contours but without DEM and without 
show-porfiles=1 in my options args file the elevation profile is greyes out and 
not available. Only if I use show-porfiles=1 an altitude profile is available 
when making a route. So please keep this option or make it default.


Van: mkgmap-dev  namens Carlos Dávila 

Verzonden: donderdag 11 januari 2018 00:14:29
Aan: mkgmap-dev@lists.mkgmap.org.uk
Onderwerp: Re: [mkgmap-dev] option --show-profiles and DEM

If you compile a map with contour lines and show-profiles=1 MapSource
does calculate route profile. I've been using a command like the
following for a long time and it worked for me:
java -ea -Xmx4500M -jar mkgmap.jar --output-dir=./tmp --tdbfile --latin1
--code-page=1252 --description="OSM+$CURVAS-$MAPA" --country-name=$PAIS
--country-abbr=$ABR --family-name="OSM+$CURVAS $MAPA" --family-id=3$FID
--product-id=1 --product-version=$VERSION --series-name="OSM+$CURVAS
$MAPA" --area-name="$MAPA" --overview-mapname=$ABR-3$FID
--overview-mapnumber=653${FID}000 --index --road-name-config=$CONFIG
--show-profiles=1 tmp/551${FID}*.img curvas/602${FID}*.img
typ/$ABR-3${FID}.TYP
Where tmp/551${FID}*.img are precompiled regular map tiles and
curvas/602${FID}*.img are precompiled contour lines tiles. The only
issue is MapSource doesn't display contour lines, only height numbers.

El 11/01/18 a las 09:03, Gerd Petermann escribió:
> Hi all,
>
> the help says
> --show-profiles=1
>Sets a flag in tdb file which marks set mapset as having contour
>lines and allows showing profile in MapSource. Default is 0
>which means disabled.
>
> I've tried this with MapSource. My findings:
> The option is not related to contour lines, those are always displayed and 
> height is shown when you select one.
> I found two effects of show-profiles=1:
> 1) The button "Show Profile..." in the Route Properties popup is enabled even 
> if no DEM data is available.
> Without DEM data this button is of no use, the displayed profile is a 
> straight line at height 0.
> 2) With DEM data available Mapsource displays the height in the status line 
> when you hover over a hill-shaded area
> with valid data.
>
> The button "Show Profile..." in the Route Properties popup is always enabled 
> when DEM data is available.
>
> My conclusion:
> The option is useless without DEM data and with DEM data it should default to 
> --show-profiles=1
>
> In other words: I think the option should be removed and the flag should be 
> set depending on the DEM data.
>
> Comments?
> Gerd
> ___
> 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
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] option --show-profiles and DEM

I'm sorry Gerd but you are wrong.

When I have a map merged with contours but without DEM and without 
show-porfiles=1 in my options args file the elevation profile is greyes out and 
not available. Only if I use show-porfiles=1 an altitude profile is available 
when making a route. So please keep this option or make it default.


Van: mkgmap-dev  namens Carlos Dávila 

Verzonden: donderdag 11 januari 2018 00:14:29
Aan: mkgmap-dev@lists.mkgmap.org.uk
Onderwerp: Re: [mkgmap-dev] option --show-profiles and DEM

If you compile a map with contour lines and show-profiles=1 MapSource
does calculate route profile. I've been using a command like the
following for a long time and it worked for me:
java -ea -Xmx4500M -jar mkgmap.jar --output-dir=./tmp --tdbfile --latin1
--code-page=1252 --description="OSM+$CURVAS-$MAPA" --country-name=$PAIS
--country-abbr=$ABR --family-name="OSM+$CURVAS $MAPA" --family-id=3$FID
--product-id=1 --product-version=$VERSION --series-name="OSM+$CURVAS
$MAPA" --area-name="$MAPA" --overview-mapname=$ABR-3$FID
--overview-mapnumber=653${FID}000 --index --road-name-config=$CONFIG
--show-profiles=1 tmp/551${FID}*.img curvas/602${FID}*.img
typ/$ABR-3${FID}.TYP
Where tmp/551${FID}*.img are precompiled regular map tiles and
curvas/602${FID}*.img are precompiled contour lines tiles. The only
issue is MapSource doesn't display contour lines, only height numbers.

El 11/01/18 a las 09:03, Gerd Petermann escribió:
> Hi all,
>
> the help says
> --show-profiles=1
>Sets a flag in tdb file which marks set mapset as having contour
>lines and allows showing profile in MapSource. Default is 0
>which means disabled.
>
> I've tried this with MapSource. My findings:
> The option is not related to contour lines, those are always displayed and 
> height is shown when you select one.
> I found two effects of show-profiles=1:
> 1) The button "Show Profile..." in the Route Properties popup is enabled even 
> if no DEM data is available.
> Without DEM data this button is of no use, the displayed profile is a 
> straight line at height 0.
> 2) With DEM data available Mapsource displays the height in the status line 
> when you hover over a hill-shaded area
> with valid data.
>
> The button "Show Profile..." in the Route Properties popup is always enabled 
> when DEM data is available.
>
> My conclusion:
> The option is useless without DEM data and with DEM data it should default to 
> --show-profiles=1
>
> In other words: I think the option should be removed and the flag should be 
> set depending on the DEM data.
>
> Comments?
> Gerd
> ___
> 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
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] option --show-profiles and DEM

2018-01-11 Thread Carlos Dávila

If you compile a map with contour lines and show-profiles=1 MapSource 
does calculate route profile. I've been using a command like the 
following for a long time and it worked for me:
java -ea -Xmx4500M -jar mkgmap.jar --output-dir=./tmp --tdbfile --latin1 
--code-page=1252 --description="OSM+$CURVAS-$MAPA" --country-name=$PAIS 
--country-abbr=$ABR --family-name="OSM+$CURVAS $MAPA" --family-id=3$FID 
--product-id=1 --product-version=$VERSION --series-name="OSM+$CURVAS 
$MAPA" --area-name="$MAPA" --overview-mapname=$ABR-3$FID 
--overview-mapnumber=653${FID}000 --index --road-name-config=$CONFIG 
--show-profiles=1 tmp/551${FID}*.img curvas/602${FID}*.img 
typ/$ABR-3${FID}.TYP
Where tmp/551${FID}*.img are precompiled regular map tiles and 
curvas/602${FID}*.img are precompiled contour lines tiles. The only 
issue is MapSource doesn't display contour lines, only height numbers.


El 11/01/18 a las 09:03, Gerd Petermann escribió:

Hi all,

the help says
--show-profiles=1
Sets a flag in tdb file which marks set mapset as having contour
lines and allows showing profile in MapSource. Default is 0
which means disabled.

I've tried this with MapSource. My findings:
The option is not related to contour lines, those are always displayed and 
height is shown when you select one.
I found two effects of show-profiles=1:
1) The button "Show Profile..." in the Route Properties popup is enabled even 
if no DEM data is available.
Without DEM data this button is of no use, the displayed profile is a straight 
line at height 0.
2) With DEM data available Mapsource displays the height in the status line 
when you hover over a hill-shaded area
with valid data.

The button "Show Profile..." in the Route Properties popup is always enabled 
when DEM data is available.

My conclusion:
The option is useless without DEM data and with DEM data it should default to 
--show-profiles=1

In other words: I think the option should be removed and the flag should be set 
depending on the DEM data.

Comments?
Gerd
___
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] option --show-profiles and DEM


Hi Gerd

I've come to the same conclusion looking  and was quite confused when 
Frank introduced his dem builder:


I too noticed  the tdb DEM flag was always set eventhough there was no dem.

Nick


On 11/01/2018 08:03, Gerd Petermann wrote:

Hi all,

the help says
--show-profiles=1
Sets a flag in tdb file which marks set mapset as having contour
lines and allows showing profile in MapSource. Default is 0
which means disabled.

I've tried this with MapSource. My findings:
The option is not related to contour lines, those are always displayed and 
height is shown when you select one.
I found two effects of show-profiles=1:
1) The button "Show Profile..." in the Route Properties popup is enabled even 
if no DEM data is available.
Without DEM data this button is of no use, the displayed profile is a straight 
line at height 0.
2) With DEM data available Mapsource displays the height in the status line 
when you hover over a hill-shaded area
with valid data.

The button "Show Profile..." in the Route Properties popup is always enabled 
when DEM data is available.

My conclusion:
The option is useless without DEM data and with DEM data it should default to 
--show-profiles=1

In other words: I think the option should be removed and the flag should be set 
depending on the DEM data.

Comments?
Gerd
___
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

[mkgmap-dev] option --show-profiles and DEM