IOUREA_2009DD

Metadata also available as

Frequently-anticipated questions:


What does this data set describe?

Title: IOUREA_2009DD
Abstract:
Electric Service Area Boundaries -- Investor Owned Utilities and Rural Electric Associations
Supplemental_Information:
Originally digitized by the PUCO in 1989, this database was re-created from scratch in 2007-2009. The 24,000 scale electric boundary Mylar quadrangle maps were scanned and then digitized. All changes made in boundary cases were incorporated in the new database. Quadrangles making up the boundary of each individual utility were edge matched, and the utility boundaries were then merged to create a statewide data set. Dataset has been updated with new boundary change approvals through 9/09.
  1. How should this data set be cited?

    REQUIRED: The name of an organization or individual that developed the data set., REQUIRED: The date when the data set is published or otherwise made available for release., IOUREA_2009DD.

    Online Links:

    • \\mapping\gisdata\databases\DD\IOUREA_2009DD.shp

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -84.820217
    East_Bounding_Coordinate: -80.518922
    North_Bounding_Coordinate: 41.977493
    South_Bounding_Coordinate: 38.403150

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Calendar_Date: 2009
    Currentness_Reference: ground condition

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):

      • G-polygon (36)

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.000000. Longitudes are given to the nearest 0.000000. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Resolution: 0.000010
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates

  7. How does the data set describe geographic features?

    IOUREA_2009DD

    COMPNAME
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape_Leng
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    compcode
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    Shape_Area
    Area of feature in internal units squared. (Source: ESRI)

    Positive real numbers that are automatically generated.

    SHAPE
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    Public Utilities Commission of Ohio

  3. To whom should users address questions about the data?

    Public Utilities Commission of Ohio
    180 E. Broad St.
    Columbus, OH 43215
    Franklin


Why was the data set created?

For use in utility mapping


How was the data set created?

  1. From what previous works were the data drawn?

  2. How were the data generated, processed, and modified?

    (process 1 of 6)
    Dataset copied.

    Data sources used in this process:

    • \\OPI106\C\Projects\Puco\Arc\Utilities Boundary\Databases\Puco_Temp.mdb

    (process 2 of 6)
    Dataset copied.

    Data sources used in this process:

    • \\BAIRDTXP\D$\ElectricOPI_2007.mdb

    (process 3 of 6)
    Dataset copied.

    Data sources used in this process:

    • \\mapping\gisdata\databases\electric_edit.mdb

    (process 4 of 6)
    Dataset copied.

    Data sources used in this process:

    • \\PERINIXP\D$\Databases\ElectricOPI_final.mdb

    Date: 04-Aug-2009 (process 5 of 6)
    Dataset copied.

    Data sources used in this process:

    • \\mapping\gisdata\databases_ElecOPI\ElecQuadsMergeAug4_09\New Personal Geodatabase.mdb

    Date: 03-Sep-2009 (process 6 of 6)
    Dataset copied.

    Data sources used in this process:

    • \\mapping\gisdata\databases\Utility.mdb

  3. What similar or related data should the user be aware of?


How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

  2. How accurate are the geographic locations?

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

  5. How consistent are the relationships among the observations, including topology?


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: None
Use_Constraints: None

  1. Who distributes the data set?[Distributor contact information not provided.]

  2. What's the catalog number I need to order this data set?

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 03-Sep-2009
Metadata author:
REQUIRED: The organization responsible for the metadata information.
c/o REQUIRED: The person responsible for the metadata information.
REQUIRED: The city of the address., REQUIRED: The state or province of the address. REQUIRED: The ZIP or other postal code of the address.

REQUIRED: The telephone number by which individuals can speak to the organization or individual. (voice)

Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:


Generated by mp version 2.9.6 on Thu Sep 03 11:35:27 2009