PSC (Property Service Connection)
SDE Feature Class - MSDDATA.PSC
FGDC, ESRI Metadata
DescriptionSpatialData StructureData SourceData DistributionMetadata
+ Resource Description
Citation
Information used to reference the data.
Title: PSC (Property Service Connection)
Originators: MSD
Publication date: 3/1999
Data type: vector digital data
Description
A characterization of the data, including its intended use and limitations.
Abstract:
The layer consists of points that indicate

which properties have a sewer service line

connection.
Purpose:
General query and display.
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
Fax: (502) 540-6180
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: MSDDATA.PSC
Data type: vector digital data
Data format: SDE Feature Class
Native dataset environment: Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 9.3.1.3000
Time Period of Data
Time period(s) for which the data corresponds to the currentness reference.
Date: 3/1997
Currentness reference:
ground condition
Status
The state of and maintenance information for the data.
Data status: Complete
Update frequency: Weekly
Key Words
Words or phrases that summarize certain aspects of the data.
Theme:
Keywords: structure
Keyword thesaurus: ArcIMS Metadata Server Theme Codes
Place:
Keywords: Louisville, Louisville Metro, Jefferson County, Kentucky
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.001250
Ordinate resolution: 0.001250
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
BoundaryCoordinate
Left 1163923.750000 (survey feet)
Right 1307342.375000 (survey feet)
Top 316648.062500 (survey feet)
Bottom 203989.297500 (survey feet)
In Unprojected coordinates (geographic)
GCS North American 1983
BoundaryCoordinate
West-85.911804 (longitude)
East-85.406751 (longitude)
North38.363757 (latitude)
South38.048408 (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 MSDDATA.PSC
Detailed descriptions of entity type, attributes, and attribute values for the data.
Name: MSDDATA.PSC
Type of object: Feature Class
Geometry type: Point
Number of records: 276735
Description:
Sanitary Property Service Connection
Source:
Hansen
Attributes
ADDRQUAL
Alias: ADDRQUAL Type: String Width: 254 Precision: 0 Scale: 0
UNITID
Alias: UNITID Type: String Width: 16 Precision: 0 Scale: 0
OBJECTID
Definition:
Internal feature number.
Alias: OBJECTID Type: OID Width: 4 Precision: 10 Scale: 0
Attribute values: Sequential unique whole numbers that are automatically generated.
Attribute definition source:
ESRI
COMPKEY
Definition:
Component Key -- Unique identifier assigned by V7IMS application
Alias: COMPKEY Type: Integer Width: 4 Precision: 10 Scale: 0
ADDRESS
Alias: ADDRESS Type: String Width: 35 Precision: 0 Scale: 0
INST_DATE
Definition:
Date the project was constructed
Alias: INST_DATE Type: Date Width: 36 Precision: 0 Scale: 0
AGENCY
Definition:
Agency Responsible for PSC
Alias: AGENCY Type: String Width: 4 Precision: 0 Scale: 0
Attribute domain values
ValueDefinition
MSD
MSD owned and operated
P
Private
P
Private facility going to MSD facility
PMSD
Private but maintained by MSD
PTP
Private facility going to a private treatment plant
ZIPCODE
Alias: ZIPCODE Type: String Width: 5 Precision: 0 Scale: 0
LOC
Alias: LOCATION Type: String Width: 4 Precision: 0 Scale: 0
UNITTYPE
Alias: UNITTYPE Type: String Width: 6 Precision: 0 Scale: 0
DIAMETER
Alias: DIAMETER Type: Double Width: 8 Precision: 38 Scale: 8
LENGTH
Alias: LENGTH Type: Double Width: 8 Precision: 38 Scale: 8
COMPTYPE
Definition:
Component Type -- Type of feature; in this case  always 26 (sewer service line)
Alias: COMPTYPE Type: Integer Width: 4 Precision: 10 Scale: 0
DEPTH
Alias: DEPTH Type: Double Width: 8 Precision: 38 Scale: 8
ASBUILT
Definition:
Record Drawing Number -- Record number from the MSD project drawing set of the plan sheet for the particular facility
Alias: ASBUILT Type: String Width: 10 Precision: 0 Scale: 0
MAINTYP
Alias: MAINTYPE Type: Integer Width: 4 Precision: 10 Scale: 0
MAIN_ID
Alias: MAIN_ID Type: String Width: 16 Precision: 0 Scale: 0
MAINTYP2
Alias: MAINTYP2 Type: Integer Width: 4 Precision: 10 Scale: 0
MAIN_ID2
Alias: MAIN_ID2 Type: String Width: 16 Precision: 0 Scale: 0
SMNKEY
Alias: MAINKEY Type: Integer Width: 4 Precision: 10 Scale: 0
SERV_STATUS
Alias: SERV_STATUS Type: String Width: 4 Precision: 0 Scale: 0
REC_TPNAME
Alias: REC_TPNAME Type: String Width: 30 Precision: 0 Scale: 0
REC_TPNUM
Alias: REC_TPNUM Type: String Width: 16 Precision: 0 Scale: 0
STNO
Alias: STNO Type: String Width: 6 Precision: 0 Scale: 0
PREDIR
Alias: PREDIR Type: String Width: 3 Precision: 0 Scale: 0
STNAME
Alias: STNAME Type: String Width: 20 Precision: 0 Scale: 0
SUFFIX
Alias: SUFFIX Type: String Width: 4 Precision: 0 Scale: 0
SHAPE
Definition:
Feature geometry.
Alias: SHAPE Type: Geometry Width: 4 Precision: 0 Scale: 0
Attribute values: Coordinates defining the features.
Attribute definition source:
ESRI
ESRI Subtypes of MSDDATA.PSC
Describes the subtypes that have been defined for a feature class in a geodatabase
In the following list the subtype code is followed by the subtype name. Attributes (subtype fields) for each subtype are described in terms of their default value, valid domain values, value after merging or splitting features, etc.
Subtypes
26 - Property Service Connection
Attributes
COMPTYPE
Default value: 26
LOC
Attribute defined domain:
Domain name: MSD_Loc
Domain description: MSD asset locations.
Domain owner: msddata
Field type: String
Domain type: Coded Value
Merge rule: Default value
Split rule: Duplicate
UNITTYPE
Attribute defined domain:
Domain name: MSD_PSCUnitType
Domain description: Type of Property Service Connection
Domain owner: MSDDATA
Field type: String
Domain type: Coded Value
Merge rule: Default value
Split rule: Default value
MAINTYP
Attribute defined domain:
Domain name: MSD_SewerEndPoint
Domain description: Sewer End Point Types
Domain owner: MSDDATA
Field type: Integer
Domain type: Coded Value
Merge rule: Default value
Split rule: Default value
MAINTYP2
Attribute defined domain:
Domain name: MSD_SewerEndPoint
Domain description: Sewer End Point Types
Domain owner: MSDDATA
Field type: Integer
Domain type: Coded Value
Merge rule: Default value
Split rule: Default value
AGENCY
Default value: MSD
Attribute defined domain:
Domain name: MSD_Owner
Domain description: Asset ownership
Domain owner: msddata
Field type: String
Domain type: Coded Value
Merge rule: Default value
Split rule: Duplicate
SERV_STATUS
Default value: I
Attribute defined domain:
Domain name: MSD_ServStat
Domain description: Service status
Domain owner: msddata
Field type: String
Domain type: Coded Value
Merge rule: Default value
Split rule: Duplicate
ESRI Feature Description
Description of spatial objects in the data using the Environmental Systems Research Institute (ESRI) terminology.
Environmental Systems Research Institute (ESRI) terms
MSDDATA.PSC
ESRI feature type: Simple
Geometry type: Point
Topology: FALSE
Feature count: 276735
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
MSDDATA.PSC
Type: Entity point
Count: 276735
+ 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:
The addresses for the PSC in the IMS Oracle

tables were addressmatched against the

Siteadd layer. Rejects are processed on

Mondays.
Process Step 2
Process description:
Metadata imported.
Data Source used
H:\data\lojic\metadata\jeff\MSDDATA_PSC.xml
Process Step 3
Process description:
Metadata imported.
Data Source used
H:\MetaData_Transfer\MSDData\psc.xml
Process Step 4
Process description:
Dataset copied.
Data Source used
Server=lojicora1; Service=esri_sde; User=bcarroll; Version=MSDDATA.SEWER_E
Process Step 5
Process description:
Dataset copied.
Data Source used
\\gishome1.pc.lojic.local\home\bcarroll\Data Backups\MSDDATA.gdb
Process Step 6
Process description:
Metadata imported.
Process date: 20091022 Process time: 08341200
Data Source used
J:\common\MSD\metadata_shapefiles\SewerPSC.xml
ESRI geoprocessing history
Description of ESRI geoprocessing commands, settings, and tolerances applied to the data.
ESRI geoprocessing command information
1 Process
Date: 20091013 Time: 113308
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Conversion Tools.tbx\FeatureClassToFeatureClass
Command issued: FeatureClassToFeatureClass "Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC" H:\Shapefiles point_psc.shp # "COMPKEY 'COMPKEY' true true false 4 Long 0 10 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,COMPKEY,-1,-1;COMPTYPE 'COMPTYPE' true true false 4 Long 0 10 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,COMPTYPE,-1,-1;UNITID 'UNITID' true true false 16 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,UNITID,-1,-1;ADDRESS 'ADDRESS' true true false 35 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,ADDRESS,-1,-1;ZIPCODE 'ZIPCODE' true true false 5 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,ZIPCODE,-1,-1;LOC 'LOCATION' true true false 4 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,LOC,-1,-1;UNITTYPE 'UNITTYPE' true true false 6 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,UNITTYPE,-1,-1;DIAMETER 'DIAMETER' true true false 8 Double 8 38 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,DIAMETER,-1,-1;LENGTH 'LENGTH' true true false 8 Double 8 38 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,LENGTH,-1,-1;DEPTH 'DEPTH' true true false 8 Double 8 38 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,DEPTH,-1,-1;INST_DATE 'INST_DATE' true true false 36 Date 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,INST_DATE,-1,-1;ASBUILT 'ASBUILT' true true false 10 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,ASBUILT,-1,-1;MAINTYP 'MAINTYPE' true true false 4 Long 0 10 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,MAINTYP,-1,-1;MAIN_ID 'MAIN_ID' true true false 16 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,MAIN_ID,-1,-1;MAINTYP2 'MAINTYP2' true true false 4 Long 0 10 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,MAINTYP2,-1,-1;MAIN_ID2 'MAIN_ID2' true true false 16 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,MAIN_ID2,-1,-1;AGENCY 'AGENCY' true true false 4 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,AGENCY,-1,-1;SMNKEY 'MAINKEY' true true false 4 Long 0 10 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,SMNKEY,-1,-1;SERV_STATU 'SERV_STATUS' true true false 4 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,SERV_STATUS,-1,-1;ADDRQUAL 'ADDRQUAL' true true false 254 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,ADDRQUAL,-1,-1;REC_TPNAME 'REC_TPNAME' true true false 30 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,REC_TPNAME,-1,-1;REC_TPNUM 'REC_TPNUM' true true false 16 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,REC_TPNUM,-1,-1;STNO 'STNO' true true false 6 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,STNO,-1,-1;PREDIR 'PREDIR' true true false 3 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,PREDIR,-1,-1;STNAME 'STNAME' true true false 20 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,STNAME,-1,-1;SUFFIX 'SUFFIX' true true false 4 Text 0 0 ,First,#,Database Connections\Connection to lojicora1.sde\MSDDATA.Sewer\MSDDATA.PSC,SUFFIX,-1,-1" # H:\Shapefiles\point_psc.shp
2 Process
Date: 20100113 Time: 115216
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\SelectLayerByLocation
Command issued: SelectLayerByLocation tmpLayer INTERSECT overlay_Layer # NEW_SELECTION tmpLayer
3 Process
Date: 20100114 Time: 111157
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\SelectLayerByLocation
Command issued: SelectLayerByLocation tmpLayer INTERSECT overlay_Layer # NEW_SELECTION tmpLayer
4 Process
Date: 20100114 Time: 155818
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\SelectLayerByLocation
Command issued: SelectLayerByLocation tmpLayer INTERSECT overlay_Layer # NEW_SELECTION tmpLayer
5 Process
Date: 20100115 Time: 173103
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\SelectLayerByLocation
Command issued: SelectLayerByLocation tmpLayer INTERSECT overlay_Layer # NEW_SELECTION tmpLayer
6 Process
Date: 20100203 Time: 171451
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\SelectLayerByLocation
Command issued: SelectLayerByLocation tmpLayer INTERSECT overlay_Layer # NEW_SELECTION tmpLayer
7 Process
Date: 20100215 Time: 134803
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\SelectLayerByLocation
Command issued: SelectLayerByLocation tmpLayer INTERSECT overlay_Layer # NEW_SELECTION tmpLayer
8 Process
Date: 20100316 Time: 094127
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\SelectLayerByLocation
Command issued: SelectLayerByLocation tmpLayer INTERSECT overlay_Layer # NEW_SELECTION tmpLayer
9 Process
Date: 20100322 Time: 140541
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\SelectLayerByLocation
Command issued: SelectLayerByLocation tmpLayer INTERSECT overlay_Layer # NEW_SELECTION tmpLayer
10 Process
Date: 20100401 Time: 111930
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\SelectLayerByLocation
Command issued: SelectLayerByLocation tmpLayer INTERSECT overlay_Layer # NEW_SELECTION tmpLayer
11 Process
Date: 20100423 Time: 153127
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\SelectLayerByLocation
Command issued: SelectLayerByLocation tmpLayer INTERSECT overlay_Layer # NEW_SELECTION tmpLayer
+ 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.000
Transfer size: 0.000
+ Metadata Reference
Metadata Date
Dates associated with creating, updating and reviewing the metadata.
Last updated: 20100503
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
Profile: ESRI Metadata Profile
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.