<?xml version="1.0" encoding="ISO-8859-1"?>
<metadata>
<idinfo>
<citation>
<citeinfo>
<origin>Bureau of Transportation Statistics, (BTS)</origin>
<pubdate>19990000</pubdate>
<title>FIXED-GUIDEWAY TRANSIT NETWORK</title>
<edition>20010000</edition>
<geoform>SHAPE</geoform>
<onlink>http://www.bts.gov/</onlink>
</citeinfo>
</citation>
<descript>
<abstract>The Fixed-Guideway Transit and Ferry Network is a comprehensive network database of Florida&apos;s fixed-guideway transit and ferry systems. This includes heavy rail, light rail, monorail, ferry boat, cable car, dedicated HOV roadway, inclined plane, and automated guideway.</abstract>
<purpose>BTS strives to make high-quality data and information available for the transportation community and other individuals or groups interested in transportation. Strong leadership, planning, educational outreach, and the pursuit of a superior working team frame our vision.  The 1991 Intermodal Surface Transportation Efficiency Act (ISTEA) established the Bureau of Transportation Statistics (BTS) for data collection, analysis, and reporting and to ensure the most cost-effective use of transportation-monitoring resources.  We strive to increase public awareness of the nation&apos;s transportation system and its implications and improve the transportation knowledge base of decisionmakers.</purpose>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>19990000</caldate>
</sngdate>
</timeinfo>
<current>Ground Condition</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>Irregular</update>
</status>
<spdom>
<bounding>
<westbc>-87.429040</westbc>
<eastbc>-79.872251</eastbc>
<northbc>30.983191</northbc>
<southbc>24.492815</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>NONE</themekt>
<themekey>Bureau of Transportation Statistics</themekey>
<themekey>Rail network</themekey>
<themekey>Ferry network</themekey>
<themekey>Planning</themekey>
</theme>
<place>
<placekt>NONE</placekt>
<placekey>Florida</placekey>
<placekey>Fixed-Guideway Transit Networks</placekey>
</place>
<temporal>
<tempkt>NONE</tempkt>
<tempkey>1990&apos;s</tempkey>
</temporal>
</keywords>
<accconst>NONE</accconst>
<useconst>
The data provide users with information about the location and type of fixed-guideway transit and terminal facilities primarily for regional  cartographic, spatial and network analysis purposes.  Attribute information was obtained from individual transit agencies through telephone conversations and follow-up written material provided by the agency.  The level of detail and completeness of this information varied, depending on the source.  Attribute data were transcribed directly into the database with no independent verification.  Attribute data is incomplete at this time, and what data is included reflects information received from individual transit agencies during 1994.

THE DATA INCLUDED IN THIS APPLICATION ARE BASED ON INTERPRETATION OF AVAILABLE INFORMATION AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING.

Scale is an important factor in data usage. Certain scale data sets are not suitable for some projects, analysis, or modeling purposes. Please be sure you are using the best available data.

1:24000 scale data sets 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 data sets are recommended for projects that are at the multi-county or regional level.  1:250000 scale data sets 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 analyses. 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 web pages at: http://www.geoplan.ufl.edu/education.html
</useconst>
<native>For more information, visit: http://www.bts.gov/</native>
<crossref>
<citeinfo>
<origin>Bureau of Transportation Statistics, (BTS)</origin>
<pubdate>19990000</pubdate>
<title>Unavailable</title>
<geoform>Map</geoform>
</citeinfo>
</crossref>
</idinfo>
<dataqual>
<attracc>
<attraccr>Relied on the integrity of the attribute information within the original data layer.</attraccr>
</attracc>
<logic>After completing topological and attribute verification using ARC/INFO, the data was extracted and reformatted into the BTS ACSII format.Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file.  All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly.  This process is documented in the Process_Step.)  Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates.  All internal polygons are tested for closure.  Certain attributes and/or entities, e.g. closure line, convey data quality information.  When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of &quot;9s&quot;; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of &quot;9s.&quot;</logic>
<complete>Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file.  All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly.  This process is documented in the Process_Step.)  Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates.  All internal polygons are tested for closure.  Certain attributes and/or entities, e.g. closure line, convey data quality information.  When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of &quot;9s&quot;; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of &quot;9s.&quot;</complete>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>Bureau of Transportation Statistics, (BTS)</origin>
<pubdate>19990000</pubdate>
<title>Unavailable</title>
<geoform>Map</geoform>
</citeinfo>
</srccite>
<srcscale>N/A</srcscale>
<typesrc>Map</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>19990000</caldate>
</sngdate>
</timeinfo>
<srccurr>Ground Condition</srccurr>
</srctime>
<srccitea>BTS</srccitea>
<srccontr>Data representing Fixed-Guideway Transit networks, Ferry networks within the state of Florida</srccontr>
</srcinfo>
<procstep>
<procdesc>
The process step describes, in general, the process used in the production of data sets.  The originating agencies created the original spatial coverage.  GeoPlan, during the QA/QC process included the following aspects:
(1) Reprojected data to FGDL Albers
(2) Set Tolerances to FGDL Standard
(3) Dropped item FEATURID (repeat of FEATURID)
(4) Moved descript to the end of table
(5) Related attribute tables were joined
</procdesc>
<procdate>20000000</procdate>
</procstep>
</lineage>
</dataqual>
<spref>
<horizsys>
<planar>
<mapproj>
<mapprojn>Albers Conical Equal Area</mapprojn>
<albers>
<stdparll>24.000000</stdparll>
<stdparll>31.500000</stdparll>
<longcm>-84.000000</longcm>
<latprjo>24.000000</latprjo>
<feast>400000.00000</feast>
<fnorth>0.00000</fnorth>
</albers>
</mapproj>
<planci>
<plance>coordinate pair</plance>
<coordrep>
<absres>0.001024</absres>
<ordres>0.001024</ordres>
</coordrep>
<plandu>METERS</plandu>
</planci>
</planar>
<geodetic>
<horizdn>D_North_American_1983_HARN</horizdn>
<ellips>GRS1980</ellips>
<semiaxis>6378137.000000</semiaxis>
<denflat>298.257222</denflat>
</geodetic>
</horizsys>
</spref>
<eainfo>
<detailed>
<enttyp>
<enttypl>TRNSIT.DBF</enttypl>
<enttypd>Database File</enttypd>
<enttypds>None</enttypds>
</enttyp>
<attr>
<attrlabl>RECTYPE</attrlabl>
<attrdef>Record type, &apos;L&apos; for line</attrdef>
<attrdefs>BTS record</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>VERSION</attrlabl>
<attrdef>File version number, 2</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>REVISION</attrlabl>
<attrdef>Record revision number</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>MODDATE</attrlabl>
<attrdef>Record modification date</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>LINKID</attrlabl>
<attrdef>Unique sequential line identification</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>FEATUREID</attrlabl>
<attrdef>Unique line identification</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>ANODE</attrlabl>
<attrdef>Node identification for the beginning node of the line</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>BNODE</attrlabl>
<attrdef>Node identification for the ending node of the line</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>STFIPS1</attrlabl>
<attrdef>Primary State FIPS Code</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>STFIPS2</attrlabl>
<attrdef>Secondary State FIPS Code</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>RTS_SRVD</attrlabl>
<attrdef>Routes Served</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>GRD_ELEV</attrlabl>
<attrdef>Grade/elevation</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<edom>
<edomv>1</edomv>
<edomvd>At grade</edomvd>
<edomvds>Same</edomvds>
</edom>
<edom>
<edomv>2</edomv>
<edomvd>Elevated</edomvd>
<edomvds>Same</edomvds>
</edom>
<edom>
<edomv>3</edomv>
<edomvd>Below grade</edomvd>
<edomvds>Same</edomvds>
</edom>
<edom>
<edomv>4</edomv>
<edomvd>On structure</edomvd>
<edomvds>Same</edomvds>
</edom>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>TR_TYPE</attrlabl>
<attrdef>Track Type</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>UZA</attrlabl>
<attrdef>Urbanized Area Name</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>STATUS</attrlabl>
<attrdef>Status</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<edom>
<edomv>1</edomv>
<edomvd>Planned</edomvd>
<edomvds>Same</edomvds>
</edom>
<edom>
<edomv>2</edomv>
<edomvd>Out of service</edomvd>
<edomvds>Same</edomvds>
</edom>
<edom>
<edomv>3</edomv>
<edomvd>Active</edomvd>
<edomvds>Same</edomvds>
</edom>
<edom>
<edomv>4</edomv>
<edomvd>Construction</edomvd>
<edomvds>Same</edomvds>
</edom>
<edom>
<edomv>5</edomv>
<edomvd>Unknown (not referred to by BTS)</edomvd>
<edomvds>Same</edomvds>
</edom>
<edom>
<edomv></edomv>
<edomvd>Not defined</edomvd>
<edomvds>Same</edomvds>
</edom>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>DESCRIPT</attrlabl>
<attrdef>Type of transit system</attrdef>
<attrdefs>Same</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntperp>
<cntper>Operator</cntper>
<cntorg>FLORIDA GEOGRAPHIC DATA LIBRARY</cntorg>
</cntperp>
<cntaddr>
<addrtype>Physical</addrtype>
<address>
431 Architecture Building
PO Box 115706
</address>
<city>Gainesville</city>
<state>Florida</state>
<postal>32611-5706</postal>
</cntaddr>
<cntvoice>(352) 3920997, Operator</cntvoice>
<cntemail>http://www.fgdl.org/fgdldocs/document/techsupp.htm</cntemail>
<hours>24 Hours / Day</hours>
<cntinst>
Please visit the web site, http://www.fgdl.org, for all
questions or concerns.
</cntinst>
</cntinfo>
</distrib>
<distliab>Florida Geographic Data Library is a product of the University of Florida GeoPlan Center with support from the Florida Department of Transportation and the Florida Department of Environmental Protection. THE FGDL DATA AS PROVIDED BY CONTRIBUTING ORGANIZATIONS AND ANY PROGRAMMING SOFTWARE CREATED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER (COLLECTIVELY THE &quot;MATERIALS&quot;) ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE &quot;DATA PROVIDERS&quot;). DO NOT REPRODUCE, REDISTRIBUTE OR RESELL THE MATERIALS, OR PROVIDE THE MATERIALS FOR FREE TO CUSTOMERS OR CLIENTS, OR PLACE THE MATERIALS FOR DOWNLOAD ON A WEBSITE. ADDITIONALLY, WHEN USING FGDL DATA OR SOFTWARE IN PROJECTS, MAPS, ETC.; YOU AGREE TO ACKNOWLEDGE THE FGDL AS A DATA SOURCE. THE MATERIALS ARE PROVIDED &quot;AS IS&quot;. 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 MAKES NO WARRANTIES, GUARANTIES OR REPRESENTATIONS AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DATA PROVIDED BY THE FGDL CONTRIBUTING ORGANIZATIONS. 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.</distliab>
</distinfo>
<metainfo>
<metd>2001</metd>
<metc>
<cntinfo>
<cntperp>
<cntper>Operator</cntper>
</cntperp>
<cntaddr>
<addrtype>Physical</addrtype>
<address>400 Seventh Street, SW</address>
<city>Washington</city>
<state>DC</state>
<postal>20590</postal>
</cntaddr>
<cntvoice>1-202-366-3640</cntvoice>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
</metainfo>
</metadata>

