Re: Worldwide routable Garmin maps: URL REMOVED

Lambertus wrote:

As I understand, from the discussion between you and Kukuk above, the creation of the ready-to-use tiles is a bit tricky. I'm thinking of using Phyghtmap for downloading the data in large PBF chunks, merge the osm files with Osmosis into a planet and then use Splitter to create suitably sized tiles. Can you or Kukuk tell me if this could work? What are the pitfalls?

The number of nodes, or better you will run out of IDs. With the west part of the USA I run already out of node IDs because of a 32bit signed tile splitter bug. The bug is meanwhile fixed, but this only means you will run into the problem again later. And this without merging the SRTM data with the OSM data, starting with node ID=1.
The other problem is, that 8GB of main memory are already critical for the US alone.

A few specific questions:
- What is a useful interval of the contour lines, 20 or perhaps 50 meters?

Depends on the density in the area, in some areas 10 meters are a good value, in others 50. But I haven't found a good way to find out when to use which interval.

- What base ID should be used for the nodes and ways?

If you want to merge with OSM data: I don't know, Else start with 1.

- Is incorporating viewfinderpanorama data useful?

Yes, I can only recommend to prefer that data. The NASA data for europe has quite some "holes".

- I found this wiki page that describes how to properly process the SRTM data. Seems quite complex to me, is it necessary?

Yes and no. I have implemented the --max-nodes-per-way option for phyghtmap some time ago and I use it with "--max-nodes-per-way=250". This should prevent this artefacts. If you still see such artefacts, lower the number even more.

Thorsten