<?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>U.S. Army Corps of Engineers</origin>
        <pubdate>20200116</pubdate>
        <title>U.S. Army Corp of Engineers Ports in Florida - 2020</title>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <pubplace>Alexandria, VA</pubplace>
          <publish>U.S. Army Corps of Engineers</publish>
        </pubinfo>
        <othercit>State of Florida</othercit>
        <onlink>https://data-usdot.opendata.arcgis.com/</onlink>
        <lworkcit>
          <citeinfo>
            <origin>Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)</origin>
            <pubdate>20150101</pubdate>
            <title>National Transportation Atlas Databases (NTAD) 2014</title>
            <geoform>vector digital data</geoform>
            <pubinfo>
              <pubplace>Washington, DC</pubplace>
              <publish>Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)</publish>
            </pubinfo>
            <onlink>&lt;http://www.bts.gov/programs/geographic_information_services/&gt;</onlink>
          </citeinfo>
        </lworkcit>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This dataset contains the US Army Corp of Engineers (USACE) port locations within the state of Florida. The data consists of location description, street address, city, county name, congressional district FIPS code, type of construction, cargo-handling equipment, water depth alongside the facility, facility type ( dock, fleeting area, lock and/or dam) berthing space, latitude, longitude, current operators and owner's information, list of commodities handled at facility, road/railway connections, equipment available at facility, storage facilities, cranes, transit sheds, grain elevators, marine repair plants, fleeting areas, and docking, and facility start/stop date. Collection of data is performed on a rotational basis to ensure on-site accuracy at each facility. This dataset is an update to the acport_2019 layer.</abstract>
      <purpose>The Navigation Data Center had several objectives in developing the U.S. Waterway Data. These objectives support the concept of a National Spatial Data Provide public access to national waterway data. Foster interagency and intra-agency cooperation through data sharing. Provide a mechanism to integrate waterway data (U.S. Army Corps of Engineers Port/Facility and U.S. Coast Guard Accident Data, for example) Provide a basis for intermodal analysis. Assist standardization of waterway entity definitions (Ports/Facilities, Locks, etc.). Provide public access to the National Waterway Network, which can be used as a basemap to support graphical overlays and analysis with other spatial data (waterway and modal network/facility databases, for example). Provide reliable data to support future waterway and intermodal applications.</purpose>
      <supplinf>A description of the physical and Intermodal (infrastructure) characteristics of the ports in Florida.</supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <sngdate>
          <caldate>20191230</caldate>
        </sngdate>
      </timeinfo>
      <current>ground condition</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>As needed</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-87.341247</westbc>
        <eastbc>-79.781083</eastbc>
        <northbc>30.926454</northbc>
        <southbc>24.500302</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>ISO 19115 Topic Category</themekt>
        <themekey>transportation</themekey>
      </theme>
      <theme>
        <themekt>None</themekt>
        <themekey>transportation</themekey>
      </theme>
      <theme>
        <themekt>None</themekt>
        <themekey>port</themekey>
        <themekey>Point</themekey>
        <themekey>NGDA</themekey>
      </theme>
      <place>
        <placekt>GNIS</placekt>
        <placekey>US Territories</placekey>
        <placekey>Florida</placekey>
        <placekey>United States</placekey>
      </place>
      <stratum>
        <stratkt>None</stratkt>
        <stratkey>ground</stratkey>
      </stratum>
      <temporal>
        <tempkt>None</tempkt>
        <tempkey>2009</tempkey>
        <tempkey>2013</tempkey>
        <tempkey>2010</tempkey>
        <tempkey>2007</tempkey>
        <tempkey>2012</tempkey>
        <tempkey>2014</tempkey>
        <tempkey>2011</tempkey>
        <tempkey>2008</tempkey>
      </temporal>
    </keywords>
    <accconst>None</accconst>
    <useconst>None. Acknowledgment of the Research and Innovative Technology Administration's Bureau of Transportation Statistics National Transportation Atlas Database 2014 would be appreciated in products derived from these data.</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>U.S. Army Corps of Engineers</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>7701 Telegraph Road, Casey Building</address>
          <city>Alexandria</city>
          <state>VA</state>
          <postal>22315-3868</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>703.428.9061</cntvoice>
        <cntfax>703.428.6047</cntfax>
      </cntinfo>
    </ptcontac>
    <datacred>The National Waterway Network was created on behalf of the Research and Innovative Technology Administration's Bureau of Transportation Statistics, the U.S. Army Corps of Engineers, the U.S. Bureau of Census, and the U.S. Coast Guard by Vanderbilt University and Oak Ridge National Laboratory. Additional agencies with input into network development include Volpe National Transportation Systems Center, Maritime Administration, Military Traffic Management Command, Tennessee Valley Authority, U.S. Environmental Protection Agency, and the Federal Railroad Administration.</datacred>
    <secinfo>
      <secsys>none</secsys>
      <secclass>Unclassified</secclass>
    </secinfo>
    <native>Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362</native>
    <crossref>
      <citeinfo>
        <origin>Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)</origin>
        <title>National Transportation Atlas Databases</title>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <pubplace>Washington DC</pubplace>
          <publish>Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)</publish>
        </pubinfo>
        <othercit>Navigation Data Center: http://www.navigationdatacenter.us</othercit>
        <onlink>&lt;http://www.bts.gov/programs/geographic_information_services/&gt;</onlink>
      </citeinfo>
    </crossref>
  </idinfo>
  <dataqual>
    <attracc>
      <attraccr>GeoPlan relied on the integrity of the attribute information within the original data.</attraccr>
    </attracc>
    <logic>RITA/BTS quality checks were to cross reference the place dataset with the state dataset, to determine that the spatial data and attribute data were accurate</logic>
    <complete>This data is provided 'as is' by GeoPlan and is complete to our knowledge.</complete>
    <posacc>
      <horizpa>
        <horizpar>The accuracy of each point element is correlated to the data source used to derive that element. For example, links and nodes derived from 1:100,000 scale Digital Line Graphs are more accurate than links and nodes derived from 1:500,000 scale NOAA Navigational Charts. Elements with an "M" in the source field (indicating an unknown or missing source) are the least accurate.</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>Extraction of the USACE identified port nodes from the National Waterway Network file.</procdesc>
        <srcused>PORT</srcused>
        <procdate>20060101</procdate>
      </procstep>
      <procstep>
        <procdesc>GeoPlan obtained the data from the Bureau of Transportation Statistics from the BTS data website June 2021: https://data-usdot.opendata.arcgis.com/datasets/ports During the QA/QC process, GeoPlan performed the following tasks. - Projected to Albers Conical Equal Area (fgdl_square) using the WGS_1984_(ITRF00)_To_NAD_1983 + NAD_1983_To_HARN_Florida transformation. - Extracted features where "STATE_POST" = 'FL' to select features in Florida. - Selected points in Florida, which removed 12 points that fell outside the extent of Florida - Added DESCRIPT field and populated it based on NAV_UNIT_N - Added FGDLAQDATE field and populated it based on the date GeoPlan received the data - Added MGRS Fields - Removed secondary LAT &amp; LONG fields as well as additional OBJECTID fields - Restructured table by reducing field lengths to better suit data. - Uppercased all records in the table - Renamed the dataset from ports.shp to acport_jan20</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20210602</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>Entity point</sdtstype>
        <ptvctcnt>1181</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>ACPORT_2020</enttypl>
        <enttypd>ACPORT_2020.DBF</enttypd>
        <enttypds>USACE</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>ID</attrlabl>
        <attrdef>Unique Identifier</attrdef>
        <attrdefs>BTS</attrdefs>
        <attrdomv>
          <udom>Numeric String</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>NAV_UNIT_I</attrlabl>
        <attrdef>Alphanumeric unique identifier for a facility</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>UNLOCODE</attrlabl>
        <attrdef>United Nations Location Code</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>NAV_UNIT_N</attrlabl>
        <attrdef>Name of facility</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>LOCATION_D</attrlabl>
        <attrdef>Textual description of the location of the facility</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>FACILITY_T</attrlabl>
        <attrdef>Facility type i.e. ('Dock', 'Fleeting Area', 'Lock and/or Dam', 'Milepoint', etc.)</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>STREET_ADD</attrlabl>
        <attrdef>Address of facility</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>CITY_OR_TO</attrlabl>
        <attrdef>City or town where facility is located</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>STATE_POST</attrlabl>
        <attrdef>State where facility is located</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>ZIPCODE</attrlabl>
        <attrdef>Postal zip code</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>COUNTY_NAM</attrlabl>
        <attrdef>County name</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>COUNTY_FIP</attrlabl>
        <attrdef>The 3-character FIPS code of the County or County equivalent</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>CONGRESS</attrlabl>
        <attrdef>Congress number (i.e. 108, 109, etc.)</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>CONGRESS_F</attrlabl>
        <attrdef>Congressional District FIPS code</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>WTWY_NAME</attrlabl>
        <attrdef>Name of waterway where facility is located</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>PORT_NAME</attrlabl>
        <attrdef>Port in which the wharf is located</attrdef>
        <attrdefs>USACE</attrdefs>
        <attrdomv>
          <udom>Character String</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>MILE</attrlabl>
        <attrdef>Waterway mile of wharf location above or below a datum point</attrdef>
        <attrdefs>USACE</attrdefs>
        <attrdomv>
          <udom>Number</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>BANK</attrlabl>
        <attrdef>Bank of river for wharf location (Left or Right)</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>OPERATORS</attrlabl>
        <attrdef>Current operators of the facility with phone and fax numbers</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>OWNERS</attrlabl>
        <attrdef>Current owner or owner/operators of the facility with phone and fax numbers</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>PURPOSE</attrlabl>
        <attrdef>Purpose for which wharf is used, including commodities handled and/or services performed</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>HIGHWAY_NO</attrlabl>
        <attrdef>Surface road connections</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>RAILWAY_NO</attrlabl>
        <attrdef>Railway connections</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>LOCATION</attrlabl>
        <attrdef>Waterborne Commerce Statistics Center's five digit location code</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>DOCK</attrlabl>
        <attrdef>Waterborne Commerce Statistics Center's three digit dock code</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>COMMODITIE</attrlabl>
        <attrdef>List of commodities handled at the facility at the two digit Lock Performance Monitoring System level</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>CONSTRUCTI</attrlabl>
        <attrdef>Description of type of construction</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>MECHANICAL</attrlabl>
        <attrdef>Description of equipment available at the facility</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>REMARKS</attrlabl>
        <attrdef>Remarks, including description of wharf - related storage facilities and their operators</attrdef>
        <attrdefs>USACE</attrdefs>
        <attrdomv>
          <udom>Character String</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>VERTICAL_D</attrlabl>
        <attrdef>Depth/Height Datum used</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>DEPTH_MIN</attrlabl>
        <attrdef>Minimum depth alongside facility</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>DEPTH_MAX</attrlabl>
        <attrdef>Maximum depth alongside facility</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>BERTHING_L</attrlabl>
        <attrdef>Largest single berthing space in feet</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>BERTHING_T</attrlabl>
        <attrdef>Total berthing space in feet</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>DECK_HEIGH</attrlabl>
        <attrdef>Minimum deck height</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>DECK_HEIG1</attrlabl>
        <attrdef>Maximum deck height</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>SERVICE_IN</attrlabl>
        <attrdef>Date facility started service</attrdef>
        <attrdefs>USACE</attrdefs>
      </attr>
      <attr>
        <attrlabl>SERVICE_TE</attrlabl>
        <attrdef>Date facility stopped service</attrdef>
        <attrdefs>USACE</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</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>GOOGLEMAP</attrlabl>
        <attrdef>Webpage hyperlink to location in Google Maps</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>DESCRIPT</attrlabl>
        <attrdef>GeoPlan added field based on NAV_UNIT_N</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>FGDLAQDATE</attrlabl>
        <attrdef>The date GeoPlan acquired the data from the source.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>AUTOID</attrlabl>
      </attr>
    </detailed>
  </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>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
        <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>Web site: http://www.fgdl.org</cntemail>
        <cntemail>For FGDL Software: http://www.fgdl.org/software.html</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>
    <stdorder>
      <digform>
        <digtinfo>
          <formname>ESRI Shapefile</formname>
          <formvern>2015</formvern>
          <filedec>No compression applied. However, if using digital transfer online option, note access instructions.</filedec>
        </digtinfo>
        <digtopt>
          <offoptn>
            <offmedia>dvd</offmedia>
            <reccap>
              <recden>650</recden>
              <recdenu>megabytes</recdenu>
            </reccap>
          </offoptn>
        </digtopt>
      </digform>
      <fees>None</fees>
      <ordering>Call (202-366-DATA), or E-mail (answers@bts.gov) RITA/BTS to request the National Transportation Atlas Databases (NTAD) 2014 DVD. The NTAD DVD can be ordered from the online bookstore at www.bts.gov. Individual datasets from the NTAD can also be downloaded from the Office of Geospatial Information Systems website at http://www.bts.gov/programs/geographic_information_services/</ordering>
    </stdorder>
    <availabl>
      <timeinfo>
        <sngdate>
          <caldate>20190626</caldate>
        </sngdate>
      </timeinfo>
    </availabl>
    <techpreq>This data is intended for use with a Geographic Information Systems or Remote Sensing software package.</techpreq>
  </distinfo>
  <metainfo>
    <metd>20210729</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>Research and Innovative Technology Administration's Bureau of Transportation Statistics, U.S. Army Corps of Engineers</cntorg>
          <cntper>Office of Geospatial Information Systems</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>1200 New Jersey Ave. S.E.</address>
          <city>Washington</city>
          <state>D.C.</state>
          <postal>20590</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>(202) 366-3282</cntvoice>
        <cntfax>(202) 366-3640</cntfax>
        <cntemail>answers@bts.gov</cntemail>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
    <metsi>
      <metscs>none</metscs>
      <metsc>Unclassified</metsc>
    </metsi>
  </metainfo>
</metadata>