Hi Mike,
I'd rather change the code so that you don't see those tags. They are for
internal use only.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Mittwoch, 31. Januar 2018 20:20
An: 'Development list for mkgmap'
Betreff: [mkgmap-dev] S
I notice the style manual has no mention of mkgmap:stylefilter or
mkgmap:tagsincomplete in it. I see these in the output of the echotags
command when handling a relation. Can they be added to the documentation?
Cheers,
Mike
___
mkgmap-dev mailing list
m
Hi all,
sorry, I wrote
"A work around is to tell splitter that it should use e.g. height 0 for these
values:
--x-dem-outside-polygon=0"
Of course this is an (undocumented) mkgmap option, not one for splitter.
Gerd
Von: mkgmap-dev im Auftrag von Gerd
Pe
Hi DEM experts,
the problem seems to be the value that is encoded for heights outside of the
polygon.
So far mkgmap writes the same value that is used to signal a void in the data.
This seems to cause trouble, maybe even more as I see full rows of such voids.
A work around is to tell splitter tha
Hi all,
some more details:
The problem only appears when a route on the map created with --dem-poly
crosses tile boundaries.
It doesn't seem to depend on the route itself, I've tested 5 different routes
crossing tile boundaries
and always got a crash when clicking on "Show profile..."
It also do
Thanks Gerd
One certainly gets more of the lumps and bumps with a distance of 1664
Nick
On 31/01/2018 13:20, Gerd Petermann wrote:
Hi Nick,
well, Andrzej reported that this oversampling might improve precision.
My understanding is that it reduces the error that is added by interpolation.
Fo
Hi Nick,
well, Andrzej reported that this oversampling might improve precision.
My understanding is that it reduces the error that is added by interpolation.
For sure it adds a lot of bytes to the img file, so one has to find out what is
more imprtant.
Gerd
Hi Gerd
Thanks for the detailed explanations.
' if you want more precision and map size doesn't matter half of it '
I'm not quite sure how halving these values produce greater precision
for resolution 24.
Interestingly , you mention 1664 .
One of my topos has 1648 as in
1648,3312,13248
I had also noticed that crash when clicking on "Show profile..." button, but didn't have time to investigate it and report.---Mensaje original---Hi all,
I've just noticed that MapSource crashed after pressing the "Show Profile..." button for a route.
I can reproduce the crash on MapSource,
Hi all,
I've just noticed that MapSource crashed after pressing the "Show Profile..."
button for a route.
I can reproduce the crash on MapSource, Basecamp just says
"The current map does not contain any elevation data on the selected route(s)"
This problem disappears when I remove the --dem-poly
Hi Minko,
I'd also like to know a good rule how to calculate the dem-dists values.
Again the basic formulars:
Typical hgt formats use a raster with either 1200 (3'') or 3600 (1'')
points/degree as resolution.
The corresponding resolutions for DEM are 2^32/(1200*360) ~ 9942 or 2^32(3600 *
360) ~
Yes, it would be helpful if we mention where we can get the hgt files, a few
examples of the dem-dist values and an explanation how to calculate it. This
information is already there but mentioned in the many updates of the branch
versions.
I use http://www.javawa.nl/srtm/index.php?lang=nl be
12 matches
Mail list logo
