Hi Gerd
Many thanks
so far I've got similar results as you have had
ie
an old GB TOPO :1648,3312,13248,53024
an old Swiss : 3312,13248,53024,212096
another one : 3312,6624,26512,106048,424192,1696768
I've also been extracting the dem from some GMP files but clearly the
structure is quite different with no offsetts at 0x21 and then 0x30
Nick
On 12/01/2018 10:00, Gerd Petermann wrote:
Hi Nick,
I've uplodaed display.jar r515:
http://files.mkgmap.org.uk/download/388/display.jar
See http://www.mkgmap.org.uk/websvn/revision.php?repname=display&rev=515
The previous one also contained an experimental patch in MdrCheck which was not
in the svn repo.
Gerd
________________________________________
Von: mkgmap-dev <[email protected]> im Auftrag von osm@pinns
<[email protected]>
Gesendet: Donnerstag, 11. Januar 2018 15:39:04
An: [email protected]
Betreff: 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 <[email protected]> im Auftrag von osm@pinns
<[email protected]>
Gesendet: Donnerstag, 11. Januar 2018 15:30:11
An: [email protected]
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 <[email protected]> im Auftrag von osm@pinns
<[email protected]>
Gesendet: Donnerstag, 11. Januar 2018 15:16:18
An: [email protected]
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 <[email protected]> im Auftrag von osm@pinns
<[email protected]>
Gesendet: Donnerstag, 11. Januar 2018 15:04:32
An: [email protected]
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 <[email protected]> im Auftrag von
[email protected] <[email protected]>
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<https://go.microsoft.com/fwlink/?LinkId=550986> für Windows 10
Von: Henning Scholland<mailto:[email protected]>
Gesendet: Donnerstag, 11. Januar 2018 12:55
An: [email protected]<mailto:[email protected]>
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
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
