OpenHikingMap

From OpenStreetMap Wiki
Jump to navigation Jump to search

This is the official OpenHikingMap (OHM) map documentation page, a Free Software mapnik 3+ style based on data from the OpenStreetMap project, I (sly) am working on, specifically designed for hikers. It features contour lines, hiking paths, mountain tracks, natural reserves, moutain huts, peaks, viewpoint, springs and so on... (See full list of rendered features further down)

There is a freely accessible raster TMS service using this style, please check the about page of the OpenMaps service for more information.


 Open bug tracker
OpenHikingMap
Slippy map: openmaps.fr
Source code: https://github.com/sletuffe/OpenHikingMap

History

The first usable version was online around november 2008 but developpement of the style has almost stalled between 2013 and 2018. But in 2020 I have a new hope for improvement by incorporating OpenTopoMap additions. In 2024 and 2025 I mainly cleaned the xml code without significant improvements. But despite a tons of ideas I have, I'm still missing a strong enough server, some help ! or free time to improve the update frequency, the display of moutain ranges, peaks prominence and so on...

Can it be used freely in another website/application ?

It was meant for that. However, there are no guarantees : the service might stop any time, or I might block IP or web site if there are too much requests. If you include tiles from tile.openmaps.fr in your project, you must accept and respect the Tile usage policy where you will also find the TMS URL.

Questions/Suggestions/bug reports/contributions

Ideas, and contributions to this style are very welcome, please use the OpenHikingMap Github issue tracker or, if you don't have an account on github, you can use Talk:OpenHikingMap

Warning : If you want to report problems or have questions about the tile.openmaps.fr tile service (outage, slow, unavailable) please use the github OpenMaps tracker

Coverage

Since 2020-01-15 it covers the world. Zoom levels are available from 0 to 18

Map Legend

  • sac_scale=* is used with 3 levels (nothing-t1-t2 or t3-t4 or t5-t6). smaller the dash are, harder it is !
  • trail_visibility=* is used with 2 levels (below intermediate or over bad) (red and some sort of pink/salmon )
  • smoothness=* is used on tracks only. Support for use by unknown, cars ("bad" with 2 parallel lines), off roads vehicle ("very_bad" 1 line parallel with dashed line) , off highway vehicles ("horrible" and "very_horrible" with 2 parallel dashed lines)
  • using highway=path path is rendered the same as footway in my styles
  • highway=via_ferrata is rendered as black crosses looking like a chain
  • boundary=protected_area is rendererd with a green border for protect_id 1 to 4
  • Contours, hillshading and elevation color was composed and kindly provided by User:Yvecai from the OpenSnowMap project and based on :
    • ASTER GDEM is a product of METI and NASA
    • SRTM 1 Arc-Second Global
    • EU-DEM: Prroduced using Copernicus data and information funded by the European Union
    • France – RGE ALTI® 5m © IGN
    • Switzerland – Alti3D © swisstopo
    • US & Canada – NED 1arcsec U.S. Geological Survey
    • Austria – DHM 10m - CC-BY-4.0: Land Kärnten - data.gv.at
    • Italy – Tinitaly 10m – CC BY 4.0 Tarquini S., I. Isola, M. Favalli, A. Battistini, G. Dotta (2023). Istituto Nazionale di Geofisica e Vulcanologia (INGV).
    • Norway - DTM 10 Terrengmodell (UTM33) – CC BY 4.0 Kartverket

WARNING Data elevation model is approximative and may be wrong in mountains by a hundred meters, do not use it to place summits and do not trust it too much !

Map legend 2 (in construction...)

Map reprensentation meaning and link for more information
path=* of unspecified difficulty or T1/T2 (see sac_scale=*)
path=* with T3/T4 difficulty (see sac_scale=*)
X Y
X Y
X Y
X Y
X Y
X Y
X Y
X Y
X Y
X Y

Is the wiki really the best tool for creating a map legend ? just wondering...

Frequently asked Questions

Garmin version ?

No, there isn't. Having a apache/tirex/mapnik/postgresql/osm data rendering stack is very different from having offline maps in a garmin, I don't plan on maintaining a Garmin version of this map

Off line version ?

See "usage policy" up here, it is possible, but since there are limits for downloads you will only be able to collect small areas.

Why are datas updated so rarely ?

Indeed, the data from OpenStreetMap are re-imported manually every two years or so. And it is not by choice, but by constraint : My server's storage are rotative disks and the whole import process takes around 3 weeks... (yes, you read it well, that is a 3 consecutive weeks non stop import !) During that time the server is disk I/O saturated and all others operations on it are slown down as hell. And that is why I rarely update datas. To give perspective, when I had access to large enough NVMe drives, the exact same process took around 20 hours. sletuffe (talk) 13:39, 12 December 2024 (UTC)

See also