<?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>20180119</pubdate>
        <title>PARCELS DISSOLVED BY DECADE OF ACTUAL YEAR BUILT - FLORIDA DOT DISTRICT 2 - 2017</title>
        <edition>Florida_Parcels_2017_arcgis1041v2.gdb</edition>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <pubplace>Gainesville, FL</pubplace>
          <publish>University of Florida GeoPlan Center</publish>
        </pubinfo>
        <othercit>FDOT District 2</othercit>
        <onlink>http://www.fgdl.org</onlink>
        <lworkcit>
          <citeinfo>
            <othercit>Source - 2017 Automated - 2018</othercit>
          </citeinfo>
        </lworkcit>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This dataset contains parcels dissolved by the decade of the actual year built for each respective parcel polygon within the Florida Department of Transportation (FDOT) District 2. Actual Year Built for each parcel polygon represents the original year that the structure / building on the property was built. Effective Year Built represents the last date which the structure / building was updated / renovated, etc. This is an update to the FGDL YB_DECADES_D2_2015.shp data layer.</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>FDOT District 1 SOUTHWEST FLORIDA * Major cities: Arcadia, Bartow, Bradenton, Fort Myers, Lakeland, Naples, North Port, Sarasota, Sebring, and Venice. * Counties: Charlotte, Collier, De Soto, Glades, Hardee, Hendry, Highlands, Lee, Manatee, Okeechobee, Polk, and Sarasota. FDOT District 2 NORTHEAST FLORIDA * Major cities: Gainesville, Jacksonville, Lake City, Palatka, Perry, Saint Augustine, and Starke. * Counties: Alachua, Baker, Bradford, Clay, Columbia, Dixie, Duval, Gilchrist, Hamilton, Lafayette, Levy, Madison, Nassau, Putnam, St. Johns, Suwannee, Taylor, and Union. FDOT District 3 NORTHWEST FLORIDA * Major cities: Apalachicola, Chipley, Crestview, Fort Walton Beach, Marianna, Panama City, Pensacola, Quincy, and Tallahassee. * Counties: Bay, Calhoun, Escambia, Franklin, Gadsden, Gulf, Holmes, Jackson, Jefferson, Leon, Liberty, Okaloosa, Santa Rosa, Wakulla, Walton, and Washington. FDOT District 4 SOUTHEAST FLORIDA * Major cities: Belle Glade, Boca Raton, Fort Lauderdale, Fort Pierce, Hollywood, Pompano Beach, Stuart, Vero Beach, and West Palm Beach. * Counties: Broward, Indian River, Martin, Palm Beach, and St. Lucie. FDOT District 5 CENTRAL FLORIDA * Major cities: Daytona Beach, DeLand, Melbourne, Merritt Island, Ocala, Orlando, and Titusville. * Counties: Brevard, Flagler, Lake, Marion, Orange, Osceola, Seminole, Sumter, and Volusia. FDOT District 6 SOUTH FLORIDA * Major cities: Coral Gables, Hialeah, Key West, and Miami. * Counties: Miami-Dade and Monroe. FDOT District 7 WEST CENTRAL FLORIDA * Major cities: Brooksville, Clearwater, Dunedin, Largo, New Port Richey, St. Petersburg, and Tampa. * Counties: Citrus, Hernando, Hillsborough, Pasco, and Pinellas.</supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>20170926</begdate>
          <enddate>20171222</enddate>
        </rngdates>
      </timeinfo>
      <current>publication date</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>As needed</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-83.991717</westbc>
        <eastbc>-81.182634</eastbc>
        <northbc>30.844848</northbc>
        <southbc>28.971093</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>Built</themekey>
        <themekey>Cadastre</themekey>
        <themekey>Year</themekey>
        <themekey>Trends</themekey>
        <themekey>Growth</themekey>
        <themekey>Planning</themekey>
      </theme>
      <theme>
        <themekt>ISO 19115 Topic Category</themekt>
        <themekey>planningCadastre</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>Florida</placekey>
        <placekey>FDOT District 2</placekey>
      </place>
      <temporal>
        <tempkt>None</tempkt>
        <tempkey>2017</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>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>131 Architecture Building, PO Box 115706</address>
          <city>Gainesville</city>
          <state>FL</state>
          <postal>32611-5706</postal>
          <country>US</country>
        </cntaddr>
        <cntemail>FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html</cntemail>
        <cntemail>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
        <cntemail>FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html</cntemail>
        <cntemail>Web site: http://www.fgdl.org</cntemail>
        <cntemail>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
      </cntinfo>
    </ptcontac>
    <datacred>Florida Department of Revenue, County Property Appraisers, and the GeoPlan Center.</datacred>
    <native> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</native>
    <crossref>
      <citeinfo>
        <othercit>Florida Geographic Data Library: http://www.fgdl.org/ For Department of Revenue info: http://floridarevenue.com/property/Pages/Home.aspx</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>
        <srccite>
          <citeinfo>
            <origin>Florida Department of Revenue and County Property Appraisers</origin>
            <pubdate>20180119</pubdate>
            <title>COUNTY PARCEL DATA</title>
            <othercit>County Specific</othercit>
            <onlink>http://floridarevenue.com/property/Pages/Home.aspx</onlink>
          </citeinfo>
        </srccite>
        <srcscale>0</srcscale>
        <typesrc>onLine</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20170926</begdate>
              <enddate>20171222</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>GeoPlan</srccitea>
        <srccontr>Spatial and Attribute Information</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>GeoPlan collected and used the available Florida Department of Transportation (FDOT) District 2 2017 parcel tax data records gathered from the State Department of Revenue (DOR) and County Property Appraisers to create the shapefile. [Original Statewide Parcel Layer: Florida_Parcels_2017_arcgis1041.gdb] Process for dissolving parcel polygons based on decade of actual year built: - For each county a new field representing Actual Year Built [AYRBLT] was populated based on the attribute table information for the following fields; ACTYRBLT and AYRB. - First [AYRBLT] was set equal to ACTYRBLT, - Next a selection set was created where [AYRBLT] = 0, these selected features were set equal to AYRB. - Also checked for data in the Effective Year Built field where ACTYRBLT = 0. - The [AYRBLT] field was then repopulated as ((Mid[AYRBLT], 1, 3) &amp; "0") Ex. 1999 becomes 1990. - The parcel polygon boundaries were then Dissolved (as single part features) based on the Actual Year Built [AYRBLT] field. - The Dissolved layers were then run through the Repair Geometry Command 3x. - Next the Simplify Polygon GeoProcessing Function was used with the Point Remove Algorithm to remove redundant points, such as over-digitized vertices found throughout the layer, this function was also used to compress the file size of the layer via a relatively low degree of simplification. Then during this simplification process a tolerance equal to 1-meter was set in order to allow for a maximum offset of 1m from the original source data. Because the original file size of the layer prohibited the use of the 'Resolve Errors' option, a 'No Check' option was used during the process; because of this the algorithm may have introduced small topological errors to the simplified results. To correct for topological errors created during this process the Repair Geometry Function was run three times. - Next the Dissolved Layers were then run through the Integrated Command at 1m. - The Dissolved layers were then run through the Repair Geometry Command 3x. - A spatial Join was then run with the Dissolved Layers and they corresponding Full County Parcel Label Points (which where dissolved on PARCELID) in order to get Parcel Count for each dissolved feature. - The shapefiles were then merged together based on the FDOT District that each County fell in, creating seven district wide shapefiles. - The [DECADE] field was then renamed [YB_DECADE]. - The final shapefile represents polygons of parcels which structures/ buildings were originally built in the same decade. - Several other fields were added to the attribute table: [DESCRIPT] - Based on [YB_DECADE] [FGDLAQDATE] - The date FGDL acquired the original data from the Source. As well as [CNTYNAME], [FIFTY_YEAR], [LAT_DD], [LONG_DD], [MGRS], [GOOGLEMAP], [ACRES], and [AUTOID]. Please Note: Tabular spatial information was derived from the feature's label point and not the feature's centroid.</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20180518</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>GT-polygon composed of chains</sdtstype>
        <ptvctcnt>358736</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>YB_DECADES_D2_2017</enttypl>
        <enttypd>YB_DECADES_D2_2017.DBF</enttypd>
        <enttypds>FDOR</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.LEN</attrlabl>
        <attrdef>Perimeter in meters</attrdef>
        <attrdefs>GeoPlan</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>CNTYNAME</attrlabl>
        <attrdef>The County Name.</attrdef>
        <attrdefs>GeoPlan Center</attrdefs>
      </attr>
      <attr>
        <attrlabl>YB_DECADE</attrlabl>
        <attrdef>The range of the actual year builts by decades.</attrdef>
        <attrdefs>GeoPlan Center</attrdefs>
      </attr>
      <attr>
        <attrlabl>PAR_COUNT</attrlabl>
        <attrdef>Number of individual parcels in dissolved polygon.  Please Note: Some Multi-part Parcels have been split during the Single Part Dissolve process, for those polygons there will be only one record for the actual parcel count, which will result in a few of these features having a PARCOUNT = 0. One Example would be a Multi-part Parcel which contains two separate polygons split by a road, there is only one centroid created for the count field, so one of the halves will have a PARCOUNT = 1 while the other will have a PARCOUNT = 0. Since there isn't that many Multi-part parcels this should affect less than 3% of the records.</attrdef>
        <attrdefs>GeoPlan Center</attrdefs>
      </attr>
      <attr>
        <attrlabl>FIFTY_YEAR</attrlabl>
        <attrdef>Identifies the collective age of structures relative to the fifty year milestone.</attrdef>
        <attrdefs>GeoPlan Center</attrdefs>
        <attrdomv>
          <edom>
            <edomv>1</edomv>
            <edomvds>GeoPlan Center</edomvds>
            <edomvd>Greater than 50 years</edomvd>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>2</edomv>
            <edomvds>GeoPlan Center</edomvds>
            <edomvd>Less than forty years</edomvd>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>3</edomv>
            <edomvds>GeoPlan Center</edomvds>
            <edomvd>Between 40 and 50 years</edomvd>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>9</edomv>
            <edomvd>Parcels with no values</edomvd>
            <edomvds>GeoPlan Center</edomvds>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>LAT_DD</attrlabl>
        <attrdef>Latitude in decimal degrees.</attrdef>
        <attrdefs>GeoPlan Center</attrdefs>
      </attr>
      <attr>
        <attrlabl>LONG_DD</attrlabl>
        <attrdef>Longitude in decimal degrees.</attrdef>
        <attrdefs>GeoPlan Center</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 Center</attrdefs>
      </attr>
      <attr>
        <attrlabl>GOOGLEMAP</attrlabl>
        <attrdef>Webpage hyperlink to location in Google Maps.</attrdef>
        <attrdefs>GeoPlan Center</attrdefs>
      </attr>
      <attr>
        <attrlabl>ACRES</attrlabl>
        <attrdef>Number of Acres.</attrdef>
        <attrdefs>GeoPlan Center</attrdefs>
      </attr>
      <attr>
        <attrlabl>DESCRIPT</attrlabl>
        <attrdef>Based on YB_DECADE.</attrdef>
        <attrdefs>GeoPlan Center</attrdefs>
      </attr>
      <attr>
        <attrlabl>FGDLAQDATE</attrlabl>
        <attrdef>The date FGDL acquired the data from the source.</attrdef>
        <attrdefs>GeoPlan Center</attrdefs>
      </attr>
      <attr>
        <attrlabl>AUTOID</attrlabl>
        <attrdef>Unique ID added by GeoPlan</attrdef>
        <attrdefs>GeoPlan Center</attrdefs>
      </attr>
      <attr>
        <attrlabl>SHAPE.AREA</attrlabl>
        <attrdef>Area in meters</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
    </detailed>
    <overview />
  </eainfo>
  <distinfo>
    <distrib>
      <cntinfo>
        <cntorgp>
          <cntorg>Florida Geographic Data Library (FGDL)</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>131 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>20200302</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>University of Florida GeoPlan Center</cntorg>
          <cntper>Kate Norris</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>131 Architecture Building, PO Box 115706</address>
          <city>Gainesville</city>
          <state>FL</state>
          <postal>32611-5706</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>