FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION VERSION 2006 TITLE: FDOT DISTRICT 5 - CEMETERY LOCATIONS Geodataset Name: CEMETERY_D5_JAN07 Geodataset Type: SHAPEFILE Geodataset Feature: Point Feature Count: 471 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): FDOT District 5, DTS, GeoPlan Center SCALE OF ORIGINAL SOURCE MAPS: VARIES DATE OF AUTOMATION OF SOURCE: 20061206 GEODATASET EXTENT: FDOT District 5 |
FEATURE ATTRIBUTE TABLES:
Datafile Name: CEMETERY_D5_JAN07.DBF
ITEM NAME | WIDTH | TYPE |
OBJECTID
|
4 | OID |
NAME
|
100 | String |
ALTERNATE
|
40 | String |
ADDRESS
|
65 | String |
CITY
|
40 | String |
ZIPCODE
|
9 | Number |
OPERATING
|
60 | String |
OP_CLASS
|
10 | String |
TYPE
|
50 | String |
YEAR
|
5 | String |
STATUS
|
24 | String |
PARCEL_ID
|
25 | String |
SOURCE
|
100 | String |
NOTES
|
50 | String |
DESCRIPT
|
100 | String |
FLAG
|
5 | String |
UPDATE_DAY
|
8 | Date |
FGDLAQDATE
|
8 | Date |
AUTOID
|
9 | Number |
SHAPE
|
4 | Geometry |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
OBJECTID |
Internal feature number. |
|
NAME |
Cemetery designation |
|
ALTERNATE |
Alternative name of cemetery. |
|
ADDRESS |
Physical location |
|
CITY |
City of physical location |
|
ZIPCODE |
US postal delivery designation |
|
OPERATING |
Responsible managing organization |
|
OP_CLASS |
Classification of operating entity |
|
TYPE |
Category of cemetery |
|
YEAR |
4-digit year of establishment |
|
STATUS |
Current status of cemetery. |
|
PARCEL_ID |
Parcel Identification Number. |
|
SOURCE |
The Source of the base dataset from which the existing dataset was derived from. |
|
NOTES |
Any notes on the particular feature. |
|
DESCRIPT |
Based on 'NAME'. |
|
FLAG |
Type of update that occurred.
|
|
UPDATE_DAY |
The last day the file was updated by the source. |
|
FGDLAQDATE |
Date FGDL obtained data from source. |
|
AUTOID |
GeoPlan Center internal feature number. |
|
SHAPE |
Feature geometry. |
This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology. |
This data is provided 'as is' by GeoPlan and is complete to our knowledge. |
GeoPlan relied on the integrity of the attribute information within the original data. |
Data development is a component of the Efficient Transportation Decision Making Process (ETDM). The primary objectives of the ETDM initiative include: Effective/timely decision making without compromising environmental quality. Integrating review and permitting process. - Early NEPA reviews and approvals - Full and early participation - Meaningful dispute resolution For more information about these initiatives an on-line search using keyword 'ETDM' will provide a number of resources. A listing of relevant documents and resources is included under: http://fdotenvironmentalstreamlining.urs-tally.com/Library/default.htm. - DTS USE CONSTRAINTS - All provided GIS data is to be considered a generalized spatial representation which is subject to revisions. The feature Boundaries are not to be used to establish legal boundaries or entitlements. For specific information, contact the appropriate department or agency. This information is provided as a visual representation only and is not intended to be used as a legal or official representation of legal boundaries or entitlements. The user assumes all responsibility for determining whether this file is appropriate for a particular purpose. |
Data Transfer Solutions (DTS) is working with the Florida Department of Transportation, District 5 to create regional maps of "sociocultural" features, including hospitals, parks, cemeteries, school boundaries, and others. The maps will provide the FDOT with improved spatial information required for planning roadway projects. |
This data is provided "as is" and its horizontal positional accuracy has not been verified by GeoPlan |
This data is provided "as is" and its horizontal positional accuracy has not been verified by GeoPlan |
THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING. 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 |
FGDL Metadata Explorer http://www.fgdl.org/metadataexplorer/explorer.jsp Data Transfer Solutions http://www.edats.com/index.htm |
Data for Flagler County Process Steps: Collected cemetery data for Flagler County from Florida Geographic Data Library (FGDL). From FGDL funeral home data was deleted from shapefile so only cemeteries remained. Reprojected data set into State Plane Florida East NAD 83, feet. Searched Flagler County Property Appraiser parcel database and extracted polygons that could be cemeteries based on VALUE. Converted the polygons to points and added to the data obtained from FGDL. Searched Google Earth and added missing cemeteries found on Google Earth to the cemetery point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. Staff found additional features from the following web-sites: (http://www.rootsweb.com/~flflagle) In-house staff performed QA/QC of data. Process Date: 20061201 |
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: |
Data Transfer Solutions DTS 4037 Avalon Park Blvd East Orlando, FL 32828 407-382-5222 |
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