20190814
14591400
1.0
FGDC CSDGM Metadata
FALSE
ELEV_2019_contour1ft
797371.183333
797826.000000
381461.183333
381919.000000
1
002
Projected
GCS_North_American_1983_HARN
Linear Unit: Foot_US (0.304801)
NAD_1983_HARN_WISCRS_Fond_du_Lac_County_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/3.1.0'><WKT>PROJCS["NAD_1983_HARN_WISCRS_Fond_du_Lac_County_Feet",GEOGCS["GCS_North_American_1983_HARN",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",802999.999],PARAMETER["False_Northing",0.016],PARAMETER["Central_Meridian",-88.5],PARAMETER["Scale_Factor",1.0000286569],PARAMETER["Latitude_Of_Origin",42.71944444444445],UNIT["Foot_US",0.3048006096012192],AUTHORITY["Esri",103419]],VERTCS["NAVD_1988",VDATUM["North_American_Vertical_Datum_1988"],PARAMETER["Vertical_Shift",0.0],PARAMETER["Direction",1.0],UNIT["Foot_US",0.3048006096012192]]</WKT><XOrigin>-17646100</XOrigin><YOrigin>-48340000</YOrigin><XYScale>137237503.15761152</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.0032808333333333331</XYTolerance><ZTolerance>0.0032808333333333331</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>103419</WKID><LatestWKID>103419</LatestWKID></ProjectedCoordinateSystem>
20230504
11121600
20230504
11121600
ELEV_2019_contour1ft
Feature Class
0
OBJECTID
objectid
OID
4
10
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
Shape
shape
Geometry
8
0
0
Feature geometry.
Esri
Coordinates defining the features.
Id
Id
Integer
4
10
0
ELEVATION
ELEVATION
SmallInteger
2
5
0
Index10ft
Index10ft
SmallInteger
2
5
0
Index20ft
Index20ft
SmallInteger
2
5
0
Index50ft
Index50ft
SmallInteger
2
5
0
st_length(shape)
st_length(shape)
Double
0
0
0
Karen Kwsanowski
GroundPoint Technologies LLC
Chief Technical Officer
315-459-1515
17 Highland Dr
Marcellus
NY
13108
US
20230504
ArcGIS Metadata
1.0
Fon Du Lac, WI
999-999-9999
Not available
Not available
PA
99999
US
withheld
Enterprise Geodatabase Feature Class
ELEV_2019_contour1ft
2019-08-26
Karen Kwasnowski
document
Lidar Data Products for the Fon Du Lac, WI collection area includes a 3ft DEM, 1ft Contour tiles , Voids in the Ground Surface >= 8 meters squared (86.11 ft squared), Voids in the 1st Return Surface >=4meters squared (21.703 ft squared), Hydrographic Breaklines, Bridge and General Breaklines, Percent Slope and Degree Slope.
The lidar dataset was collected to be utilized for the creation of a digital elevation model, contours and hydrographic breaklines, and void polygons, and slope rasters. Other uses expected.
Thom S. Salter
Pictometry International Corp.
Manager, Photogrammetric Production
585-486-0093
585-486-0098
100 Town Centre Drive, Suite A
Rochester
NY
14623
US
0900-1700
Wisconsin
Fon Du Lac County
Geographic Names Index Service
LiDAR
EDI Thesaurus
LiDAR
Wisconsin
Fon Du Lac County
See access and use constraints information.
Access to this data is constrained by the license agreements between Pictometry International and Fon Du Lac, WI
Access to this data is constrained by the license agreements between Pictometry International and Fon Du Lac, WI.
Esri ArcGIS 13.1.0.41833
Publication Date
2019-01-01
-112.125088
-111.678816
43.623514
43.78476
1
-88.521307
-88.519585
43.767224
43.765967
Access to this data is constrained by the license agreements between Pictometry International and Fon Du Lac, WI.
Visual checks were used to make sure all features and feature classes are complete. The following topology rules are run on the contour tiles: Must not overlap, Must not have dangles, Must not self intersect.
Visual checks were used to make sure all features and feature classes are complete. The following topology rules are run on the contour tiles: Must not overlap, Must not have dangles, Must not self intersect.
Visual checks were used to make sure all features and feature classes are complete.
Breaklines for hydrographic features are digitized using the lidar data supplied by Pictometry International. The hydrographic features, include water bodies (> 0.5acres), wide rivers and channels (> 25ft wide), an artifical path representing the centerline of the wide rivers and waterbodies, stream centerlines (drainage features < 25ft wide), culverts, connectors, and general breaklines for bridges and surface features as needed. Elevation values from the lidar data are conflated to the “z-values” of the features at using QCoherent’s LP360 software. Elevation values are conflated to the Single Line Stream, Artifical Path, and Culvert features using a downstream constraint algorithm. After the artificial paths are conflated, the lp360 flatten polygon tool is used to copy the elevation values from the vertices of the artificial path to the corresponding vertices of the wide river polygon, which flattens the wide river from streambank to streambank. Elevation values for the water body polygons are conflated to the z value of the vertices and added as an attribute to the feature class based on the minimum lidar elevation value along the shoreline of the water body. Lidar ground points that are within a 2' buffer of waterbodies and widerivers and within 3’ of the stream centerlines are removed from the Ground class to create the bare earth surface. The remaining ground points, water bodies, widerivers, centerlines, and breaklines are used to create a bare earth surface (DEM) with 3ft cell resolution. Percent Rise and Degree slope rasters are created from this DEM as well as a hillshade with ESRI’s default illumination parameters. The DEM is also used to create the 1ft tiled contours. The contours are edited in the following manner: Lines shorter than 18ft (2 raster cells) are removed as they are most likely from noise in the lidar data. The contour lines are smoothed using a PAEK algorithm with a 3m smoothing tolerance. Attributes are added for 10ft, 20ft, and 50ft Index contours. The following topology rules are checked and edited: Lines Must Not Overlap, Lines Must Not Have Dangles, and Lines Must Not Self Intersect. Voids: The void analysis is based on the FEMA specifications for the Ground Point data and USGS American National Geospatial Program Lidar Base Specification v1.2 of 2014 for the 1st Return data. The USGS specification states that Data Voids => 4*Nominal Post Spacing in the 1st return lidar points is unacceptable in a single lidar swath except where caused by water bodies, areas of low infrared reflectivity, or where filled in by another swath. The FEMA specification defines data voids as Ground areas that are not within two times the DEM posting of data points, which equates to 4m for the 2ft contour interval accuracy standard. Data voids are acceptable over bodies of water or where points have been removed over man-made structures. Data voids are not acceptable with LiDAR system malfunction or flight error. Data voids need to be flagged in areas where LiDAR points have been removed due to dense vegetation. If the data voids in areas of dense vegetation are less than 1 acre then the voids may usually be filled by interpolation. If the data voids are greater than 1 acre then cross sections must be cut to fill the void areas. The lidar ground points are converted to an LAS Dataset Layer with a filter for Ground. The LAS Dataset Layer is converted to raster using the LAS Point Statistics to Raster tool, with Point Count assigned to the Method and a 9.28ft (~2.83m) cell size. The 1st Return lidar points are converted to an LAS Dataset layer with a filter for first return (does not used points flagged as Overlap or Withheld in the analysis) and then to raster using the LAS Point Statistics to Raster tool, with Point Count assigned to the Method and a 4.66ft cell size. The rasters are reclassified as NoData: 1 and Any_Value: NoData. The reclassified rasters are converted to polygon. Attributes are added for ‘Acreage” and “LandCover”. For the Ground surface, data voids > 1 acre are noted for landcover type using publicly available imagery. And a terrain dataset is created of the lidar groundpoints and breakline features classes as well.
2019-08-26
dataset
Esri
9.2.0
0
Simple
FALSE
0
TRUE
FALSE