Re: [mkgmap-dev] r4015 in dem-tdb branch implements --x-overview-dem-dist

2017-12-23 Thread Henning Scholland
Hi Gerd,

after thinking a while about overview-dem and it's not really logical to
me. Mainly the proposed x-overview-dem-dist=0 isn't really intuitive. I
should have thought more better before proposing it. It would be better
to have a separate parameter -x-dem-overview=yes/no, where yes is
default when DEM is activated.

I will try to find a value for overview DEM with my maps. Keep you posted.

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


Re: [mkgmap-dev] WG: r4015 in dem-tdb branch implements --x-overview-dem-dist

2017-12-23 Thread Gerd Petermann
I don't know and have no time today to look at it.
Maybe it looks more detailed but the data isn't better?

Gerd


Von: mkgmap-dev  im Auftrag von lig 
fietser 
Gesendet: Samstag, 23. Dezember 2017 12:55:39
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] WG: r4015 in dem-tdb  branch  implements  
--x-overview-dem-dist

Hi, although I use 3" hgt files, 3312 looks much more detailed than 9942?



Van: mkgmap-dev  namens Gerd Petermann 

Verzonden: zaterdag 23 december 2017 03:33:30
Aan: Development list for mkgmap
Onderwerp: [mkgmap-dev] WG: r4015 in dem-tdb branch implements 
--x-overview-dem-dist

Hi!
I've just noticed that I replied to Minko instead of the list. Please see below.

Gerd


Von: Gerd Petermann 
Gesendet: Samstag, 23. Dezember 2017 12:04
An: lig fietser
Betreff: AW: [mkgmap-dev] r4015 in dem-tdb branch implements
--x-overview-dem-dist

I am not sure what to think about that.
When you use 3'' hgt files (size is  ~2.8MB) the resolution in that data is 
2^32/(360 * 1200) ~ 9942.
When you use 1'' hgt files (size is  ~26MB) the resolution in that data is 
2^32/(360 * 3600) ~ 3314.
The current implementation in mkgmap interpolates the values found in the hgt 
file. It assumes
continous slope between two points at the same lat, so e.g. if one is 123 and 
the other is 135,
it assumes that a point in the middle is at 129.
I assumed that the Garmin algo does something similar when calculating the 
heights, but maybe it
doesn't.

I did not yet try to find out the best values for dem-dists, so it would be 
good to hear about results.

Gerd


Von: lig fietser 
Gesendet: Samstag, 23. Dezember 2017 11:45:21
An: Gerd Petermann
Betreff: Re: [mkgmap-dev] r4015 in dem-tdb branch implements
--x-overview-dem-dist

Thanks Gerd, the value of 3312 works much better now!


Van: Gerd Petermann 
Verzonden: zaterdag 23 december 2017 02:36:32
Aan: lig fietser
Onderwerp: AW: [mkgmap-dev] r4015 in dem-tdb branch implements 
--x-overview-dem-dist

Hi Minko,

to convert the parms for BuildDEMFile you have to multiply by 2^32/360 :
0.00027761 * 2^32/360  ~ 3312.

Gerd


Von: lig fietser 
Gesendet: Samstag, 23. Dezember 2017 11:30:20
An: Gerd Petermann; Development list for mkgmap
Betreff: Re: [mkgmap-dev] r4015 in dem-tdb branch implements
--x-overview-dem-dist

Hi Gerd,
Thanks for the good work to implement DEM into mkgmap!
I have tested a few tiles, I noticed that BuildDEMFile with--dlon=0.00027761 
has a much more detailed relief than the default values x-dem-dists=5520, 
16560, 44176, 88368 How can I get the same results as with dlon=0.00027761?
___
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] Hillshading Details

2017-12-23 Thread Arndt Röhrig

Sorry if that should be double. This is without a picture attachment, only a link to the picture:http://www.speichenkarte.de/beta/Hillshading%20Detail.PNGHope it helps..Arndt
 
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] WG: r4015 in dem-tdb branch implements --x-overview-dem-dist

2017-12-23 Thread lig fietser
Hi, although I use 3" hgt files, 3312 looks much more detailed than 9942?



Van: mkgmap-dev  namens Gerd Petermann 

Verzonden: zaterdag 23 december 2017 03:33:30
Aan: Development list for mkgmap
Onderwerp: [mkgmap-dev] WG: r4015 in dem-tdb branch implements 
--x-overview-dem-dist

Hi!
I've just noticed that I replied to Minko instead of the list. Please see below.

Gerd


Von: Gerd Petermann 
Gesendet: Samstag, 23. Dezember 2017 12:04
An: lig fietser
Betreff: AW: [mkgmap-dev] r4015 in dem-tdb branch implements
--x-overview-dem-dist

I am not sure what to think about that.
When you use 3'' hgt files (size is  ~2.8MB) the resolution in that data is 
2^32/(360 * 1200) ~ 9942.
When you use 1'' hgt files (size is  ~26MB) the resolution in that data is 
2^32/(360 * 3600) ~ 3314.
The current implementation in mkgmap interpolates the values found in the hgt 
file. It assumes
continous slope between two points at the same lat, so e.g. if one is 123 and 
the other is 135,
it assumes that a point in the middle is at 129.
I assumed that the Garmin algo does something similar when calculating the 
heights, but maybe it
doesn't.

I did not yet try to find out the best values for dem-dists, so it would be 
good to hear about results.

Gerd


Von: lig fietser 
Gesendet: Samstag, 23. Dezember 2017 11:45:21
An: Gerd Petermann
Betreff: Re: [mkgmap-dev] r4015 in dem-tdb branch implements
--x-overview-dem-dist

Thanks Gerd, the value of 3312 works much better now!


Van: Gerd Petermann 
Verzonden: zaterdag 23 december 2017 02:36:32
Aan: lig fietser
Onderwerp: AW: [mkgmap-dev] r4015 in dem-tdb branch implements 
--x-overview-dem-dist

Hi Minko,

to convert the parms for BuildDEMFile you have to multiply by 2^32/360 :
0.00027761 * 2^32/360  ~ 3312.

Gerd


Von: lig fietser 
Gesendet: Samstag, 23. Dezember 2017 11:30:20
An: Gerd Petermann; Development list for mkgmap
Betreff: Re: [mkgmap-dev] r4015 in dem-tdb branch implements
--x-overview-dem-dist

Hi Gerd,
Thanks for the good work to implement DEM into mkgmap!
I have tested a few tiles, I noticed that BuildDEMFile with--dlon=0.00027761 
has a much more detailed relief than the default values x-dem-dists=5520, 
16560, 44176, 88368 How can I get the same results as with dlon=0.00027761?
___
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] WG: r4015 in dem-tdb branch implements --x-overview-dem-dist

2017-12-23 Thread Gerd Petermann
Hi!
I've just noticed that I replied to Minko instead of the list. Please see below.

Gerd


Von: Gerd Petermann 
Gesendet: Samstag, 23. Dezember 2017 12:04
An: lig fietser
Betreff: AW: [mkgmap-dev] r4015 in dem-tdb branch implements
--x-overview-dem-dist

I am not sure what to think about that.
When you use 3'' hgt files (size is  ~2.8MB) the resolution in that data is 
2^32/(360 * 1200) ~ 9942.
When you use 1'' hgt files (size is  ~26MB) the resolution in that data is 
2^32/(360 * 3600) ~ 3314.
The current implementation in mkgmap interpolates the values found in the hgt 
file. It assumes
continous slope between two points at the same lat, so e.g. if one is 123 and 
the other is 135,
it assumes that a point in the middle is at 129.
I assumed that the Garmin algo does something similar when calculating the 
heights, but maybe it
doesn't.

I did not yet try to find out the best values for dem-dists, so it would be 
good to hear about results.

Gerd


Von: lig fietser 
Gesendet: Samstag, 23. Dezember 2017 11:45:21
An: Gerd Petermann
Betreff: Re: [mkgmap-dev] r4015 in dem-tdb branch implements
--x-overview-dem-dist

Thanks Gerd, the value of 3312 works much better now!


Van: Gerd Petermann 
Verzonden: zaterdag 23 december 2017 02:36:32
Aan: lig fietser
Onderwerp: AW: [mkgmap-dev] r4015 in dem-tdb branch implements 
--x-overview-dem-dist

Hi Minko,

to convert the parms for BuildDEMFile you have to multiply by 2^32/360 :
0.00027761 * 2^32/360  ~ 3312.

Gerd


Von: lig fietser 
Gesendet: Samstag, 23. Dezember 2017 11:30:20
An: Gerd Petermann; Development list for mkgmap
Betreff: Re: [mkgmap-dev] r4015 in dem-tdb branch implements
--x-overview-dem-dist

Hi Gerd,
Thanks for the good work to implement DEM into mkgmap!
I have tested a few tiles, I noticed that BuildDEMFile with--dlon=0.00027761 
has a much more detailed relief than the default values x-dem-dists=5520, 
16560, 44176, 88368 How can I get the same results as with dlon=0.00027761?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


Re: [mkgmap-dev] r4015 in dem-tdb branch implements --x-overview-dem-dist

2017-12-23 Thread Henning Scholland
Hi,
it would be my expected behaviour if you just delete the OSM data and keep the 
area still in your map area.

Henning

⁣Sent from BlueMail ​

On 23 Dec 2017, 10:12, at 10:12, Ervin Malicdem  wrote:
>Hi Gerd,
>
>This is regarding hillshade still being rendered even if the area was
>excluded in the osm file.
>As an example, I specifically removed borneo island in the southwest
>but
>DEM still showed up.
>
>https://www.dropbox.com/s/m6pdz90d3jo1unq/borneo.jpg?dl=0
>
>Ervin M.
>*Schadow1 Expeditions* - A Filipino must not be a stranger to his own
>motherland.
>http://www.s1expeditions.com
>
>On Sat, Dec 23, 2017 at 4:08 PM, Gerd Petermann <
>gpetermann_muenc...@hotmail.com> wrote:
>
>> Hi Ervin,
>>
>> I think there is no longer a need to change splitter since DEM files
>are
>> allowed to grow > 16MB with r4016.
>> Just to make that clear: When I write about DEM files I mean the
>files in
>> the Garmin DEM format, they are either contained in a *.img
>> or in a *.DEM, and they contain the text "GARMIN DEM". I guess DEM
>means
>> something like "Digital Elevation Model".
>> Besides that I don't understand what you mean. Is it about the
>contour
>> lines created by tools like srtm2osm or phyghtmap?
>> What could be improved in splitter?
>>
>> Gerd
>>
>> 
>> Von: ebmalic...@cxsmedia.com  im Auftrag von
>> Ervin Malicdem 
>> Gesendet: Samstag, 23. Dezember 2017 06:21:36
>> An: Development list for mkgmap; gpetermann_muenc...@hotmail.com
>> Betreff: Re: [mkgmap-dev] r4015 in dem-tdb branch implements
>> --x-overview-dem-dist
>>
>> Getting better each time! Great!
>> A suggestion once you will be working with splitter is for the dem to
>be
>> cut using a poly file as well.
>>
>> Ervin M.
>> Schadow1 Expeditions - A Filipino must not be a stranger to his own
>> motherland.
>> http://www.s1expeditions.com
>>
>> On Sat, Dec 23, 2017 at 12:11 AM, Gerd Petermann <
>>
>gpetermann_muenc...@hotmail.com>
>> wrote:
>> Hi,
>>
>> okay, so we now have three new (still undocumented options) to enable
>> hillshading and calculation of elevation data in routes.
>> Here is a summary of the new options:
>>
>> --x-dem=path_to_dir[,path_to_other_dir,...]
>> gives one or more directories containing *.hgt files.
>> --x-dem-dists=n1,n2,n3,...
>> Sample from a Garmin Demo map: --x-dem-dists="5520, 16560, 44176,
>88368"
>> should contain one number for each level in case you want to use the
>DEM
>> data in a gmapsupp, the values give
>> the number of DEM units between two points. A DEM unit is 360° / 2
>^32.
>> The higher the numbers the smaller the DEM file. Useful values for
>level 0
>> start
>> at 1600 if you have 1'' hgt data and a small area, for large areas
>> consider to use 8000 or more. If this option is missing mkgmap will
>> calculate one DEM
>> level based on the resolution of the hgt files.
>> --x-overview-dem-dist=n
>> Use this option to add DEM also to the overview map. The value again
>gives
>> the distance between two DEM points.
>> It the option is not given or the value is 0 the creation of DEM data
>for
>> the overview map is disabled. This might be needed for large areas
>and for
>> overview img files which
>> are already close to 16MB .
>> Useful are probably values > 10, e.g. 256000
>>
>> Expect to see "There is not enough room in a single garmin map for
>all the
>> input data. The .osm file should be split into smaller pieces first."
>> when experimenting with these options. The additional amount of bytes
>for
>> the DEM files depend on the above options, and the relief of the
>area.
>> Mountains
>> require much more space compared to flat areas like the netherlands.
>> If you have contour lines in your overview map try without.
>>
>> I'll try to add code to splitter so that it creates smaller tiles for
>> areas with many mountains. I don't know yet how to store that info.
>>
>> 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] r4015 in dem-tdb branch implements --x-overview-dem-dist

2017-12-23 Thread Andrzej Popowski

Hi,

Gerd has published formula for his parameters, you have to multiply your 
dlon by 2^32/360. Value dlon=0.00027761 is equivalent of about 
x-dem-dists=3313.


Basically 1" arc DEM ~ 3314, 3" arc DEM ~ 9942.
Or so I hope, I haven't tested.

--
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] r4015 in dem-tdb branch implements --x-overview-dem-dist

2017-12-23 Thread lig fietser
Hi Gerd,
Thanks for the good work to implement DEM into mkgmap!
I have tested a few tiles, I noticed that BuildDEMFile with--dlon=0.00027761 
has a much more detailed relief than the default values x-dem-dists=5520, 
16560, 44176, 88368 How can I get the same results as with dlon=0.00027761?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] r4015 in dem-tdb branch implements --x-overview-dem-dist

2017-12-23 Thread Ervin Malicdem
Hi Gerd,

This is regarding hillshade still being rendered even if the area was
excluded in the osm file.
As an example, I specifically removed borneo island in the southwest but
DEM still showed up.

https://www.dropbox.com/s/m6pdz90d3jo1unq/borneo.jpg?dl=0

Ervin M.
*Schadow1 Expeditions* - A Filipino must not be a stranger to his own
motherland.
http://www.s1expeditions.com

On Sat, Dec 23, 2017 at 4:08 PM, Gerd Petermann <
gpetermann_muenc...@hotmail.com> wrote:

> Hi Ervin,
>
> I think there is no longer a need to change splitter since DEM files are
> allowed to grow > 16MB with r4016.
> Just to make that clear: When I write about DEM files I mean the files in
> the Garmin DEM format, they are either contained in a *.img
> or in a *.DEM, and they contain the text "GARMIN DEM". I guess DEM means
> something like "Digital Elevation Model".
> Besides that I don't understand what you mean. Is it about the contour
> lines created by tools like srtm2osm or phyghtmap?
> What could be improved in splitter?
>
> Gerd
>
> 
> Von: ebmalic...@cxsmedia.com  im Auftrag von
> Ervin Malicdem 
> Gesendet: Samstag, 23. Dezember 2017 06:21:36
> An: Development list for mkgmap; gpetermann_muenc...@hotmail.com
> Betreff: Re: [mkgmap-dev] r4015 in dem-tdb branch implements
> --x-overview-dem-dist
>
> Getting better each time! Great!
> A suggestion once you will be working with splitter is for the dem to be
> cut using a poly file as well.
>
> Ervin M.
> Schadow1 Expeditions - A Filipino must not be a stranger to his own
> motherland.
> http://www.s1expeditions.com
>
> On Sat, Dec 23, 2017 at 12:11 AM, Gerd Petermann <
> gpetermann_muenc...@hotmail.com>
> wrote:
> Hi,
>
> okay, so we now have three new (still undocumented options) to enable
> hillshading and calculation of elevation data in routes.
> Here is a summary of the new options:
>
> --x-dem=path_to_dir[,path_to_other_dir,...]
> gives one or more directories containing *.hgt files.
> --x-dem-dists=n1,n2,n3,...
> Sample from a Garmin Demo map: --x-dem-dists="5520, 16560, 44176, 88368"
> should contain one number for each level in case you want to use the DEM
> data in a gmapsupp, the values give
> the number of DEM units between two points. A DEM unit is 360° / 2 ^32.
> The higher the numbers the smaller the DEM file. Useful values for level 0
> start
> at 1600 if you have 1'' hgt data and a small area, for large areas
> consider to use 8000 or more. If this option is missing mkgmap will
> calculate one DEM
> level based on the resolution of the hgt files.
> --x-overview-dem-dist=n
> Use this option to add DEM also to the overview map. The value again gives
> the distance between two DEM points.
> It the option is not given or the value is 0 the creation of DEM data for
> the overview map is disabled. This might be needed for large areas and for
> overview img files which
> are already close to 16MB .
> Useful are probably values > 10, e.g. 256000
>
> Expect to see "There is not enough room in a single garmin map for all the
> input data. The .osm file should be split into smaller pieces first."
> when experimenting with these options. The additional amount of bytes for
> the DEM files depend on the above options, and the relief of the area.
> Mountains
> require much more space compared to flat areas like the netherlands.
> If you have contour lines in your overview map try without.
>
> I'll try to add code to splitter so that it creates smaller tiles for
> areas with many mountains. I don't know yet how to store that info.
>
> 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