2FT CONTOUR LINES - ESCAMBIA COUNTY

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: Florida Division of Emergency Management
Publication_Date: 20080501
Publication_Time: Unknown
Title:
2FT CONTOUR LINES - ESCAMBIA COUNTY
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Tallahassee, FL
Publisher: Florida Division of Emergency Management
Other_Citation_Details:
Escambia County
Online_Linkage: http://www.floridadisaster.org/gis
Description:
Abstract:
Lidar generated 2-foot contours for North Florida.
Purpose:
Contours consistent with the deliverables and including a certain level of 
smoothing. Index, Intermediate, Depression, Supplementary and Low confidence 
contours are coded.
Supplemental_Information:
A complete description of this dataset is available in the Minimum Technical 
Standard ( MTS report) "Final Report OF Specific Purpose LiDAR Survey - 
LiDAR-Generated Breaklines and Contours" submited to Florida Division of 
Emergency Management.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20080501
Currentness_Reference:
publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -87.518580
East_Bounding_Coordinate: -86.839949
North_Bounding_Coordinate: 30.698475
South_Bounding_Coordinate: 30.282586
Keywords:
Theme:
Theme_Keyword_Thesaurus: NONE
Theme_Keyword: Breakline
Theme_Keyword: DTM
Theme_Keyword: DSM
Theme_Keyword: Contour
Theme_Keyword: Elevation
Theme_Keyword: Lidargrammetry
Theme_Keyword: Lidar
Place:
Place_Keyword_Thesaurus: None
Place_Keyword: Florida
Place_Keyword: Escambia County
Place_Keyword: United States
Access_Constraints: This data may be used by the requested party for stated purposes and should not be re-distributed.
Use_Constraints:
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.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Florida Division of Emergency Management
Contact_Address:
Address_Type: mailing and physical address
Address:
2555 Shumard Oak Boulevard
City: Tallahassee
State_or_Province: FL
Postal_Code: 32399-2100
Country: USA
Contact_Voice_Telephone: 850-413-9907
Contact_Facsimile_Telephone: 850-488-1016
Contact_Electronic_Mail_Address: gis@dca.state.fl.us
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.1.4000
Cross_Reference:
Citation_Information:
Other_Citation_Details:
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
Back to Top
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
GeoPlan relied on the integrity of the attribute information within
the original data.
Logical_Consistency_Report:
Data covers the tile scheme provided for the county and was verified for correct 
topology (no intersection, overlap or dangles). Dewberry performed a full 
qualitative review of the contour data for smoothness and consistency of feature 
codes.
Completeness_Report:
A visual qualitative assessment was performed to ensure the data completness. 
No void or missing data except for the west end of the Santa Rosa island (missing 
Lidar data in existing dataset); concern FDEM tiles 051347_N, 051348_N, 
051349_N.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
The contours inherit the accuracy of the Lidar dataset it was acquired from.
Lidar source compiled to meet 1m horizontal accuracy.
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report:
The contours inherit the accuracy of the Lidar dataset it was acquired from.
Quantitative_Vertical_Positional_Accuracy_Assessment:
Vertical_Positional_Accuracy_Value: 0.137
Vertical_Positional_Accuracy_Explanation:
Based on the vertical accuracy testing conducted by Dewberry, using NSSDA 
and FEMA guidelines, vertical accuracy at the 95% confidence level (called 
Accuracyz) is computed by the formula RMSEz x 1.9600. The dataset for 
Escambia County, Florida satisfies the criteria:
Countywide lidar dataset tested 13.7 cm vertical accuracy at 95% confidence 
level in open terrain, based on open terrain RMSEz (7 cm) x 1.9600.
Countywide lidar dataset tested 33.3 cm vertical accuracy at 95% confidence 
level in all land cover categories combined, based on consolidated RMSEz (17 
cm) x 1.9600.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: NOAA
Publication_Date: 200703
Publication_Time: Unknown
Title:
Lidar
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details:
LiDAR Survey of Escambia County, Florida, conducted in the summer of 2006 under a contract of the National Oceanic and Atmospheric Administration (NOAA) in support of the Northwest Florida Water Management District (NWFWMD) used without modification or correction except for a reprojection and retiling. Because the LiDAR is used "as is" there may be instances where breakline or contour products do not match the LiDAR. Known instances are tile 049753_N-the coastal shoreline breakline does not follow the masspoint feature class derived from the LiDAR.
Source_Scale_Denominator: Unknown
Type_of_Source_Media: Hard Drive
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2006
Source_Currentness_Reference:
ground condition
Source_Citation_Abbreviation:
FDEM
Source_Contribution:
Spatial and Attribute Information
Process_Step:
Process_Description:
The ABGPS, IMU, and raw scans are integrated using proprietary software 
developed by the Leica Geosystems and delivered with the Leica ALS50 System. 
The resultant file is in a LAS binary file format . The LAS file version 1.0  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 UTM Zone 16, with units in meters 
and referenced to the NAD83 horizontal datum and  GRS80 vertical datum.  The 
date and time for each flight line can be determined using the Julian date and time. 
 The Julian date is a continuous count of days and fractions since noon Universal 
Time on January 1, 4713 BCE on the Julian Calendar.
Source_Used_Citation_Abbreviation:
Airborne Global Positioning System Data
Source_Used_Citation_Abbreviation:
Inertial Measurement Unit
Source_Used_Citation_Abbreviation:
LiDAR Scans
Process_Date: 2006
Source_Produced_Citation_Abbreviation:
LiDAR Point Cloud LAS 1.0 format
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: 3001,Inc
Contact_Position: LiDAR Manager
Contact_Address:
Address_Type: mailing and physical address
Address:
501 Robert Blvd.
Address:
2nd Floor
City: Slidell
State_or_Province: LA
Postal_Code: 70458
Country: USA
Contact_Voice_Telephone: (985) 661-3001
Contact_Facsimile_Telephone: (985) 649 - 5082
Contact_Electronic_Mail_Address: klewis@3001inc.com
Hours_of_Service: 8:00 - 5:00 CT
Process_Step:
Process_Description:
The unedited data are classified to facilitate the application of the appropriate 
feature extraction filters. A combination of proprietary filters are applied as 
appropriate for the production of bare earth digital terrain models (dtms).  
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. The LiDAR mass 
points were delivered in American Society for Photogrammetry and Remote 
Sensing LAS 1.0 format.  The header file for each dataset is complete as define by 
the LAS 1.0 specification.  In addition the following fields are included:  Flight Date 
Julian, Year, and Class.  The LAS files do not include overlap. 
The data was classified as follows:
Class 1 = Unclassified.  This class includes vegetation, buildings, noise etc.
Class 2 = Ground
Class 9 = Water
Source_Used_Citation_Abbreviation:
LiDAR Point Cloud LAS 1.0 format
Process_Date: 2006
Source_Produced_Citation_Abbreviation:
Classified LiDAR datasets
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: 3001, Inc.
Contact_Position: LiDAR Manager
Contact_Address:
Address_Type: mailing and physical address
Address:
501 Robert Blvd.
Address:
2nd Floor
City: Slidell
State_or_Province: LA
Postal_Code: 70458
Country: USA
Contact_Voice_Telephone: (985) 661-3001
Contact_Facsimile_Telephone: (985) 649 - 5082
Contact_Electronic_Mail_Address: klewis@3001inc.com
Hours_of_Service: 8:00 - 5:00 CT
Process_Step:
Process_Description:
Conversion from UTM coordinates (meters) NAD83 into State Plane coordinates 
(U.S. Survey Feet) NAD83 HARN and conversion from ellipsoid heights (meters) 
into orthometric heights (U.S. Survey Feet).
Source_Used_Citation_Abbreviation:
Classified LiDAR datasets
Process_Date: 200802
Source_Produced_Citation_Abbreviation:
Projected and tiled LiDAR datasets
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: URS
Contact_Address:
Address_Type: mailing and physical address
Address:
200 Orchard Ridge Drive, Suite 101
City: Gaithersburg
State_or_Province: MD
Postal_Code: 20878
Country: USA
Contact_Voice_Telephone: (301) 258-9780
Process_Step:
Process_Description:
Dewberry used GeoCue software to develop LiDAR stereo models. The raster 
resolution was 8ft.
Source_Used_Citation_Abbreviation:
Projected and tiled LiDAR datasets
Process_Date: 200802
Source_Produced_Citation_Abbreviation:
Lidar - stereopairs
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Dewberry - Geospatial Services Group
Contact_Address:
Address_Type: mailing and physical address
Address:
8401 Arlington Boulevard
City: 22031
State_or_Province: VA
Postal_Code: 22031
Country: USA
Contact_Voice_Telephone: 703.849.0100
Process_Step:
Process_Description:
LiDAR intensity stereopairs were viewed in 3-D stereo using Socet Set softcopy 
photogrammetric software, the breaklines were  stereo-compiled  in accordance 
with the Data Dictionary. The LiDARgrammetry was performed under the direct 
supervision of an ASPRS Certified Photogrammetrist.  The breaklines conform with 
data format requirements outlined by the FDEM Baseline Specifications.
Source_Used_Citation_Abbreviation:
Lidar - stereopairs
Process_Date: 200802
Source_Produced_Citation_Abbreviation:
3D breaklines
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Dewberry - Geospatial Services Group
Contact_Address:
Address_Type: mailing and physical address
Address:
8401 Arlington Boulevard
City: 22031
State_or_Province: VA
Postal_Code: 22031
Country: USA
Contact_Voice_Telephone: 703.849.0100
Process_Step:
Process_Description:
Using proprietary procedures developed by Dewberry using ArcGIS, a 
hydroenforced bare earth TIN was created. The nodes were gridded ground 
masspoints derived from the Lidar dataset, the 3D breaklines were included in this 
TIN.
Source_Used_Citation_Abbreviation:
Lidar ground masspoints
Source_Used_Citation_Abbreviation:
3D Breaklines
Process_Date: 200803
Source_Produced_Citation_Abbreviation:
Hydroenforced TIN
Process_Step:
Process_Description:
1ft contours were modeled from a hydroenforced bare earth TIN and then 
smoothed and simplified using proprietary procedures developed by Dewberry 
using ArcGIS.
Source_Used_Citation_Abbreviation:
Hydroenforced TIN
Process_Date: 200804
Source_Produced_Citation_Abbreviation:
1ft Contours
Process_Step:
Process_Description:
2ft contours were extracted from the 1ft contours dataset and suplemental 
contours were manually added from the 1ft contours dataset when needed.
Source_Used_Citation_Abbreviation:
1ft Contours
Process_Date: 200804
Source_Produced_Citation_Abbreviation:
2ft Contours
Process_Step:
Process_Description:
GeoPlan received this data via hard drive from Jones Edmunds on 8/27/09 and 
on 5/5/10. When received the data was in multiple file geodatabases. The 
feature classes were projected to Albers HPGN.

For the vendors other than pds, GeoPlan merged the data then clipped by county. 
For PDS the data was not merged and clipped. Therefore, the contours don't 
follow county boundaries exactly, but generally the edge of the contours are very 
close to the county boundary.

PDS data had contours with 1 foot intervals in the 2 foot contour feature class. 
The following selection was performed on each county and the odd contours were 
deleted from the feature class using and edit session with ArcMap:
MOD( "CONTOUR_ELEVATION_MS" , 2 ) = 1

The following counties had the associated amount of odd contours deleted:
bay - 3259
brevard - 84
clay - 16
dixie - 10810
escambia - 34
flagler - 33249
franklin - 2298
gulf - 28084
jefferson - 2272
levy - 6791
nassau - 38
okaloosa - 107
putnam - 47
santa rosa - 2356
taylor - 6009
wakulla - 100
walton - 7884

-Added SOURCE field and populated all values to PDS
-Added FGDLAQDATE field based on date GeoPlan acquired data from source
-Changed name to TOPO2FT_PDS_COUNTY
Source_Used_Citation_Abbreviation:
GeoPlan
Process_Date: 20100824
Process_Step:
Process_Description:
Metadata imported.
Source_Used_Citation_Abbreviation:
H:\lidar_output\meta\post_danny\pds_20100825.xml
Process_Date: 20100910
Process_Time: 11494000
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: String
Point_and_Vector_Object_Count: 43239
Back to Top
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Albers Conical Equal Area
Albers_Conical_Equal_Area:
Standard_Parallel: 24.000000
Standard_Parallel: 31.500000
Longitude_of_Central_Meridian: -84.000000
Latitude_of_Projection_Origin: 24.000000
False_Easting: 400000.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.000100
Ordinate_Resolution: 0.000100
Planar_Distance_Units: meters
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_Datum_Name: North American Vertical Datum of 1988
Altitude_Resolution: 0.000500
Altitude_Distance_Units: feet
Altitude_Encoding_Method: Explicit elevation coordinate included with horizontal coordinates
Back to Top
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: TOPO2FT_PDS_ESCAMBIA
Entity_Type_Definition:
TOPO2FT_PDS_ESCAMBIA
Entity_Type_Definition_Source:
PDS
Attribute:
Attribute_Label: OBJECTID
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: CONTOUR_ELEVATION_MS
Attribute_Definition:
Elevation of represented contour in feet
Attribute_Definition_Source:
"Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2"
Attribute:
Attribute_Label: CONTOUR_TYPE_DESC
Attribute_Definition:
Type of contour
Attribute_Definition_Source:
"Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2"
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain_Value_Definition:
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.
Enumerated_Domain_Value_Definition_Source:
"Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2"
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 2
Enumerated_Domain_Value_Definition:
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.
Enumerated_Domain_Value_Definition_Source:
"Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2"
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 3
Enumerated_Domain_Value_Definition:
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.
Enumerated_Domain_Value_Definition_Source:
"Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2"
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 4
Enumerated_Domain_Value_Definition:
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.
Enumerated_Domain_Value_Definition_Source:
"Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2"
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 5
Enumerated_Domain_Value_Definition:
Intermediate Low Confidence
Enumerated_Domain_Value_Definition_Source:
"Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2"
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 6
Enumerated_Domain_Value_Definition:
Supplementary Low Confidence
Enumerated_Domain_Value_Definition_Source:
"Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2"
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 7
Enumerated_Domain_Value_Definition:
Depression Low Confidence
Enumerated_Domain_Value_Definition_Source:
"Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2"
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 8
Enumerated_Domain_Value_Definition:
Index Low Confidence
Enumerated_Domain_Value_Definition_Source:
"Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2"
Attribute:
Attribute_Label: DATESTAMP_DT
Attribute_Definition:
The date the feature was imported into the geodatabase
Attribute_Definition_Source:
"Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2"
Attribute:
Attribute_Label: Shape_Length
Attribute_Definition:
Length of feature in internal units.
Attribute_Definition_Source:
ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Positive real numbers that are automatically generated.
Attribute:
Attribute_Label: SOURCE
Attribute_Definition:
Abbreviated 3-letter code representing the data source.
Attribute_Definition_Source:
GeoPlan
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: PDS
Enumerated_Domain_Value_Definition:
PDS
Attribute:
Attribute_Label: FGDLAQDATE
Attribute_Definition:
Date FGDL acquired data from source
Attribute_Definition_Source:
GeoPlan
Back to Top
Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Florida Geographic Data Library (FGDL)
Contact_Person:
Contact_Position:
Contact_Address:
Address_Type: mailing address
Address:
431 Architecture PO Box 115706
City: Gainesville
State_or_Province: Florida
Postal_Code: 32611-5706
Country: United States
Contact_Voice_Telephone:
Contact_TDD/TTY_Telephone:
Contact_Facsimile_Telephone:
Contact_Electronic_Mail_Address: Web site: http://www.fgdl.org
Contact_Electronic_Mail_Address: Technical Support: http://www.fgdl.org/fgdlfeed.html
Contact_Electronic_Mail_Address: For FGDL Software: http://www.fgdl.org/software.html
Contact_Electronic_Mail_Address: FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html
Contact_Electronic_Mail_Address: Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html
Hours_of_Service:
Contact Instructions:


Resource_Description: DOWNLOADABLE DATA
Distribution_Liability:
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
Technical_Prerequisites:
This data is intended for use with a Geographic Information Systems or Remote Sensing software package.
Back to Top
Metadata_Reference_Information:
Metadata_Date: 20100910
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Florida Division of Emergency Management
Contact_Person: Richard Butgereit
Contact_Position: GIS Administrator
Contact_Address:
Address_Type: mailing and physical address
Address:
2555 Shumard Oak Boulevard
City: Tallahassee
State_or_Province: FL
Postal_Code: 32399-2100
Country: USA
Contact_Voice_Telephone: 850-413-9907
Contact_Facsimile_Telephone: 850-488-1016
Contact_Electronic_Mail_Address: richard.butgereit@em.myflorida.com
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
Metadata_Extensions:
Online_Linkage: http://www.esri.com/metadata/esriprof80.html
Profile_Name: ESRI Metadata Profile
Back to Top