| ArcGIS REST Services Directory |
| Home > services > Maint_AM (FeatureServer) > All Layers and Tables | | API Reference |
FDOT Bridge Inventory is maintained in a restricted database called the Bridge Management System (BMS), formerly PONTIS. Monthly the GIS unit extracts/updates this feature class via script for the visualization of bridge structures in GIS. Bridges are represented as points at the start of the structure in the direction of travel of the roadway. A structure number is inset at the begin point of the structure in the direction of travel. Some Bridge numbers represent both directions of a two structure bridge. In other cases a second number is given to the separate structure for the opposite direction of travel of the roadway. Included also are Pedestrian Crossing Bridge Structures.
FDOT Bridge Inventory is maintained in a restricted database called the Bridge Management System (BMS), formerly PONTIS. Monthly the GIS unit extracts/updates this feature class via script for the visualization of bridge structures in GIS. Bridges are represented as points at the start of the structure in the direction of travel of the roadway. A structure number is inset at the begin point of the structure in the direction of travel. Some Bridge numbers represent both directions of a two structure bridge. In other cases a second number is given to the separate structure for the opposite direction of travel of the roadway. Included also are Pedestrian Crossing Bridge Structures.
This feature class represents the location of High Mast Light Poles which are a subset of FDOT Bridge Inventory. It is maintained in a restricted database called the Bridge Management System (BMS), formerly PONTIS. Monthly the GIS unit extracts/updates this feature class via script for the visualization of bridge structures in GIS. Bridges (which includes mast arms, high mast light poles, and large sign structures are represented as points at the start of the structure in the direction of travel of the roadway. A structure number is inset at the begin point of the structure in the direction of travel.
Mast Arms are a subcategory of the FDOT Bridge Inventory. It is maintained in a restricted database called the Bridge Management System (BMS), formerly PONTIS. Monthly the GIS unit extracts/updates this feature class via script for the visualization of bridge structures in GIS. Mast Arms are represented as points at the intersection. There may be more than one mast arm structure for each point. Mast Arms at a given intersection are given a subscript of V1, V2, etc., starting at the SW corner of the intersection. Inspections are required at least once every 5 years
This feature class represents the location of the control structures in District 4. A device that serves to impede the flow of storm water in order to meet water quality and/or flood criteria. Examples include: Bubble Up, Weir, Orifice, Weir/Orifice Combo, or Control Structure.
Updated routinely - points are collected by ESciences through georeferenced asbuilt plans and imported manually to FDOT GIS databases
This feature class represents the location of the storm discharges in District 4.
Updated routinely - points are collected by ESciences through georeferenced asbuilt plans and imported manually to FDOT GIS databases
The pipes are digitized from end points that have been GPS located and identified. The direction of digitization will indicate the water flow direction. In some cases this flow direction seems questionable to office personnel and should be field verified.
Updated routinely - points are collected by ESciences through georeferenced asbuilt plans and imported manually to FDOT GIS databases
NPDES Database:Information that has been obtained from plans includes (when available and applicable): FM Number, State Project Number, construction date, dimensions, and materials.
NPDES Asset ID:Unique 5 digit number assigned by NPDES consultant when new assets are entered into the database.
Stormwater Facility (SWF) ID:Assigned by NPDES consultant when new assets are entered into the database. Alpha (SWF) numeric ID –the numbers indicate the County in which the asset is located (ex: SWF 3000 = Broward). (3000s and 4000s = Broward; 5000s and 6000s = Palm Beach; 10000s = Martin; 11000 = St. Lucie; 12000 = Indian River)
Receiving Waterbody:The receiving waterbody for each facility is determined by the location of the discharge point. The waterbody may be classified as a Water of the State or it discharges to a Water of the State. The Florida Department of Environmental Protection routinely assesses these waterbodies to determine if they are impaired for specific parameters (e.g., nutrients). Permit information in the NPDES Database was obtained from Environmental Resource Permits authorized by the Water Management Districts in District 4 (South Florida and St. Johns River Water Management Districts).
Updated routinely - points are collected by ESciences through georeferenced asbuilt plans and imported manually to FDOT GIS databases
Maintenance Memorandum of Agreement (MMOA)– Agreement between local government agencies and the state so that local agencies agree to maintain newly constructed or installed improvements such as lights, bridges, hardscapes, etc.
This feature contains miscellanous agreement types. Documents are stored in EDMS and linked to GIS features. This feature is updated frequently by the D4 Maintenance Office
Maintenance Memorandum of Agreement (MMOA)– Agreement between local government agencies and the state so that local agencies agree to maintain newly constructed or installed improvements such as lights, bridges, hardscapes, etc.
This feature contains miscellanous agreement types. Documents are stored in EDMS and linked to GIS features. This feature is updated frequently by the D4 Maintenance Office
Maintenance Memorandum of Agreement (MMOA)– Agreement between local government agencies and the state so that local agencies agree to maintain newly constructed or installed improvements such as lights, bridges, hardscapes, etc.
This feature contains miscellanous agreement types. Documents are stored in EDMS and linked to GIS features. This feature is updated frequently by the D4 Maintenance Office
This feature conatins landscape agreements and attached documents for Memorandum of Agreement vegetation, hardscape, and irrigation matintnenance. The agreements may originate out ot the Landscape Architect's office in connection with a new project or be executed at the behest of the local entitly or through the appropriate maintenance office. Occassionaly they are a result of permit installed vegetation improvements.
Two types – project agreements or inclusive agreements (multiple projects included)
This feature contains miscellanous agreement types. Documents are stored in EDMS and linked to GIS features. This feature is updated frequently by the D4 Maintenance Office
This feature conatins landscape agreements and attached documents for Memorandum of Agreement vegetation, hardscape, and irrigation matintnenance. The agreements may originate out ot the Landscape Architect's office in connection with a new project or be executed at the behest of the local entitly or through the appropriate maintenance office. Occassionaly they are a result of permit installed vegetation improvements.
Two types – project agreements or inclusive agreements (multiple projects included)
This feature contains miscellanous agreement types. Documents are stored in EDMS and linked to GIS features. This feature is updated frequently by the D4 Maintenance Office
This is a polygonal area of DOT-owned ROW. This ROW data has been created by referencing existing property appraiser parcel data and drawing polygons in gaps where FDOT ROW would exist. Using multiple ROW resources, polygons were modified to better fit dimensions of existing ROW. It should be used as an "approximate reference item". Survey, Title Search and ROW maps should always take precedence. This feature class is being maintained jointly by the GIS unit from documents forwarded by ROW acquisition agents and by the PLEM GIS support staff as to roadway transferred areas. New acquisition is being maintained as well as surplussed property deleted. In addition, as new ROW maps are signed and acquisition occurs changes are made. Finally, there is still an ongoing effort to geo-reference older ROW maps and adjust the autogenerated ROW.
The features in this feature class are actively maintained and edited as part of the GIS maintenance process, with edits that are made by Design/Planning/ROW staff being moved from the ROW version to the main production version weekly.
This feature class represents the location of the storm inlets in District 4.
Updated routinely - points are collected by ESciences through georeferenced asbuilt plans and imported manually to FDOT GIS databases
ObjectID: Given by GIS when file is created.NPDES_ID: Unique 5 digit number assigned by NPDES consultant when a new NPDES asset is entered.OutfallSys: The outfall system ID is assigned by NPDES consultant when new information is entered into the database. This number is the same as the ID assigned to the corresponding inlets, pipes, and outfall for that outfall system. If there are multiple manholes per outfall, they will have the same outfall system ID and different NPDES_ID numbers.Asset_Name: Unique to each Outfall System ID and used to identify assets in the field (ex: OC1).AssetShape: The shape of the manhole cover.Material: The material of the manhole cover.
Updated routinely - points are collected by ESciences through georeferenced asbuilt plans and imported manually to FDOT GIS databases
Location of backflow prevention valves. Initial dataset was developed by D4 Drainage section and is intended to be used and updated in Drainage Inquiry GIS Application (DIGA)
Updated as needed
This shapefile tracks mowing areas maintained by the Operations Centers in D4. This includes amount of areas and locational information for each record.