-DEM layers."
Gerd
Von: mkgmap-dev im Auftrag von Carlos
Dávila
Gesendet: Samstag, 27. Januar 2018 17:50
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Is dem-tdb branch ready for trunk ?
Thanks for sharing your results. Have you tested data
@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Is dem-tdb branch ready for trunk ?
Thanks for the info!!
El 28/01/18 a las 14:20, Peter Danninger escribió:
> I've downloaded and testet.
>
> look at attachment.
>
> In short-form:
> -
> really
Thanks for the info!!
El 28/01/18 a las 14:20, Peter Danninger escribió:
I've downloaded and testet.
look at attachment.
In short-form:
-
really good, comparable with the
USGS-NASA .hgt-files.
N74E018, N74E019:
Bjornoya (Bäreninsel) missing,
only
Thanks for sharing your results. Have you tested data from
http://opendem.info/opendemeu_download_4326.html ?
El 27/01/18 a las 15:56, Peter Danninger escribió:
Some results from my .hgt-tests:
I wanted to find usable .hgt files for my
web-application zu add height data to .gpx
http://peter.m
require much new code.
Gerd
Von: mkgmap-dev im Auftrag von Henning
Scholland
Gesendet: Samstag, 27. Januar 2018 14:21
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Is dem-tdb branch ready for trunk ?
Hi Gerd,
first I would suggest to wait for
El 27/01/18 a las 14:57, Carlos Dávila escribió:
I have no objective method to compare hgt sources (is there any?)
Well, a method I have already used is to get the number of voids in a
hgt file using QGIS.
___
mkgmap-dev mailing list
mkgmap-dev@li
Hi
I think before having such a container we would need to have a clear
idea what hgt sources are best. I have no objective method to compare
hgt sources (is there any?) but I have done some test comparing contour
lines generated from different sources. Copernicus (EU-DEM) data has
been commen
Hi Gerd,
first I would suggest to wait for Steve is merging the block size branch
and just afterwards merge DEM branch to trunk. I think it's causing
trouble merging DEM branch before, as user might end up with errors.
Later start another branch for DEM-optimization.
I don't know how other global
; Development list for mkgmap
Betreff: Re: [mkgmap-dev] Is dem-tdb branch ready for trunk ?
Hi Thomas,
I see two major problems with this:
1) A file containing all DEM data for e.g. dem-dist=9936 would be huge, and
most users only need a small portion of it
2) I am not sure if it is allowed to publish this
, 27. Januar 2018 10:40
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Is dem-tdb branch ready for trunk ?
Maybee we can create a ready to use DEM-model, store it like the bounds.zip
and see.zip ? The user can download it and mkgmap reads the DEM from
downloaded #DEM.ZIP# ?
This met
--
Von: "Gerd Petermann"
Datum: Samstag, 27. Januar 2018 08:54
An:
Betreff: [mkgmap-dev] Is dem-tdb branch ready for trunk ?
Hi all,
I am not aware of any erros in r4091, so I think it is time to merge
it into trunk.
I see only one problem: HGT data changes rarely, so I'd pr
--
Von: "Gerd Petermann"
Datum: Samstag, 27. Januar 2018 08:54
An:
Betreff: [mkgmap-dev] Is dem-tdb branch ready for trunk ?
Hi all,
I am not aware of any erros in r4091, so I think it is time to merge it
into trunk.
I see only one problem: HGT data changes
Hi all,
I am not aware of any erros in r4091, so I think it is time to merge it into
trunk.
I see only one problem: HGT data changes rarely, so I'd prefer to do the costly
DEM calculations
only once and be able to store the results.
I've already described how to do this here [1] but I'd prefer
13 matches
Mail list logo
