This dataset contains the point result of the intersection between layers FDOT_LOCALNAMES_APR18 and NHD24FLOWLINE_DEC17 for the USCG District 8. This layer identifies locations where FDOT roads cross/abut water drainage flowlines such as stream/river, artificial path, etc. This layer is used in the EST for the notification tool. This layer is the parent layer for RCI_NHD24FLOW_DISSOLVE_D7 and RCI_NHD24FLOW_DISSOLVE_D8, RCI_NHD24FLOW_USCG_D7 and RCI_NHD24FLOW_USCG_D8.
The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes.
None
publication date
None
431 Architecture Building, PO Box 115706
www.fgdl.org
FDOT, and USGS/FDEP
GeoPlan relied on the integrity of the attribute information within the original data.
All data for this dataset are logically consistent.
This dataset is complete as of date of production.
This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan
Spatial and Attribute Information
The GeoPlan Center created RCI_NHD24FLOW_APR18.shp on 4/24/18.
This dataset was created by intersecting the following two layers:
Florida Department Of Transportation - Local Names of RCI Roadways - April 2018
FDOT_LOCALNAMES_APR18.shp
National Hydrography Dataset - Linear Surface Water Drainage Network 1:24K - December 2017
NHD24FLOWLINE_DEC17.shp
Intersect Process Steps:
The ArcToolbox GeoProcessing tool 'Intersect' was invoked.
The Input Features were set to:
FDOT_LOCALNAMES_APR18.shp
NHD24FLOWLINE_DEC17.shp
The Output Feature Class was set to:
RCI_NHD24FLOW_APR18.SHP
Join Attributes was set to:
ALL
XY Tolerance was set to:
Default
Output Type was set to:
POINT
Spatial Join Process:
target = RCI_NHD24FLOW_APR18.shp
Join Features = USCG_BND
Join Operation was set to:
JOIN_ONE_TO_ONE
Keep All Target Features was checked
Match Option was set to:
Intersects (in the future consider CLOSEST)
After spatial join look for records that have USCG null and attribute to the closest USCG District.
GeoPlan added and/or populated the following fields:
ROADWAY = Field came from FDOT_LOCALNAME layer, originally called ROADWAY
RCI_DESC = Field came from FDOT_LOCALNAME layer, originally called DESCRIPT
GNIS_ID = Field came from NHD24FLOWLINE layer, originally called GNIS_ID
GNIS_NAME = Field came from NHD24FLOWLINE layer, originally called GNIS_NAME
REACHCODE = Field came from NHD24FLOWLINE layer, originally called REACHCODE
NHD_DESC = Field came from NHD24FLOWLINE layer, originally called DESCRIPT
LAT_DD = Based on the Latitude in Decimal Degrees
LONG_DD = Based on the Longitude in Decimal Degrees
USCG = Based on USCG field from USCG_BND
MGRS = MGRS ID calculated using toolbox tool: Convert Coordinate Notation with
GOOGLEMAP = "https://www.google.com/maps/place/" & [MGRS]
GCID
DESCRIPT = Based on the Combination of: NHD_DESC & " AT " & RCI_DESC
FGDLAQDATE = Date FDOT_LOCALNAME_APR18 acquired from the Source.
Notes for field calculations:
Lat_DD Double (Calc geometry to decimal degrees, wgs84)
LONG_DD Double (Calc geometry to decimal degrees, wgs84)
MGRS 15 String
GOOGLEMAP 100 String
GCID Long (FID or OBJECTID + 1)
To calculate the MGRS field you must use the following:
ArcToolbox > Convert Coordinate Notation
Input Coordinate Format = DD_2 (Longitude and latitude values are in two separate fields.)
X = LONG_DD
Y = Lat_DD
Output Coordinate Format = MGRS
After this layer gets created two layers must be created:
RCI_NHD24FLOW_USCG_D7
RCI_NHD24FLOW_USCG_D8
-to create these layers select from RCI_NHD24FLOW based on USCG district
RCI_NHD24FLOW_DISSOLVE_D7
RCI_NHD24FLOW_DISSOLVE_D8
-to create these layers dissolve above layers
Dataset copied.
Internal feature number.
ESRI
Feature geometry.
ESRI
A unique 8-character identification number assigned to a roadway or section of a roadway either On or Off the State Highway System for which information is maintained in the Department's Roadway Characteristics Inventory (RCI).
Florida Department of Transportation, Transportation Statistics Office
Name of the roadway
Florida Department of Transportation, Transportation Statistics Office
Unique identifier assigned by GNIS
USGS
Proper name specific term or expression by which a particular geographic entity is known.
USGS
Unique identifier composed of two parts. The first eight digits is the subbasin code as defined by FIPS The next six digits are randomly assigned squential numbers that are unique within a Catalog Unit.
USGS
GeoPlan added field based on FTYPE. Contains text description of feature type.
GeoPlan
Abstraction to facilitate hydrologic modeling through open water bodies and along coastal and Great Lakes shorelines and to act as a surrogate for lakes and other water bodies.
USGS
Artificial open waterway constructed to transport water, to irrigate or drain land, to connect two or more bodies of water, or to serve as a waterway for watercraft.
USGS
Line that follows the main outline of the land, including bays, but crosses rivers at their mouths. In the NHD, the outlines of selected coastal islands are included as part of the coastline.
USGS
Known, but nonspecific, connection between two nonadjacent network segments.
USGS
Closed conduit, with pumps, valves and control devices, for conveying fluids, gases, or finely divided solids.
USGS
Body of flowing water.
USGS
A set of naturally occurring subsurface drainage channels formed from the dissolution of soluble rocks in Karst terrain or in terrain similar to karst but formed in nonsoluble rocks, as by melting of permafrost or ground ice, collapse after mining, and by outflow of liquid lava from beneath its solidified crust. Not a named feature.
USGS
Latitude in Decimal Degrees.
GeoPlan
Longitude in Decimal Degrees.
GeoPlan
Based on spatial join of USCG field from USCG_BND.
GeoPlan
Military Grid Reference System Identifier
Esri
Google Map hyper link
Geoplan
GeoPlan Center created ID used for internal purposes
GeoPlan
Based on the following combination of fields: NHD_DESC & RCI_DESC
GeoPlan
Date FGDL acquired the data from the Source.
GeoPlan
Unique ID added by GeoPlan
GeoPlan
431 Architecture PO Box 115706
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
shapefile
431 Architecture Building, PO Box 115706
www.fgdl.org