Wyoming

From OpenStreetMap Wiki
Jump to: navigation, search
Wyoming, United States
Latitude: (43.02, Longitude: -107.6
Browse Wyoming map
Edit map
External links:
Use this template for your city

Wyoming is a state in United States at latitude 43° 1′ 12″ North, longitude 107° 36′ 0″ West.

OpenStreetMap images (and underlying map data) are freely available under the OpenStreetMap License.

For information specific to the State of Wyoming

To Do

Highway relations

Most highways in Wyoming still need relations applied to them.

There are a number of US Highways that go through Wyoming. According to the Wyoming Wikipedia article, the U.S. highways that pass through the state are U.S. Highways 14, 16, 18, 20, 26, 30, 85, 87, 89, 189, 191, 212, and 287.

There are also quite a few WY State highways. The Wikipedia article State highways in Wyoming lists many of them. This may or may not be a complete list.

Relations for Interstates are here.

Relations for US numbered highways may be found here.

Relations for Wyoming state highways should be listed here.

If a relation isn't in the applicable list for a given highway, please add it to the list, or create it and add it to the list if it doesn't exist. State and Federal highways should use a single relation for each highway. If highway physically splits into two ways and separates the two directions (such as an Interstate), the same relation should be used for both directions, with a role indicating north/south or east/west (see Wyoming's I-80 for an example.) A single way may have more than one relation if it is signed for more than one highway, that is, if two or more highways overlap for a distance.

The Interstates and US highways should use relations specific to Wyoming: don't use a relation used for the same Interstate/Highway in a different state. Once super relations are supported, the separate relations will be easily related together into a single entity, and it keeps the relations' sizes more manageable.

Sources

Note, that Google Maps and other sources incompatible with the OSM license are often used as sources for this type of info in Wikipedia, so this information should not be used directly without verifying Wikipedia's listed sources as compatible. The TIGER import data will have US or state highway names for the relevant ways, and they should (at least mostly) all be set as Primary or Secondary roads already based on that. Basically, feel free to use Google Maps to help find the highways, but don't tag anything based on data from Google. See OpenStreetMap License for more information.

WYDOT does have a public domain highway map in PDF format available here. Being public domain, all information in the map may be used in OSM without restriction, meager as it is. There is also a WYDOT Reference Marker Book (Novemeber 2004) here and a Route Marker Book here. Neither one includes any indication of how they may be used, but there is a copyright notice on the website that may cover those publications here. And if you are feeling really adventurous, they have a Bicycle Route Map here.

Done

County Boundaries

Counties boundaries have been added to relations. See relation:boundary for more information about using relations for boundaries.

USGS data has been imported that includes county borders. Relations were added to these imported county borders.

The imported borders are not perfect. Along the Montana border, the imported county boundaries overlap into Montana, obviously not correct. Another (compatible) source is needed to verify which is correct, or someone needs to go there with a GPS unit and mark border signage.

All counties have had relations added. See the table below.

County Relation Tags

Wyoming county relations have have the following tags. They can be adjusted later if the need arises.

key value notes
key:type boundary
key:boundary administrative
key:admin_level 6 Per this page, 6 is a county in the US
key:name (county name) include the word "County". Example: Natrona County
key:is_in WY;WYO;Wyoming Some suggest also including US and United States, but that seems redundant to me. Some also consider key:is_in as deprecated, but nothing has replaced it.

Current County Relations

The actual relations, so if we do need to make any adjustments, or you want to zoom to a particular county, links are provided.

County County Seat License Plate # Relation Info County County Seat License Plate # Relation Info
Natrona Casper 1 Relation 288534 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Converse Douglas 13 Relation 288640 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Laramie Cheyenne 2 Relation 289323 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Niobrara Lusk 14 Relation 289328 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Sheridan Sheridan 3 Relation 288660 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Hot Springs Thermopolis 15 Relation 288536 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Sweetwater Green River 4 Relation 288625 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Johnson Buffalo 16 Relation 288636 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Albany Laramie 5 Relation 289325 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Campbell Gillette 17 Relation 288642 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Carbon Rawlins 6 Relation 288626 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Crook Sundance 18 Relation 289338 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Goshen Torrington 7 Relation 289327 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Uinta Evanston 19 Relation 289347 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Platte Wheatland 8 Relation 289324 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Washakie Worland 20 Relation 288535 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Big Horn Basin 9 Relation 289343 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Weston Newcastle 21 Relation 289335 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Fremont Lander 10 Relation 288533 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Teton Jackson 22 Relation 289189 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Park Cody 11 Relation 288537 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Sublette Pinedale 23 Relation 289191 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Lincoln Kemmerer 12 Relation 289194 (view, XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

License plate numbers are listed because I found it interesting. Any valid OSM use for those? Vehicle registration is handled by the counties in Wyoming. They use a common state-wide plate design, with the county plate number as the first digit or two of the license number. Driver's Licenses are handled by WYDOT's Driver Services. Basically, there is no "DMV" one-stop-shop for all vehicle and driving related issues.

Other

Town limit relations seem to be already done, perhaps as part of an import process or via script?

Intra-State Routing

WYDOT has a mileage chart available(Mileage Chart 2), with distances (in miles) between 38 Wyoming communities. If someone were feeling adventurous, one could use a routing service to use OSM data to find shortest routes, and compare it to the WYDOT chart. Any values that seem unreasonable could be investigated (or posted here to be investigated by someone else) to find the OSM errors (or WYDOT errors...?)

Find it, flag it, fix it

As with anywhere else, if you Find something you think may be wrong, Flag it. If you know how to resolve a flagged item, Fix it. You can skip the 'Flag it' step if you can Fix it. This is what OpenStreetMap is all about.

What else do you want...?

What else should be here about Wyoming that's not already available here or on Wikipedia?