Grand Canyon National Park
|Part of WikiProject United States.|
|Grand Canyon National Park, Arizona, United States|
|latitude: 36.3099, longitude: -112.7835|
|Browse map of the Grand Canyon National Park 36°18′36″ N, 112°47′01″ W|
|Use this template for your city|
|OpenStreetMap images (and underlying map data) are freely available under the OpenStreetMap License.|
- 1 Boundary
- 2 Roads and Tracks
- 3 Trails
- 4 Manmade Features
- 5 Natural Features
- 6 Wikipedia Integration
- 7 See also
- 8 External Links
Roads and Tracks
Apart from the AZ 64 and many of the roads of the Grand Canyon Village, almost all of the forest service roads and other tracks have been unreviewed since the Tiger import in 2007. Many of the tracks are either mapped incorrectly or don't exist at all. A lot of work to be done here.
Sources of data include
- Kaibab National Forest quad maps
- Tiger 2012 and satellite imagery
- Ground surveys of tracks that are open to the public.
The aim of this project is to map all of the official hiking trails listed in the Wikipedia entry.
Within the Grand Canyon, OSM data is already, I think, superior to other online maps in coverage and accuracy (Google is particularly poor here). There are a number of ways we can enhance the usefulness of OSM to mappers and hikers in the future;
- Much greater use of trail_visibility=* and tracktype=* (or surface=*) tags on ways
- Using sac_scale=*, incline=* tags on ways, and ascent=*, descent=* on relations to indicate relative difficulties of the trails.
- Upgrading the official trails to relations (nearly complete, see below)
Trails within the canyon itself are closed to bicyles and motorbikes, so the ways representing trails should be tagged;
See Hiking for possible tagging of hiking trails.
Ultimately we're aiming to represent all the trails as a set of relations. This has several advantages over a way-based approach;
- Solves the problem of how to describe different trails using the same way. The main example here is the Arizona Trail, which marches straight through the corridor over the North and South Kaibab trails.
- Enforces an end to end consistency in a trail - with relation analysis tools it's immediately obvious if a trail is gappy or incomplete.
- Enables apps and renderers to easily pick out entire trails or sets of trails to provide for; highlighting trails on maps, distance calculations, altitude profiles etc.
- Let's you download gpx files for entire trails - particularly useful for more off the beaten track hikers.
Currently the following tag schema is used for these relations;
- name=* (the full name of the trail)
- ref=* (a 3 to 5 letter short version of the name)
- operator=United States National Park Service
Optional tags can be added for wikipedia or other web entries. See Walking Routes for further ideas on how to tag hiking relations.
|Bright Angel Trail|
|North Kaibab Trail|
|Plateau Point Trail|
|South Kaibab Trail||
|Clear Creek Trail|
|Dripping Springs Trail|
|Thunder River Trail||Incomplete - Tapeats Creek section missing|
|Bill Hall Trail||Complete|
|Deer Creek Trail|
|Havasu Canyon Route|
|Kanab Creek Trail|
|Lava Falls Trail|
|North Bass Trail||Underlying way based on gpx which looks a bit dodgy in places. Needs refining.|
|New Hance Trail (Red Canyon Trail)|
|South Bass Trail||Complete. Tracks and roads from Grand Canyon Village to South Bass trailhead need reviewing.|
|South Canyon Trail|
|Tonto Trail||Entire trail from Garnet Canyon to Red Canyon measures out as 131 km (81 miles) - longer than any published figure (Wikipedia reckons 70 miles). Problem?|
|Royal Arch Route|
|Bright Angel Point Trail||Complete|
|Cape Final Trail||Complete|
|Cape Royal Trail||Complete|
|Cliff Spring Trail||Complete|
|Fire Point Trail|
|Francois Matthes Trail|
|Ken Patrick Trail||Large section missing|
|Komo Point Trail|
|Rim Trail||Incomplete - Village to Pima Point only|
|Tiyo Point Trail|
|Transept Trail||Slightly unclear where the northern trailhead is (in the Transept campground), otherwise complete|
|Uncle Jim Trail|
|Walhalla Glades Trail|
|Walhalla Spur Trail|
Water sources, emergency telephones, campgrounds, ranger stations, toilets, parking and trailheads. Also the buildings and facilities in the North Rim, Grand Canyon Village and Desert View.
Mountains, rivers, valleys, waterfalls, springs, minor canyons, rock formations and other points of natural interest.
There is currently some discussion in the OSM community about the tagging of dry rivers, but until there's a consensus this project is using the following schema;
Dry creeks, washes, arroyos and other dry stream beds should be tagged;
Though it's a moot point when applied to dry rivers, according to OSM guidelines a river becomes a stream if 'it can be jumped across by an active, able-bodied person', or roughly less than 2 meters in width.
The latest Tiger 2014 data has a comprehensive and reasonably accurate set of line data for waterways in Coconino county which can be used as a guide for tracing creeks or imported directly. A few points;
- Some of the data points are very dense - simplify ways with excessive nodes before uploading into OSM
- There is naming information in the Tiger data (the FULLNAME tag), but this is incomplete, uses abbreviations (crk instead of creek) and sometimes incorrect. Check and correct all names against other sources, e.g. the USGS Topographic Maps layer in JOSM
- There are still some errors in the Tiger data - at a minimum all new waterways should be visually checked against Bing imagery before uploading. In particular the direction of water flow is often incorrect.
To make the map more useful and expose it to a wider audience, any relevant object in the map should be linked to its corresponding Wikipedia article. Just add a wikipedia=* tag to the node, way or relation and reference the relevant wikipedia article - use the URL for the article after the final forward slash. The WIWOSM preferred format is; wikipedia=lang:article
and the relevant tag is;