Frequently-anticipated questions:
Title: stm.DBO.StormPipes_ln
Abstract: Inventoried pipes in Mecklenburg County
- How should this data set be cited?
Charlotte-Mecklenburg Storm Water Services Agency
- What geographic area does the data set cover?
West_Bounding_Coordinate: -81.013727
East_Bounding_Coordinate: -80.602090
North_Bounding_Coordinate: 35.511319
South_Bounding_Coordinate: 35.015191
- What does it look like?
- Does the data set describe conditions during a particular time period?
Calendar_Date: 2004 forward
Time_of_Day: unknown
Currentness_Reference: publication date
- What is the general form of this data set?
Geospatial_Data_Presentation_Form: vector digital data
- How does the data set represent geographic features?
- How are geographic features stored in the data set?
This is a Vector data set. It contains the following vector data types (SDTS terminology):
- What coordinate system is used to represent geographic features?
The map projection used is Lambert Conformal Conic.
Projection parameters:
Standard_Parallel: 34.333333
Standard_Parallel: 36.166667
Longitude_of_Central_Meridian: -79.000000
Latitude_of_Projection_Origin: 33.750000
False_Easting: 2000000.002617
False_Northing: 0.000000
Planar coordinates are encoded using coordinate pair
Abscissae (x-coordinates) are specified to the nearest 0.000625
Ordinates (y-coordinates) are specified to the nearest 0.000625
Planar coordinates are specified in survey feet
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: 1.000000
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates
- How does the data set describe geographic features?
stm.DBO.StormPipes_ln
OBJECTID
Internal feature number. (Source: ESRI)
Sequential unique whole numbers that are automatically generated.
PIPE_ID
Unique ID for pipe (Source: City of Charlotte Storm Water)
Work Zone ID, unique number, upstream structure ID
DS_DEPTH
Depth of downstream structure/junction (Source: City of Charlotte Storm Water)
Depth of downstream structure/junction
INVEN_BY
Person who collected inventory (Source: City of Charlotte Storm Water)
Person who collected inventory
DS_ELEV
Top elevation of downstream point (Source: City of Charlotte Storm Water)
Top elevation of downstream point
DS_INVERT
Invert of downstream structure in dec feet (Source: City of Charlotte Storm Water)
Invert of downstream structure in dec feet
NOTES
Notes referring to feature (Source: City of Charlotte Storm Water)
Notes
DS_FUNC
Whether downstream end is functioning (Source: City of Charlotte Storm Water)
|
Value
|
Definition
|
|
Yes
|
Yes, downstream end is functioning
|
|
No
|
No downstream end is not functioning
|
ENABLED
Feature geometry. (Source: ESRI)
Coordinates defining the features.
SHAPE
Feature geometry. (Source: ESRI)
Coordinates defining the features.
MEDIA_LINK
Link to picture (Source: City of Charlotte Storm Water)
Filepath for pictures
DS_ID
Down Stream ID (Source: WISE)
Auto populated down stream ID
STD_CMMNT
Standard Comments (Source: City of Charlotte Storm Water)
|
Value
|
Definition
|
|
No access to structure
|
(structures) Unable to physically access structure - minimal attributes input
|
|
Pipe not followed
|
(pipestubs) Pipe not followed to next structure/junction
|
|
Next structure not found
|
(pipestubs) Next structure not found
|
|
Channel data estimated
|
(channels) Large stream dimensions estimated
|
Coordinates defining the features.
US_ID
Up Stream ID (Source: WISE)
Auto populated up stream ID
Shape
Feature geometry. (Source: ESRI)
Coordinates defining the features.
TYPE
Type of pipe (Source: City of Charlotte Storm Water)
|
Value
|
Definition
|
|
Pipe
|
|
|
Pipestub
|
|
PI_SHAPE
Pipe shape (Source: City of Charlotte Storm Water)
|
Value
|
Definition
|
|
Circ
|
Circular
|
|
Arch
|
Arch
|
|
Box
|
Box
|
|
Unk
|
Unknown
|
|
Elps
|
Elliptical
|
|
Oth
|
Other (Input shape below)
|
|
N/A
|
Not Applicable
|
PI_SHP_OTH
Other pipe shape if not listed in domain (Source: City of Charlotte Storm Water)
Other pipe shape
DIAMETER
Diameter of pipe (Source: City of Charlotte Storm Water)
|
Value
|
Definition
|
|
1
|
1.00 (12")
|
|
1.25
|
1.25 (15")
|
|
1.5
|
1.50 (18")
|
|
2
|
2.00 (24")
|
|
2.5
|
2.50 (30")
|
|
3
|
3.00 (36")
|
|
3.5
|
3.50 (42")
|
|
4
|
4.00 (48")
|
|
4.5
|
4.50 (54")
|
|
5
|
5.00 (60")
|
|
5.5
|
5.50 (66")
|
|
6
|
6.0 (72")
|
|
9999
|
Input diameter in feet tenths below
|
DIAM_OTHER
Other diameter if not listed in domain (Source: City of Charlotte Storm Water)
Other pipe diameter
US_ELEV
Top elevation of upstream point (Source: City of Charlotte Storm Water)
Top elevation of upstream point
PIPE_RISE
Pipe rise (Source: City of Charlotte Storm Water)
Pipe rise
PIPE_SPAN
Span of pipe in decimal feet (Source: City of Charlotte Storm Water)
Pipe span in decimal feet
MATERIAL
Pipe material (Source: City of Charlotte Storm Water)
|
Value
|
Definition
|
|
RCP
|
Reinforced Concrete Pipe
|
|
VCP
|
Vitrified Clay
|
|
Oth
|
Other - Other (input material below)
|
|
Unk
|
Unknown
|
|
N/A
|
Not Applicable
|
|
CMP
|
Corrugated Metal or Steel
|
|
HOPE
|
Plastic Pipe
|
MAT_TEXT
Other material if not listed in domain (Source: City of Charlotte Storm Water)
Other pipe material
US_FUNC
Whether upstream is end functioning (Source: City of Charlotte Storm Water)
|
Value
|
Definition
|
|
Yes
|
Yes upstream end is functioning
|
|
No
|
No upstream end is not functioning
|
INV_DATE
Date of inventory collection (Source: City of Charlotte Storm Water)
Date of inventory collection
Enabled
Feature geometry (Source: ESRI)
Auto generated integer
US_DEPTH
Depth of upstream structure/junction (Source: City of Charlotte Storm Water)
Depth of upstream structure/junction
US_INVERT
Invert of upstream structure/junction (Source: City of Charlotte Storm Water)
Invert of upstream structure/junction
SLOPE
len_1
SHAPE.STLength()
- Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
- Who also contributed to the data set?
- To whom should users address questions about the data?
Catherine Crigler
City of Charlotte
Inventory Coordinator
600 E 4th St
Charlotte, NC 28202
704-336-5735 (voice) or email: ccrigler@charlottenc.gov
Create inventory network to track assets and use with Storm Water projects
- From what previous works were the data drawn?
- How were the data generated, processed, and modified?
(process 1 of 5)
Locate structures with GPS technology and enter structure attributes and linear features using mobile GIS software.
Data sources used in this process:
- Server=isp-sde-01.isp.lcl; Service=5151; User=SDE; Version=sde.DEFAULT
(process 2 of 5)
Dataset copied.
Data sources used in this process:
- Server=virt-sde-01; Service=5162; Database=storm; User=storm; Version=STORM.Storm_edit
Date: 11-Nov-2008 (process 3 of 5)
Metadata imported.
Data sources used in this process:
- H:\Metadata\sw_drainage.xml
(process 4 of 5)
Metadata imported.
Data sources used in this process:
- H:\Metadata\Storm_pipe.xml
(process 5 of 5)
Metadata imported.
Data sources used in this process:
- H:\Metadata\Storm_pipe.xml
- What similar or related data should the user be aware of?
- How well have the observations been checked?
We try to minimize the room for input error by creating domains and automatically populated fields. However, there is still room for error and we check all field data for missing attributes and logical errors.
- How accurate are the geographic locations?
sub-meter GPS accuracy for 2004 and beyond
- How accurate are the heights or depths?
based on 2002 DTM (10 ft cells)
- Where are the gaps in the data? What is missing?
The inventory collection is ongoing with a goal to recapture the pre-2004 data and complete all remaining inventory within the city limits. After initial completion, the inventory effort will continue in order to collect data on new construction, repaired systems, and annexed areas.
- How consistent are the relationships among the observations, including topology?
All data with an Inventory Date of 2004 and beyond has been collected with sub-meter GPS equipment and reviewed for locational accuracy against aerial photography. All data with an Inventory Date before 2004 was located manually and not all of the data has been checked against current aerial photography.
Are there legal restrictions on access or use of the data?
User must understand and read disclaimer provided with the data and terms of use on Charmeck.org
- Who distributes the data set? (Distributor 1 of 1)
Catherine Crigler
City of Charlotte
Inventory Coordinator
600 E 4th St
Charlotte, NC 28202
704-336-5735 (voice)
- What's the catalog number I need to order this data set?
Downloadable Data
- What legal disclaimers am I supposed to read?
In no event shall the City of Charlotte and/or Mecklenburg County Government be liable for any special, indirect, or loss of use, data or profits, whether in an action of contract, negligence or other tortuous action, arising out of or in connection with the use or performance of software, documents, provision of, or failure to provide services or information available from this data.
- How can I download or order the data?
- Availability in digital form: from Charmeck.org/stormwater
Dates:
Last modified: 09-Mar-2011
Metadata author:
Samantha Willis, GIS Analyst, City of Charlotte, E&PM, Storm Water Services Agency
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:
· <http://www.esri.com/metadata/esriprof80.html>
· <http://www.esri.com/metadata/esriprof80.html>
· <http://www.esri.com/metadata/esriprof80.html>
· <http://www.esri.com/metadata/esriprof80.html>
Generated by mp version 2.9.6 on Wed Mar 09 12:38:23 2011