Geodataset Name:       TOPO2FT_CDM
Geodataset Type:       FILE GEODATABASE (ArcGIS 9.2 or later)
Geodataset Feature:    Polyline
Feature Count:         837894

DATA SOURCE(S):                    Florida Division of Emergency Management
SCALE OF ORIGINAL SOURCE MAPS:     24000
GEODATASET EXTENT:                 Duval County

PUBLICATION DATE:                  20090211
TIME PERIOD OF CONTENT:            Begin Date: 20070317    End Date: 20070318
DOWNLOAD LINK:                     http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: TOPO2FT_CDM.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
Shape	Feature geometry.
EntID	Undefined by Source
CONTOUR_ELEVATION_MS	Contour elevation
CONTOUR_TYPE_DESC	Contour type 1 = INTERMEDIATE contours (the three or four lines between adjacent index contours) are about half the line weight of index contours. They are normally continuous throughout a map, but may be dropped or joined with an index contour where the slope is steep and where there is insufficient space to show all of the intermediate lines. 2 = SUPPLEMENTARY contours are used to portray important relief features that would otherwise not be shown by the index and intermediate contours (basic contours). They are normally added only in areas of low relief, but they may also be used in rugged terrain to emphasize features. Supplementary contours are shown as screened lines so that they are distinguishable from the basic contours, yet not unduly prominent on the published map. 3 = DEPRESSION contours are closed contours that surround a basin or sink. They are shown by right-angle ticks placed on the contour lines, pointed inward (down slope). Fill contours are a special type of depression contours, used to indicate an area that has been filled to support a road or railway grade. 4 = INDEX contours are defined as every 5th contour line. For example, with the Contour_2FT feature class, the first positive intermediate contour would be 0 with the following index contours at 10, 20, 30 feet, etc. 5 = INTERMEDIATE LOW CONFIDENCE 6 = SUPPLEMENTARY LOW CONFIDENCE 7 = DEPRESSION LOW CONFIDENCE 8 = INDEX LOW CONFIDENCE
DATESTAMP_DT	When the feature was added to the Geodatabase
CARRYING_CONTOUR_ELEVATION_MS	Undefined by Source
SOURCE	Abbreviated 3-letter code representing the data source.
FGDLAQDATE	Date FGDL acquired data from source
AUTOID	Unique ID added by GeoPlan
SHAPE.LEN	Length in meters

Entity and Attribute information designed in accordance to FDEM Baseline Specifications 0.9 (Attachment 3)

USER NOTES:

Contours were generated from 30-foot DEM generated from the LIDAR data and breaklines. These breaklines were determined from LiDAR and stereo tile (LiDAR grammetry) data of specific dates and that model the land/water contributions and extents on those dates. The 3-D vector line work was created using stereo-compilation. A thorough QC procedure was implemented to verify the elevation of the breaklines and to ensure no zero elevations were found except in coastal areas where it is possible to find z values equal to mean sea level. Additional QC steps were taken to ensure all breaklines agree with the vertical location of the LiDAR. The DTM was developed in accordance with the Baseline Specifications 0.9. The DTM is intended to support 2-foot contours, and the vertical accuracy of ground points in unobscured areas is not to exceed 0.6-feet RMSE. A thorough QC was implemented to verify the breakline elevation accuracy.

All breakline features are an accurate three-dimensional representation of the surface with varying elevations. Roadbreakline features were captured at edge of pavement. The LiDAR (masspoint) feature class consists of 1054 tiles (Duval County).

GeoPlan relied on the integrity of the attribute information within the original data.

Sensor Description - Intergraph DMC serial number 001-0046

The DTM was developed to support the Florida Division of Emergency Management (FDEM) development and maintenance of Regional Evacuation Studies (Study), which include vulnerability assessments and assist disaster response personnel in understanding threats to Florida's citizens and visitors. Breaklines improve the digital elevation model in areas where the point density is insufficient.

Horizontal accuracy is +/- 3.8-foot at the 95% confidence level using RMSE(r) x 1.7308 as defined by the FGDC Geospatial Positional Accuracy Standards, Part 3: NSSDA.

0.3-feet RMSE for unobscured ground points. The accuracy assessment was performed using a standard method to compute the root mean square error (RMSE) based on a comparison of ground control points and filtered LiDAR data points. Filtered LiDAR data has had vegetation and cultural features removed and by analysis represents bare earth elevations. The RMSE figure was used to compute the vertical National Standard for Spatial Data Accuracy (NSSDA).

This data is for planning purposes only and should not be used for legal or cadastral purposes. Regional Evacuation Studies are currently being updated and www.floridadisaster.org/gis should be consulted for revisions.

The Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist. Furthermore, the GIS data available in the FGDL are provided 'as is'. The University of Florida GeoPlan Center makes no warranties, guaranties or representations as to the truth, accuracy or completeness of the data provided by the data sources. The University of Florida GeoPlan Center makes no representations or warranties about the quality or suitability of the materials, either expressly or implied, including but not limited to any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. The University of Florida GeoPlan Center shall not be liable for any damages suffered as a result of using, modifying, contributing or distributing the materials. A note about data scale: Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modeling purposes. Please be sure you are using the best available data. 1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:125000 scale datasets are recommended for projects that are at the regional or state level or larger. Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analysis. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our webpage at: http://geoplan.ufl.edu/education.html

REFERENCES:

http://www.floridadisaster.org/gis/LiDAR/index.htm Baseline Specifications for Orthophotography and LiDAR: http://www.floridadisaster.org/gis/specifications/Documents/BaselineSpecifications_1.2.pdf Standards for 1:24,000 Scale Digital Line Graphs: http://rockyweb.cr.usgs.gov/nmpstds/acrodocs/dlgqmap/7dqm0401.pdf

DATA LINEAGE SUMMARY:

The Airborne Global Positioning System (ABGPS), inertial measurement unit (IMU), and raw scans are collected during the LiDAR aerial survey. The ABGPS monitors the xyz position of the sensor and the IMU monitors the orientation. During the aerial survey laser pulses reflected from features on the ground surface are detected by the receiver optics and collected by the data logger. GPS locations are based on data collected by receivers on the aircraft and base stations on the ground. The ground base stations are placed no more than 20 mile radius from the flight survey area. Process Date: 20090211 The ABGPS, IMU, and raw scans are integrated. The resultant file is in a LAS binary 1.1 file format. The LAS file format can be easily transferred from one file format to another. It is a binary file format that maintains information specific to the LiDAR data (return#, intensity value, xyz, etc.). The resultant points are produced in the Florida State Plane east Zone coordinate system, with units in feet and referenced to the NAD83/90 HARN horizontal datum and NAVD88 vertical datum. Process Date: 20090211 The unedited data are classified to facilitate the application of the appropriate feature extraction filters. Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. Process Date: 20090211 Filtered Lidar and vector data are subjected to rigorous QA/QC procedures designed by Sanborn. Terramodel software was used to display the edited LiDAR points and associated GEOTIFF orthophotos to construct breaklines for the edge pavement. Breakline elevations were linearly ramped between identified critical elevation points along roads. Process Date: 20090211 The contours are generated from Lidar data and breaklines using a contour generation function in Terrascan. The Lidar data is gridded to a 30' grid and incorporated with the 3d breaklines. A process is run to remove the gridded point from within 15' of the breaklines and Terrascan automatically generates the contours using specific input criteria to include contour interval, line type, smoothness and minimum size. Process Date: 20090211 GeoPlan received this data via hard drive from Jones Edmunds on 8/27/09. When received the data was in 3 personal geodatabases. The data was merged into 1 file geodatabase. The feature class was then projected from UTM NAD83 HARN - feet to Albers HPGN. -Added SOURCE field and populated all values to CDM -Added FGDLAQDATE field based on date GeoPlan acquired data from source -Changed name from DUVAL_CONTOUR_CENTRAL, DUVAL_CONTOUR_EAST, DUVAL_CONTOUR_WEST to TOPO2FT_DUVAL Process Date: 20091002

MAP PROJECTION PARAMETERS:

Projection                          ALBERS
Datum                               HPGN
Units                               METERS
Spheroid                            GRS1980
1st Standard Parallel               24  0  0.000
2nd Standard Parallel               31 30  0.000
Central Meridian                   -84 00  0.000
Latitude of Projection's Origin     24  0  0.000
False Easting (meters)              400000.00000
False Northing (meters)             0.00000

DATA SOURCE CONTACT (S):

Name:
Abbr. Name:
Address:


Phone:

Web site:
E-mail:
Contact Person:
         Phone:
        E-mail:

Florida Division of Emergency Management
FDEM
2555 Shumard Oak Boulevard
Tallahassee, Florida
32399-2100
850-413-9907


http://www.floridadisaster.org/gis
richard.butgereit@em.myflorida.com
Richard Butgereit

Name:                   FLORIDA GEOGRAPHIC DATA LIBRARY
Abbr. Name:             FGDL
Address:                Florida Geographic Data Library
                        431 Architecture Building
                        PO Box 115706
                        Gainesville, FL  32611-5706
Web site:               http://www.fgdl.org

Contact FGDL: 

      Technical Support:	        http://www.fgdl.org/fgdlfeed.html
      FGDL Frequently Asked Questions:  http://www.fgdl.org/fgdlfaq.html
      FGDL Mailing Lists:		http://www.fgdl.org/fgdl-l.html
      For FGDL Software:                http://www.fgdl.org/software.html