Ohio: Difference between revisions

From OpenStreetMap Wiki
Jump to navigation Jump to search
(Cycle and transport maps)
(→‎Tagging suggestions for Ohio: No local mapper has used OH ### or US:OH ### in years)
Line 46: Line 46:
| <code>US ##</code> || US highways. || US 40
| <code>US ##</code> || US highways. || US 40
|- valign="top"
|- valign="top"
| <code>SR ##<br />OH ##<br />US:OH ##</code> || State routes. The shorter forms are more likely to be rendered in Mapnik. While the US:OH form is specific, it doesn't look great on maps or in directions, and that specificity can also be accomplished using route relations. || SR 13
| <code>SR ## || State routes. Do not use <code>OH ###</code> or <code>US:OH ###</code>. Ohio state routes can be distinguished from other state's routes using [[/Route relations/Networks|route relations]]. || SR 13
|- valign="top"
|- valign="top"
| <code>CR ##<br />C-##</code> || County routes. This probably should only be used for roads where the county route number is signed as clearly as on a state route; otherwise, consider putting this in loc_ref instead. The TIGER data often includes <code>name_1=County Highway <var>xx</var></code> in counties that signpost county routes. ||
| <code>CR ##<br />C-##</code> || County routes. This probably should only be used for roads where the county route number is signed as clearly as on a state route; otherwise, consider putting this in loc_ref instead. The TIGER data often includes <code>name_1=County Highway <var>xx</var></code> in counties that signpost county routes. ||

Revision as of 07:52, 10 September 2013

VTE
Ohio, United States
Wikidata

latitude: 40.25, longitude: -83
Browse map of Ohio 40°15′00.00″ N, 83°00′00.00″ W
Edit map
External links:
Use this template for your locality

Ohio is a state in the United States at latitude 40°15′00.00″ North, longitude 83°00′00.00″ West.

<slippymap lat="40.25" lon="-83" z="7" w="450" h="400" layer="mapnik" /> <slippymap lat="40.25" lon="-83" z="7" w="450" h="400" layer="cycle" /> <slippymap lat="40.25" lon="-83" z="7" w="450" h="400" layer="transport" />

Local Organization and Events

There is an idle OpenStreetMap meetup group for central Ohio. This group needs an organizer to schedule group meetings. Do you want to help lead the growth of OSM in Ohio? 17 group members are waiting for the next meeting.


Active mappers

Tagging suggestions for Ohio

Most of these examples are taken from the Cincinnati area, but feel free to add your own from elsewhere in the state:

Key Value Description Examples
highway motorway Interstate highways, including loops and spurs; significant portions of US and state routes built to Interstate standards (high-speed, fully access-controlled). I-71
I-275
Ohio Turnpike (I-76/80/90)
Ronald Reagan Cross County Highway (SR 126)
trunk Selected U.S. and state routes not built to Interstate standards. High-speed, limited-access, divided highways with at least two lanes in each direction. May have occasional traffic lights and unlit street-level crossings, but mostly controlled-access with on- and off-ramps. Two-lane undivided (but still limited-access) sections of Trunk might make sense if they are extensions of divided Trunk highway or Motorway. Appalachian Highway (SR 32)
Columbia Parkway (US 50)
Various Cincinnati viaducts
primary Other U.S. routes; major state routes, such as those that connect larger county seats not directly connected by US routes, or are important connectors between primary or higher roads. An example of which routes might be promoted to primary can be found here. Sections of primary roads generally should not "dead-end" at lower-class roads. US 22
US 40
SR 4
SR 309
secondary Other state routes; good connecting roads, such as those that connect cities not directly connected by state routes, or are important connectors between secondary or higher roads. Sections of secondary roads generally should not "dead-end" at lower-class roads. SR 48
Fra CR 3
tertiary County routes (signed or unsigned) and other major local roads, typically along section lines or connecting towns. Loveland–Miamiville Road (CR 75)
unclassified Rural roads, serving mostly farmland or forest properties, of little to no value as through routes.
residential City/neighborhood streets not qualifying as tertiary or higher, or rural roads which have become lined with houses.
ref I-## Interstate highways. I-71
I-670
US ## US highways. US 40
SR ## State routes. Do not use OH ### or US:OH ###. Ohio state routes can be distinguished from other state's routes using route relations. SR 13
CR ##
C-##
County routes. This probably should only be used for roads where the county route number is signed as clearly as on a state route; otherwise, consider putting this in loc_ref instead. The TIGER data often includes name_1=County Highway xx in counties that signpost county routes.
TR ##
T-##
Township routes. This probably should only be used for roads where the township route number is signed as clearly as on a state route; otherwise, consider putting this in loc_ref instead.
maxspeed 105
65 mph
Most rural and suburban motorways and trunks. I-270
97
60 mph
Some urban motorways and trunks.
89
55 mph
Most rural primary, secondary, tertiary roads. Some urban motorways and trunks. SR 605
80
50 mph
Some rural tertiary, unclassified roads. Some major urban and suburban roads.
72
45 mph
Some rural tertiary, unclassified roads. Many major urban and suburban roads.
64
40 mph
Some rural tertiary, unclassified roads. Many urban and suburban boulevards.
56
35 mph
Some rural unclassified roads. Many urban and suburban feeder roads.
48
30 mph
Some urban and suburban roads.
40
25 mph
Many urban, suburban, and residential streets.
32
20 mph
Some school service roads.
24
15 mph
Many urban alleys.
16
10 mph
Some private roads.
8
5 mph
Some private (especially unpaved) roads. Generally, "aisles" in parking lots.

Note that speed limits in OSM are typically specified in kilometers per hour. However, you can now tag speed limits in miles per hour instead:

maxspeed=25 mph

Just remember to use a space and lowercase the "mph" abbreviation. See United States roads tagging for more information.

Relations

Route relations

Some highways are moving from the old way-based tagging scheme to the new route relations. Each relation should have network and ref keys, as well as a symbol key with the URL to the SVG image found on the highway's Wikipedia article. If the entire route has the same name, the name key may also be specified on the relation.

For divided highways in Ohio, roles are entered when adding relations to the constituent ways. (Potlatch provides a small textbox on the relation line for entering roles.) The de facto standard in Ohio is to add roles corresponding to the signposted direction of each carriageway (i.e., north).

Interstate highways

Mark all member relations as network=US:I. Please keep this list synchronized with Interstate Highways Relations.

Number Super-relation Relation Status and notes
70 relation 943230 Complete in Ohio. One relation for both directions, with role=west/east.
71 relation 71019 Complete in Ohio. One relation for both directions, with role=north/south.
74 relation 1444077 Complete in Ohio, with role=east/west.
75 relation 71023 relation 332637 (northbound)
relation 332641 (southbound)
Complete in Ohio.
ALT 75 relation 2118037 Missing linkups to I-75 at both ends.
76 relation 933452 From Portage–Mahoning county line to near Boardman.
77 relation 1027749 From Marietta/WV border to Stark–Summit county line; from the junction with I-76 in Akron to the northern terminus in Cleveland. One relation for both directions, with role=north/south.
80 relation 294979 relation 396249 Complete in Ohio, but needs to be double-checked. One relation both ways; tagged with role=east/west.
90 relation 303058 relation 1217292 Complete in Ohio, but needs to be double-checked. One relation both ways; tagged with role=east/west.
270 relation 123301 Complete. One relation for both directions, with role=north/south/east/west as signed.
271 relation 165600 Complete. One relation for both directions, with role=north/south.
275 relation 70932 Complete. One relation covers both directions, with role=east/west/north/south as signed, from Cross County Hwy. east to KY state line.
277 relation 286177
280 relation 1690662
470 relation 1122162
471 relation 112436 Complete. One relation for both directions, with role=north/south.
475 relation 286175
480 relation 165671 Complete. One relation for both directions, with role=east/west.
490 relation 286190
670 relation 163715 Complete. One relation for both directions, with role=east/west as signed.
675 relation 1690667
680 relation 286180

U.S. Routes

Mark all member relations as network=US:US. Please keep this list synchronized with United States Numbered Highway Relations‎. If "status" is blank for a column, that probably means the relation is not yet used in Ohio.

Number Super-relation Relation Status and notes
6 relation 113181 From Sandusky–Erie county line to Huron. May need correction in Huron.
20 relation 112101 Partial in Lake and Cuyahoga counties
22 relation 70972 Complete in Ohio.
23 relation 164610 Scioto/Pike county line to Michigan border.
24 relation 121136 relation 331090 Complete in Ohio.
25 relation 271841 Complete. US 25 in Ohio is very short.
27 relation 189086 Complete in Ohio.
30 relation 120337 From Allen–Hancock county line to Wayne–Stark county line; from west of jct SR 11 to WV border.
30 ALT relation 207918 Complete (Dalton).
33 relation 164611 Complete in Ohio. Officially east/west in Ohio, despite odd number.
35 relation 165049 Complete in Ohio. Officially east/west in Ohio, despite odd number.
35 BUS relation 185772 Complete (Xenia).
36 relation 168035 From Urbana to east terminus in Uhrichsville.
40 relation 82010 Complete in Ohio.
42 relation 168032 From Ohio River to Richland–Ashland county line. role=north/south where appropriate, reflecting official direction despite even number.
50 relation 62152 Complete in Ohio, with role=west/east where appropriate.
50 TRUCK relation 1142913 Downtown Cincinnati to Columbia–Tusculum area.
50 BUS relation 189386 Complete (Athens), role=north/south (?).
52 relation 271863 From IN state line to Brown–Adams county line, with role=east/west per SLD.
62 relation 98372 From KY border to Navarre. Officially east/west in Ohio, but signage may vary.
68 relation 139077 Complete in Ohio. Officially north/south in Ohio, despite even number.
127 relation 184771 From Ohio river to Eaton.
223 relation 255177 (northbound)
relation 255178 (southbound)
224 relation 286224
250 relation 207792 From west terminus in Sandusky to north of Milan; Ashland–Wayne county line to Cadiz; west of Bridgeport to WV border. Use role=east/west where necessary.
322 relation 169092
422

Appalachian Development Highways

Mark all member relations as network=US:Corridor. Please keep this list synchronized with United States Numbered Highway Relations.

Corridor Relation Status and notes
B
B-1
C relation 165047 Scioto/Pike county line to north terminus at Columbus. One relation for both directions, with role=north/south.
C-1
D relation 114680 Complete in Ohio. One relation for both directions, with role=east/west.

Forest routes

Mark National Forest Development Routes as network=US:NFD and Forest Roads as network=US:USDA:Wayne.

State routes

Main article: /Route relations/State routes
OH-blank.svg

Mark all member relations as network=US:OH. Bannered routes like "ALT" can be tagged network=US:OH:Alternate and modifier=ALT for good measure. Ohio's Byways routes can be tagged network=US:OH:Byway.

County routes

County blank.svg

Mark all member relations as network=US:OH:ABC where ABC is the uppercase county abbreviation. (See map of abbreviations below.) Specifying the county is important, because Ohio counties use a wide variety of shield designs, not just those specified in the Ohio MUTCD.

If used, county route relations can potentially become very numerous. Since such route relations should be, by definition, confined to a specific county, finding out if a particular route relation exists and its extent shouldn't be too difficult in map editors. For these reasons, a table of county route relations is not included here.

A full listing of county, township, and city route networks is available at Ohio/Route relations/Networks.

U.S. Bike Routes

Main article: /Route relations/Bicycle routes#U.S. Bike Routes

Mark all member relations as network=ncn; state=proposed; operator=AASHTO. Please keep this list synchronized with WikiProject U.S. Bicycle Route System.

State bike routes

Main article: /Route relations/Bicycle routes#State bike routes
OH Bike 1.svg

Mark all member relations as network=rcn. The lettered routes below are designated by ODOT; tag them as operator=Ohio Department of Transportation. (Most other routes are maintained by county park districts. For such routes that cross county lines, tag the individual ways, not the relation.)

Boundary relations

Counties

County borders were originally supplied by the USGS. Those boundaries are not of great precision. Also, that import process created a lot of overlapping ways, and didn't use the admin_level=* key.

Much work has been done on the county boundaries. There is now a boundary relation for each county, and all county boundary ways have been split and merged as necessary so that only one chain of non-overlapping ways defines the boundary between any two adjacent counties. (Along Ohio's border, Ohio's county boundaries were merged with the TIGER-imported state boundary. Generally, the boundaries of counties in adjacent states have not been modified, and remain sourced from imprecise USGS data.)

There are still tasks to be done, however. Where county and city boundaries overlap, they should be merged; the merged boundaries should have admin_level=6, unless of course they're also part of the state boundary, which would be 4. The accuracy of the USGS-sourced boundaries can be improved, by following the endpoints of TIGER data or clues visible in the aerial imagery; these clues might include visible property lines, and especially natural waterways. Check USGS topo maps when in doubt.

A very important task pertaining to county boundaries is not about the boundaries themselves, though the work can be done at the same time other improvements to the boundaries are made. The TIGER dataset was imported county by county. As a result, roads that cross county lines aren't connected in the resulting OSM data. These should be joined by collapsing duplicate nodes. A little bit trickier is when a road follows a county line, it will be duplicated in OSM data. The road should be split where it joins or leaves the county line (if applicable) and then one copy of it deleted, then any duplicate nodes collapsed. Then, the county boundary should be made to follow the road by adding the road to the applicable counties' relations, adding appropriate boundary tags to the road's way, and connecting the rest of the county boundary to it. If this is done, there should not be a separate way parallel to the road representing the county line. This process might be called "TIGER welding".

Tasks and Progress
Code Name Relation Boundary Source* City Boundary Merging TIGER welding
ADA Adams relation 911255 KY = T; Bro, Hig, Pik, Sci = U
ALL Allen relation 911260 U
ASD Ashland relation 911247 U
ATB Ashtabula relation 350382 maritime = M; land PA = T; Tru, Gea, land Lak = U
ATH Athens relation 911269 U
AUG Auglaize relation 911251 U
BEL Belmont relation 911264 WV = T; Moe, Nob, Gue, Has, Jef = U
BRO Brown relation 163283 KY = T; Cle = Yt; Cli, Hig, Ada = U Cle
BUT Butler relation 104783 IN = T; Pre, Mot, partial War = U; partial War, Ham = Yt partial War, Ham?
CAR Carroll relation 911249 U
CHP Champaign relation 180915 Log, Uni, Mad, Cla = Yt; Mia, She = U Log, Uni, Mad, Cla
CLA Clark relation 180912 Chp, Mad, Gre = Yt; Mot, Mia = U Chp, Mad, Gre
CLE Clermont relation 104779 KY = T; Bro, Ham = Yt; War = U Complete Ham, Bro, KY
CLI Clinton relation 104780 Gre, Fay = Ty; Hig, Bro, War = U Gre, Fay
COL Columbiana relation 911253 PA, WV = T; Jef, Car, Sta, Mah = U
COS Coshocton relation 241687 Mus, Lic, Kno = Yt; Hol, Tus, Gue = U Mus, Lic, Kno
CRA Crawford relation 911262 U
CUY Cuyahoga relation 350381 maritime = M; land Lak, Gea, Sum, Med, land Lor = U
DAR Darke relation 911258 IN = T; Mer, She, Mia, Mot, Pre = U
DEF Defiance relation 911265 IN = T; Wil, Hen, Put, Pau = U
DEL Delaware relation 178339 YTt Fra Complete
ERI Erie relation 350378 maritime = MT; land Lor, Hur, land San = U Ott Ott?
FAI Fairfield relation 178391 Yt Complete
FAY Fayette relation 270616 Yt Complete
FRA Franklin relation 177915 YTt Mad, Del Complete
FUL Fulton relation 911263 MI = T; Luc = Yt; Hen, Wil = U Luc Luc
GAL Gallia relation 911268 WV = T; Law, Jac, Vin, Meg = U
GEA Geauga relation 911256 U
GRE Greene relation 104781 Yt Complete
GUE Guernsey relation 911270 U
HAM Hamilton relation 104784 KY = T; But, War, Cle, IN = Yt Complete Complete
HAN Hancock relation 911252 U
HAR Hardin relation 911267 Uni = Yt; Log, Aug, All, Han, Wya, Mar = U Uni
HAS Harrison relation 911248 U
HEN Henry relation 911257 Luc = Yt; Woo, Put, Def, Wil, Ful = U Luc Luc
HIG Highland relation 271300 Fay, Ros = Yt; Pik, Ada, Bro, Cli = U Fay, Ros
HOC Hocking relation 270614 Ros, Pic, Fai, Per = Yt; Ath, Vin = U Ros, Pic, Fai, Per
HOL Holmes relation 911250 U
HUR Huron relation 911254 U
JAC Jackson relation 911266 U
JEF Jefferson relation 911261 WV = T; Bel, Has, Car, Col = U
KNO Knox relation 185763 Cos, Lic, Del, Mrw = Yt; Ric, Asd, Hol = U Cos, Lic, Del, Mwr
LAK Lake relation 350372 maritime = M; land Atb, Gea, land Cuy = U
LAW Lawrence relation 911271 WV, KY = T; Sci, Jac, Gal = U
LIC Licking relation 178389 Yt Complete
LOG Logan relation 184059 Uni, Chp = Yt; She, Aug, Har = U Uni, Chp
LOR Lorain relation 350377 maritime = M; land Cuy, Med, Asd, Hur, land Eri = U
LUC Lucas relation 350384 land Ott, Woo, Hen, Ful, land MI = Yt; maritime = M Complete Complete
MAD Madison relation 177916 Yt Fra Complete
MAH Mahoning relation 911312 PA = T; Col, Sta, Por, Tru = U
MAR Marion relation 185761 Mrw, Del, Uni = Yt; Har, Wya, Cra = U Mrw, Del, Uni
MED Medina relation 911294 U
MEG Meigs relation 911311 WV = T; Gal, Vin, Ath = U
MER Mercer relation 911290 IN = T; Van, Aug, Dar = U
MIA Miami relation 911306 U
MOE Monroe relation 911293 WV = T; Was, Nob, Bel = U
MOT Montgomery relation 104782 Gre = Yt; War, But, Pre, Dar, Mia, Cla = U Gre
MRG Morgan relation 911302 U
MRW Morrow relation 185762 Kno, Del, Mar = Yt; Cra, Ric = U Kno, Del, Mar
MUS Muskingum relation 241688 Per, Lic, Cos = Yt; Gue, Nob, Mrg = U Per, Lic, Cos
NOB Noble relation 911300 U
OTT Ottawa relation 350380 land Luc = Yt; maritime = MT; land San, Woo = U Luc, Eri Luc, Eri?
PAU Paulding relation 911314 IN = T; Def, Put, Van = U
PER Perry relation 241689 Hoc, Fai, Lic, Mus = Yt; Mrg, Ath = U Hoc, Fai, Lic, Mus
PIC Pickaway relation 178392 Yt Complete
PIK Pike relation 911307 U
POR Portage relation 911288 U
PRE Preble relation 911259 IN = T; Dar, Mot, But = U
PUT Putnam relation 911301 U
RIC Richland relation 911309 U
ROS Ross relation 270615 Hig, Fay, Pic, Hoc = Yt; Vin, Jac, Pik = U Hig, Fay, Pic, Hoc
SAN Sandusky relation 911303 maritime = M; land Eri, Hur, Sen, Woo, land Ott = U
SEN Seneca relation 911297 U
SCI Scioto relation 911291 KY = T; Ada, Pik, Jac, Law = U
SHE Shelby relation 911292 U
STA Stark relation 911298 U
SUM Summit relation 911310 U
TRU Trumbull relation 911299 PA = T; Mah, Por, Gea, Atb = U
TUS Tuscarawas relation 911305 U
UNI Union relation 178021 Yt Complete
VAN Van Wert relation 911295 IN = T; Pau, Put, All, Aug, Mer = U
VIN Vinton relation 911308 U
WAR Warren relation 104778 Ham, partial But, Gre = Yt; partial But, Mot, Cli, Cle = U Ham, partial But
WAS Washington relation 911289 WV = T; Ath, Mrg, Nob, Moe = U
WAY Wayne relation 911304 U
WIL Williams relation 911287 IN, MI = T; Ful, Hen, Def = U
WOO Wood relation 911313 Luc = Yt; Ott, San, Sen, Han, Hen = U Luc Luc
WYA Wyandot relation 911296 U

*Boundary Sources:

  • U: USGS data import
  • M: USGS topographic map
  • T: TIGER data import (state/municipality borders)
  • Y: Yahoo! or other acceptable aerial imagery
  • t: Implied from non-boundary TIGER data

Cities

The TIGER city limits have been imported for Ohio. There are a few pre-existing, hand-drawn boundaries that should be merged with the new data:

The TIGER city limits import omitted the customary name:left=* and name:right=* tags on the ways that some renderers might potentially use to display both adjacent cities. Please consider adding them where appropriate. (To determine "left" and "right", imagine that the way is a oneway road and you are driving down that road.)

CDPs

In the city import process, census-designated places were included, which are not real cities; but just like actual cities, they were added with boundary=administrative and admin_level=8. They're just areas drawn arbitrarily for the Census for statistical purposes.

There seems to be agreement on talk-us that these shouldn't be tagged with boundary=administrative at all.

Clues that indicate a boundary might be a CDP is that it primarily follows roadway centerlines, and doesn't reflect well the actual boundaries of a community; that is, it might strangely omit houses on one side of the road, or it might include large chunks of farmland. One way to identify a CDP with certainty in Ohio is in its relation's tagging. The tiger:NAMELSAD tag will have the CDP's name with "CDP" added to the end. Wikipedia will also have an article on any CDP or municipality in Ohio, identifying whether or not it is a CDP. Finally, the Wikipedia article for each county in Ohio will have a section listing CDPs it contains, if any.

Since these CDPs do not relate to anything administrative, they should probably be stripped of their border=administrative and admin_level=8 tags. This should be done on the relation, and on the ways that make up the boundary (unless of course the ways are also parts of other administrative boundaries). The relation should retain its place=locality tag.

Counties with CDPs:

County CDP admin tags removed?
Ashtabula County yes
Athens County yes
Belmont County yes
Butler County yes*
Clark County yes
Clermont County yes
Columbiana County yes
Erie County yes
Fairfield County yes
Franklin County yes
Geauga County no
Greene County no
Hamilton County yes
Lake County no
Lawrence County no
Licking County yes
Lorain County no
Madison County yes
Mahoning County no
Montgomery County no
Muskingum County no
Pickaway County yes
Portage County no
Ross County no
Sandusky County no
Scioto County no
Stark County no
Summit County no
Trumbull County no
Warren County no
Washington County no

Counties without CDPs: Adams, Allen, Ashland, Auglaize, Brown, Carroll, Champaign, Clinton, Coshocton, Crawford, Cuyahoga, Darke, Defiance, Delaware, Fayette, Fulton, Gallia, Guernsey, Hancock, Hardin, Harrison, Henry, Highland, Hocking, Holmes, Huron, Jackson, Jefferson, Knox, Logan, Lucas, Marion, Medina, Meigs, Mercer, Miami, Monroe, Morgan, Morrow, Noble, Ottawa, Paulding, Perry, Pike, Preble, Putnam, Richland, Seneca, Shelby, Tuscarawas, Union, Van Wert, Vinton, Wayne, Williams, Wood, Wyandot

Notes:

  • *The CDP of South Middletown, in Butler County, seems to be missing.

County Abbreviations

ODOT has a system of 3-letter abbreviations for each county in Ohio. For most, the abbreviation is the same as the first three letters of the county name, but there are exceptions. These may be generally useful to us in a number of ways.

Ohio County Abbreviations.png

To do