Hi Gerd
I've been struggling with that idea as well and am slowly creating a
dbase containing sea hgts
One almost needs a sea.poly of some kind.
Nick
On 09/01/2018 10:11, Gerd Petermann wrote:
Hi Nick,
no, but it logs it with a warning level.
It sometimes tries to read a hgt file that doesn't exist because it would be in
the ocean, so for some maps you will find many of those messages, not meaning
any error.
I am not 100% happy with this, maybe I should code a list of files which should
not be searched and produce an error message for the rest?
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von osm@pinns
<o...@pinns.co.uk>
Gesendet: Dienstag, 9. Januar 2018 11:05:50
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] DEM Noddy Guide
Hi Gerd
Oops !
sorry my mistake ; you are absolutely right.
Does the dem option provide an error msg when it can't find a hgt file?
r
Nick
On 09/01/2018 10:01, Gerd Petermann wrote:
hi Nick,
now I am confused. The attached zip contains a dem.args that contains an empty
dem option.
Do you keep the *.hgt files in the working directory?
Or maybe you generate the file ?
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von osm@pinns
<o...@pinns.co.uk>
Gesendet: Dienstag, 9. Januar 2018 10:45:41
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] DEM Noddy Guide
Hi Gerd
Run file:
java -Xmx1024m -ea -jar F:\vb6\A_MAPU~1\mkgmaps\MKA1FF~1\mkgmap.jar
--mapname=41061037 --family-id=993 F:\vb6\A_MAPU~1\TOPO_6~1.TYP
--series-name="map3" --family-name="map3" --overview-mapname="map3"
--remove-short-arcs --style-file=F:\vb6\A_MAPU~1\styles
--style="default" --keep-going --check-roundabouts --drive-on=right
--output-dir=F:\vb6\A_MAPU~1\temp --transparent --index --route --nsis
--add-pois-to-areas --add-pois-to-lines --merge-lines
--name-tag-list=int_name,name --location-autofill=is_in,nearest
--housenumbers --tdbfile --draw-priority=10 -c
F:\vb6\A_MAPU~1\args\DEM~1.ARG -c F:\vb6\A_MAPU~1\args\TEMPLA~2.ARG
Attached are the args
On 09/01/2018 09:34, osm@pinns wrote:
Hi Gerd
Bear with me
Nick
On 09/01/2018 09:29, Gerd Petermann wrote:
Hi Nick,
seems that something goes wrong with the dem option, it seems to
contain only a blank.
No idea what goes wrong, maybe you have repeated the option --dem
somewhere?
Please post the full command.
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag
von osm@pinns <o...@pinns.co.uk>
Gesendet: Dienstag, 9. Januar 2018 10:22:28
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] DEM Noddy Guide
Hi Gerd
I now get
SEVERE (HGTReader): F:\garmin\maps\ukraine\12345700.osm.pbf:
extracted path >< does not exist, check
Number of MapFailedExceptions: 0
Number of ExitExceptions: 0
Time finished: Tue Jan 09 09:21:10 GMT 2018
Total time taken: 20273ms
.
On 09/01/2018 09:13, Gerd Petermann wrote:
Hi Nick,
yes, the message looks that strange because the variable "dir" is
empty or maybe contains a blank when this code is executed:
File f = new File (dir);
if (!f.exists()) log.error(dir, "does not exist");
The file name for the *.pbf is added by the logging method, because
the dem option is parsed for each osm input file.
With r4039 I've changed the code for the error message to this:
log.error("extracted path >" + dir + "< does not exist, check",
dirsWithHGT);
Please try to reproduce the error with r4039 and let me know what it
reports now.
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag
von osm@pinns <o...@pinns.co.uk>
Gesendet: Dienstag, 9. Januar 2018 09:57:49
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] DEM Noddy Guide
Hi Gerd
I'm merely questioning the phrasing of the message -, ie it wasn't the
pdf that was causing the problem as the msg implied.
Nick
On 09/01/2018 08:51, Gerd Petermann wrote:
Hi Nick,
I cannot reproduce that message without using a wrong option like
dem=path1,,path2
(extra comma)
Anyhow, I try to improve the message.
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag
von osm@pinns <o...@pinns.co.uk>
Gesendet: Dienstag, 9. Januar 2018 09:40:23
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] DEM Noddy Guide
Hi Gerd
I used
dem=e:\dem\europe\
overview-dem-dist=88888
dem-dists=3312,13248,26512,53024
dem-poly=F:\garmin\ukraine\areas.poly
when I added the required .hgt files it worked OK
On 09/01/2018 08:20, Gerd Petermann wrote:
On 09/01/2018 08:20, Gerd Petermann wrote:
Hi Nick,
I think this message may appear if you have blanks in the option
--dem. What exactly do you use?
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im
Auftrag von osm@pinns <o...@pinns.co.uk>
Gesendet: Dienstag, 9. Januar 2018 09:14:14
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] DEM Noddy Guide
Hi Gerd,
Just come across a misleading error message:
SEVERE (HGTReader): F:\garmin\maps\ukraine\12345700.osm.pbf:
does not exist
Number of MapFailedExceptions: 0
Number of ExitExceptions: 0
The pbf existed, as it produced the map with out DEM !
However,some of the .hgt files were missing which caused the error.
Just a minor point
r
Nick
On 09/01/2018 06:09, Gerd Petermann wrote:
Hi all,
I did not note this before, but there is probably a typo in this
description:
overview-dem-dist=888888 is far too high, I assume Arndt meant
88888.
Besides that I think there is need to use --dem-poly in
combination with the poly file created by splitter.
This poly file just describes the outer boundaries of the tiles,
and mkgmap calculates this polygon anyway.
The --dem-poly can be used with the rather complex *.poly files
from geofabrik. I've tested with bolivia.poly which has 1176 nodes
and the additional tests for the polygon bounds did not take
long. Still, you may want to draw your own simpler poly files
because those from
geofabrik are rather close to country borders.
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im
Auftrag von Arndt Röhrig <ar...@speichenkarte.de>
Gesendet: Freitag, 5. Januar 2018 21:41:57
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] DEM Noddy Guide
Hi Mike,
it´s simple:
- Download hgt files )*
- give mkgmap the option x-dem=path to the hgt files
- x-dem-dists=3314,4000,6000,8000,10000,15000 (maybe other values
are better)
1 value for each level (options file: exampel levels = 0:24,
1:23, 2:22, 3:21, 4:20, 5:19)
- x-overview-dem-dist=888888 writes DEM to the overviewmap (maybe
other value is better)
- x-dem-poly=path to a poly file for example areas.poly from
splitter result.
That´s all.
)* hgt files are downloadable here:
http://www.viewfinderpanoramas.org/dem3.html
I use phyghtmap to create SRTM contourlines as .pbf. the program
download hgt files from viewfinderpanoramas to build the pbfs.
After that you find a folder hgt on your pc with hgt files inside.
http://katze.tfiu.de/projects/phyghtmap/
Greetings
Arndt
Mike Baggaley hat am 5. Januar 2018 um 21:19 geschrieben:
Hi all,
I've been following the discussions of DEM with interest, but
have so far
not attempted to create a map including this. Is there a guide to
the steps
involved in producing the DEM data? I have contour data in OSM
format - is
there a simple way to get this into a suitable input format (or
is there a
specification of the input format available, so I can knock up
something to
convert it)? I'm assuming that the height data contains the same
information
as contour data but in a different format.
Thanks,
Mike
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap<mailto: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
_______________________________________________
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
_______________________________________________
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
