| Ohio, United States|
|latitude: 40.25, longitude: -83|
|Browse map of Ohio 40°15′00.00″ N, 83°00′00.00″ W|
|Use this template for your city|
Ohio is a state in the United States at latitude 40°15′00.00″ North, longitude 83°00′00.00″ West.
See a comprehensive rundown of common OSM tags and Ohio-specific tagging recommendations and examples. Some city-level mapping portals:
- Bowling Green
- Cincinnati (including Northern Kentucky and Southeastern Indiana)
We use relations to represent complex features like routes and jurisdictional boundaries. There's a wealth of information at these two pages:
The default aerial imagery layers in iD and Potlatch are of high resolution but may be up to six years old, so check the vintage of an OSM feature before remapping it based on aerial imagery.
As of 2018, DigitalGlobe Standard and Mapbox imagery are the most up-to-date and highest-resolution imagery layers available in urban and suburban parts of Ohio, while Bing and DigitalGlobe are generally more up-to-date in rural areas. This table of corn mazes gives a good idea of the vintage of each aerial imagery layer by county. The Bing aerial imagery analyzer is another tool for determining Bing imagery vintage, although these days it only reports a very broad date range. Through the National Agriculture Imagery Program, Ohio has published aerial imagery from 2017, but it has very low resolution compared to Bing and Mapbox, and it isn't compatible with the online editors iD and Potlatch 2.
Mapillary covers major highways in much of the state, major roads in Columbus and the northeast, and every nook and cranny in north-central Ohio. OpenStreetCam has more recent coverage along the Interstates and has similar coverage of north-central Ohio.
OGRIP has created a public domain, high-precision dataset of centerlines and addresses for 75 counties as part of an E911 initiative. 
Active mapping communities have sprung up in some of Ohio's larger cities. Mappers in the Cleveland area have organized through Open Cleveland and Open Geo Cleveland. Organizing real-life meetups is a great to way to attract more mappers in your city!
- Main article: :Category:Users in Ohio
If you have questions, these mappers may be able to help you out. (Let everyone know where you like to contribute!)
- Bored – Mostly Akron, occasionally rural areas
- jwolter – Mostly Cleveland Southwest
- Mike_Sherman – Mostly North Eastern Ohio
- Minh Nguyễn – Greater Cincinnati, Greater Dayton, occasionally elsewhere in the west and south
- Nate_Wessel – Cincinnati and Northern Kentucky
- S_H – Mostly Columbus, Ohio
- skorasaurus – Cleveland and Cuyahoga County
- Stefan Bethke – Mostly between Zanesville and Marietta
- Vid the Kid – Mostly Central Ohio
- Johnny Mapperseed - Northern Ohio, especially near Lake Erie and Northwest Ohio.
- Doktorpixel14 - Northern Central Ohio, espacially Columbus, as well as Morrow and Richland County (not local)
Find non-wiki-using mappers using Who's around me? And be sure to subscribe to the talk-us mailing list, where the broader U.S. mapping community discusses tagging, imports, policy, evangelization, and more. If you have any questions, you can also ask on the
#ohio channel of the U.S. community's Slack workspace (invite yourself).
OpenStreetMap's coverage of Ohio may have started mid-2006, with an import of TIGER 2005 street data for the Greater Cincinnati Tri-State area in response to a request by Teratornis.  If the import did make it to Cincinnati, it was later purged due to widespread quality issues. Aside from that, Ohio was mostly blank, nothing but I-70 west of Columbus, I-75 north of Wapakoneta, the Ohio Turnpike west of Toledo, other Toledo highways, I-76 west of Youngstown, and the City of Berea.
In 2007, Dave Hansen and others imported the same street data that was previously requested (Greene County was imported twice). Yellowbkpk imported county lines from the USGS in 2008, and Chris Lawrence imported TIGER 2007 city limits the following year. USGS GNIS imports provided airfields in 2007 and various other points of interest in 2009.
Ohioans appear to have begun contributing to the map in 2008 and 2009. With help from out-of-staters, we've cleaned up all kinds of issues, such as outdated streets and overlapping county lines. In particular, NE2 added virtually all state and U.S. routes to route relations and cleaned up many railways throughout the state.
In 2012, students of GeodSciE 607 and Geography 688 at Ohio State made many improvements to the map. Later that year, a tweet comparing OSM's coverage of Bowling Green State to various commercial map services went viral. The global OSM community swarmed in, fully micromapping Bowling Green in a matter of days.
Since 2012, some students of GEO109 at the University of Kentucky have also helped map the Greater Cincinnati area.
In 2017, the Ohio Valley Regional Development Commission (OVRDC) imported sidewalks and crosswalks in their 12-county region.  Later that year, Miami University organized a mapathon to help the Humanitarian OSM Team map Puerto Rico following Hurricane Maria. The mapathon received coverage in the Cincinnati and Dayton press. 
- Statewide statistics
- Statistics about the Cincinnati metropolitan area, which extends into Kentucky and Indiana
OSM in the wild
Here are some statewide and regional items that need attention. Feel free to add your own:
- Clean up rural TIGER-imported roads. Thousands of private drives are tagged as residential streets. Many others simply don't exist, which is usually clear from the aerial imagery. Many were also clearly digitized at a small scale and need closer alignment with the large scale imagery. (Completed for Tuscarawas and Carroll Counties).
- Add landuses pretty much everywhere.
- Verify imported airport points.
- Complete Cuyahoga Valley National Park and start mapping Wayne National Forest.
- Sift through Mapillary street-level images for amenities and landmarks to map. Logo signs can help us figure out which gas station/restaurant is which.
- Add township lines.
- Merge city limits with county lines.
- "Weld" roads and rivers to county lines – but only where they actually run along county lines. (In particular, don’t weld anything to the Ohio River, because the law is based on its old northern bank.)
- Complete U.S. Bicycle Route 50 in Dayton.
- Identify more county and township route networks and add these routes to relations.
- Complete route relations for Appalachian Development Highways.
- Create route relations for USDA forest routes.
- Map more downtowns in glorious 3D. (See Cincinnati for an example.)
We use ODOT's three-letter county abbreviations for various purposes. For most counties, the abbreviation consists of the first three letters of the county's name, but there are exceptions.
Three-letter county abbreviations