ISO Table View
Alternate Views:
Get Data,
FAQ,
ISO Rubric,
CSW,
HTML,
Components, XML
Metadata Identifier: gov.noaa.csc.maps:2006_FL_SWFWMD_North_m65
MD_DataIdentification
| 1 |
|
2006 Southwest Florida Water Management District (SWFWMD) Lidar: North
District
|
This data set is one component of a digital terrain model (DTM) for the Southwest
Florida Water Management District's FY2006 Digital Orthophoto (B089) and LiDAR Project
(L470/L471), encompassing approximately 1,216 square miles across Citrus and Sumter
counties. The 2006 LiDAR dataset is comprised of 3-D masspoints delivered in the LAS
file format based on the District's 5,000' by 5,000' grid (1,356 cells). The other
DTM component is 2-D and 3-D breakline features in the ESRI ArcGIS Personal Geodatabase
format. In accordance with the 2006 SWFWMD Topographic Database Design, the following
breakline features are contained within the database: closed water bodies (lakes,
reservoirs, etc) as 3-D polygons; linear hydrographic features (streams, canals, swales,
embankments, etc) as 3-D breaklines; coastal shorelines as 3-D linear features; edge
of pavement road features as 3-D breakines; soft features (ridges, valleys, etc.)
as 3-D breaklines; obscured vegetation polygons as 2-D polygons; overpasses and bridges
as 3-D breaklines; 1-foot contours for visualization purposes; and island features
as 3-D polygons. This data falls in Citrus and Sumter Counties. Intensity values,
or the measure of reflectance of the laser are also captured. Breakline features were
captured to develop a hydrologically correct DTM. Contours (1-foot) were generated
from the DTM that meet the National Map Accuracy Standards for 2-foot contours (FEMA
specifications). Bare earth LiDAR masspoint data display a vertical accuracy of at
least 0.3-feet root mean square error (RMSE) in open unobscured areas
|
SV_Identification
| 1 |
|
2006 Southwest Florida Water Management District (SWFWMD) Lidar: North District |
|
|
| 1 |
|
North American Datum 1983 |
|
|
| 2 |
|
none |
|
|
| 1 |
|
|
|
|
|
resourceProvider |
http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 |
| 1 |
|
Chris O'Neill, CP, PSM |
Woolpert, Inc. |
Project Manager |
|
processor |
|
| 1 |
NOAA CSC (publisher) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
publisher |
|
| 1 |
NOAA CSC(distributor) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
distributor |
|
| 1 |
NOAA CSC (processor) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
processor |
|
| 1 |
EPSG Registry |
|
European Petroleum Survey Group |
|
|
publisher |
http://www.epsg-registry.org/ |
| 1 |
|
Mapping and GIS Section |
Southwest Florida Water Management District |
|
|
pointOfContact |
|
| 1 |
Mike Sutherland(author) |
Mike Sutherland |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
mike.sutherland@noaa.gov |
author |
|
| 1 |
Mike Sutherland |
Mike Sutherland |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
mike.sutherland@noaa.gov |
distributor |
|
| 1 |
|
Pamela Grothe |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
|
processor |
|
| 1 |
|
|
Southwest Florida Water Management District (SWFWMD) |
|
|
originator |
|
| 1 |
|
http://www.epsg-registry.org/ |
European Petroleum Survey Group Geodetic Parameter Registry |
Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured
dataset of Coordinate Reference Systems and Coordinate Transformations.
|
search |
| 1 |
|
http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 |
NAD83 |
Link to Geographic Markup Language (GML) description of reference system. |
information |
| 1 |
|
Ellipsoid in Meters |
| 1 |
|
urn:ogc:def:crs:EPSG::4269 |
|
Bounding Box |
Temporal Extent |
| 1 |
|
|
-82.73904 |
-81.94110 |
29.06432 |
28.29512 |
|
|
| 1 |
|
-82.73904 |
-81.94110 |
29.06432 |
28.29512 |
| 1 |
Lidar Use Limitation |
These data depict the elevations at the time of the survey and are only
accurate for that time. Users should be aware that temporal changes may
have occurred since this data set was collected and some parts of this data may no
longer represent actual surface conditions. Users should not use this data
for critical applications without a full awareness of its limitations. Any conclusions
drawn from analysis of this information are not the responsibility of NOAA
or any of its partners. These data are NOT to be used for navigational purposes.
|
| 1 |
Ellipsoid |
Ellipsoid in Meters |
|
| 1 |
NAD83 |
urn:ogc:def:crs:EPSG::4269 |
North American Datum 1983 |
| 1 |
|
2007-01-05T00:00:00 |
The LiDAR data was acquired using a Leica ALS50 from an altitude of
2,400' above ground level to provide an nominal ground sample distance of 2.4-feet.
The scanner field of view was 28-degrees, and the scan rate was 46-hertz. First and
last return data was collected along with the signal return intensity. A total of
278 flights of LiDAR data were acquired. Flight lines were flown with a 30% sidelap,
providing a line-to-line swath width of 957-feet. Thirty (30) Two redundant airborne
GPS bases stations were utilized during the data acquisition with maximum line-of-sight
distance between the base station and aircraft of 20-km. The LiDAR data was reduced
using Grafnav (Waypoint Consulting) for GPS post-processing, PosProc (Applanix Crop)
for IMU processing, ALS50 Post Processor (LH Systems) to initial LiDAR processing,
TerraScan (Terrasolid) for initial point classification, and proprietary Woolpert
developed software for refining the point classification and QC. The LAS files contain
5 classifications: 1 = unclassified; 2 = ground; 9 = water; and 10 = photogrammetric
mass points and 11=swamp/wetland points. The class 1 consists of all points not on
the ground. Class 2 consists of bare earth points. Class 9 points are those points
falling within lake/pond polygons. Class 10 consists of supplementary mass points
that were photogrametrically compiled on points features suchs as peaks or pits, and
they were created to maintain the accuracy of the DTM. Class 11 consists of points
within swamps and/or wetlands polygons classified as ground. For a complete description
of survey methods, processing methods, software, system parameters, and accuracy analysis,
see the Florida MTS Report of Specific Purpose Survey, North District LiDAR DTM Project
(L470/L471), dated January 2007.
|
| 1 |
|
2008-01-01T00:00:00 |
The NOAA Coastal Services Center (CSC) received the the files in LAS
format. The files contained Lidar elevation measurements. The data was in Florida
State Plane Projection and NAVD88 vertical datum. CSC performed the following processing
to the data to make it available within the LDART Retrieval Tool (LDART): 1. The data
were converted from Florida State Plane West coordinates to geographic coordinates.
2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid)
heights using Geoid03. 3. The LAS data were sorted by latitude and the headers were
updated.
|
| 1 |
|
2009-07-14T00:00:00 |
The NOAA National Geophysical Data Center (NGDC) received lidar data
files via ftp transfer from the NOAA Coastal Services Center. The data are
currently being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/.
The data can be used to re-populate the system. The data are archived in LAS
or LAZ format. The LAS format is an industry standard for LiDAR data developed by
the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless
compressed version of LAS developed by Martin Isenburg (http://www.laszip.org/). The
data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data
are referenced vertically to the ellipsoid (either GRS80 or ITRF94), allowing for
the ability to apply the most up to date geoid model when transforming to orthometric
heights.
|
|
