ArcGIS REST Services Directory Login | Get Token
Home > services > Test_DPW_Stormwater (FeatureServer) > Bridges and Culverts Help | API Reference
JSON

Layer: Bridges and Culverts (ID: 1)

View In:   ArcGIS Online Map Viewer

Name: Bridges and Culverts

Display Field: StreetNameLocation

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: INDEXSection 1: Responsible PartiesSection 2: Explanation of Attribute DataSection 3: Handling of Data and RecommendationsSection 4: Additional ConsiderationsSECTION 1 Responsible PartiesParties responsible for updating this layer:- The Public Works Department is responsible for updating and maintaining this layer. Additions or editing of features within this layer should be administered or approved by the Asset Manager.SECTION 2Explanation of Attribute DataStructureID – identification code from the inspection report.StreetNameLocation – closest address to bridge\culvert’s location, full address - without ZIP code.FeatureIntersected – type of feature intersected by the bridge\road culvert.StreetWaterwayRailroadMultipleNotes:- Domain: “Bridges_Culverts_Feature_Intersected”BridgeorCulvert – whether the asset is a bridge or a road culvert.BridgeCulvertNotes:- Domain: “Bridges_or_Culverts”NumberofCulverts – total number of channels contained within the culvert.SingleDoubleTripleOtherNotes:- Domain: “Number_of_Culverts”CulvertShape – shape of the culvertCircularEllipticalBoxNotes:- Domain: “Culvert_Shape”CulvertMaterial – material of the culvert.Precast ConcreteCMPNotes:- Domain: “Culvert_Material”CulvertWidth – (inches) length of the longest edge\diameter of culvert, value from inspection report.CulvertHeight - (inches) height of the of culvert, value from inspection report.InstallDate - this is the year that the curb was physically installed, value from inspection report.OwnedBy - designation of the entity that has ownership of the curb.CityOtherNotes:- Domain: “Curb_Owned_By”MaintainedBy - designation of the entity that is responsible for maintaining the curb.CityOtherNotes:- Domain: “Curb_Maintained_By”LastInspectionDate - date of the last inspection on the curb.Condition – conditional status that describes the curb - this should be found in the Inspection Report.ConditionDate – date that the condition of the curb was inspected.Enabled – 1 or 0Attachment – static photo of the curb.Plan Link – file path to location where site plans for the corresponding curb is found.InspectionsLink - link to the City Works report form - full path name.Location – closest address to curb’s location, full address - without ZIP code.PlanDate – date of the site plan where the corresponding curb is found.UniqueID - Unique identifying value assigned to a feature, generally same as OBJECTID. Assets created after May 2023 follow new UniqueID value: Month & Year + OBJECTID – Example: If the asset was created in June of 2023, the Unique ID will be 0623 - OBJECTIDcreated_user – default editor tracking field, who created the feature.created_date – default editor tracking field, when the feature was created.last_edited_user – default editor tracking field, who last edited the feature.last_edited_date - default editor tracking field, when the feature was last edited.GlobalID - default editor tracking field, unique serial number for the feature.Shape – geometric shape of these features are polylines.SECTION 3Handling of Data and RecommendationsPlacement of Point FeatureBridge/culvert points should be placed in the center of the structure, unless they overlap with another feature – if this occurs, offset the culvert point featureIf a culvert overlaps with a bridge feature – refer to the inspection report “Orientation” field to help determine on which side of the culvert to place the point.Inspection ReportsThe current inspection reports for bridges and culverts can be found here: N:\Streets\Maintenance\InventoriesN/ATitle ofHandlingTopic #3[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #4[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandling Topic #5[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] SECTION 4Additional ConsiderationsA. History & Logic of the Data[For future reference, please list facets of the history of the decision-making process related to the data’s use – the how and why things were specifically done the way that they were.] (If the data should be handled/collected a specific way, that should be listed and explained here.)------7/6/2016 - Initial Planning: Will contain data for Cityworks. This will include road and pedestrian bridges. All bridges and culverts that require structural “bridge” inspections.6/19/2018 – Bridge point features should be maintained in the center of their respective structures, culvert points that overlap a bridge feature should be offset to one of the ends of the culvert – this is determined by the “Orientation” field found in the inspection report. B. Department Notes- Cityworks will need to track:Last Inspection DateConditionCondition NotesLast Maintenance DateSchedule Maintenance - for bridge washing after winter, annually. No other reoccurring scheduled work. Other maintenance work would come from work orders. Work orders C. Unresolved Questions- N/AD. Other- Endwalls are part of the culvert/ bridges

Copyright Text: The BridgesandRoadCulverts data layer was created by Nate Rexrode in the Public Works Department of the City of Harrisonburg, on 7/19/2016. This information was created under the supervision of the Systems Analyst and in association with the Department of Community Development for the City of Harrisonburg.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 15000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: true

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field:

Fields: Templates:
Capabilities: Query,Create,Update,Delete,Uploads,Editing

Sync Can Return Changes: true

Is Data Versioned: true

Supports Rollback On Failure: false

Supports ApplyEdits With Global Ids: false

Supports ApplyEdits By Upload Id: true

Edit Fields Info:
Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Supported Operations:   Query   Query Attachments   Query Analytic   Apply Edits   Add Features   Update Features   Delete Features   Calculate   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata