Sanitary Sewer Overflow - Unauthorized Discharges

+ Resource Description

Citation

Information used to reference the data.

Title: Sanitary Sewer Overflow - Unauthorized Discharges

Originators: MSD

Publication date: 7/1999

Data type: vector digital data

Data location: \\pc.lojic.local\data\common\MSD\SSO.shp

Description

A characterization of the data, including its intended use and limitations.

Abstract:

Point layer of unauthorized sanitary sewer and combined sewer discharges that are flagged as documented, suspected, repaired, eliminated, etc. The feature attribute table has several fields that characterizes the discharge.  Nothing is expressly coded as an SSO.  A logical query that excludes UNITIDs which contain "CSO" is required to extract the SSOs from the data set.

Purpose:

Large and small scale cartographics and

general query and analysis.

Language of dataset: en

Point Of Contact

Contact information for the individual or organization that is knowledgeable about the data.

Person: Julie Buckler

Organization: MSD

Phone: (502) 540-6443

Email: buckler@msdlouky.org

Address type: mailing and physical address

Address:

700 W. Liberty St.

City: Louisville

State or Province: Kentucky

Postal code: 40203

Data Type

How the data are represented, formatted and maintained by the data producing organization.

File or table name: SSO

Data type: vector digital data

Data format: Shapefile

Native dataset environment: Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 9.2.4.1420

Time Period of Data

Time period(s) for which the data corresponds to the currentness reference.

Date: 6/1998

Currentness reference:

ground condition

Status

The state of and maintenance information for the data.

Data status: Complete

Update frequency: As needed

Key Words

Words or phrases that summarize certain aspects of the data.

Theme:

Keywords: location, inlandWaters

Keyword thesaurus: ArcIMS Metadata Server Theme Codes

Place:

Keywords: Kentucky, Jefferson County, Louisville, Louisville Metro

Keyword thesaurus: None

Data Access Constraints

Restrictions and legal prerequisites for accessing or using the data after access is granted.

Access constraints:

Data access is restricted to LOJIC Participants, their contractors and Licensees only

Use constraints:

LIMITATION OF LIABILITY: MSD and the participants of the Louisville/Jefferson County Information Consortium (LOJIC) have no indication or reason to believe that there are any inaccuracies or defects of information incorporated in this work and make NO REPRESENTATIONS OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, THE WARRANTIES OF MERCHANTBILITY OR FITNESS FOR A PARTICULAR USE, NOR ARE ANY SUCH WARRANTIES TO BE IMPLIED, WITH RESPECT TO THE INFORMATION OR DATA, FURNISHED HEREIN.



The attached data is owned by the LOJIC participants and is protected by United States Copyright laws and applicable international copyright treaties and/or conventions.

+ Spatial Reference Information

Horizontal Coordinate System

Reference system from which linear or angular quantities are measured and assigned to the position that a point occupies.

Projected coordinate system:

Name: NAD 1983 StatePlane Kentucky North FIPS 1601 Feet

Map units: survey feet

Geographic coordinate system:

Name: GCS North American 1983

Coordinate System Details

Map projection

Map projection name: Lambert Conformal Conic

Standard parallel: 37.966667

Standard parallel: 38.966667

Longitude of central meridian: -84.250000

Latitude of projection origin: 37.500000

False easting: 1640416.666667

False northing: 0.000000

Planar Coordinate Information

Planar coordinate encoding method: coordinate pair

Coordinate representation:

Abscissa resolution: 0.000000

Ordinate resolution: 0.000000

Planar distance units: survey feet

Geodetic model

Horizontal datum name: North American Datum of 1983

Ellipsoid name: Geodetic Reference System 80

Semi-major axis: 6378137.000000

Denominator of flattening ratio: 298.257222

Vertical Coordinate System

Reference system from which vertical distances (altitudes or depths) are measured.

Altitude system definition:

Altitude resolution: 1.000000

Altitude encoding method: Explicit elevation coordinate included with horizontal coordinates

Spatial Domain

The geographic areal domain of the data that describes the western, eastern, northern, and southern geographic limits of data coverage.

Bounding Coordinates

In Projected or local coordinates

NAD 1983 StatePlane Kentucky North FIPS 1601 Feet

Boundary	Coordinate
Left	1164398.750000 (survey feet)
Right	1305352.750000 (survey feet)
Top	316104.740000 (survey feet)
Bottom	205446.062500 (survey feet)

In Unprojected coordinates (geographic)

GCS North American 1983

Boundary	Coordinate
West	-85.910113 (longitude)
East	-85.413724 (longitude)
North	38.362196 (latitude)
South	38.052431 (latitude)

+ Data Structure and Attribute Information

Overview

Summary of the information content of the data, including other references to complete descriptions of entity types, attributes, and attribute values for the data.

Direct spatial reference method: Vector

Attributes of SSO - Unauthorized Discharges

Detailed descriptions of entity type, attributes, and attribute values for the data.

Name: SSO

Type of object: Feature Class

Geometry type: Point

Number of records: 4803

Description:

Comprehensive point cover of all unauthorized discharges

Attributes

SHAPE

Definition:

Feature geometry.

Alias: SHAPE Type: Geometry Width: 4 Precision: 0 Scale: 0

Attribute values: Coordinates defining the features.

Attribute definition source:

ESRI

FID

Definition:

Internal feature number.

Alias: FID Type: OID Width: 4 Precision: 0 Scale: 0

Attribute values: Sequential unique whole numbers that are automatically generated.

Attribute definition source:

ESRI

OBJECTID

Definition:

Internal feature number.

Alias: OBJECTID Type: Number Width: 10

Attribute values: Sequential unique whole numbers that are automatically generated.

Attribute definition source:

ESRI

COMPKEY

Definition:

Unique identifier assigned by Hansen.

Alias: COMPKEY Type: Number Width: 9

DESCRIPT

Definition:

Descriptive location of overflow.

Alias: DESCRIPT Type: String Width: 254

ADDRQUAL

Definition:

Address qualifier.

Alias: ADDRQUAL Type: String Width: 254

UNITID

Definition:

Identifier of asset.

Alias: UNITID Type: String Width: 16

Shape

Definition:

Feature geometry.

Alias: Shape Type: Number Width: 4

Attribute values: Coordinates defining the features.

Attribute definition source:

ESRI

COMPTYPE

Definition:

Comptype of the asset.  Assigned by Hansen.

Alias: COMPTYPE Type: String Width: 4

Attribute domain values

Value	Definition
15	Sewer Pump Station
21	Sewer Main
22	Sewer Manhole
24	Sewer Node
26	Property Service Connection
35	Sewer Valve
98	Treatment Plant
77	Storm Pump Station
29	Storm Inlet

ASBUILT

Definition:

Record drawing number of the construction project.

Alias: ASBUILT Type: String Width: 10

INST_DATE

Definition:

Installation date of the facility.

Alias: INST_DATE Type: Date Width: 8

AGENCY

Definition:

Owner of the facility.

Alias: AGENCY Type: String Width: 4

Attribute domain values

Value	Definition
MSD	Owned and Operated by MSD
PMSD	Private - Operated by MSD
Private	Private sytem flows to an MSD plant
PTP	Private system flows to the a private plant

REC_TPNAME

Definition:

Name of Treatment Plant the feature flows to.

Alias: REC_TPNAME Type: String Width: 30

REC_TPNUM

Definition:

Number of the Treatment Plant the feature flows to.

Alias: REC_TPNUM Type: String Width: 16

COMPCODE

Definition:

Abbreviation of Compdesc.

Alias: COMPCODE Type: String Width: 4

Attribute domain values

Value	Definition
STIN	Storm Inlet
SV	Sewer Valve
SPL	Sewer Treatment Plant
SSL	Sewer Service Line (PSC)
SMH	Sewer Manhole
SLS	Sewer Lift/Pump Station
SND	Sewer Node
STLS	Storm Lift/Pump Station

COMPDESC

Definition:

Description of compcode.

Alias: COMPDESC Type: String Width: 30

SSO

Definition:

TO BE DELETED

Alias: SSO Type: String Width: 1

DIR_DIS

Definition:

Feature to which overflow discharges.

Alias: DIR_DIS Type: String Width: 16

REC_STR

Definition:

Receiving stream name.

Alias: REC_STR Type: String Width: 32

TYPE_DIS

Definition:

Qualifier that indicates whether a location is a constructed overflow or regularly pumped.

Alias: TYPE_DIS Type: String Width: 1

PLAN

Definition:

TO BE DELETED

Alias: PLAN Type: String Width: 1

HISTORY

Definition:

TO BE DELETED

Alias: HISTORY Type: String Width: 254

RAINFALL

Definition:

TO BE DELETED

Alias: RAINFALL Type: Number Width: 5 Number of decimals: 1

EVNTDTTM

Definition:

Date of most recent discharge.

Alias: EVNTDTTM Type: Date Width: 8

STATUS

Definition:

Discharge Status.

Alias: STATUS Type: String Width: 1

Attribute domain values

Value	Definition
D	Documented
E	Eliminated
F	Force Majeure
N	No Reported Discharge
R	Repaired - Issue resolved
S	Suspected

SERV_STATU

Definition:

Service Status of the facility.

Alias: SERV_STATU Type: String Width: 4 Precision: 0 Scale: 0

Attribute domain values

Value	Definition
I	Asset In Service
O	Asset Out of Service

ESRI Feature Description

Description of spatial objects in the data using the Environmental Systems Research Institute (ESRI) terminology.

Environmental Systems Research Institute (ESRI) terms

SSO

ESRI feature type: Simple

Geometry type: Point

Topology: FALSE

Feature count: 4803

Spatial index: TRUE

Linear referencing: FALSE

SDTS Feature Description

Description of point and vector spatial objects in the data using the Spatial Data Transfer Standards (SDTS) terminology.

Spatial data transfer standard (SDTS) terms

SSO

Type: Entity point

Count: 4803

+ Data Source and Process Information

Process Steps

Information about events, parameters, tolerances and techniques applied to construct or derive the data.

Process step information

Process Step 1

Process description:

Discharges can occur on multiple types of sanitary assets.  These assets are flagged in Hansen when a discharge occurs.  The point layer is created through a series of queries on the sewer main, manhole, psc, sewer nodes, sanitary pump stations and sanitary treatment plant layers and are then merged into a single point cover once they related back to Hansen for the respective discharge flag.

Process Step 2

Process description:

Dataset copied.

Data Source used

J:\UNIXLinks\wsjearl\metadata\jeff\MSDDATA_SSO

Process Step 3

Process description:

Metadata imported.

Data Source used

H:\MetaData_Transfer\Old Metadata\MSDDATA_SSO.xml

Process Step 4

Process description:

Dataset copied.

Data Source used

Server=lojicora1; Service=esri_sde; User=jbuckler; Version=SDE.DEFAULT

ESRI geoprocessing history

Description of ESRI geoprocessing commands, settings, and tolerances applied to the data.

ESRI geoprocessing command information

1 Process

Date: 20080531 Time: 173416

Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\UpgradeSpatialReference

Command issued: UpgradeSpatialReference "Database Connections/pl_MSDDATA.sde/msddata.sso" 0.00125 0.025 0.025 "Database Connections/pl_MSDDATA.sde/msddata.sso"

2 Process

Date: 20100502 Time: 080844

Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Conversion Tools.tbx\MetadataImporter

Command issued: MetadataImporter J:\lojic\MetaData_Transfer\MSDData\sso.xml "Database Connections\pl_msddata.sde\MSDDATA.sso_1" "Database Connections\pl_msddata.sde\MSDDATA.sso_1"

3 Process

Date: 20100502 Time: 080846

Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\Analyze

Command issued: Analyze "Database Connections\pl_msddata.sde\MSDDATA.sso_1" BUSINESS;', 'FEATURES'' "Database Connections\pl_msddata.sde\MSDDATA.sso_1"

4 Process

Date: 20100503 Time: 021014

Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\ChangePrivileges

Command issued: ChangePrivileges "Database Connections/pu_msddata.sde\msddata.sso" LOJIC_ROLE GRANT # "Database Connections/pu_msddata.sde\msddata.sso"

+ Data Distribution Information

General

Description of the data known by the party from whom the data may be obtained, liability of party distributing data, and technical capabilities required to use the data.

Resource description:

Downloadable Data

Standard Order Process

Common ways in which data may be obtained.

Digital form:

Size of the data: 0.128

Transfer size: 0.128

+ Metadata Reference

Metadata Date

Dates associated with creating, updating and reviewing the metadata.

Last updated: 20080917

Language of metadata: en

Metadata Point of Contact

Contact information for the individual or organization responsible for the metadata information.

Organization: LOJIC

Person: Jeff Ackerman

Phone: (502) 540-6372

Fax: (502) 540-6499

Email: ackerman@lojic.org

Address type: mailing and physical address

Address:

700 West Liberty St.

City: Louisville

State or Province: Kentucky

Postal code: 40203

Metadata Standards

Description of the metadata standard used to document the data and reference to any additional extended profiles to the standard used by the metadata producer.

Standard name: FGDC Content Standards for Digital Geospatial Metadata

Standard version: FGDC-STD-001-1998

Time convention: local time

Metadata profiles defining additonal information:

Profile: ESRI Metadata Profile

Online linkage: http://www.esri.com/metadata/esriprof80.html

FGDC Plus Metadata Stylesheet

Stylesheet: FGDC Plus Stylesheet

File name: FGDC Plus.xsl

Version: 2.2

Description: This metadata is displayed using the FGDC Plus Stylesheet, which is an XSL template that can be used with ArcGIS software to display metadata. It displays metadata elements defined in the Content Standard for Digital Geospatial Metadata (CSDGM) - aka FGDC Standard, the ESRI Profile of CSDGM, the Biological Data Profile of CSDGM, and the Shoreline Data Profile of CSDGM. CSDGM is the US Federal Metadata standard. The Federal Geographic Data Committee originally adopted the CSDGM in 1994 and revised it in 1998. According to Executive Order 12096 all Federal agencies are ordered to use this standard to document geospatial data created as of January, 1995. The standard is often referred to as the FGDC Metadata Standard and has been implemented beyond the federal level with State and local governments adopting the metadata standard as well. The Biological Data Profile broadens the application of the CSDGM so that it is more easily applied to biological data that are not explicitly geographic (laboratory results, field notes, specimen collections, research reports) but can be associated with a geographic location. Includes taxonomical vocabulary. The Shoreline Data Profile addresses variability in the definition and mapping of shorelines by providing a standardized set of terms and data elements required to support metadata for shoreline and coastal data sets. The FGDC Plus Stylesheet includes the Dublin Core Metadata Element Set. It supports W3C DOM compatible browsers such as IE7, IE6, Netscape 7, and Mozilla Firefox. It is in the public domain and may be freely used, modified, and redistributed. It is provided "AS-IS" without warranty or technical support.

Instructions: On the top of the page, click on the title of the dataset to toggle opening and closing of all metadata content sections or click section links listed horizontally below the title to open individual sections. Click on a section name (e.g. Description) to open and close section content. Within a section, click on a item name (Status, Key Words, etc.) to open and close individual content items. By default, the Citation information within the Description section is always open for display.

Download: FGDC Plus Stylesheet is available from the ArcScripts downloads at www.esri.com.