OpenStreetMap data in HuntGrid
Some HuntGrid map layers are made from OpenStreetMap data, © OpenStreetMap contributors, under the Open Database License (ODbL). Here is exactly how we make each one, free.
What we offer
The ODbL asks anyone who publishes data made from OpenStreetMap to offer the result or the method that made it. We offer the method: the tag filters, the rules, the tools and their versions, and the date of the OpenStreetMap extract. With an extract of the same date, anyone can rebuild the same data. The whole list is also machine-readable (JSON), with each method file below. To get a copy of the data itself, email support@huntgrid.net: it's free.
Protected areas outside the US and Canada
- App
- HuntGrid Hunt ·
public-lands-osm - From
- OpenStreetMap: Geofabrik country extracts or the planet file
- Extract date
- the
versionofosm-protectedin our list of imported data (JSON), also in each tile file’s metadata
How it is made
- Every multipolygon tagged boundary=protected_area, boundary=national_park or leisure=nature_reserve, read with GDAL's OSM driver and osmconf.ini.
- Geometry made valid. Each area's country is the Natural Earth country (public domain) under a point on its surface; the US, Canada and their territories are left out (they use PAD-US and CPCAD).
- name, operator, ownership, protection_title or designation, access and hunting are mapped to our fields (osm.sql); nothing else is kept.
- Tiles: tippecanoe, zooms 4 to 14 (zooms 4 to 6 at a quarter of the detail), plus one label point per named area.
Method files
tools/geodata/public-land/osmtools/geodata/public-land/osmconf.initools/geodata/public-land/osm.sqltools/geodata/lib/common.shtools/geodata/lib/tiles-build
Tools: GDAL (ogr2ogr, OSM driver) 3.11.4, PostgreSQL 17 + PostGIS 3 17 / 3, tippecanoe 2.79.0
Places where hunting is usually not allowed (US and Canada)
- App
- HuntGrid Hunt ·
land-exclusions - From
- OpenStreetMap: Geofabrik extracts of the US and Canada
- Extract date
- the
versionofosm-exclusionsin our list of imported data (JSON), also in each tile file’s metadata
How it is made
- Multipolygons tagged as parks, gardens, playgrounds, golf courses, sports grounds, cemeteries, schools, colleges, hospitals, campgrounds, zoos, theme parks or residential, commercial and retail land (the -where filter in osm-exclusions, osmconf-exclusions.ini).
- Each becomes one kind (osm-exclusions.sql). Parks over 2,000 ha are left out: the official protected-area layers carry their real rules.
- Each area's state or province is the one under a point on its surface; only the states and provinces the extract fully covers are replaced.
- Tiles: tippecanoe, zooms 8 to 14, largest areas first.
Method files
tools/geodata/land-status/osm-exclusionstools/geodata/land-status/osmconf-exclusions.initools/geodata/land-status/osm-exclusions.sqltools/geodata/lib/common.sh
Tools: GDAL (ogr2ogr, OSM driver) 3.11.4, PostgreSQL 17 + PostGIS 3 17 / 3, tippecanoe 2.79.0
Tracks, paths, gates, stands, springs, shelters and parking
- App
- HuntGrid Hunt ·
outdoor-osm - From
- OpenStreetMap: Geofabrik extracts or the planet file
- Extract date
- the
versionofosm-outdoorin our list of imported data (JSON), also in each tile file’s metadata
How it is made
- Planetiler reads the OpenStreetMap file with the custom schema outdoor.yml: which tags make each feature, the attributes kept and the zoom each appears at are all in that one file.
- No other data is added; the tiles are written straight from the schema.
Method files
Tools: Planetiler 0.9.2
Tracks, trails and riding routes (unofficial)
- App
- HuntGrid Offroad ·
offroad-osm - From
- OpenStreetMap: Geofabrik state, province and country extracts
- Extract date
- the
versionofosm-offroadin our list of imported data (JSON), also in each tile file’s metadata
How it is made
- Ways: highway=track (zoom 10 and up), highway=path or bridleway (zoom 12 and up), highway=service without a service=* subtag, and highway=unclassified when its surface is unpaved or it has a tracktype (zoom 11 and up), read by Planetiler with offroad-osm.yml.
- Only these tags are kept on a way: highway, name, ref, access, motor_vehicle, motorcar, motorcycle, atv, ohv, snowmobile, 4wd_only and the :conditional of each, smoothness, surface, tracktype, width, maxwidth, trail_visibility, ford, operator and designation.
- Routes: route=atv, route=snowmobile and route=mtb relations and ways, and ways tagged piste:type=snowmobile (route snowmobile), read with GDAL's OSM driver and osmconf-offroad.ini; route, name, ref, network and operator are kept.
- Places, from zoom 12: amenity=fuel (with its fuel:* kinds and opening hours), amenity=charging_station, toilets and drinking_water, tourism=camp_site and camp_pitch, highway=trailhead, and amenity=parking tagged hgv or trailer; nodes as points, areas as a point on their surface; name, operator, brand, opening_hours, access, fee, capacity, hgv, trailer and the fuel:* kinds are kept, and backcountry, ref and tents on camp sites and toilets:disposal on toilets (offroad-osm.yml).
- Tiles: Planetiler for the ways and places and tippecanoe for the routes, zooms 10 to 14, joined into one file with tile-join; the launch regions' files are joined the same way (build-launch, join); nothing else is joined in.
Method files
tools/geodata/offroad-osm/buildtools/geodata/offroad-osm/offroad-osm.ymltools/geodata/offroad-osm/routestools/geodata/offroad-osm/osmconf-offroad.initools/geodata/offroad-osm/build-launchtools/geodata/offroad-osm/join
Tools: Planetiler 0.9.2, GDAL (ogr2ogr, OSM driver) 3.11.4, tippecanoe 2.79.0
Routing graph of roads and tracks, with fuel and charging points (unofficial)
- App
- HuntGrid Offroad ·
offroad-graph-osm - From
- OpenStreetMap: Geofabrik state, province and country extracts, or the North America file
- Extract date
- the
versionofosm-offroad-graphin our list of imported data (JSON), also in each tile file’s metadata
How it is made
- Ways: highway=track, unclassified, service (not driveways or parking aisles), residential, tertiary, secondary, primary and trunk, highway=path only with a motor-vehicle tag, a width or a tracktype, and piste:type=snowmobile; ways tagged access=private or no without a vehicle tag that opens them are left out. Read with GDAL’s OSM driver and osmconf.ini, clipped to the build’s box (build-osm).
- Each way gets a state per vehicle class (yes, no or untagged) from its access, vehicle, motor_vehicle, motorcar, ohv, atv, motorcycle, snowmobile, 4wd_only and electric_bicycle tags, a public-road flag, surface, smoothness, tracktype, width, oneway, ford (its own tag or a ford node on it), a flag when a *:conditional restriction applies, name, ref and way id (osm_graph.py).
- Ways are cut into edges at the vertices they share and at their ends, with ends under 1 m from another way joined to it (noding.py); each edge gets its length and its climb from the Mapterhorn elevation model (elevation.py). Nodes are keyed by their coordinate on a 1e-5 degree grid.
- Points: amenity=fuel (name, brand and the fuel:* kinds tagged yes) and amenity=charging_station.
- Tiles: tippecanoe at zoom 11 only, layer e (edges, whole in every tile they touch, nothing simplified or dropped) and layer p (points), in their own file (tiles.py); never joined with other data.
Method files
tools/geodata/offroad-graph/build-osmtools/geodata/offroad-graph/osmconf.initools/geodata/offroad-graph/osm_graph.pytools/geodata/offroad-graph/graphs.jsontools/geodata/route-graph/lib/noding.pytools/geodata/route-graph/lib/nodeid.pytools/geodata/route-graph/lib/elevation.pytools/geodata/route-graph/lib/tiles.pytools/geodata/route-graph/lib/graphs.py
Tools: GDAL (ogr2ogr, OSM driver) 3.11.4, tippecanoe 2.79.0
Portages, canoe and hiking routes, rapids and fire pits (unofficial)
- App
- HuntGrid Backcountry ·
backcountry-osm - From
- OpenStreetMap: Geofabrik state, province and territory extracts
- Extract date
- the
versionofbackcountry-osmin our list of imported data (JSON), also in each tile file’s metadata
How it is made
- Portages: ways tagged portage=yes or designated, or canoe=portage (zoom 10 and up); name, ref, sac_scale, trail_visibility, surface and access are kept. Read by Planetiler with backcountry-osm.yml.
- Water, from zoom 11: waterway=rapids and waterfall, and anything tagged whitewater=*; nodes as points, areas as a point on their surface, whitewater ways as lines; waterway, whitewater, whitewater:rapid_grade, whitewater:section_grade and name are kept.
- Fire pits, from zoom 13: leisure=firepit, nodes as points and areas as a point on their surface, with name and access.
- Routes: route=canoe, hiking and foot relations, read with GDAL's OSM driver and osmconf-backcountry.ini; route, name, ref, network and operator are kept.
- Tiles: Planetiler for the portages, water and fire pits and tippecanoe for the routes (zooms 8 to 14), joined into one file with tile-join; the regions' files are joined the same way (build-all, join); nothing else is joined in.
Method files
tools/geodata/backcountry-osm/buildtools/geodata/backcountry-osm/backcountry-osm.ymltools/geodata/backcountry-osm/routestools/geodata/backcountry-osm/osmconf-backcountry.initools/geodata/backcountry-osm/build-alltools/geodata/backcountry-osm/jointools/geodata/backcountry-osm/registertools/geodata/backcountry-osm/apply_sql.py
Tools: Planetiler 0.9.2, GDAL (ogr2ogr, OSM driver) 3.11.4, tippecanoe 2.79.0
Used as published
These come from OpenStreetMap through other projects and we don’t change the data:
- The basemap (roads, water, places, terrain labels) and offline basemaps: OpenFreeMap's weekly planet build (OpenMapTiles schema), served as published
- Place search: Photon with GraphHopper's published OpenStreetMap search index, unchanged
Licence
This data is © OpenStreetMap contributors and available under the Open Database License 1.0. The tiles we make from it are under the same licence, and each one says so in its own metadata.