<?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>20210507</pubdate>
        <title>Crashes on Florida's Local and State Highway System (SHS) Roadways - 2017</title>
        <geoform>Vector Digital Data Set (Point)</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 crashes on Florida roadways. This data originated at the the Florida Department of Highway Safety and Motor Vehicles (FLHSMV) and was processed by the Signal4 team at the University of Florida - Geoplan Center. This is a snapshot of crashes for the year 2017.</abstract>
      <purpose>This crash data is for use with FDOT's Efficient Transportation Decision Making (ETDM) process.</purpose>
    </descript>
    <timeperd>
      <timeinfo>
        <sngdate>
          <caldate>20170101</caldate>
        </sngdate>
      </timeinfo>
      <current>Unknown</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>As needed</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-87.586736</westbc>
        <eastbc>-79.824857</eastbc>
        <northbc>31.042031</northbc>
        <southbc>24.507930</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>ISO 19115 Topic Category</themekt>
        <themekey>transportation</themekey>
      </theme>
    </keywords>
    <accconst>FDOT use only</accconst>
    <useconst>FDOT use only</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>University of Florida GeoPlan Center</cntorg>
        </cntorgp>
        <cntpos>GIS Manager</cntpos>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>431 Architecture Building</address>
          <city>Gainesville</city>
          <state>Fl</state>
          <postal>32511</postal>
        </cntaddr>
        <cntvoice>325-392-8686</cntvoice>
      </cntinfo>
    </ptcontac>
    <datacred>University of Florida GeoPlan Center</datacred>
    <native>Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362</native>
    <crossref>
      <citeinfo>
        <othercit>https://www.flhsmv.gov/pdf/courts/crash/CrashManualComplete.pdf</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>The Signal4 team exported this data on 3/18/21. The data was exported from the Oracle database in the form of two tables: GEOCODE_RESULT (feature class) and CRASH_EVT2 (view). -Data was joined based on HSMV_RPT_NBR. -Selected only CRASH_YR in (2017) -Removed all fields except what was relevant for ETDM -Created metadata based on information from Signal4 and https://www.flhsmv.gov/pdf/courts/crash/CrashManualComplete.pdf -Upcased all text fields -Added DESCRIPT based on ST_NM -Added FGDLAQDATE based on date exported from Signal4 database\ Records with a match_result_cd &lt; 3 should be be considered to have a lower confidence in spatial location. To find these records use this selection: match_status_cd = 'U' and match_result_cd = 2. There are known issues with crash points being located in the ocean.</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20210331</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>Entity point</sdtstype>
        <ptvctcnt>723780</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>S4_CRASH_2017</enttypl>
        <enttypd>S4_CRASH_2017</enttypd>
        <enttypds>University of Florida GeoPlan Center</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>HSMV_RPT_NBR</attrlabl>
        <attrdef>FLHSMV report ID</attrdef>
        <attrdefs>GeoPlan </attrdefs>
      </attr>
      <attr>
        <attrlabl>MATCH_STATUS_CD</attrlabl>
        <attrdef>Geocoding status</attrdef>
        <attrdefs>GeoPlan </attrdefs>
        <attrdomv>
          <edom>
            <edomv>F</edomv>
            <edomvd>Final.  This status code is only used when the investigating officer maps the crash in the field using the web-based S4 Geolocation Service.  Crashes mapped using this service bypass automatic batch geocoding.</edomvd>
          </edom>
          <edom>
            <edomv>M</edomv>
            <edomvd>Matched</edomvd>
          </edom>
          <edom>
            <edomv>T</edomv>
            <edomvd>Tied</edomvd>
          </edom>
          <edom>
            <edomv>U</edomv>
            <edomvd>Unmatched</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>MATCH_RESULT_CD</attrlabl>
        <attrdef>Geospatial location confidence level</attrdef>
        <attrdefs>GeoPlan </attrdefs>
        <attrdomv>
          <edom>
            <edomv>0</edomv>
            <edomvd>Not Geocoded</edomvd>
          </edom>
          <edom>
            <edomv>1</edomv>
            <edomvd>Unmatched (crash point could not be determined)</edomvd>
          </edom>
          <edom>
            <edomv>2</edomv>
            <edomvd>For Review (found one or more crash points and chose one, but not confident of accuracy)</edomvd>
          </edom>
          <edom>
            <edomv>3</edomv>
            <edomvd>Confident (found a crash point, confident in its accuracy)</edomvd>
          </edom>
          <edom>
            <edomv>4</edomv>
            <edomvd>Interactive (crash mapped after the fact by a human using the S4 Geocoding Tool)</edomvd>
          </edom>
          <edom>
            <edomv>5</edomv>
            <edomvd>Geolocation Service (crash mapped in the field by investigating officer using the S4 Geolocation Service)</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>ST_NM</attrlabl>
        <attrdef>Street name of crash</attrdef>
        <attrdefs>GeoPlan </attrdefs>
      </attr>
      <attr>
        <attrlabl>SHAPE</attrlabl>
        <attrdef>Feature geometry.</attrdef>
        <attrdefs>Esri</attrdefs>
        <attrdomv>
          <udom>Coordinates defining the features.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>KEY_CRASH_DT</attrlabl>
        <attrdef>Date of crash</attrdef>
        <attrdefs>GeoPlan </attrdefs>
      </attr>
      <attr>
        <attrlabl>CRASH_YR</attrlabl>
        <attrdef>Year of crash</attrdef>
        <attrdefs>GeoPlan </attrdefs>
      </attr>
      <attr>
        <attrlabl>CRASH_SEV_DTL</attrlabl>
        <attrdef>Injury severity description</attrdef>
        <attrdefs>GeoPlan </attrdefs>
      </attr>
      <attr>
        <attrlabl>FATALITY_CNT</attrlabl>
        <attrdef>Number of fatalities associated with the crash. This number includes Injury Severity = 5 - Fatal (within 30 days) </attrdef>
        <attrdefs>GeoPlan </attrdefs>
      </attr>
      <attr>
        <attrlabl>DESCRIPT</attrlabl>
        <attrdef>GeoPlan added field based on ST_NM</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>FGDLAQDATE</attrlabl>
        <attrdef>GeoPlan added field based on date exported from Signal4 database</attrdef>
        <attrdefs>GeoPlan </attrdefs>
      </attr>
      <attr>
        <attrlabl>AUTOID</attrlabl>
      </attr>
    </detailed>
  </eainfo>
  <distinfo>
    <distrib>
      <cntinfo>
        <cntorgp>
          <cntorg>Florida Geographic Data Library (FGDL)</cntorg>
        </cntorgp>
        <cntpos>GIS Manager</cntpos>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>431 Architecture PO Box 115706</address>
          <city>Gainesville</city>
          <state>Florida</state>
          <postal>32611</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>n/a</cntvoice>
      </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>
    <stdorder>
      <digform>
        <digtinfo>
          <formname>Vector Digital Data Set (Point)</formname>
        </digtinfo>
      </digform>
    </stdorder>
    <techpreq>This data is intended for use with a Geographic Information Systems or Remote Sensing software package.</techpreq>
  </distinfo>
  <metainfo>
    <metd>20210730</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>University of Florida GeoPlan Center</cntorg>
        </cntorgp>
        <cntpos>GIS Manager</cntpos>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>431 Architecture Building</address>
          <city>Gainesville</city>
          <state>Fl</state>
          <postal>32611</postal>
        </cntaddr>
        <cntvoice>352-392-8686</cntvoice>
        <cntemail>data@fgdl.org</cntemail>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
  </metainfo>
</metadata>