<?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>
        <title>Florida Department of Transportation Five Year Work Program - 2020</title>
        <geoform>vector digital data</geoform>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This data set contains the FDOT Adopted Work Program (2021 - 2025) roadways. This data was created based on linear referencing, using the five year work program spreadsheet in conjunction with RCI Basemap Roads. Roadways are designated in one of at least 16 phases. Of particular importance to ETDM are the following 7 phases: Construction (CST) phase - Project actively in construction; Design Build (DSB) phase - Project in a condensed process where the firm completing the design also construct the project; Environmental (ENV) phase - Projects where multiple alternatives are being evaluated; Project Development and Environment (PDE) phase - Projects where multiple alternatives are being evaluated; Preliminary Engineering (PE) phase - Project has single preferred alternative that has been selected, and during this phase, the project is actually being designed; Planning (PLN) phase - Project is in the concept and information gathering stage; Right of Way (ROW) phase - The Right of Way office is identifying and acquiring right-of-way for construction of the project.</abstract>
      <purpose>The work program spreadsheet is used by the FDOT to report on its Work Program of road, bridge, freight logistics and passenger operations, maintenance, planning, research, and other transportation related projects. The Department strives to maintain the stability of the Work Program; however, updated cost estimates, revised schedules, and other events outside the Department's control, such as changes in revenue estimates, all necessitate modifications to the Work Program during the course of the year. Users of the data contained in the accompanying file should bear this in mind and may wish to consider confirming project specific information with the Department's District Offices (Or at our Work Program Application site) for changes that may have occurred since the last posting.</purpose>
    </descript>
    <spdom>
      <bounding>
        <westbc>-87.567514</westbc>
        <eastbc>-79.874497</eastbc>
        <northbc>31.034967</northbc>
        <southbc>24.512309</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>transportation</themekey>
        <themekey>work program</themekey>
      </theme>
    </keywords>
    <accconst>None</accconst>
    <useconst>FDOT only</useconst>
    <native> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</native>
  </idinfo>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>String</sdtstype>
        <ptvctcnt>6948</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>FDOT_WP_2020</enttypl>
        <enttypd>FDOT_WP_2020</enttypd>
        <enttypds>FDOT</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>DISTRICT</attrlabl>
        <attrdef>This field indicates the District where the project is located.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>WPITEM</attrlabl>
        <attrdef>This field is the identifying sequential number assigned to each work program item. This number is assigned by the system. This is a six digit field in character format, with numeric data.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>WPITMSEG</attrlabl>
        <attrdef>The Item segment may be used to segment a project for scheduling or funding reasons. Item segments may be used when the boundaries of construction projects are different from the PE and/or ROW phase of a 'Project', or it is desirable to use the same item number to track projects along a corridor. For example, the department may want or need to let different segments at different times. Item segments may not cross county lines, except for district wide items.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>COUNTY_CODE</attrlabl>
        <attrdef>County Code</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>COUNTY_NAME</attrlabl>
        <attrdef>County Name</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>DESCRIPTION</attrlabl>
        <attrdef>This represents the Local Name of the roadway or other.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>BEGIN_MILE</attrlabl>
        <attrdef>This represents the beginning milepost to 3 decimal places.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>END_MILE</attrlabl>
        <attrdef>This represents the ending milepost to 3 decimal places.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>LENGTH</attrlabl>
        <attrdef>This field describes the length of the project to 3 decimal places.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>PROJECT_TYPE</attrlabl>
        <attrdef>Type of Work</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>PHASE_NAME</attrlabl>
        <attrdef>Phase name. Three letter code and written description.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>FISCAL_YEAR</attrlabl>
        <attrdef>The year range of the record (Department's Fiscal Year Range is July through June.  Example: Fiscal Year 2013 = 7/1/2012 - 6/30/2013)</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>AMOUNT</attrlabl>
        <attrdef>The dollar amount (to the nearest dollar) of the record.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>BOXNAME</attrlabl>
        <attrdef>Further Description of the Project.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>CATEGORY</attrlabl>
        <attrdef>Undefined by Source</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>WPITEM_SEG</attrlabl>
        <attrdef>Item number and item segment combined. This field created by concatenating WPITEM and WPITMSEG.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>PHASE_YEAR</attrlabl>
        <attrdef>Three letter phase code concatenated with year</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>PHASE</attrlabl>
        <attrdef>Three letter phase code.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>LOC_ERROR</attrlabl>
        <attrdef>This field is created from the linear referencing command. Values indicate if there were errors during linear referencing process.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>DESCRIPT</attrlabl>
        <attrdef>GeoPlan added field based on phase name</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>FGDLAQDATE</attrlabl>
        <attrdef>Date GeoPlan acquired data from source.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>AUTOID</attrlabl>
      </attr>
      <attr>
        <attrlabl>SHAPE.LEN</attrlabl>
      </attr>
    </detailed>
  </eainfo>
  <metainfo>
    <metd>20200728</metd>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
  </metainfo>
</metadata>