Cuyahoga County Planimetric Geospatial Data

Conversion To Latitude/ Longitude Coordinate System

In ArcInfoTM and MapInfoTM Formats

nodis.gif (34156 bytes)

The Northern Ohio Data & Information Service (NODIS) in The Urban Center of the Maxine Goodman Levin College of Urban Affairs at Cleveland State University are making available a series of geospatial data sets of 18 planimetric data layers for Cuyahoga County and two miles outside the county border.

The data layers are:

roads walls
road names driveways
building footprints bridges
railroads interstates
2 foot elevation contours recreation areas
10 foot elevation contours trees
10 foot elevation labels dense trees
spot elevations cities
water county

 

The methodology used to convert data from its original format to a latitude/ longitude coordinate system and to ArcInfoTM and MapInfoTM formats(1) is described below.

 

Background

The data in these files represent all lines, polygons, and text as seen on selected planimetric layers from digital orthophotographs. They were developed from files supplied originally by the Cuyahoga County Engineer's Office in .dwg (AutoCADTM) format. The Cuyahoga County Engineer contracted Aerocon Photogrametric Services Inc. to create digital orthophotographs and to develop these files in AutoCADTM file format. The AutoCADTM files are used by the Cuyahoga County Engineer for project-specific engineering work. The files are current as of March 1993.

In order to make these data useful to other users of Geographic Information Systems (GIS), three obstacles had to be overcome. First, the County’s files were developed using the Cleveland Regional Geodetic Survey (CRGS) as the coordinate system. This coordinate system is locally unique and prevents other potential users of the data to overlay (combine and relate) other geospatial data which are developed in more common coordinate systems such as latitude/longitude or state plane coordinates.

Second, many GIS users use ArcInfoTM and/or MapInfoTM software and may have difficulty importing and using AutoCADTM drawing data.

Third, the data layers were originally created in over 900 AutoCADTM drawing files (.dwg), and each map was comprised of many data layers covering 4,000-foot by 5,000-foot rectangular areas. With so many files it is laborious to assemble the data for a municipality or other geographic areas of interest. Furthermore, the arbitrary rectangular structure ignores municipal boundaries, adding an obstacle to using the data on a community by community basis.

Thus, in their original format, the data are unavailable and/or difficult to use for many GIS users.

Therefore, NODIS undertook the task of converting the data to latitude/longitude coordinates and to ArcInfoTM and MapInfoTM formats, and to create a fewer number of data files.

The converted data are made available on CD-ROM.

 

Methodology

ArcInfoTM software was used to build arcs, polygons, and text from AutoCADTM .dwg(2) data. ArcViewTM v. 3.2 was used to define the CRGS custom projection. The CRGS parameters are based on the revised "McFadden Shift" method. McFaddden was staff member of the Cuyahoga County Engineer's Office. The "McFadden Shift" method and parameters are described in a series of reports produced by the Engineer's Office from the 1930's to the 1950's. Errors of up to 7 feet were observed at the northeastern edges of the county. The Cuyahoga County Planning Commission discovered a "Scale Factor" as well as some other parameter adjustments such as a Stereographic Projection to improve the CRGS projection accuracy. The Planning Commission defined the CRGS projection in MapInfoTM. NODIS created the CRGS projection in ArcViewTM 3.2 and ArcInfoTM Beta v. 8.02. The locational accuracy was very similar. The stereographic method was tested using 500 USGS monument and GPS control points that have known x and y coordinate values in CRGS and US State Plane NAD 83 meters. 78% of all the projected points were within 1 foot and 96% were within 2 feet of the known x and y locations of the control points.

figure_1.jpg (59068 bytes) (See Figure 1: 500 GPS and USGS Monument Control Points).

 

The ArcViewTM v. 3.2 projection file associated with the shapefile would be as follows:

PROJCS["Custom",GEOGCS["GCS_North_American_1927",DATUM["D_North_

American_1927",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PR

IMEM["Greenwich",0],UNIT["Degree",0.0174532925199433]],

PROJECTION["Stereographic"],PARAMETER["False_Easting",75001],PAR

AMETER["False_Northing",60000.8],PARAMETER["Central_Meridian",-

81.7345799999999],PARAMETER["Scale_Factor",1.00005],

PARAMETER["Central_Parallel",41.41859],UNIT["Foot_US",0.30480060

96012192]]

The parameters are:

Coordinate System Type: Projected; Name: Custom; Units: Foot_US

Geographic Coordinate System: GCS_NorthAmerican_1927

False Easting: 75001; False Northing: 60000.8; Prime Meridian: Greenwich

Base Projection: Stereographic

Central Meridian: -81.73458; Central Parallel: 41.41859; Scale Factor: 1.00005

The CRGS projection can then be changed to any standard projection such as US State Plane NAD83 feet or the latitude/longitude coordinate system.

The planimetric files are provided in the latitude/longitude coordinate system since it is a projection-free coordinate system and since it may be difficult for some GIS users to use projection-based coordinate systems such as CRGS and State Plane. 

The CRGS projection can also now be defined in the latest release of ArcInfoTM beta v. 8.02. Comparisons to the known CRGS coordinate values are the same as is seen in ArcViewTM. However, NODIS discovered that the datum conversion to US State Plane NAD83 (NADCON 1927 to 1983) in ArcInfoTM Beta v. 8.02 does NOT work at this time (2/15/00).

 

Accuracy

NODIS does not guarantee the completeness nor accuracy of the data.

Potential errors may result from any combination of the following.

  1. The original planimetric data may have some errors of unknown character.
  2. The city border data set may not be highly accurate in areas where the city border follows parcel boundaries and not     planimetric features. The source of any such error is in the County’s original planimetric data.

NODIS has overlaid Cuyahoga planimetric and parcel layers. The planimetric data are assumed to contain a higher degree of accuracy than the parcel data. In most areas, the planimetric spatial objects are located relatively accurately to the parcel polygons. This includes road pavement edges and building footprints. There are some areas where the parcel polygons are apparently displaced relative to the planimetric features.

 

Attribute Data

The data have been converted to ArcInfoTM export ("e00") and MapInfoTM formats. The only attribute data fields that are attached to any of the various layers are the following:

 

File Organization

Each layer was created as one file containing geographic coverage for the entire county (plus the two-mile area beyond the county border). The layers are listed below. File names are shown in parenthesis and spatial object type (arcs, points, polygons, and text) are noted in brackets.

Layers, File Names, and Data Types

road (road) [arcs] dense tree (dtree) [arcs]
road name text (roadlbl) [text] city (city) [polygons]
interstate (inst) [arcs] county (county) [polygond]
spot elevation points (spot) [points] original sheet index (planidxl) [polygons]
railroad (rail) [arcs] building footprint (bldg) [polygons]
water (wtr)[arcs] 2 foot elevation contours (elv2) [arcs]
wall (wall) [arcs] 10 foot elevation contours (elv10) [arcs]
driveway (dvwy) [arcs] elevation labels of 10 foot contours (elvlb) [text]
bridge (brdg) [arcs] tree clusters (tree) [arcs] Note: These are not closed polygons.
recreation (recre) [polygons]  

 

figure2.jpg (473588 bytes) (Figure 2: Digital Orthophotograph Index Map shows the original 900 digital orthophoto outline areas.)

 

Credits

Please provide the following credits in any published report or map

 

Notes

1. ArcInfoTM (and its related ArcViewTM) and MapInfoTM are among the most commonly used Geographic Information System (GIS) software in the world.

2. dwg is an AutoCADTM native format..


Prices - Cuyahoga County Parcel Data on CD-ROM

Supplied by Northern Ohio Data & Information Services at Cleveland State University

Contact Jim Wyles at 216-687-2221 or wyles@urban.csuohio.edu

Source data for all files originated from Cuyahoga County Engineer, current as of March 1993.

NODIS cannot guarantee the completeness or accuracy of the source data. Prices may change. Please confirm price when ordering. All data available only on CD-ROM.

Data Compression: The ArcInfoTM .e00 data on the CD-ROM has been compressed into archive files to reduce the number of CD-ROM disks required to contain the data. Use software compatible with PK-ZIP 2.04g to decompress the data. Info-Zip's software (Zip, Unzip and related utilities) are examples of packages that can be used. The Info-Zip software is free and can be obtained as source code or executables on various computer platforms. One site from which this software can be downloaded is: http://www.cdrom.com/pub/infozip/UnZip.html


1. ArcInfoTM export format files (e00):

Planimetric files covering all of Cuyahoga County and two miles outside the county border:

Filename = planall.zip 565 MB (uncompressed .e00 = 3.2 GB)

This compressed file, planall.zip, contains the following .e00 files: road (road), road name text (roadlbl), interstate (inst), spot elevation points (spot), railroad (rail), water (wtr), wall (wall), driveway (dvwy), bridge (brdg), recreation polygons (recre), dense tree (dtree), city polygons (city), county polygons (county), original 900 sheet index (planidxl), building footprint polygons (bldg), 2 foot elevation contour lines (elv2), 10 foot elevation contour lines (elvlb), and trees (tree) as lines.

 

Coordinate system: Latitude/ longitude NAD 83, Northern Ohio Units- decimal degrees

All .e00 files are contained on one CD (565 MB- compressed, 3.2 GB- uncompressed)

Cost…………………… $ 1,200


2. MapInfoTM native format files (.map,tab,id,dat,ind):

Planimetric files covering all of Cuyahoga County and 2 miles outside the county border: road (road), road name text (roadlbl), interstate (inst), spot elevation points (spot), railroad (rail), water (wtr), wall (wall), driveway (dvwy), bridge (brdg), recreation polygons (recre), dense tree (dtree), city polygons (city), county polygons (county), original 900 sheet index (planidxl), building footprint polygons (bldg), 2 foot elevation contour lines (elv2), 10 foot elevation contour lines (elvlb), and trees (tree) as lines.

 

Coordinate system: Latitude/ longitude NAD 83, Northern Ohio Units- decimal degrees

All MapInfoTM native format files are contained on one CD (578 MB)

Cost…………………… $ 1,200