<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="./fgdc_classic_fgdl.xsl"?>
<!DOCTYPE metadata SYSTEM "http://www.fgdc.gov/metadata/fgdc-std-001-1998.dtd">
<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>University of Florida GeoPlan Center</origin>
        <pubdate>20190531</pubdate>
        <title>CEMETERY FACILITIES IN FLORIDA - 2019</title>
        <edition>2019 Q2</edition>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <pubplace>Gainesville, FL</pubplace>
          <publish>University of Florida GeoPlan Center</publish>
        </pubinfo>
        <othercit>State of Florida</othercit>
        <onlink>https://www.fgdl.org/</onlink>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This dataset contains 2019 cemetery location information for the State of Florida. It is a combination of cemeteries and other types of burial ground locations from approximately 24 different data sources including; Florida counties, parcel centroids, the U.S. Board on Geographic Names (GNIS), Florida Division of Historical Resources (SHPO) cemetery centroids, SuperPage cemetery address locations, and more. This dataset contains fields denoting the location, and other information for cemeteries located in Florida. This data is meant to be used for planning purposes only and is not intended to represent a 100% inventory of cemeteries in Florida. Cemetery locations that have been verified are marked with the letter V in the FLAG field. Please Note: Boundary information is often generalized and not exact. This layer is an update of the previously released FGDL layer GC_CEMETERY_NOV15.shp</abstract>
      <purpose>The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes.</purpose>
      <supplinf>Florida Department of State, Division of Historical Resources, Archaeology, Human Remains: Chapter 872, Florida Statutes makes it is illegal to willfully and knowingly disturb human remains. Under these provisions, the State Archaeologist may take jurisdiction over and control of human remains from individuals who have been dead for at least 75 years. Below are a set of guidelines for what to do if you encounter human remains. Please visit the cemetery laws page for more information on statutes and rules related to historic and abandoned cemeteries and unmarked human remains. Please treat all human remains and burial items with the utmost respect. Note: Chapter 872 of the Florida Statutes applies to all land in Florida, including private, state, and federal property. SOURCE: https://dos.myflorida.com/historical/archaeology/human-remains/ -----------------------------------------------------------------------------</supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>19990531</begdate>
          <enddate>20190531</enddate>
        </rngdates>
      </timeinfo>
      <current>publication date</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>As needed</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-87.585302</westbc>
        <eastbc>-79.895187</eastbc>
        <northbc>31.035481</northbc>
        <southbc>24.510117</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>grave site</themekey>
        <themekey>family cemetery</themekey>
        <themekey>human remains</themekey>
        <themekey>mausoleum</themekey>
        <themekey>burial ground</themekey>
        <themekey>graveyard</themekey>
        <themekey>columbarium</themekey>
        <themekey>monument</themekey>
        <themekey>crypt</themekey>
        <themekey>cemetery</themekey>
        <themekey>burial site</themekey>
      </theme>
      <theme>
        <themekt>ISO 19115 Topic Category</themekt>
        <themekey>society</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>Florida</placekey>
      </place>
      <temporal>
        <tempkt>None</tempkt>
        <tempkey>2019</tempkey>
      </temporal>
    </keywords>
    <accconst>None</accconst>
    <useconst>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</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>University of Florida GeoPlan Center</cntorg>
          <cntper>Kate Norris</cntper>
        </cntorgp>
        <cntpos>Geospatial Data Manager &amp; Senior GIS Specialist</cntpos>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>131 ARCH BLDG, PO Box 115706</address>
          <city>Gainesville</city>
          <state>FL</state>
          <postal>32611</postal>
          <country>US</country>
        </cntaddr>
        <cntemail>data@fgdl.org</cntemail>
        <cntinst>www.fgdl.org</cntinst>
      </cntinfo>
    </ptcontac>
    <datacred>See data source section of process steps.</datacred>
    <native> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</native>
    <crossref>
      <citeinfo>
        <othercit>Super Pages website: https://www.superpages.com/ Cemetery Transcription Library: http://www.interment.net/us/fl/ D'ADDEZIO.com: http://www.daddezio.com/cemetery/junction/CJ-FL-NDX.html State of Florida Funeral and Cemetery Services: https://www.myfloridacfo.com/division/funeralcemetery/ Florida Department of State, Division of Historical Resources Bureau of Archaeological Research, SHPO https://dos.myflorida.com/historical/archaeology/human-remains/ Find a Grave, Cemetery Search https://www.findagrave.com/cemetery Billion Graves, Cemetery Lookup https://billiongraves.com/search#action=search_cemetery</othercit>
      </citeinfo>
    </crossref>
  </idinfo>
  <dataqual>
    <attracc>
      <attraccr>GeoPlan relied on the integrity of the attribute information within the original data.</attraccr>
    </attracc>
    <logic>This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology</logic>
    <complete>This data is provided 'as is' by GeoPlan and is complete to our knowledge.</complete>
    <posacc>
      <horizpa>
        <horizpar>This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan</horizpar>
      </horizpa>
      <vertacc>
        <vertaccr>This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan</vertaccr>
      </vertacc>
    </posacc>
    <lineage>
      <srcinfo>
        <srcscale>0</srcscale>
        <typesrc>onLine</typesrc>
        <srccontr>Spatial and Attribute Information</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>GeoPlan reviewed and updated the GC_CEMETERY_SEP08 layer. Each existing feature was inspected using aerials and Google earth/street view to confirm their existence. Features that were deemed outdated or inaccurate, were removed from the dataset. Many features were spatially adjusted or their attributes were updated based on the latest data. The most updated shapefiles from GNIS, SHPO, Parcels as well as Orange, St. Johns, Seminole, and Putnam Counties were inspected to determine additional features to be added to the dataset. In addition, the State of Florida's Funeral, Cemetery &amp; Consumer Services provided an Excel table representing registered cemeteries in the State of Florida which was geocoded and inspected to determined additional features to be added. In total, 244 features were removed and 197 were added from various sources from the previous version. The following files were used in the update. -SHPO_CEMETERIES_JUL11 -GNIS_AUG11 -CEMList(7-25-11).XSL (Spreadsheet sent by Lashonda Morris of the State of Florida's Funeral, Cemetery &amp; Consumer Services on 11/3/2011) -Putnam County Cemetery Shapefile downloaded from http://www.putnam-fl.com/GIS/ gis_downloads.php on 11/14/2011. -St Johns County Cemetery Shapefile downloaded from http://www.sjcfl.us/GIS/DataDepot.aspx on 11/14/2011 -Seminole County Cemetery Shapefile downloaded from http://www.seminolecountyfl.gov/cs/gis/ layerbib2_cms.asp on 11/14/2011. -Orange County Cemetery Shapefile After updating the cemetery shapefile, the USNG_FL_1K, LAT_DD, LONG_DD, PARCELNO, ACRES, and AYRBLT were recalculated to account for any spatial changes during the update. The "ADDRESS" field was updated with parcel data were available for features without any prior address information.</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20011128</procdate>
      </procstep>
      <procstep>
        <procdesc>The GeoPlan Center performed the following steps in order to create the 2008 statewide cemetery data layer. 17 Different Sources Comprise the Cemetery Dataset. The following Sources were either reprojected to the FGDL Albers NAD83 HPGN map projection or if no spatial data existed they were geocoded to a statewide 2007 TeleAtlas Streets dataset. For downloaded county and district wide polygon layers the label points were created and then used for each facility. Once the point sources were created via geocoding or reprojected existing point data they were merged into one statewide layer. Record (facility) duplications were removed by manually viewing and editing the statewide layer's attribute table for each of the 67 counties. Where record duplication existed source information of previously corrected FDOT Districts and Regional Planning Council data took preference followed by, County data, and finally geocoded data. Below are the data Sources as described in the Source field in the attribute table. Next GeoPlan Center performed the following attribute table adjustments. -Upper cased all records. -Added DESCRIPT field based on NAME -Socio-Cultural Effect data fields and definitions were added. FLAG, UPDATE_DAY, AUTOID, NAME, ADDRESS, CITY, ZIPCODE, OPERATING, OP_CLASS, SERVICES, COMMON_USE USE, YR_BUILT, FGDLAQDATE.</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20080916</procdate>
      </procstep>
      <procstep>
        <procdesc>SOURCE DATA INFORMATION - 17 Sources STRUCTURE: SOURCE NAME (RECORD COUNT) UPDATE DAY FILE NAME PROJECTION SCALE WEBSITE OTHER ****************************** DTS (460 Features) 12/6/2006 CEMETERY_D5_JAN07.shp State Plane Florida East NAD 83, feet Varies Data Transfer Solutions (DTS) under contract with FDOT District 5 in 2006 ****************************** ESCAMBIA COUNTY (24 Features) 7/30/2004 points_of_interest.shp NAD_1983_HARN_StatePlane_Florida_North_FIPS_0903 N/A http://www.co.escambia.fl.us/departments/gis/default.php ****************************** GNIS 2006 (580 Features) 7/19/2006 GNIS_JUL06.shp World Geographic NAD83 N/A U.S. Board on Geographic Names Definition list http://geonames.usgs.gov/domestic/feature_class.htm ****************************** JACKSON COUNTY (74 Features) 08/08/2008 UFMerge08_08_08.shp GCS_WGS_1984 Varies http://www.jacksoncountyfl.com/geographic_information_services_division.htm ****************************** LEE COUNTY (11 Features) 4/15/2008 lee_Cemeteries.shp NAD_1983_StatePlane_Florida_West_FIPS_0902_Feet Varies http://leegis.leegov.com/GISData.htm ****************************** LEON COUNTY (7 Features) 7/18/2005 COMMON_PLACES.SHP NAD1983_HARN_StatePlane_Florida_North_FIPS_0903_Ft N/A ****************************** MANATEE COUNTY (25 Features) 1/1/2003 Cemeteries.shp NAD_1983_StatePlane_Florida_West_FIPS_0902_Feet N/A http://www.mymanatee.org/internet/information_services_site.nsf/ContentLookup/gis_data_downloads ****************************** NCFRPC (138 Features) 2/1/2005 CEMETERY_D2_JUN06.shp Albers Conical Equal Area *Geographic coordinate system name: GCS_North_American_1983_HARN Varies ****************************** NEFRPC (340 Features) 9/5/2005 CEMETERY_D2_JUN06.shp Albers Conical Equal Area *Geographic coordinate system name: GCS_North_American_1983_HARN Varies ****************************** PALM BEACH COUNTY (23 Features) 06/01/2003 LANDMARKS.shp NAD_1983_StatePlane_Florida_East_FIPS_0901_Feet N/A ftp://ftp.co.palm-beach.fl.us/ ****************************** PARCELS 2006 (350 Features) 12/31/2006 county_parcels_06.shp Varies Varies Florida Department of Revenue ****************************** PINELLAS COUNTY P.A. (11 Features) 1/30/2008 PARCELS.shp NAD_1927_StatePlane_Florida_West_FIPS_0902 Varies http://gis.pinellascounty.org/gisData/gisDataSets.aspx ****************************** SARASOTA COUNTY (4 Features) 5/4/2008 FILE NAME PROJECTION SCALE http://gis.scgov.net/data_download_page.asp OTHER ****************************** SHPO (576 Features) 4/7/2008 shpo_cemeteries_apr08.shp Geographic, Datum: NAD27, Spheroid: Clarke 1866, Units: Decimal Degrees 1:24000 7/9/2008 shpo_cemeteries_jul08.shp Geographic, Datum: NAD27, Spheroid: Clarke 1866, Units: Decimal Degrees 1:24000 ****************************** ST LUCIE COUNTY (17 Features) 1/29/2008 SLC_Cemeteries.shp NAD_1983_StatePlane_Florida_East_FIPS_0901_Feet N/A http://199.201.190.29/GIS/Downloads.asp ****************************** SUPER PAGES (49 Features) 8/11/2008 FILE NAME Albers Conical Equal Area *Geographic coordinate system name: GCS_North_American_1983_HARN Varies http://www.superpages.com/fl/melbourne/ ****************************** VOLUSIA COUNTY (7 Features) 3/25/2008 Cemetery.shp NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901_Feet N/A http://volusia.org/gis/download/shapes.htm ******************************</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20080916</procdate>
      </procstep>
      <procstep>
        <procdesc>GeoPlan reviewed and updated the GC_CEMETERY_NOV11 layer as as part of the development of the GC_CEMETERYBND_AUG12 layer. As part of this update, each feature was assigned a unique GeoPlan ID (GCID). Each existing feature was inspected using aerials and Google earth/street view to confirm their existence. Features that were deemed outdated or inaccurate, were removed from the dataset. Some were spatially adjusted based on the latest data. The most updated shapefiles from GNIS and SHPO were inspected to determine additional features to be added to the dataset. In total, 22 features were removed and 3 were added. Of the remaining 2630 features, 2114 were visually verified. The following files were used in the update. -SHPO_CEMETERIES_JAN12 -GNIS_AUG12 Once a point was moved to the proper location, the corresponding parcel(s) were extracted from the 2010 statewide parcel geodatabase (GC_CEMETERYBND_AUG12). These parcels were assigned the same GeoPlan ID given to the cemetery's point. Appropriate attributes were extracted from the parcel database and added to the cemetery point layer. Additional attributes were added to capture information pertaining to the cemetery's accompanying parcel including COMMON_USE, USE, and LINK. If a cemetery point is associated with more than one parcel, the information from the parcel deemed primary was used to calculate the fields. These variables as well as ADDRESS, ACRES, and, AYRBLT were updated using the information in the GC_CEMETERYBND_AUG12 layer. The USNG_FL_1K, LAT_DD, LONG_DD were also recalculated to account for any spatial changes during the update.</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20120914</procdate>
      </procstep>
      <procstep>
        <procdesc>GeoPlan Center Process Steps During the following time period, 2-15-2013 to 3-5-2013 a new data Source: Parcels 2012, was used to add 498 new features. Imagery was used to Verify locations as well as the following website. http://www.findagrave.com/cgi-bin/fg.cgi?page=cs&amp;CScnty=326&amp;CSsr=1&amp; Fields for the 498 new records were populated primarily from the Source, While the USNG_FL_1K, LAT_DD, LONG_DD, and date fields were calculated based on Spatial location and time. During this update process several existing features were review and a few cemetery point duplicates were deleted.</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20130306</procdate>
      </procstep>
      <procstep>
        <procdesc>The GeoPlan Center performed the following steps in order to create the November 2015 statewide cemetery data layer. GeoPlan added 144 cemetery features. Cemetery locations were checked using imagery and Google Street View and either marked as Verified or Not Verified in the FLAG field, please see the FLAG field Attribute Definition for more information. During the Spatial and Tabular QAQC duplicates were removed. Next GeoPlan Center performed the following attribute table adjustments. -Socio-Cultural Effect data fields were updated. -Added PARCELID and OWNER information from the GC_CEMETERYBND_NOV.shp layer. -Added DESCRIPT field based on NAME. -Added FGDLAQDATE field and populated it. Next the GeoPlan Center joined over the SHPO_CEMETERIES_OCT15.shp SITEID, YEARESTAB, and STATUS fields. Finally GeoPlan Center Upper cased all records and reviewed/updated the Metadata.</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20151111</procdate>
      </procstep>
      <procstep>
        <procdesc>The GeoPlan Center performed the following steps in order to create the May 2019 statewide cemetery data layer. GeoPlan added 61 cemetery features. Some of the features added were discovered through SHPO. Other features were acquired via the 2018 Parcel dataset and county website textual information. Cemetery locations were checked using imagery and Google Street View and either marked as Verified or Not Verified in the FLAG field, please see the FLAG field Attribute Definition for more information. During the Spatial and Tabular QAQC updates were made. Next GeoPlan Center performed the following attribute table adjustments. -Socio-Cultural Effect data fields were updated. -Upper cased all records. -Added DESCRIPT field based on NAME. -Added FGDLAQDATE field and populated it. Next the GeoPlan Center created Label Points from the Cemetery Polygons in order to create this GC_CEMETERY_MAY19 data layer.</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20190531</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>Entity point</sdtstype>
        <ptvctcnt>3317</ptvctcnt>
      </sdtsterm>
    </ptvctinf>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <mapproj>
          <mapprojn>NAD 1983 HARN Florida GDL Albers</mapprojn>
          <albers>
            <stdparll>24.0</stdparll>
            <stdparll>31.5</stdparll>
            <longcm>-84.0</longcm>
            <latprjo>24.0</latprjo>
            <feast>400000.0</feast>
            <fnorth>0.0</fnorth>
          </albers>
        </mapproj>
        <planci>
          <plance>coordinate pair</plance>
          <coordrep>
            <absres>0.0001</absres>
            <ordres>0.0001</ordres>
          </coordrep>
          <plandu>meter</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>D North American 1983 HARN</horizdn>
        <ellips>GRS 1980</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.257222101</denflat>
      </geodetic>
    </horizsys>
  </spref>
  <eainfo>
    <detailed>
      <enttyp>
        <enttypl>GC_CEMETERY_MAY19</enttypl>
        <enttypd>GC_CEMETERY_MAY19.DBF</enttypd>
        <enttypds>GeoPlan</enttypds>
      </enttyp>
      <attr>
        <attrlabl>OBJECTID</attrlabl>
        <attrdef>Internal feature number.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Sequential unique whole numbers that are automatically generated.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Shape</attrlabl>
        <attrdef>Feature geometry.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Coordinates defining the features.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>PARCELID</attrlabl>
        <attrdef>Parcel Identification Number, derived from the 2014 or 2018 statewide parcel layer.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>NAME</attrlabl>
        <attrdef>Facility name.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>ALTERNATE</attrlabl>
        <attrdef>Facility alternate name.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>ADDRESS</attrlabl>
        <attrdef>A description of a facility's physical location providing direction for delivery and provision of emergency services.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>CITY</attrlabl>
        <attrdef>City of facility's physical location.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>ZIPCODE</attrlabl>
        <attrdef>US postal delivery designation of facility's physical location.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>COUNTY</attrlabl>
        <attrdef>County of facility's physical location.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>TYPE</attrlabl>
        <attrdef>The Type of facility.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>OWNER</attrlabl>
        <attrdef>Entity owner of the facility.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>OPERATING</attrlabl>
        <attrdef>The responsible organization for management and operation of a facility (e.g., public, private, quasi-public).</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>OP_CLASS</attrlabl>
        <attrdef>Classification of the operating entity.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>SHPOSITEID</attrlabl>
        <attrdef>This is the official state site number assigned by the Florida Master Site File. The state site number is an eight character string containing a two character county code, a five character numeric code, and an optional single letter character suffix (suffix letter is generally used to indicate sites that are functionally or spatially related).</attrdef>
        <attrdefs>Bureau of Archaeological Research</attrdefs>
      </attr>
      <attr>
        <attrlabl>SHPO_YEAR</attrlabl>
        <attrdef>If known, the actual date the cemetery was established.</attrdef>
        <attrdefs>Bureau of Archaeological Research</attrdefs>
      </attr>
      <attr>
        <attrlabl>NOTES</attrlabl>
        <attrdef>Current status of cemetery.</attrdef>
        <attrdefs>Bureau of Archaeological Research</attrdefs>
      </attr>
      <attr>
        <attrlabl>FSOURCE</attrlabl>
        <attrdef>Feature Spatial Source.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>DATASOURCE</attrlabl>
        <attrdef>Feature Data/Tabular Source.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>LAT_DD</attrlabl>
        <attrdef>Latitude in decimal degrees.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>LONG_DD</attrlabl>
        <attrdef>Longitude in decimal degrees.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>MGRS</attrlabl>
        <attrdef>Military Grid Reference System (MGRS) Coordinate of the Facility. The MGRS is the geocoordinate standard used by NATO militaries for locating points on the earth. The MGRS provides a means to represent any location on the surface of the Earth using an alphanumeric string. Hierarchical references are based on the Universal Transverse Mercator (UTM) coordinate system. The MGRS is used for the entire earth. http://mgrs-data.org/</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>GOOGLEMAP</attrlabl>
        <attrdef>Webpage hyperlink to location in Google Maps.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>GCID</attrlabl>
        <attrdef>The GeoPlan Center identification number that links this point feature layer with its corresponding polygon feature layer.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>ACRES</attrlabl>
        <attrdef>Facility acreage.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>DESCRIPT</attrlabl>
        <attrdef>Field added by FGDL based on NAME.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>FLAG</attrlabl>
        <attrdef>Describes if the facility was visually verified or not.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
        <attrdomv>
          <edom>
            <edomv>NV</edomv>
            <edomvd>Not Verified</edomvd>
            <edomvds>GeoPlan</edomvds>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>V</edomv>
            <edomvd>Verified, in most cases this NAME field verification was based on ESRI/Google Imagery and Google Street View.  The exact cemetery boundaries are not verified and in many cases only based on parcel boundaries.</edomvd>
            <edomvds>GeoPlan</edomvds>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>UPDATE_DAY</attrlabl>
        <attrdef>The date the data was last updated by the Source.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>FGDLAQDATE</attrlabl>
        <attrdef>The date FGDL acquired the data from the Source.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>AUTOID</attrlabl>
        <attrdef>Unique ID added by GeoPlan</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
    </detailed>
    <overview>
      <eaover>Cemetery Types:
CEMETERY / COMMUNITY
CEMETERY / COMPANY TOWN
CEMETERY / EPIDEMIC
CEMETERY / FAMILY 
CEMETERY / FAMILY/MILITARY
CEMETERY / FRATERNAL ORDER
CEMETERY / GRAVE SITE
CEMETERY / MEMORIAL
CEMETERY / MILITARY
CEMETERY / MUNICIPAL
CEMETERY / NATIONAL
CEMETERY / OTHER
CEMETERY / PET CEMETERY
CEMETERY / PRISON
CEMETERY / PUBLIC
CEMETERY / RELIGIOUS
CEMETERY / RURAL MOVEMENT
CEMETERY / UNSPECIFIED

Value: CEMETERY / COMMUNITY
Value Definition: A cemetery established by a group of families or residents of small 
villages which do not have an organized political structure.

Value: CEMETERY / COMPANY TOWN
Value Definition: A cemetery associated with a community established for individual 
workers by a specific company mining, textile, iron working, cigar manufacturing, 
etc.

Value: CEMETERY / EPIDEMIC
Value Definition: A cemetery that was established to bury victims of an epidemic 
disease such as cholera, yellow fever, or influenza.

Value: CEMETERY / FAMILY
Value Definition: A small, private burial place for members of the immediate or 
extended family.

Value: CEMETERY / FRATERNAL ORDER
Value Definition: A burial ground established for a fraternity or other social 
organization.

Value: CEMETERY / MEMORIAL PARK
Value Definition: A cemetery established as a component part of a memorial park.

Value: CEMETERY / MILITARY NOT NATIONAL
Value Definition: A burial ground established for war casualties, veterans, and 
eligible dependents.

Value: CEMETERY / MUNICIPAL
Value Definition: A cemetery established by an agency of local government.

Value: CEMETERY / NATIONAL
Value Definition: One of 130 burial grounds established by the Congress of the 
United States since 862 for interment of armed forces servicemen and women 
whose last service ended honorably.

Value: CEMETERY / POTTER'S FIELD
Value Definition: A place for the burial of indigent or anonymous persons.

Value: CEMETERY / PRISON
Value Definition: A cemetery associated with a state or federal prison that is used for
burial of inmates who died while incarcerated.

Value: CEMETERY / RELIGIOUS
Value Definition: A cemetery or graveyard associated with an organized religion.

Value: CEMETERY / RURAL MOVEMENT
Value Definition: A burial place characterized by spacious landscaped grounds and 
romantic commemorative monuments established in a rural setting in the period of 
the young republic and at the dawn of the Victorian era.

Value: CEMETERY / OTHER
Value Definition: If the cemetery type does not fall into one of the categories listed 
above it may be listed as other.

Value: CEMETERY / UNSPECIFIED
Value Definition: If the cemetery type is not specified or listed.</eaover>
    </overview>
  </eainfo>
  <distinfo>
    <distrib>
      <cntinfo>
        <cntorgp>
          <cntorg>Florida Geographic Data Library (FGDL)</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>431 Architecture PO Box 115706</address>
          <city>Gainesville</city>
          <state>Florida</state>
          <postal>32611-5706</postal>
          <country>US</country>
        </cntaddr>
        <cntemail>Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html</cntemail>
        <cntemail>FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html</cntemail>
        <cntemail>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
        <cntemail>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
        <cntemail>Web site: http://www.fgdl.org</cntemail>
      </cntinfo>
    </distrib>
    <resdesc>DOWNLOADABLE DATA</resdesc>
    <distliab>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</distliab>
  </distinfo>
  <metainfo>
    <metd>20200303</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>University of Florida GeoPlan Center</cntorg>
          <cntper>Kate Norris</cntper>
        </cntorgp>
        <cntpos>Geospatial Data Manager &amp; Senior GIS Specialist</cntpos>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>131 ARCH BLDG, PO Box 115706</address>
          <city>Gainesville</city>
          <state>FL</state>
          <postal>32611</postal>
          <country>US</country>
        </cntaddr>
        <cntemail>data@fgdl.org</cntemail>
        <cntinst>www.fgdl.org</cntinst>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
  </metainfo>
</metadata>