Geodataset Name:       CEMETERY_D2_JUN06
Geodataset Type:       Shapefile
Geodataset Feature:    POLYGON
Feature Count:         540

DATA SOURCE(S):                    NCFRPC, NEFRPC, GeoPlan Center
SCALE OF ORIGINAL SOURCE MAPS:     VARIES
DATE OF AUTOMATION OF SOURCE:      20060614
GEODATASET EXTENT:                 FDOT District 2

FEATURE ATTRIBUTE TABLES:

Datafile Name: CEMETERY_D2_JUN06.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
AUTOID	GeoPlan Center internal feature number.
Shape	Feature geometry
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.
DESCRIPT	Based on 'NAME'.
SOURCE	The source from which FGDL acquired the data.
FLAG	Type of update that occurred. A = Attribute edit S = Spatial edit. B = Both attribute and spatial edit N = New D = Delete. NIN = Not in new (See data lineage summary for more details - A5)
UPDATE_DAY	The last day the file was updated by the source.
OBJECTID	Internal feature number.
SHAPE	Feature geometry.
SHAPE.AREA	No description
FGDLAQDATE	Date FGDL obtained data from source.
SHAPE.LEN	No description

USER NOTES:

This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology The methods used in creating this layer were very consistent. The shapefile had one author and all listed sources were consulted to verify locations of features. This included field visits to many of the sites in question.

This data is provided 'as is' by GeoPlan and is complete to our knowledge. Many cemeteries from the past have not been located due to lost records, lack of maintenance, lost grave markers, or a combination thereof. Of the sources that were consulted, the majority of the listed cemeteries has been demarcated. There are still several small family burials that have been lost in time, as well as possible larger ones. Some cemeteries that were once thought lost are located in this layer. The existing data from Geoplan and the FDOS included about 40 cemeteries for Alachua County. The SCE map, using additional local sources, contains over 108 sites. Gilchrist County showed a bigger improvement. This layer can benefit significantly from the SCE mapping effort. Cemeteries were a major emphasis for several reasons: they appear to be important for FDOT planning purposes; there is a great deal of information available for some counties, such as Alachua; existing maps do not reflect the available information. Methods to locate cemeteries are very different from most other layers - the standard data sources, such as parcel data and the yellow pages, are not generally helpful. Aerial photos and a variety of local sources tend to be very useful. Most counties have individual experts or historical societies that can provide critical information. Only a small portion of all burial areas have been located, and the smaller, private cemeteries may never be well-documented. But most of the larger cemeteries associated with churches and towns or otherwise recorded can be mapped.

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

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

A note concerning data scale: Scale is an important factor in data usage. Certain scale datasetsare 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:250000 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 analyses. Every effort has been made to supply the user with data documentation. For additional information, see the References sectionand the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our web pages at: http://www.geoplan.ufl.edu/education.html

REFERENCES:

North Central Florida Regional Planning Council NCFRPC 2009 N.W. 67th Place, Suite A Gainesville, FL 32653 407-314-8683 http://www.ncfrpc.org/ Carol Laine laine@ncfrpc.org Northeast Florida Regional Planning Council NEFRPC 6850 Belfort Oaks Place Jacksonville, FL 32216 (904) 279-0880 Fax (904) 279-0881 http://www.nefrpc.org/ info@nefrc.org Keith Joiner KJoiner@nefrc.org

DATA LINEAGE SUMMARY:

North Central Florida Regional Planning Council - Process Steps: ALACHUA: Layer was created by using the geocoded point layer, buffering to 100m, and creating a polygon shapefile to be used for editing. New features were added when necessary to make the complete shapefile as it now exists. GILCHRIST: Layer was created by using the geocoded point layer, buffering to 100m, and creating a polygon shapefile to be used for editing. Added fields: ACCESS, SOURCES, ALTERNATE, RESOLVE, CONFIDENCE, and others required by SCE specifications. Deleted unnecessary fields. ACCESS tells the user how accessible the site is. SOURCES indicate the main sources helpful in verifying the cemetery location. ALTERNATE indicates other names used for the site. RESOLVE was used to differentiate polygons that were verified and finished. 0 means the site is incomplete, not located, or not verifiable. 1 means site is complete. CONFIDENCE is the author's level of confidence that the cemetery is correctly located on the map or in existence. Process Date: 20050601 Northeast Florida Regional Planning Council - Process Steps: The 2005 cadastral GIS databases were obtained from the following counties: Baker, Clay, Duval, Nassau, Putnam, St Johns. Each cadastral dataset was projected to Albers Conical Equal Area (Florida Geographic Data Library) as defined by GEO Plan. 2 existing FGDLsource layers were used as references. These were gc_cemetery_sep05 (geocoded points), and par_cemetery 04 (polygons) The geocoded points gc_cemetery_sep05 were buffered by 1/2 mile and all parcel polygons that fell within the buffer were analyzed to find the correct polygons. The DOR attributes used for the analysis purpose were Owner Name, and DOR Code (7600). The existing FGDL polygons par_cemetery_04 were buffered by 1/2 mile and all parcel polygons that fell within the buffer were analyzed to find the correct polygons. The DOR attributes used for the analysis purpose were Owner Name, and DOR Code (7600). The existing locations that were not located in the DOR parcels were field checked to verify that they do not exist . These locations are not part of the final dataset.. After all of the existing locations as defined by FGDL were verified, other sources were used to find any missing locations. Following are the other sources that were used: yellow pages, Florida Tombstone Transcription Project (http://www.rootsweb.com/~cemetery/florida/florida.htm), lat-long.com, local funeral homes, Putnam County GIS Department, Duval County GIS, St Johns County GIS Department, loval historical societies, local churches. All of these sources were analyzed, located and their coincidental parcel polygons were added to the cemeteries layer and attributed. Process Date: 20060501 GeoPlan Center - Process Steps: GeoPlan received this data, via CDROM, and performed the following: -Reprojected to the FGDL Albers HPGN map projection. -Restructured the attribute table to fit the SCE Data Specification Document Standards. -Merged datasets together to create one FDOT District-wide shapefile. -Added FGDLAQDATE field based on the date FGDL acquired the data from the source. -Added DESCRIPT field based on 'NAME' Process Date: 20060614 Metadata imported. Process Date:

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:

GeoPlan Center
431 ARCH BLDG
Gainesville, FL
32611




image@fgdl.org

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