Name: Ohio House Districts (2012- 2022)

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: The district maps represents the results of the 2012-2022 apportionment plan for the State of Ohio. The shapefiles were obtained from the Ohio Secretary of State's Office website. Detailed information regarding the development of these shapefiles can be found at: http://www.sos.state.oh.us/SOS/reshape/GADistricts/adoptedMap.aspxPart A. General Overview  1.   To assist users in their review of the legislative district plan, the plan geography is being provided in different formats. These include a geographic data file known as a shape file and a tabular data file known as an assignment file. The geographic file includes the boundaries for each district. The tabular data file includes one record for the lowest level of geography used to create the plan and the district to which it is assigned.  2.   Users with Geographic Information Systems (GIS) software may note a handful of instances in which the appearance of the geography assigned to each district may not match the legal boundaries. Notes follow on these instances below.  3.   As a general caveat, whatever the geographic representation might appear to be when the legislative plan is viewed via any software, the controlling document as to the status of any geography is the legal definitions as submitted by the Joint Secretaries to the Ohio Apportionment Board. Those definitions can be found in this document.  4.   Any geographic area of the state not specifically named in this legal definition for House and Senate Districts that is wholly contained within the boundaries of a district but not contiguous to any district boundary, is assigned to that district. Any geographic area of the state not specifically named in this legal definition that is contiguous to any district boundary is assigned to that district with which it has the longest continuous boundary. If two or more boundaries are of equal length, the area is assigned to the district with less population. All districts are contiguous including those that are contiguous only by bodies of water.  5.   The legal definition will be posted at the following website designated by the Ohio Apportionment Board: http://www.reshapeohio.org.   [link not valid as of 2/13/2015] Part B. Geographic Database  The underlying geographic database used to create plans for legislative districts was developed by the Urban Center at Cleveland State University (CSU) in conjunction with the Voinovich Center at Ohio University (OU) as part of the project to develop the 2010 Ohio Common and Unified Redistricting Database (OCURD). CSU was selected by bipartisan action by the co-chairs of the Ohio Legislative Task Force on Redistricting, Reapportionment and Demographic Research. The lowest level of geography in this database is not the census block but the split census block.  1.   The overall purpose of the project was to accommodate for the fact that many census blocks contain portions of multiple higher levels of geography, such as a precinct or a municipality. In geographic terms, these are known as ‘split’ units because they did not nest into the higher levels of geography. The project also enabled the creation of geographic layers for wards (which were not part of the census geographic products) and precincts that more closely reflect the boundaries used in the 2008 and 2010 elections.  2.   To create a geographic system that allowed for topological integrity, the OCURD project used the boundaries of the higher levels of geography as overlays and assigned the underlying census block, or portions thereof, to each of the higher levels. When the higher level geography crossed the census block, a new geographic unit was created known as a split block. It is this ‘block split’ layer of geography that was the lowest level of geography from which the legislative districts were created.  3.   Another goal of the OCURD project was to estimate the population in each portion of the split blocks. The project researched several means by which this could be accomplished and chose a method based upon the length of the streets in each such block. Because the population was estimated for each portion, the number of persons was not rounded to a whole person and thus some fractional numbers will be found.  4.   Another issue arose as the OCURD database was being used by the Joint Secretaries of the Ohio Apportionment Board to create legislative plans. This issue relates to the fact that many of the higher levels of geography, notably municipalities, wards, and precincts, contain multiple pieces of territory that are separated by distances short and long. In geographic terms, these are known as ‘non-contiguous areas’ (NCA) because there is some other land or water between the pieces. There are two types of NCAs: those that are not contiguous because they are islands surrounded by water and those that are not contiguous because they are legally or technically a portion of a geographic unit but surrounded by other land-based geographic units. Examples of the first type are the islands off the coast of Lake Erie. Examples of the second type abound in the state.  5.   In most cases, the multi-part units are combined for geographic representation in GIS software. In geographic terms, these are known as ‘shapes’ and are assigned to a district as one unit, even though there may be separate estimates of population for the blocks that comprise the higher level unit. Because they are combined as an entire shape they can only be assigned to one district by the GIS software used for the redistricting phase of the apportionment process. The software used by the Board to undertake this process was Maptitude for Redistricting (MTR) by Caliper Corporation.  6.   Requirements of the Ohio Constitution relate to both creating districts from contiguous territory and the maintenance of political subdivision boundaries. Therefore, making use of a multi-part area as the boundary of a district could present a situation in which a political subdivision would be split and a district would be created using non-contiguous territory.  7.   Whatever the geographic representation of the GIS software, the controlling document as to the status of any geography is the legal definition as adopted by the Apportionment Board. 8.   Because some areas in the higher geographic levels are multi-part units the software flagged some districts as being non-contiguous. Notes on these situations follow.   Part C. Notes on Specific Districts:  The following areas include districts that were designated by the Maptitude software as having some non-contiguous areas:  1.   District 38—Stark County. Block 391517147013085 is split into two pieces including portions of precincts 151ANY & 151AEB. The portion in 151ANY contains no population and is a part of district 49. See the item 4 in Part A and the legal definition.  2.   District 46—Lucas County. Several islands are located off the Lake Erie coast but are portions of Jerusalem Township. See the item 4 in Part A and the legal definition.  3.   District 48—Stark County. Block 391517123002009 is split into three pieces including portions of precincts 151ACD, 151AME, and 151ANG. Each of these portions contains no population. The triangular portion at the lower south east of the block is a part of district 49. See the item 4 in Part A and the legal definition.  4.   District 55—Lorain County. Several islands are located off the Lake Erie coast but are portions of Avon Lake City. See the item 4 in Part A and the legal definition.  5.   District 83—Hardin and Logan Counties. There is one unit in the ‘Block Split’ layer, 390650007003086091AAR, that is unassigned in the map. It contains no population and is surrounded by district 83. See the item 4 in Part A and the legal description.  6.   District 88—Sandusky County. One island is located in Sandusky Bay but is a portion of Riley Township. See the item 4 in Part A and the legal definition.7.   District 89—Ottawa County. This district has three components: the portion above Sandusky Bay; the portion below Sandusky Bay; and several islands off the Lake Erie coast. See the item 4 in Part A and the legal definition. 

Service Item Id: 327e71201c53449aa7b64d4dce2790f6

Copyright Text: The Ohio Secretary of state

Default Visibility: true

MaxRecordCount: 2000

MaxSelectionCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: false

Supports Statistics: false

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: 1310182.75887914
YMin: 146941.73616705835
XMax: 2518351.8609088063
YMax: 1455146.6896338165
Spatial Reference: 102723  (3735)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [0, 0, 0, 0]
Outline:
Style: esriSLSSolid
Color: [255, 0, 0, 255]
Width: 2
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Feature Draw Order:

N/A

Advanced Query Capabilities:

Supports Statistics: false
Supports OrderBy: false
Supports Distinct: false
Supports Pagination: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: false
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: false
Supports Having Clause: false
Supports Count Distinct: false
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: false
Supports Query With Current User: true

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• ID ( type: esriFieldTypeInteger, alias: ID )
• DISTRICT ( type: esriFieldTypeString, alias: DISTRICT, length: 12 )
• MEMBERS ( type: esriFieldTypeDouble, alias: MEMBERS )
• LOCKED ( type: esriFieldTypeString, alias: LOCKED, length: 1 )
• NAME ( type: esriFieldTypeString, alias: NAME, length: 43 )
• POPULATION ( type: esriFieldTypeDouble, alias: POPULATION )
• IDEAL_VALU ( type: esriFieldTypeDouble, alias: IDEAL_VALU )
• DEVIATION ( type: esriFieldTypeDouble, alias: DEVIATION )
• F_DEVIATIO ( type: esriFieldTypeDouble, alias: F_DEVIATIO )
• SQ_MI ( type: esriFieldTypeDouble, alias: SQ_MI )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• FID ( type: esriFieldTypeOID, alias: FID )
• OBJECTID ( type: esriFieldTypeInteger, alias: OBJECTID )
• AREA ( type: esriFieldTypeDouble, alias: AREA )
• Shape_STAr ( type: esriFieldTypeDouble, alias: Shape_STAr )
• Shape_STLe ( type: esriFieldTypeDouble, alias: Shape_STLe )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata