Am 15.02.2010 12:02, schrieb Felix Hartmann: > Okay here are my results (actually the same as with gmaptool, I did not > notice that "how" profile can be shown). > > 1.Only normal map without contourlines: > Mapsource/Basecamp "show profile" is greyed out. > > 2. Only contourline map: > Working in both: Mapsource 6.13.6, 6.15.11 as well as Basecamp 2.0.8 > > 3. Mixed map made out of .img with osm mapt data and .img with > contourlines (joined using: java -ea -jar -Xmx512M mkgmap.jar --index > --description=%srtm% --route --country-abbr=%abr%_srtm > --country-name="%date%_srtm" --mapname=%FID%0000 --family-id=%FID% > --product-id=1 --series-name=%srtm% --family-name=%srtm% --tdbfile > --overview-mapname=mapset --area-name=%country% 6*.img 7*.img :) > Mapsource 6.13.6 on clicking on "show profile" empty profile comes up. > Mapsource 6.15.11 clicking on "show profile": crash > Basecamp: Clicking on elevation profile: Message "The current map does > not contain any elevation data on the selected route". > > 4. Normal map including contourlines (contourlines as osm file merged > with normal osm file using osmosis): > Profile working in Mapsource/Basecamp. This is a lot of work and time. > Also not legally possible with srtm data from viewfinderpanoramas.org. > > > > Is anyone able to get 3. working (without loosing autorouting)?? Does > the patch have any effect on the .img (if so I would try to recompile my > .img contourlines) > Currently I need to seperate installs: > Meaning both map as described and 2. and 3. I calculate my route on 3., > then switch to contourline only map, and now clicking on show profile > (only in Mapsoruce 6.15.11/Basecamp, not however in 6.13.x) a nice > profile is shown. In Mapsource 6.13.6 I am not able at all to get a > profile shown. (have not yet tried on GPS, but I think map as described > under 3. would work for both autorouting and profile).
There is no change to the img files. I tryed scenario 3. and got the same problems. I think MapSource gets confused having two img's for the same area. Knowing this scenaro its required to have an option to turn it off. Until now I created my maps as described in 4. But using a fix areas.list from splitter so I had not to rebuild contour lines osm again and again. Actually I am working on the integrated contour line feature of mkgmap. It failed if a map didn't fit in a single DEM data file (SRTM, CGIAR or ASTER). For SRTM data I am now able to cover larger areas. The time went up from around 1.5 hours for my germany generation to 2 hours not counting the time previously required to generate and merge elevation osm with srtm2osm and osmosis. So this approach seems to be not slower and saves disk space. _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
