FondDuLac_County_BareEarth_Points_2011

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: Ayres Associates
Publication_Date: Unknown
Title:
FondDuLac_County_BareEarth_Points_2011
Geospatial_Data_Presentation_Form: vector digital data
Description:
Abstract:
The Bare Earth LAS was developed from a LiDAR flight flown in the Fall of 2011 as part of the Fond Du Lac County 2011 WROC project.
Purpose:
The 2011 Bare Earth LAS and DWG files contain a subset of the total LiDAR point cloud. This dataset constitutes the bare terrain surface data set with all other classifications omitted. File formats include: ESRI Shapefile, AutoCAD DWG, and LAS format. Coupled with the breakline features this data set is the 2011 Fond Du Lac County digital terrain model.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: Fall 2011
Currentness_Reference:
ground condition
Status:
Progress: Complete
Maintenance_and_Update_Frequency: None planned
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate:
East_Bounding_Coordinate:
North_Bounding_Coordinate:
South_Bounding_Coordinate:
Keywords:
Theme:
Theme_Keyword: lidar
Theme_Keyword: bare earth
Theme_Keyword: 2-foot contour
Place:
Place_Keyword: Fond Du Lac
Place_Keyword: County
Place_Keyword: Wisconsin
Access_Constraints: Public Domain
Use_Constraints:
To be determined by client.
Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Terry Dietzel
Contact_Position: Land Information Officer
Contact_Address:
Address:
160 S Macy St
City: Fond Du Lac
State_or_Province: Wisconsin
Postal_Code: 54935
Contact_Voice_Telephone: (920) 929-3027
Contact_Facsimile_Telephone: (920) 929-7655
Contact_Electronic_Mail_Address: terry.dietzel@fdlco.wi.gov
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.1.3000
Back to Top
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
The file parameters of all the data are correct.
Logical_Consistency_Report:
Data is consistent throughout the dataset.
Completeness_Report:
The bare earth point data covers all of the Fond Du Lac County, WI project area with no gaps or omissions.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
All map products will meet ASPRS Class II accuracy standards. The horizontal and vertical coordinates shall be referenced to the County coordinate system (NAD83 in Feet) and NAVD88
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report:
Based on tests conducted by staff from Ayres Associates:
Survey grade elevations were taken in the project area in five different types of cover. These elevations were compared with the LiDAR terrain elevation. RMSE results: Overall: 0.343
Lineage:
Source_Information:
Source_Contribution:
The LiDAR data was post processed and manually classified to develop the bare earth subset of the raw LiDAR point cloud.
Process_Step:
Process_Description:
A combination of computer-controlled navigational equipment enables a fully automated flight control system for the plane and camera, allowing flight lines and image centers to be pre-computed and programmed to airborne global positioning system (ABGPS) coordinates and altitude.  With a complete understanding of the project's specifications, acquisition technicians will perform a thorough analysis of environmental conditions (e.g., topography and hydrography).  Technicians will determine final flight specifications such as airspeed, flight height, scan width, and pulse rate.  Ground cover (natural and cultural features) within the project area will also be considered to identify density and type of vegetation and buildings.  This analysis will not only help to determine some acquisition parameters but will also later assist in determining the optimal algorithms to be used during the automated processing stage.  Mission planning consists of several steps that ensure proper flight preparation.  First and foremost, the project boundaries are imported into the flight planning software.  Following this, available information such as elevation data, vegetation coverage data, and cultural feature extents of the area are reviewed.  General assessments are made by certified photogrammetrists to determine the proper LiDAR system settings.  Project aircraft will be guided by a GPS-controlled flight management system.  During the mission, the crew will monitor all functions involving the operations and guidance systems, allowing for continuous onboard quality assurance.  The only weather to affect LiDAR collection is precipitation and cloud development below the flight plan.  LiDAR collection will be suspended during rain, snow, strong winds, or low clouds.  LiDAR collection will take place during the window between spring snow-melt and emergent-leaf conditions.  The position of the aircraft is monitored at all times using the flight management system to maintain 50% side-lap to within +/- 5%.  Tilt and crab will be monitored during flight operations.  Tilt will be held to within 4 degrees from level, no more that 1 degree average for the entire project, and less than 5 degrees between frames.  Tilt will also be monitored during post-processing to ensure compliance.  The values for degrees heading and tracking are used to determine the crab offset.  This offset will be applied to the LiDAR system to obtain less than 5 degrees from the line of flight.  Coverage verification is achieved using the post-flight processed GPS solution.  Both horizontal and vertical aircraft position and orientation will be verified and plotted against the 3-D flight plan to ensure proper coverage of topographic data.  After each flight, the data is field-checked for coverage and quality before shipping the data for processing.  The LiDAR data is pre-processed in the field for quick projection of data acquisition swath coverage.  Any seams, holes, or other unwanted artifacts can be quickly identified at this stage to assess the need for any data acquisition reflights.  The flight operations team will remain on-site during this phase until all required project data is acquired.  A site is selected at the nearest airport to the project area to validate the system calibration.  The calibration site is flown before each data acquisition flight mission.  Two opposing flight lines, as well as a cross-flight, will be flown to identify any potential issues in the system calibration.  A system calibration file is generated with each data acquisition flight mission and is used in the processing of all LiDAR data.  Upon completion of the LiDAR acquisition mission, the ABGPS and inertial measurement unit (IMU) data is processed and synchronized.  Applanix Corporation's POSPac software will be used for the integration of GPS and IMU data to create an SBET.  The SBET describes the precise position and attitude of the plane at each moment for the full duration of the mission.  Technicians will use a database management system for housing the LiDAR dataset (usually multiple gigabytes in size).  Additionally, the program incorporates a thorough checklist of processing steps and quality assurance/quality control (QA/QC) procedures that assist the technicians in the LiDAR workflow.  After technicians establish the SBET, they apply the solution to the dataset in order to adjust each point based on aircraft position and orientation during LiDAR acquisition.  A second set of software is used to automate the initial classification of the LiDAR point cloud based on a set of predetermined parameters.  It is at this point that technicians will refer to the ground cover research (natural and cultural features) within the project area (some algorithms/filters recognize the ground in forests well, while others have greater capability in urban areas).  During this process, each point is given an initial classification (e.g., as ground, water, vegetation, or building) based on the point's coordinates and its relation to its neighbors.  Classifications to be assigned include all those outlined by ASPRS standards (Class 10 is designated as ignored ground).  The initial values offer a coarse and inexact dataset but are a good starting point for the subsequent manual classification procedure.  It is during this step that overlap points are automatically classified (those originating from neighboring flightlines).  This classification is based on information gathered from the ABGPS and IMU data.  After hydrographic breaklines have been collected using LiDARgrammetry, polygons are formed to represent open water bodies, including lakes, streams wider than 8 feet, and ponds.  All LiDAR points that fall within these areas are classified as water.  It is after this point that a manual classification of the LiDAR points occurs.  The software permits technicians to view the point cloud in a number of ways and within a number of contexts provided by other available datasets such as orthos or road centerline files.  After querying specific tiles into their workspace, technicians will begin scanning through the tile, searching for areas where the automated classification routine erred.  They will view the datasets from numerous angles, generate triangulated irregular networks (TIN) or contours, and consult shaded relief models to fully understand the data model at each point of their analysis.  Using this information and technical experience, our technicians will detect and investigate any areas that display anomalies i.e., areas where the automated classifications show weakness.  The technicians will systematically work their way through these anomalous areas: taking narrow swaths of data, viewing the swath from isometric and profile viewpoints, reclassifying each point in accordance with their judgment.  Eligible classifications are focused upon.  These include unclassified (buildings, vegetations, and other non-terrain/non-noise features), ground, and noise.  Points falling under the water and overlap categories are weeded out effectively during automated procedures.  After this process is complete for the area, the technician will generate new TINs and contours to determine that the anomaly has been fully addressed. If it has, the technician will continue scanning the tile for other anomalies.  This procedure will continue until the tile has been determined to meet or exceed project specifications.  At this point, the technician will query the next adjacent tile and continue working.
Back to Top
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: Entity point
Point_and_Vector_Object_Count: 1549748
Back to Top
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Transverse Mercator
Transverse_Mercator:
Scale_Factor_at_Central_Meridian: 1.000029
Longitude_of_Central_Meridian: -88.500000
Latitude_of_Projection_Origin: 42.719444
False_Easting: 802999.999000
False_Northing: 0.016000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.000000
Ordinate_Resolution: 0.000000
Planar_Distance_Units: survey feet
Geodetic_Model:
Horizontal_Datum_Name: D_North_American_1983_HARN
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Resolution: 0.000328
Altitude_Encoding_Method: Explicit elevation coordinate included with horizontal coordinates
Back to Top
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: FondDuLac_County_BareEarth_Points_2011
Attribute:
Attribute_Label: FID
Attribute_Definition:
Internal feature number.
Attribute_Definition_Source:
ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition:
Feature geometry.
Attribute_Definition_Source:
ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Coordinates defining the features.
Attribute:
Attribute_Label: LAYER
Attribute:
Attribute_Label: ELEVATION
Attribute:
Attribute_Label: CLASS
Attribute_Definition:
1 = Processed, Unclassified, 2 = Bare Earth Ground, 3 = Low vegetation, 4 = Medium vegetation, 5 = High vegetation, 6 = Building, 7 = Noise, 8 = Res. (Model keypoints), 9 = Water, 10 = Ignored Ground, 11 = Road, 12 = Res. (Overlap), 13= Railroad, 14, = Stream, 15 = Wire, 21 = High Points, 22 = Spurious Intensity, 31 = First of Many, 32 = Intermediate, 33 = Last of Many, 34 = Single/Only (Ground)
Attribute_Definition_Source:
http://www.asprs.org/a/society/committees/standards/asprs_las_format_v12.pdf
Attribute:
Attribute_Label: INTENSITY
Attribute_Definition:
The intensity value is the integer representation of the pulse return magnitude.
Attribute_Definition_Source:
http://www.asprs.org/a/society/committees/standards/asprs_las_format_v12.pdf
Attribute:
Attribute_Label: SCAN_ANGLE
Attribute_Definition:
The angle (rounded to the nearest integer in the absolute value sense) at which the laser point was output from the laser system including the roll of the aircraft.
Attribute_Definition_Source:
http://www.asprs.org/a/society/committees/standards/asprs_las_format_v12.pdf
Attribute:
Attribute_Label: RETURN_CNT
Attribute_Definition:
The pulse return number for a given output pulse.
Attribute_Definition_Source:
http://www.asprs.org/a/society/committees/standards/asprs_las_format_v12.pdf
Attribute:
Attribute_Label: GPS_TIME
Attribute_Definition:
The double floating point time tag value at which the point was acquired.
Attribute_Definition_Source:
http://www.asprs.org/a/society/committees/standards/asprs_las_format_v12.pdf
Back to Top
Metadata_Reference_Information:
Metadata_Date: 20120724
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Ayres Associates
Contact_Address:
Address_Type: mailing and physical address
Address:
1802 Pankratz Street
City: Madison
State_or_Province: Wisconsin
Postal_Code: 53704-9609
Contact_Voice_Telephone: (608) 443-1200
Contact_Facsimile_Telephone: (608) 443-1250
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: http://www.esri.com/metadata/esriprof80.html
Profile_Name: ESRI Metadata Profile
Back to Top