{ "culture": "en-US", "name": "", "guid": "", "catalogPath": "", "snippet": "The Bridges and Road Culverts street layer is a point-based dataset that displays the locations and information for all bridges and culverts in the city of Harrisonburg, VA. This layer will be used in conjunction with Cityworks. The data can be digitized using aerial imagery, or can be collected using a GPS-compatible device. Each point in the database should be an accurate representation of what is under the street.\n\nThe information already contained within the dataset has been manually collected by the City of Harrisonburg, which has employed the means mentioned above to create and populate the data layer. \n\nSee also, \"Bridges\" in the \u2018publicworks\u2019 dataset.", "description": "

INDEX<\/SPAN><\/SPAN><\/P>

Section 1: <\/SPAN><\/SPAN>Responsible Parties<\/SPAN><\/SPAN><\/P>

Section 2: <\/SPAN><\/SPAN>Explanation of Attribute Data<\/SPAN><\/SPAN><\/P>

Section 3: <\/SPAN><\/SPAN>Handling of Data and Recommendations<\/SPAN><\/SPAN><\/P>

Section 4: <\/SPAN><\/SPAN>Additional Considerations<\/SPAN><\/SPAN><\/P>

SECTION 1<\/SPAN><\/SPAN> <\/SPAN><\/SPAN><\/P>

Responsible Parties<\/SPAN><\/SPAN><\/P>

Parties responsible for updating this layer:<\/SPAN><\/SPAN><\/P>

- 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.<\/SPAN><\/P>

SECTION 2<\/SPAN><\/SPAN><\/P>

Explanation of Attribute Data<\/SPAN><\/SPAN><\/P>

StructureID<\/SPAN><\/SPAN> \u2013 identification code from the inspection report.<\/SPAN><\/SPAN><\/P>

StreetNameLocation \u2013 <\/SPAN><\/SPAN>closest address to bridge\\culvert\u2019s location, full address - without ZIP code<\/SPAN><\/SPAN>.<\/SPAN><\/SPAN><\/P>

FeatureIntersected<\/SPAN><\/SPAN> \u2013 type of feature intersected by the bridge\\road culvert.<\/SPAN><\/SPAN><\/P>

  • Street<\/SPAN><\/SPAN><\/P><\/LI>

  • Waterway<\/SPAN><\/SPAN><\/P><\/LI>

  • Railroad<\/SPAN><\/SPAN><\/P><\/LI>

  • Multiple<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

    Notes:<\/SPAN><\/SPAN><\/P>

    - Domain: \u201cBridges_Culverts_Feature_Intersected\u201d<\/SPAN><\/SPAN><\/P>

    BridgeorCulvert<\/SPAN><\/SPAN> \u2013 whether the asset is a bridge or a road culvert.<\/SPAN><\/SPAN><\/P>

    • Bridge<\/SPAN><\/SPAN><\/P><\/LI>

    • Culvert<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

      Notes:<\/SPAN><\/SPAN><\/P>

      - Domain: \u201cBridges_or_Culverts\u201d<\/SPAN><\/SPAN><\/P>

      NumberofCulverts<\/SPAN><\/SPAN> \u2013 total number of channels contained within the culvert.<\/SPAN><\/SPAN><\/P>

      • Single<\/SPAN><\/SPAN><\/P><\/LI>

      • Double<\/SPAN><\/SPAN><\/P><\/LI>

      • Triple<\/SPAN><\/SPAN><\/P><\/LI>

      • Other<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

        Notes:<\/SPAN><\/SPAN><\/P>

        - Domain: \u201cNumber_of_Culverts\u201d<\/SPAN><\/SPAN><\/P>

        CulvertShape<\/SPAN><\/SPAN> \u2013 shape of the culvert<\/SPAN><\/SPAN><\/P>

        • Circular<\/SPAN><\/SPAN><\/P><\/LI>

        • Elliptical<\/SPAN><\/SPAN><\/P><\/LI>

        • Box<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

          Notes:<\/SPAN><\/SPAN><\/P>

          - Domain: \u201cCulvert_Shape\u201d<\/SPAN><\/SPAN><\/P>

          CulvertMaterial<\/SPAN><\/SPAN> \u2013 material of the culvert.<\/SPAN><\/SPAN><\/P>

          • Precast Concrete<\/SPAN><\/SPAN><\/P><\/LI>

          • CMP<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

            Notes:<\/SPAN><\/SPAN><\/P>

            - Domain: \u201cCulvert_Material\u201d<\/SPAN><\/SPAN><\/P>

            CulvertWidth<\/SPAN><\/SPAN> \u2013 (inches) length of the longest edge\\diameter of culvert, value from inspection report.<\/SPAN><\/SPAN><\/P>

            CulvertHeight<\/SPAN><\/SPAN> - (inches) height of the of culvert, value from inspection report.<\/SPAN><\/SPAN><\/P>

            InstallDate<\/SPAN><\/SPAN> - this is the year that the curb was physically installed, value from inspection report.<\/SPAN><\/SPAN><\/P>

            OwnedBy<\/SPAN><\/SPAN> - designation of the entity that has ownership of the curb.<\/SPAN><\/SPAN><\/P>

            • City<\/SPAN><\/SPAN><\/P><\/LI>

            • Other<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

              Notes:<\/SPAN><\/SPAN><\/P>

              - Domain: \u201cCurb_Owned_By\u201d<\/SPAN><\/SPAN><\/P>

              MaintainedBy<\/SPAN><\/SPAN> - designation of the entity that is responsible for maintaining the curb.<\/SPAN><\/SPAN><\/P>

              • City<\/SPAN><\/SPAN><\/P><\/LI>

              • Other<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

                Notes:<\/SPAN><\/SPAN><\/P>

                - Domain: \u201cCurb_Maintained_By\u201d<\/SPAN><\/SPAN><\/P>

                LastInspectionDate<\/SPAN><\/SPAN> - date of the last inspection on the curb.<\/SPAN><\/SPAN><\/P>

                Condition<\/SPAN><\/SPAN> \u2013 conditional status that describes the curb - this should be found in the Inspection Report.<\/SPAN><\/SPAN><\/P>

                ConditionDate<\/SPAN><\/SPAN> \u2013 date that the condition of the curb was inspected.<\/SPAN><\/SPAN><\/P>

                Enabled<\/SPAN><\/SPAN> \u2013 1 or 0<\/SPAN><\/SPAN><\/P>

                Attachment<\/SPAN><\/SPAN> \u2013 static photo of the curb.<\/SPAN><\/SPAN><\/P>

                Plan Link<\/SPAN><\/SPAN> \u2013 file path to location where site plans for the corresponding curb is found.<\/SPAN><\/SPAN><\/P>

                InspectionsLink<\/SPAN><\/SPAN> - link to the City Works report form - full path name.<\/SPAN><\/SPAN><\/P>

                Location \u2013 <\/SPAN><\/SPAN>closest address to curb\u2019s location, full address - without ZIP code<\/SPAN><\/SPAN>.<\/SPAN><\/SPAN><\/P>

                PlanDate <\/SPAN><\/SPAN>\u2013 date of the site plan where the corresponding curb is found.<\/SPAN><\/SPAN><\/P>

                UniqueID <\/SPAN><\/SPAN>- Unique identifying value assigned to a feature, generally same as OBJECTID. Assets created after May 2023 follow new UniqueID value: Month & Year + OBJECTID \u2013 Example: If the asset was created in June of 2023, the Unique ID will be 0623 - OBJECTID<\/SPAN><\/P>

                created_user<\/SPAN><\/SPAN> \u2013 default editor tracking field, who created the feature.<\/SPAN><\/SPAN><\/P>

                created_date<\/SPAN><\/SPAN> \u2013 default editor tracking field, when the feature was created.<\/SPAN><\/SPAN><\/P>

                last_edited_user<\/SPAN><\/SPAN> \u2013 default editor tracking field, who last edited the feature.<\/SPAN><\/SPAN><\/P>

                last_edited_date<\/SPAN><\/SPAN> - default editor tracking field, when the feature was last edited.<\/SPAN><\/SPAN><\/P>

                GlobalID<\/SPAN><\/SPAN> - default editor tracking field, unique serial number for the feature.<\/SPAN><\/SPAN><\/P>

                Shape<\/SPAN><\/SPAN> \u2013 geometric shape of these features are polylines.<\/SPAN><\/SPAN><\/P>

                SECTION 3<\/SPAN><\/SPAN><\/P>

                Handling of Data and Recommendations<\/SPAN><\/SPAN><\/P>

                Placement of Point Feature<\/SPAN><\/SPAN><\/P><\/TD>

                Bridge/culvert points should be placed in the center of the structure, unless they overlap with another feature \u2013 if this occurs, offset the culvert point feature<\/SPAN><\/SPAN><\/P><\/TD>

                If a culvert overlaps with a bridge feature \u2013 refer to the inspection report \u201cOrientation\u201d field to help determine on which side of the culvert to place the point.<\/SPAN><\/SPAN><\/P><\/TD><\/TR>

                Inspection Reports<\/SPAN><\/SPAN><\/P><\/TD>

                The current inspection reports for bridges and culverts can be found here: <\/SPAN><\/SPAN>N:\\Streets\\Maintenance\\Inventories<\/SPAN><\/SPAN><\/A><\/P><\/TD>

                N/A<\/SPAN><\/SPAN><\/P><\/TD><\/TR>

                Title of<\/SPAN><\/SPAN><\/P>

                Handling<\/SPAN><\/SPAN><\/P>

                Topic #3<\/SPAN><\/SPAN><\/P><\/TD>

                [Brief advice/description of how to address a specific component of/issue related to the data.]<\/SPAN><\/SPAN><\/P><\/TD>

                [Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] <\/SPAN><\/SPAN><\/P><\/TD><\/TR>

                Title of<\/SPAN><\/SPAN><\/P>

                Handling<\/SPAN><\/SPAN><\/P>

                Topic #4<\/SPAN><\/SPAN><\/P><\/TD>

                [Brief advice/description of how to address a specific component of/issue related to the data.]<\/SPAN><\/SPAN><\/P><\/TD>

                [Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] <\/SPAN><\/SPAN><\/P><\/TD><\/TR>

                Title of<\/SPAN><\/SPAN><\/P>

                Handling <\/SPAN><\/SPAN><\/P>

                Topic #5<\/SPAN><\/SPAN><\/P><\/TD>

                [Brief advice/description of how to address a specific component of/issue related to the data.]<\/SPAN><\/SPAN><\/P><\/TD>

                [Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] <\/SPAN><\/SPAN><\/P><\/TD><\/TR><\/TBODY><\/TABLE>

                SECTION 4<\/SPAN><\/SPAN><\/P>

                Additional Considerations<\/SPAN><\/SPAN><\/P>

                A. History & Logic of the Data<\/SPAN><\/SPAN><\/P>

                [For future reference, please list facets of the history of the decision-making process related to the data\u2019s use \u2013 the <\/SPAN><\/SPAN>how<\/SPAN><\/SPAN> and <\/SPAN><\/SPAN>why<\/SPAN><\/SPAN> 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.)<\/SPAN><\/SPAN><\/P>

                ------<\/SPAN><\/SPAN><\/P>

                7/6/2016 - Initial Planning: Will contain data for Cityworks. This will include road and pedestrian bridges. All bridges and culverts that require structural \u201cbridge\u201d inspections.<\/SPAN><\/SPAN><\/P>

                6/19/2018 \u2013 Bridge point features should be maintained in the center of their respective structures, <\/SPAN><\/SPAN>culvert<\/SPAN><\/SPAN> points that overlap a bridge feature should be offset to one of the ends of the culvert \u2013 this is determined by the \u201cOrientation\u201d field found in the inspection report. <\/SPAN><\/SPAN><\/P>

                B. Department Notes<\/SPAN><\/SPAN><\/P>

                - Cityworks will need to track:<\/SPAN><\/SPAN><\/P>

                • Last Inspection Date<\/SPAN><\/SPAN><\/P><\/LI>

                • Condition<\/SPAN><\/SPAN><\/P><\/LI>

                • Condition Notes<\/SPAN><\/SPAN><\/P><\/LI>

                • Last Maintenance Date<\/SPAN><\/SPAN><\/P><\/LI>

                • Schedule Maintenance - for bridge washing after winter, annually. No other reoccurring scheduled work. Other maintenance work would come from work orders. <\/SPAN><\/SPAN><\/P><\/LI>

                • Work orders <\/SPAN><\/SPAN><\/P><\/LI><\/UL>

                  C. Unresolved Questions<\/SPAN><\/SPAN><\/P>

                  - N/A<\/SPAN><\/SPAN><\/P>

                  D. Other<\/SPAN><\/SPAN><\/P>

                  - Endwalls are part of the culvert/ bridges<\/SPAN><\/SPAN><\/P><\/DIV><\/DIV><\/DIV>", "summary": "The Bridges and Road Culverts street layer is a point-based dataset that displays the locations and information for all bridges and culverts in the city of Harrisonburg, VA. This layer will be used in conjunction with Cityworks. The data can be digitized using aerial imagery, or can be collected using a GPS-compatible device. Each point in the database should be an accurate representation of what is under the street.\n\nThe information already contained within the dataset has been manually collected by the City of Harrisonburg, which has employed the means mentioned above to create and populate the data layer. \n\nSee also, \"Bridges\" in the \u2018publicworks\u2019 dataset.", "title": "Bridges and Road Culverts Point Data", "tags": [ "City of Harrisonburg", "Harrisonburg", "Public Works Department", "Street", "STREET", "BridgesandRoadCulverts", "local government", "Virginia", "street", "streets", "bridge", "bridges", "culvert", "culverts", "bridges and culverts", "bridges and road culverts", "public", "public works", "works", "CityWorks", "Cityworks", "cityworks", "City Works", "City works", "city works" ], "type": "", "typeKeywords": [], "thumbnail": "", "url": "", "minScale": 150000000, "maxScale": 5000, "spatialReference": "", "accessInformation": "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.", "licenseInfo": "" }