date:20180131

Re: [mkgmap-dev] Style Manual

2018-01-31 Thread Gerd Petermann

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] Style Manual

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
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] Style Manual

2018-01-31 Thread Mike Baggaley

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
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Option --dem-profile seems to cause crash in MapSource

2018-01-31 Thread Gerd Petermann

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 
Petermann 
Gesendet: Mittwoch, 31. Januar 2018 17:55
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Option --dem-profile seems to cause crash in  
MapSource

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 that it should use e.g. height 0 for these 
values:
--x-dem-outside-polygon=0
I don't like this because it creates visible "steps" at the polygon boundary 
when height switches between
0 and the real value.

I've looked again at the Adria Topo map and it seems that Garmin uses a 
different approach:
Although tile boundaries are not rectangular the DEM data is filled for the 
full rectangular area.

My conclusion:
So, either we have an error in the encoder which occurs when it encodes many 
values with
the max height and this max height is flagged as invalid or Garmin software 
simply cannot handle
larger areas of voids.

At the moment I have only one solution which is similar to the one in the Adria 
map:
The polygon from --dem-poly is used for the tile boundaries, not the DEM data.

Attached is the corresponding patch.
A binary is here:
http://files.mkgmap.org.uk/download/409/mkgmap.jar

Note that this only works well when you also use e.g. osmconvert to filter the 
input data for splitter with the same bounding polygon.
Sample:
osmconvert --drop-author -B=xyz.poly niedersachsen.o5m -o=part.o5m
java -Xmx5G -jar d:\splitter\dist\splitter.jar --output-dir=split part.o5m > 
splitter.log
java -Xmx5G -jar d:\mkgmp\dist\mkgmap.jar --dem-poly=xyz.poly ... -c -c 
split\template.args

What do you think?
Gerd


Von: mkgmap-dev  im Auftrag von Gerd 
Petermann 
Gesendet: Mittwoch, 31. Januar 2018 15:23
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Option --dem-profile seems to cause crash in  
MapSource

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 does not seem to depend on the style or the existence of additional 
contour lines.

So, for now I'd say: Don't use --dem-poly

Gerd


Von: mkgmap-dev  im Auftrag von Gerd 
Petermann 
Gesendet: Mittwoch, 31. Januar 2018 12:19
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: [mkgmap-dev] Option --dem-profile seems to cause crash in 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 option, so I think there 
still is a problem
in the encoder :-(
The interesting thing is that my route is far away from the polygon boundary.

I'll try to find out more ...

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] Option --dem-profile seems to cause crash in MapSource

2018-01-31 Thread Gerd Petermann

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 that it should use e.g. height 0 for these 
values:
--x-dem-outside-polygon=0
I don't like this because it creates visible "steps" at the polygon boundary 
when height switches between
0 and the real value.

I've looked again at the Adria Topo map and it seems that Garmin uses a 
different approach:
Although tile boundaries are not rectangular the DEM data is filled for the 
full rectangular area.

My conclusion:
So, either we have an error in the encoder which occurs when it encodes many 
values with
the max height and this max height is flagged as invalid or Garmin software 
simply cannot handle
larger areas of voids.

At the moment I have only one solution which is similar to the one in the Adria 
map:
The polygon from --dem-poly is used for the tile boundaries, not the DEM data.

Attached is the corresponding patch.
A binary is here:
http://files.mkgmap.org.uk/download/409/mkgmap.jar

Note that this only works well when you also use e.g. osmconvert to filter the 
input data for splitter with the same bounding polygon.
Sample:
osmconvert --drop-author -B=xyz.poly niedersachsen.o5m -o=part.o5m
java -Xmx5G -jar d:\splitter\dist\splitter.jar --output-dir=split part.o5m > 
splitter.log
java -Xmx5G -jar d:\mkgmp\dist\mkgmap.jar --dem-poly=xyz.poly ... -c -c 
split\template.args

What do you think?
Gerd


Von: mkgmap-dev  im Auftrag von Gerd 
Petermann 
Gesendet: Mittwoch, 31. Januar 2018 15:23
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Option --dem-profile seems to cause crash in  
MapSource

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 does not seem to depend on the style or the existence of additional 
contour lines.

So, for now I'd say: Don't use --dem-poly

Gerd


Von: mkgmap-dev  im Auftrag von Gerd 
Petermann 
Gesendet: Mittwoch, 31. Januar 2018 12:19
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: [mkgmap-dev] Option --dem-profile seems to cause crash in 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 option, so I think there 
still is a problem
in the encoder :-(
The interesting thing is that my route is far away from the polygon boundary.

I'll try to find out more ...

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


0x4a_v2.patch
Description: 0x4a_v2.patch
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Option --dem-profile seems to cause crash in MapSource

2018-01-31 Thread Gerd Petermann

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 does not seem to depend on the style or the existence of additional 
contour lines.

So, for now I'd say: Don't use --dem-poly

Gerd


Von: mkgmap-dev  im Auftrag von Gerd 
Petermann 
Gesendet: Mittwoch, 31. Januar 2018 12:19
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: [mkgmap-dev] Option --dem-profile seems to cause crash in 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 option, so I think there 
still is a problem
in the encoder :-(
The interesting thing is that my route is far away from the polygon boundary.

I'll try to find out more ...

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

Re: [mkgmap-dev] Please help with news about new DEM options

2018-01-31 Thread osm@pinns


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.

For sure it adds a lot of bytes to the img file, so one has to find out what is 
more imprtant.

Gerd


Von: mkgmap-dev  im Auftrag von osm@pinns 

Gesendet: Mittwoch, 31. Januar 2018 13:32
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Please help with news about new DEM options

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,53024

   Nick



On 31/01/2018 11:03, Gerd Petermann wrote:

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) ~ 3314

It is quite obvious that the first value in dem-dists depends on the resolution 
of the input hgt file(s).
My understanding is that you might use a value near the hgt resolution or maybe
- if you want more precision and map size doesn't matter -
half of it, so
3'' hgt means dem-dist ~ 9942 (or 9942/2 = 4971)
1'' hgt means dem-dist ~ 3314 (or 3314/2 = 1657)
Since mkgmap now rounds these values to multiples of 16 you get
2^32/(1200*360) ~ 9942 -> 9936 rounded
2^32/(1200*360) / 2 ~ 4971 -> 4976 rounded
2^32/(3600*360) ~ 3314 -> 3312 rounded
2^32/(3600*360) / 2 ~ 1657 -> 1664 rounded

These are the values for resolution 24.
What still seems unclear is how you calculate the values for lower resolutions.
Up to now I see no reason to duplicate data with e.g. dem-dists=3312,3312,...
but I see this in Arndts "Speichenkarte" which uses resolution 23 for level 1.

I tried some different values on my Oregon 600 and I think the hill shading is
not very useful on the device. Maybe that's the reason why the setting
Map->Advanced Setup->Shaded relief->Auto
means that hill shading is not used unless you zoom out to 5km?

I also tried with only one or two DEM levels,
e.g. --dem-dists=1664,3312 or just --dem-dists=3312
It works, the device just uses the DEM from the basemap when you zoom out to 
e.g. 500 m.
The problem: The basemap has a very poor DEM resolution, so it looks wrong when 
hills
suddenly disappear while zooming out.

My current compromise for high precision with 1'' hgt input and default style:
1664,9936,26512,53024

Gerd


Von: mkgmap-dev  im Auftrag von lig fietser 

Gesendet: Mittwoch, 31. Januar 2018 09:48
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Please help with news about new DEM options

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 because it has a good 
overview map, the disadvantage is that you need to download every single tile 
manually and not in one big download. Maybe there are better alternatives?

-

Gerd wrote:

Hi all,

with r4093 I've merged the dem-tdb branch into trunk. I think it would be good 
to mention this in the
"Latest news" on [1] , maybe with one or two screen shots, but I have no idea how to 
write this "from a users view".
Do we need a how-to that describes the sources for hgt files and maybe more 
about the new options?
It would be great if somebody could help with that.

Gerd

[1] http://www.mkgmap.org.uk/
___
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

Re: [mkgmap-dev] Please help with news about new DEM options

2018-01-31 Thread Gerd Petermann

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


Von: mkgmap-dev  im Auftrag von 
osm@pinns 
Gesendet: Mittwoch, 31. Januar 2018 13:32
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Please help with news about new DEM options

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,53024

  Nick



On 31/01/2018 11:03, Gerd Petermann wrote:
> 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) ~ 3314
>
> It is quite obvious that the first value in dem-dists depends on the 
> resolution of the input hgt file(s).
> My understanding is that you might use a value near the hgt resolution or 
> maybe
> - if you want more precision and map size doesn't matter -
> half of it, so
> 3'' hgt means dem-dist ~ 9942 (or 9942/2 = 4971)
> 1'' hgt means dem-dist ~ 3314 (or 3314/2 = 1657)
> Since mkgmap now rounds these values to multiples of 16 you get
> 2^32/(1200*360) ~ 9942 -> 9936 rounded
> 2^32/(1200*360) / 2 ~ 4971 -> 4976 rounded
> 2^32/(3600*360) ~ 3314 -> 3312 rounded
> 2^32/(3600*360) / 2 ~ 1657 -> 1664 rounded
>
> These are the values for resolution 24.
> What still seems unclear is how you calculate the values for lower 
> resolutions.
> Up to now I see no reason to duplicate data with e.g. dem-dists=3312,3312,...
> but I see this in Arndts "Speichenkarte" which uses resolution 23 for level 1.
>
> I tried some different values on my Oregon 600 and I think the hill shading is
> not very useful on the device. Maybe that's the reason why the setting
> Map->Advanced Setup->Shaded relief->Auto
> means that hill shading is not used unless you zoom out to 5km?
>
> I also tried with only one or two DEM levels,
> e.g. --dem-dists=1664,3312 or just --dem-dists=3312
> It works, the device just uses the DEM from the basemap when you zoom out to 
> e.g. 500 m.
> The problem: The basemap has a very poor DEM resolution, so it looks wrong 
> when hills
> suddenly disappear while zooming out.
>
> My current compromise for high precision with 1'' hgt input and default style:
> 1664,9936,26512,53024
>
> Gerd
>
> 
> Von: mkgmap-dev  im Auftrag von lig 
> fietser 
> Gesendet: Mittwoch, 31. Januar 2018 09:48
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] Please help with news about new DEM options
>
> 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 because it has a good 
> overview map, the disadvantage is that you need to download every single tile 
> manually and not in one big download. Maybe there are better alternatives?
>
> -
>
> Gerd wrote:
>
> Hi all,
>
> with r4093 I've merged the dem-tdb branch into trunk. I think it would be 
> good to mention this in the
> "Latest news" on [1] , maybe with one or two screen shots, but I have no idea 
> how to write this "from a users view".
> Do we need a how-to that describes the sources for hgt files and maybe more 
> about the new options?
> It would be great if somebody could help with that.
>
> Gerd
>
> [1] http://www.mkgmap.org.uk/
> ___
> 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

Re: [mkgmap-dev] Please help with news about new DEM options

2018-01-31 Thread osm@pinns


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,53024

 Nick



On 31/01/2018 11:03, Gerd Petermann wrote:

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) ~ 3314

It is quite obvious that the first value in dem-dists depends on the resolution 
of the input hgt file(s).
My understanding is that you might use a value near the hgt resolution or maybe
- if you want more precision and map size doesn't matter -
half of it, so
3'' hgt means dem-dist ~ 9942 (or 9942/2 = 4971)
1'' hgt means dem-dist ~ 3314 (or 3314/2 = 1657)
Since mkgmap now rounds these values to multiples of 16 you get
2^32/(1200*360) ~ 9942 -> 9936 rounded
2^32/(1200*360) / 2 ~ 4971 -> 4976 rounded
2^32/(3600*360) ~ 3314 -> 3312 rounded
2^32/(3600*360) / 2 ~ 1657 -> 1664 rounded

These are the values for resolution 24.
What still seems unclear is how you calculate the values for lower resolutions.
Up to now I see no reason to duplicate data with e.g. dem-dists=3312,3312,...
but I see this in Arndts "Speichenkarte" which uses resolution 23 for level 1.

I tried some different values on my Oregon 600 and I think the hill shading is
not very useful on the device. Maybe that's the reason why the setting
Map->Advanced Setup->Shaded relief->Auto
means that hill shading is not used unless you zoom out to 5km?

I also tried with only one or two DEM levels,
e.g. --dem-dists=1664,3312 or just --dem-dists=3312
It works, the device just uses the DEM from the basemap when you zoom out to 
e.g. 500 m.
The problem: The basemap has a very poor DEM resolution, so it looks wrong when 
hills
suddenly disappear while zooming out.

My current compromise for high precision with 1'' hgt input and default style:
1664,9936,26512,53024

Gerd


Von: mkgmap-dev  im Auftrag von lig fietser 

Gesendet: Mittwoch, 31. Januar 2018 09:48
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Please help with news about new DEM options

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 because it has a good 
overview map, the disadvantage is that you need to download every single tile 
manually and not in one big download. Maybe there are better alternatives?

-

Gerd wrote:

Hi all,

with r4093 I've merged the dem-tdb branch into trunk. I think it would be good 
to mention this in the
"Latest news" on [1] , maybe with one or two screen shots, but I have no idea how to 
write this "from a users view".
Do we need a how-to that describes the sources for hgt files and maybe more 
about the new options?
It would be great if somebody could help with that.

Gerd

[1] http://www.mkgmap.org.uk/
___
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] "RE: Option --dem-profile seems to cause crash in "MapSource

2018-01-31 Thread cdavilam


			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, 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 option, so I think there still is a problem
in the encoder :-(
The interesting thing is that my route is far away from the polygon boundary.

I'll try to find out more ...

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] Option --dem-profile seems to cause crash in MapSource

2018-01-31 Thread Gerd Petermann

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 option, so I think there 
still is a problem
in the encoder :-(
The interesting thing is that my route is far away from the polygon boundary.

I'll try to find out more ...

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

Re: [mkgmap-dev] Please help with news about new DEM options

2018-01-31 Thread Gerd Petermann

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) ~ 3314

It is quite obvious that the first value in dem-dists depends on the resolution 
of the input hgt file(s).
My understanding is that you might use a value near the hgt resolution or maybe
- if you want more precision and map size doesn't matter -
half of it, so
3'' hgt means dem-dist ~ 9942 (or 9942/2 = 4971)
1'' hgt means dem-dist ~ 3314 (or 3314/2 = 1657)
Since mkgmap now rounds these values to multiples of 16 you get
2^32/(1200*360) ~ 9942 -> 9936 rounded
2^32/(1200*360) / 2 ~ 4971 -> 4976 rounded
2^32/(3600*360) ~ 3314 -> 3312 rounded
2^32/(3600*360) / 2 ~ 1657 -> 1664 rounded

These are the values for resolution 24.
What still seems unclear is how you calculate the values for lower resolutions.
Up to now I see no reason to duplicate data with e.g. dem-dists=3312,3312,...
but I see this in Arndts "Speichenkarte" which uses resolution 23 for level 1.

I tried some different values on my Oregon 600 and I think the hill shading is
not very useful on the device. Maybe that's the reason why the setting
Map->Advanced Setup->Shaded relief->Auto
means that hill shading is not used unless you zoom out to 5km?

I also tried with only one or two DEM levels,
e.g. --dem-dists=1664,3312 or just --dem-dists=3312
It works, the device just uses the DEM from the basemap when you zoom out to 
e.g. 500 m.
The problem: The basemap has a very poor DEM resolution, so it looks wrong when 
hills
suddenly disappear while zooming out.

My current compromise for high precision with 1'' hgt input and default style:
1664,9936,26512,53024

Gerd


Von: mkgmap-dev  im Auftrag von lig 
fietser 
Gesendet: Mittwoch, 31. Januar 2018 09:48
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Please help with news about new DEM options

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 because it has a good 
overview map, the disadvantage is that you need to download every single tile 
manually and not in one big download. Maybe there are better alternatives?

-

Gerd wrote:

Hi all,

with r4093 I've merged the dem-tdb branch into trunk. I think it would be good 
to mention this in the
"Latest news" on [1] , maybe with one or two screen shots, but I have no idea 
how to write this "from a users view".
Do we need a how-to that describes the sources for hgt files and maybe more 
about the new options?
It would be great if somebody could help with that.

Gerd

[1] http://www.mkgmap.org.uk/
___
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] Please help with news about new DEM options

2018-01-31 Thread lig fietser

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 because it has a good 
overview map, the disadvantage is that you need to download every single tile 
manually and not in one big download. Maybe there are better alternatives?

-

Gerd wrote:

Hi all,

with r4093 I've merged the dem-tdb branch into trunk. I think it would be good 
to mention this in the
"Latest news" on [1] , maybe with one or two screen shots, but I have no idea 
how to write this "from a users view".
Do we need a how-to that describes the sources for hgt files and maybe more 
about the new options?
It would be great if somebody could help with that. 

Gerd

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

Re: [mkgmap-dev] Style Manual

[mkgmap-dev] Style Manual

Re: [mkgmap-dev] Option --dem-profile seems to cause crash in MapSource

Re: [mkgmap-dev] Option --dem-profile seems to cause crash in MapSource

Re: [mkgmap-dev] Option --dem-profile seems to cause crash in MapSource

Re: [mkgmap-dev] Please help with news about new DEM options

Re: [mkgmap-dev] Please help with news about new DEM options

Re: [mkgmap-dev] Please help with news about new DEM options

[mkgmap-dev] "RE: Option --dem-profile seems to cause crash in "MapSource

[mkgmap-dev] Option --dem-profile seems to cause crash in MapSource

Re: [mkgmap-dev] Please help with news about new DEM options

Re: [mkgmap-dev] Please help with news about new DEM options

12 matches

Site Navigation

Mail list logo

Footer information