Name: Park Bridges: Non-Skid

Display Field: APP_DATE

Type: Table

Geometry Type: N/A

Description: The Park Bridges layer contains inventoried physical structures that connect a vast park trail system and assets for pedestrians, bicyclists, fishing enthusiasts, vehicles, maintenance work and equestrian use. The features were field collected by PDD (Park Development Division) Inspectors starting in 2016 using ArcGIS Collector and are broken down into three distinct Structure Types: Bridges, Boardwalks and Culverts. All features are inspected on a regular basis for evaluation of condition and safety. All structures are rated for their Structural Load or weight bearing capacity. The three classifications are pedestrian/equestrian, H5/Maintenance or H20 Vehicular. Pedestrian/equestrian is the lowest level of weight load classification. It is designed for pedestrian and/or equestrian traffic only and vehicles of any type are not permitted. H5/Maintenance load rating is for smaller maintenance and light duty vehicles. Also, an occasional ambulance. H20 rating is for heavy duty vehicles and trucks. In addition to Structure Type and Structural Load they are inspected for the presence of Non-Skid surface treatment and pertinent material and size attributes.Bridges are structures that span water bodies, wetlands, roads, valleys, or ditches. They may or may not have railings and vary in width and length. They are constructed of wood, metal, or composite materials such as fiberglass, and sit on various abutment types.Boardwalks are structures that span water bodies, wetlands, marshes, valleys, ditches, or other unsuitable surfaces. They may have railings or not and vary in width and length. Boardwalks are most often constructed of wood decking, framing, and piers that rest on concrete or steel helical piers. Sometimes they can be laid directly on bare ground with no footing and may also be constructed of composite materials. Some boardwalks are designed to float on water to convey foot traffic over and around lakes or ponds or to be used for fishing activities.Culverts are pipes that convey water or other drainage features under a path, road, or trail. These pipes vary in diameter and length and are most often circular but can be arched, elliptical, or square in shape. The pipes are typically constructed of concrete, HDPE, corrugated metal, steel, brick, or stone. They may have headwalls or endwalls attached to the ends of the pipes to avoid erosion and provide earth retention.The Non-Skid table contains a record of Non-Skid applications to the bridge, boardwalk, or culvert features. Non-Skid surface is something that is applied to the top of the bridge or boardwalk deck or the trail surface to increase the coefficient of friction and reduce the probability of slippage. It also ensures a safe non-slip surface that decreases a pedestrian of bicyclist's risk of falls causing injury. It can be in different forms, such as a metal plate that has a shaped raised surface or a paint with sand particles added in and placed on the top of deck or just using a roughened concrete surface.The Comments table contains records of comments made by inspectors regarding Park Bridges.WorkflowParks Maintained Bridges, Boardwalks & CulvertsThis layer is updated yearly to add new bridges or remove bridges that are withdrawn from use. The Park Development Division Construction section issues Work Orders to a team of approximately 5 inspectors to go out in the field and provide a visual inspection of all the Bridges/Boardwalks/Culverts on Park owned property on a 1.5-2-year cycle. A rating for each asset attribute is provided, and any deficiencies are identified. If the asset is found to be damaged or it receives a low rating, it must be repaired or replaced. The PDD data steward coordinates the bridge repairs with in-house facility maintenance personnel, or when replacement is needed, places the bridge onto a CIP (Capital Improvement Program) project list for prioritization. When funding becomes available, design and permits are acquired, and construction commences.Revenue Authority Maintained BridgesThis layer identifies all the Park bridges on Park owned golf course property that must be maintained by the Montgomery County Revenue Authority. These Bridges are Park assets and must be documented. Since they are not maintained by Montgomery Parks, no inspections, or renovations are made by M-NCPPC.DOT (Department of Transportation) Maintained BridgesThis layer identifies all the Park bridges on Park owned property which passenger vehicles use on a regular basis. Most of these Park owned vehicular bridges are inspected and maintained by the Montgomery County DOT (Department of Transportation). These Bridges are inspected every two years by DOT, and they provide PDD with an inspection report. If repairs or replacement are required, PDD works with DOT to get them repaired or replaced. When they need to be replaced, PDD provides oversight of these DOT projects through the M-NCPPC Planning Board approval process and issues a Park Permit for construction. Location(s)SDE:Q:\Layer Files\GIS Database5.sde\PARKS.EnvironmentalEngineering\PARKS.ParkBridge_PtQ:Q:\Layer Files\Environmental Engineering – Park BridgesServices:https://montgomeryplans.org/server/rest/services/EnvironmentalEngineering/ParkBridges_Pt/MapServer https://montgomeryplans.org/server/rest/services/EnvironmentalEngineering/ParkBridges_Pt/FeatureServerhttps://montgomeryplans.org/server/rest/services/EnvironmentalEngineering/ParkBridges_Pt /MapServer_EDIThttps://montgomeryplans.org/server/rest/services/EnvironmentalEngineering/ParkBridges_Pt/FeatureServer_EDIT

Service Item Id: 3a11506ebf594059935090bd797b7fc9

Copyright Text: Data Source: The regular cycle of the Park Development Division, (PDD), inspection program. Data Steward: Construction and Engineering Sections of the Park Development Division. Main contact: Brian Lewandowski.

Default Visibility: false

MaxRecordCount: 5000

MaxSelectionCount: 0

Supported Query Formats: JSON, geoJSON, PBF

Supports Advanced Queries: true

Supports Statistics: true

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Extent:

Drawing Info:

N/A

Feature Draw Order:

N/A

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: false
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: false
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeNone

Type ID Field:

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID, editable: false, nullable: false, defaultValue: null, modelName: OBJECTID )
• GUID ( type: esriFieldTypeGUID, alias: GUID, editable: true, nullable: true, length: 38, defaultValue: null, modelName: GUID )
• APP_DATE ( type: esriFieldTypeDate, alias: Application Date, editable: true, nullable: true, length: 8, defaultValue: null, modelName: APP_DATE )
• INSPECTOR ( type: esriFieldTypeString, alias: Inspector, editable: true, nullable: true, length: 80, defaultValue: null, modelName: INSPECTOR )
• COMMENT_ ( type: esriFieldTypeString, alias: Comment, editable: true, nullable: true, length: 255, defaultValue: null, modelName: COMMENT_ )
• GLOBALID ( type: esriFieldTypeGlobalID, alias: GLOBALID, editable: false, nullable: false, length: 38, defaultValue: null, modelName: GLOBALID )

Templates:

• Name: Park Bridges: Non-Skid
  Description:
  Prototype:
  COMMENT_: null
  INSPECTOR: null
  GUID: null
  APP_DATE: null
  
  Drawing Tool: esriFeatureEditToolNone

Relationships:

• Park Bridge (0) -- Related To: Park Bridges (0)

Capabilities: Query,Sync,Extract

Sync Can Return Changes: true

Is Data Versioned: true

Supports Rollback On Failure: false

Supports ApplyEdits With Global Ids: false

Supports Query With Historic Moment: false

Supports Coordinates Quantization: false

Child Resources:

Supported Operations:   Query   Query Analytic   Query Related Records   Append   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata