Boundary

+ Resource Description

Citation

Information used to reference the data.

Title: Boundary

Originators: Property Valuation Administrator (PVA)

Publication date: Varies

Data type: vector digital data

Data location: LOJIC GIS Database

Description

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

Abstract:

Arc layer that contain all of the property lines found in Jefferson County, Kentucky, and their attributes.  This layer is routinely maintained and updated by Property Valuation Administrator (PVA) in order to reflect current property records.

Purpose:

To store current Jefferson County property data.  Maintenance is carried out by PVA staff using the ParcelMapper software designed by Smart Data Strategies (SDS), Franklin, TN.

Supplemental information:

Parcel boundaries are approximate as digitized from PVA block maps and adjusted to fit LOJIC planimetric map data.  Parcel boundaries and related data do not supercede deed records and should not be used for purposed other than general property reference.

Language of dataset: English

Point Of Contact

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

Person: David Emery

Organization: Property Valuadtion Administrator (PVA)

Position: Director of Land Records Management

Phone: (502) 574-6243

Fax: (502) 574-6108

Email: demery@pvalouky.net

Address type: mailing and physical address

Address:

531 Court Place

Address:

Suite 501

City: Louisville

State or Province: Kentucky

Postal code: 40202

County: USA

Data Type

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

File or table name: PVA.Boundary

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: Varies

Currentness reference:

ground condition

Status

The state of and maintenance information for the data.

Data status: Complete

Update frequency: Daily

Key Words

Words or phrases that summarize certain aspects of the data.

Theme:

Keywords: planningCadastre

Keyword thesaurus: ArcIMS Metadata Server Theme Codes

Place:

Keywords: Louisville, Jefferson County, Metro Louisville, Kentucky, KY

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

Boundary	Coordinate
Left	1152180.375000 (survey feet)
Right	1310675.312500 (survey feet)
Top	322720.437500 (survey feet)
Bottom	185531.312500 (survey feet)

In Unprojected coordinates (geographic)

GCS North American 1983

Boundary	Coordinate
West	-85.953142 (longitude)
East	-85.394380 (longitude)
North	38.380545 (latitude)
South	37.997144 (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 Boundary

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

Name: PVA.Boundary

Type of object: Feature Class

Geometry type: Polyline

Number of records: 867380

Attributes

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

RECORDBOUNDARYID

Alias: RECORDBOUNDARYID Type: String Width: 30 Precision: 0 Scale: 0

Attribute definition source:

ESRI

RECORDBOUNDS

Alias: RECORDBOUNDS Type: String Width: 30 Precision: 0 Scale: 0

Attribute definition source:

ESRI

BOUNDARYNAME

Alias: BOUNDARYNAME Type: String Width: 30 Precision: 0 Scale: 0

Attribute definition source:

ESRI

RECORDBOUNDARYSTATUS

Alias: RECORDBOUNDARYSTATUS Type: String Width: 30 Precision: 0 Scale: 0

Attribute definition source:

ESRI

RECORDBOUNDARYTYPE

Alias: RecordBoundaryType Type: Integer Width: 4 Precision: 10 Scale: 0

Attribute definition source:

ESRI

OFFSETLEFT

Alias: OFFSETLEFT Type: Double Width: 8 Precision: 38 Scale: 8

Attribute definition source:

ESRI

OFFSETRIGHT

Alias: OFFSETRIGHT Type: Double Width: 8 Precision: 38 Scale: 8

Attribute definition source:

ESRI

RECORDBOUNDARYCOMMENT

Alias: RECORDBOUNDARYCOMMENT Type: String Width: 255 Precision: 0 Scale: 0

Attribute definition source:

ESRI

DIRECTION

Alias: DIRECTION Type: String Width: 12 Precision: 0 Scale: 0

Attribute definition source:

ESRI

DISTANCE

Alias: DISTANCE Type: String Width: 10 Precision: 0 Scale: 0

Attribute definition source:

ESRI

DIRECTIONTYPE

Alias: DIRECTIONTYPE Type: String Width: 10 Precision: 0 Scale: 0

Attribute definition source:

ESRI

DIRECTIONUNIT

Alias: DIRECTIONUNIT Type: String Width: 10 Precision: 0 Scale: 0

Attribute definition source:

ESRI

DIRECTIONQUADRANT

Alias: DIRECTIONQUADRANT Type: String Width: 10 Precision: 0 Scale: 0

Attribute definition source:

ESRI

DISTANCEUNIT

Alias: DISTANCEUNIT Type: String Width: 10 Precision: 0 Scale: 0

Attribute definition source:

ESRI

DISTANCETYPE

Alias: DISTANCETYPE Type: String Width: 10 Precision: 0 Scale: 0

Attribute definition source:

ESRI

RADIUS

Alias: RADIUS Type: String Width: 10 Precision: 0 Scale: 0

Attribute definition source:

ESRI

DELTA

Alias: DELTA Type: String Width: 10 Precision: 0 Scale: 0

Attribute definition source:

ESRI

TANGENT

Alias: TANGENT Type: String Width: 10 Precision: 0 Scale: 0

Attribute definition source:

ESRI

ARCLENGTH

Alias: ARCLENGTH Type: String Width: 10 Precision: 0 Scale: 0

Attribute definition source:

ESRI

SIDE

Alias: SIDE Type: String Width: 1 Precision: 0 Scale: 0

Attribute definition source:

ESRI

CBSOURCEID

Alias: CBSOURCEID Type: String Width: 30 Precision: 0 Scale: 0

Attribute definition source:

ESRI

SHAPE

Definition:

Feature geometry.

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

Attribute values: Coordinates defining the features.

Attribute definition source:

ESRI

BND_TYPE

Definition:

Heirarchal line definition; order of descensdy: Block, Subdivision, ROW, Lot

Alias: BND_TYPE Type: SmallInteger Width: 2 Precision: 5 Scale: 0

SHAPE.LEN

Alias: SHAPE.LEN Type: Double Width: 0 Precision: 0 Scale: 0

Attribute definition source:

ESRI

ESRI Subtypes of Boundary

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

3 - Lot Boundary

Attributes

RECORDBOUNDARYTYPE

Default value: 1

4 - Block Boundary

Attributes

RECORDBOUNDARYTYPE

Default value: 1

5 - ROW Split

Attributes

RECORDBOUNDARYTYPE

Default value: 1

2 - Subdivision Boundary

Attributes

RECORDBOUNDARYTYPE

Default value: 1

1 - Right-Of-Way

Attributes

RECORDBOUNDARYTYPE

Default value: 1

ESRI Feature Description

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

Environmental Systems Research Institute (ESRI) terms

PVA.Boundary

ESRI feature type: Simple

Geometry type: Polyline

Topology: TRUE

Feature count: 867380

Spatial index: TRUE

Linear referencing: FALSE

XY Rank: 1

Z Rank: 1

Topology weight: 5.000000

Events on validation: FALSE

Participates in topology rules:

Rule Id: 4804, 4805, 4806, 4807, 4810, 4811, 4812, 4813

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

PVA.Boundary

Type: String

Count: 867380

+ Data Source and Process Information

Data Sources

Information about the source data used to construct or derive the data.

Data source information

Data Source 1

Originators: PVA Block Maps; source scale 1" = 40' to 1" = 500'

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 data was originally generated in 1989 - 1990 from approximately 4,000 PVA Block Maps of varying scale, age, and accuracy.  Parcel boundaries were graphically adjusted within acceptable dimensional tolerances, to fit existing digital planimetric data from the LOJIC base map.  The conversion process included scanning and replotting original PVA maps, graphic adjustments to the digitized parcel data, and generation of plots, digital files and errata reports.  Parcel boundaries were created via the Arc/INFO data model along with associated attributes  to define various line types and boundary classififcations.

Process Step 2

Process description:

Dataset copied.

Data Source used

Server=lojicora1; Service=5190; User=pva; Version=SDE.DEFAULT

Process Step 3

Process description:

Dataset copied.

Data Source used

Server=lojicora1; Service=esri_sde; User=bcarroll; Version=PVA.PVA_E

Process Step 4

Process description:

Dataset copied.

Data Source used

\\gishome1.pc.lojic.local\home\bcarroll\Data Backups\PVA.gdb

Process Step 5

Process description:

Dataset copied.

Process date: 20091030 Process time: 15500200

Data Source used

Server=lojicora1; Service=esri_sde; User=bcarroll; Version=PVA.PVA_E

Process Step 6

Process description:

Dataset copied.

Process date: 20091101 Process time: 10361800

Data Source used

\\pc\home\bcarroll\Data Backups\PVA.gdb

+ 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

+ Metadata Reference

Metadata Date

Dates associated with creating, updating and reviewing the metadata.

Last updated: 20091008

Language of metadata: en

Metadata Point of Contact

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

Organization: REQUIRED: The organization responsible for the metadata information.

Person: REQUIRED: The person responsible for the metadata information.

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

Address type: REQUIRED: The mailing and/or physical address for the organization or individual.

City: REQUIRED: The city of the address.

State or Province: REQUIRED: The state or province of the address.

Postal code: REQUIRED: The ZIP or other postal code of the address.

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.