Re: [mkgmap-dev] elevation contours, wrong values

2011-01-19 Thread garvanmaew
On Tue, 2011-01-18 at 21:46 +0100, Henning Scholland wrote:
 Hi,
 in the resulting osm-file are all values correct. Eg. the
 elevationline for 20m is tagged with ele=20. Also this line is
 displayed there elevation is 20m. But this line is named as 6m.
 
 srtm2osm-call should be correct. It creates metric values unless you
 set -foot, what I haven't done.
 
 MapSource use also metric system.
 
 Henning

Assuming there is no bug in mkgmap, you should check your style file.
GARMIN store elevation heights internally in feet, so the meters must be
converted to feet by mkgmap, following settings in the style file. Form
your post it would appear that this is not happening.

I have only used contours with polish format input. With polish format
you need to add elevation=M in the header portion of the mp file to tell
mkgmap you are using meters. From what I can see this is handled by the
style file for OSM input.

Garvan


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


Re: [mkgmap-dev] elevation contours, wrong values

2011-01-19 Thread Henning Scholland
Thanks a lot, this was the hint I needed. Works now very well.

Henning

Am 19.01.2011 13:28, schrieb garvanmaew:
 On Tue, 2011-01-18 at 21:46 +0100, Henning Scholland wrote:
 Hi,
 in the resulting osm-file are all values correct. Eg. the
 elevationline for 20m is tagged with ele=20. Also this line is
 displayed there elevation is 20m. But this line is named as 6m.

 srtm2osm-call should be correct. It creates metric values unless you
 set -foot, what I haven't done.

 MapSource use also metric system.

 Henning
 Assuming there is no bug in mkgmap, you should check your style file.
 GARMIN store elevation heights internally in feet, so the meters must be
 converted to feet by mkgmap, following settings in the style file. Form
 your post it would appear that this is not happening.

 I have only used contours with polish format input. With polish format
 you need to add elevation=M in the header portion of the mp file to tell
 mkgmap you are using meters. From what I can see this is handled by the
 style file for OSM input.

 Garvan


 ___
 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] elevation contours, wrong values

2011-01-18 Thread Henning Scholland

Hi

I have an problem with the values of my elevation contours.
They where created by srtm2osm. After processing them with mkgmap, I 
opened the resulting map with MapSource, but the values are to little by 
factor ~3.3. The ele-values were retagged to name.


I think MapSource or mkgmap take my metric values as foot-values and 
transfer them to metric system. After splitter the values where correct 
in metric system.


Is this a mkgmap-bug or is it a Garmin-thing and I have to input 
foot-values?


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

Re: [mkgmap-dev] elevation contours, wrong values

2011-01-18 Thread Felix Hartmann
You have to give proper commands to srtm2osm. This has nothing to do 
with mkgmap.


On 18.01.2011 21:17, Henning Scholland wrote:

Hi

I have an problem with the values of my elevation contours.
They where created by srtm2osm. After processing them with mkgmap, I 
opened the resulting map with MapSource, but the values are to little 
by factor ~3.3. The ele-values were retagged to name.


I think MapSource or mkgmap take my metric values as foot-values and 
transfer them to metric system. After splitter the values where 
correct in metric system.


Is this a mkgmap-bug or is it a Garmin-thing and I have to input 
foot-values?


Greets,
Henning


___
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] elevation contours, wrong values

2011-01-18 Thread Ronny Klier
Am 18.01.2011 21:17, schrieb Henning Scholland:
 Hi

 I have an problem with the values of my elevation contours.
 They where created by srtm2osm. After processing them with mkgmap, I
 opened the resulting map with MapSource, but the values are to little by
 factor ~3.3. The ele-values were retagged to name.

 I think MapSource or mkgmap take my metric values as foot-values and
 transfer them to metric system. After splitter the values where correct
 in metric system.

 Is this a mkgmap-bug or is it a Garmin-thing and I have to input
 foot-values?

 Greets,
 Henning


Did you verify that MapSource uses meter as unit for elevation?

I also remember that you could specify some option on srtm2osm to define 
which unit to use.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


Re: [mkgmap-dev] elevation contours, wrong values

2011-01-18 Thread Henning Scholland

Hi,
in the resulting osm-file are all values correct. Eg. the elevationline 
for 20m is tagged with ele=20. Also this line is displayed there 
elevation is 20m. But this line is named as 6m.


srtm2osm-call should be correct. It creates metric values unless you set 
-foot, what I haven't done.


MapSource use also metric system.

Henning

Am 18.01.2011 21:36, schrieb Felix Hartmann:
You have to give proper commands to srtm2osm. This has nothing to do 
with mkgmap.


On 18.01.2011 21:17, Henning Scholland wrote:

Hi

I have an problem with the values of my elevation contours.
They where created by srtm2osm. After processing them with mkgmap, I 
opened the resulting map with MapSource, but the values are to little 
by factor ~3.3. The ele-values were retagged to name.


I think MapSource or mkgmap take my metric values as foot-values and 
transfer them to metric system. After splitter the values where 
correct in metric system.


Is this a mkgmap-bug or is it a Garmin-thing and I have to input 
foot-values?


Greets,
Henning


___
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