20221128
13160000
FALSE
20081007
08110600
20081007
08110600
1.0
ESRI ArcCatalog 9.2.6.1500
en
Rutherford County shapefile for 20 foot contours. There are three attribute fields. ELEVATION - Number of feet above sealevel. TILE - Identifies the four digit county index tile location. INTERVAL - Identifies the contour interval. (2, 4, 10, 20, 100, or 500 foot interval)
Elevation Range: 664 to 3967 feet.
Elevation Mean: 1118.6933 Feet
Elevation Standard Deviation: 374.4114
General purpose display of contour data. You should not expect the contours to be exact. The vertical datum used is NAVD 88, but the accuracy of the LIDAR is about 25cm (10 inches), however, using two foot contours might be pushing data beyond the intended accuracy.
The vertical datum used is NAVD 88.
The vertical accuracy of the LIDAR is about 25cm (10 inches).
Original data for elevation is stored in 20 foot grid cells.
Each cell represents an interpolated elevation for the 20-foot cell.
Water cause inaccuracy in the LIDAR data and
lakes and sounds might not be represented correctly.
Refer to NCDOT-GIS and Flood Mapping Web sites
NCDOT GIS Branch, based on the Flood Mapping LIDAR data.
GIS web site: http://www.ncdot.org/it/gis/
Flood Mapping web Site: http://www.ncfloodmaps.com/default_swf.asp
May, 2007
Rutherford County - Contour 20 foot
rutherford_vector.RUTHERFORD.Lidar_2007_Contours_20
vector digital data
withheld
publication date
May, 2007
As Needed
0
0
0
0
0
0
0
0
-130
6684
Feet
Contour
LiDAR
FloodMapping
Rutherford County
North Carolina
None.
The North Carolina Department of Transportation shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data. This data may not be resold.
Feature Class
NC Department of Transportation
GIS Help Desk (gishelp@dot.state.nc.us)
Mailing Address
1587 Mail Service Center
Raleigh
NC
27699-1587
USA
(919)-212-6000
8AM-5PM M-F
LIDAR data is maintained by the Flood Mapping Program.
ESRI ArcCatalog 9.2.6.1500
rutherford_vector.RUTHERFORD.Lidar_2007_Contours_20
0
0
0
0
1
-79.36057
-78.970343
35.628316
35.306643
1
en
FGDC Content Standards for Digital Geospatial Metadata
FGDC-STD-001-1998
local time
GIS Help Desk (gishelp@dot.state.nc.us)
NC Department of Transportation
Mailing Address
1587 Mail Service Center
Raleigh
NC
27699-1587
(919)-212-6000
20081007
http://www.esri.com/metadata/esriprof80.html
ESRI Metadata Profile
ISO 19115 Geographic Information - Metadata
DIS_ESRI1.0
dataset
Downloadable Data
70.035
70.035
002
withheld
Local Area Network
70.035
Feature Class
Vector
Simple
Polyline
FALSE
0
TRUE
FALSE
String
0
GCS_North_American_1983
NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet
coordinate pair
survey feet
0.000328
0.000328
Lambert Conformal Conic
34.333333
36.166667
-79.000000
33.750000
2000000.002617
0.000000
North American Datum of 1983
Geodetic Reference System 80
6378137.000000
298.257222
North American Vertical Datum of 1988
feet
Attribute values
1.000000
NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet
0
2
4532
20
7406
20
1
Elevation
Elevation
SmallInteger
4
4
0
rutherford_vector.RUTHERFORD.Lidar_2007_Contours_20
Feature Class
0
INTERVAL
INTERVAL
Number
3
Identifies the contour interval. (2, 5, 10, 20, 100, or 500 foot interval)
Shape
Shape
Number
4
Feature geometry.
ESRI
Coordinates defining the features.
TILE
TILE
String
8
Identifies the four digit county index tile location.
OBJECTID
OBJECTID
OID
4
10
0
Internal feature number.
ESRI
Sequential unique whole numbers that are automatically generated.
Interval
Interval
Number
4
Shape.len
Shape.len
Double
0
0
0
20081007
ground condition
Visual Basic Program with GeoProcessing
ArcGIS 9.2; Windows 2000; 3.192 GHZ; 1.022 GB RAM; Processing Time: 16.1 Minutes; Usercode: bmiller
July, 2007
16.1 Minutes
Bill Miller
NCDOT
Programmer
bmiller@dot.state.nc.us
To build contours,
Integer grids were used to allow for faster processing.
The integer grid is rounded to the nearest 1/10th of a foot.
A filter is run to reduce extreme elevation changes.
A resample is done to create smoother contour lines.
The input grid is also buffered by 1 mile to produce lines
that are edgematched and avoid removing valid short lines.
In mountainous areas the contours must be done
with an 20 foot interval to avoid memory errors.
Merge all the contours together to create a complete file.
Building Contours using Visual Basic
***************************************************************** dblZfactor = 0.1
***************************************************************** Call pGp.Filter_sa("MosaicGrid", "ElevFilter", "LOW", "DATA")
***************************************************************** Call pGp.SingleOutputMapAlgebra_sa("int( Resample(ElevFilter, 10, bilinear) + 0.5 )", "ElevResample")
***************************************************************** Call pGp.Contour_sa("ElevResample", "Contours_Measured", 20, (0 + 0.02), dblZfactor)
***************************************************************** Call pGp.addfield_management("Contours_Measured", "Elevation", "short", 6)
***************************************************************** ' Routine to find looping routes and set Elevation to -9 if it is a loop and less than 150 feet.
***************************************************************** Call *FindShortLoopContours("Contours_Measured")
***************************************************************** Call pGp.Select_Analysis("Contours_Measured", "Contours_Valid", "( Shape_Length > 75 and Elevation <> -9 ) or ( Shape_Length > 150 )")
***************************************************************** Call pGp.SimplifyLine_management("Contours_Valid", "Contours_Simplify", "POINT_REMOVE", "3 Feet", "FLAG_ERRORS", "NO_KEEP", "NO_CHECK")
***************************************************************** Call pGp.CalculateField_management("Contours_Simplify", "Elevation", "[Contour]")
***************************************************************** Call pGp.Identity_analysis("Contours_Simplify", "Grid10000", "Contours_Identity", "ALL", "0.1 Feet", "NO_RELATIONSHIPS") ***************************************************************** Call pGp.Clip_analysis("Contours_Identity", "ClipPolygon", "Contours_Clipped", "0.1 Feet")
Dataset copied.
withheld
20100121
11171600
You should not expect the contours to be exact. The vertical datum used is NAVD 88, but the accuracy of the LIDAR is about 25cm or about 10 inches, however, using two foot contours might be pushing data beyond the intended accuracy.