{3D77BF39-4E71-47DE-BF0A-078D3AD204A6}
20040908
06371200
FALSE
20220620
21170000
20220620
21170000
Contour_100
002
Projected
GCS_North_American_1983
Linear Unit: Foot_US (0.304801)
NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/2.9.0'><WKT>PROJCS["NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",2000000.002616666],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-79.0],PARAMETER["Standard_Parallel_1",34.33333333333334],PARAMETER["Standard_Parallel_2",36.16666666666666],PARAMETER["Latitude_Of_Origin",33.75],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2264]]</WKT><XOrigin>-121841900</XOrigin><YOrigin>-93659000</YOrigin><XYScale>3048.0060960121918</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.0032808333333333331</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102719</WKID><LatestWKID>2264</LatestWKID></ProjectedCoordinateSystem>
ESRI ArcCatalog 9.2.1.1332
en
Yancey County shapefile for 100 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: 1751 to 6682 feet.
Elevation Mean: 3350.0584 Feet
Elevation Standard Deviation: 840.5391
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
April, 2007
Yancey County - Contour 100 foot
contour
vector digital data
withheld
publication date
April, 2007
As Needed
0
0
0
0
0
0
0
0
-130
6684
Feet
Contour
LiDAR
FloodMapping
Yancey 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.
Shapefile
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 ArcGIS 12.9.2.32739
Contour_100
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
20070426
ISO 19115 Geographic Information - Metadata
DIS_ESRI1.0
dataset
Downloadable Data
70.035
70.035
002
withheld
Local Area Network
70.035
Shapefile
File Geodatabase Feature Class
Vector
Simple
FALSE
0
TRUE
FALSE
GCS_North_American_1983
NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet
coordinate pair
survey feet
0.000000
0.000000
North American Datum of 1983
Geodetic Reference System 80
6378137.000000
298.257222
North American Vertical Datum of 1988
feet
Attribute values
NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet
EPSG
6.12(9.0.0)
2
4532
20
7406
20
1
0
Contour_100
Feature Class
0
Elevation
OBJECTID
OID
4
0
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
INTERVAL
Shape
Geometry
0
Identifies the contour interval. (2, 5, 10, 20, 100, or 500 foot interval)
0
0
Esri
Coordinates defining the features.
Shape
TILE
String
8
Feature geometry.
ESRI
Coordinates defining the features.
0
0
TILE
Interval
SmallInteger
2
Identifies the four digit county index tile location.
0
0
Interval
Elevation
SmallInteger
2
0
0
Shape_Length
Shape_Length
Double
8
0
0
Length of feature in internal units.
Esri
Positive real numbers that are automatically generated.
20220620
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")
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.