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 Systems Analyst at 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 Systems Analyst.SECTION 2Explanation of Attribute DataLocationType – location of the ramp on the street.MidpointTangentNotes:- Domain: “Ramp_Location_Type”MaterialType – type of material ramp is made from.BrickConcreteNotes:- Domain: “Ramp_Location_Type”ConcreteType – type of concrete used to place the ramp.DecorativeStandardNotes:- Domain: “Ramp_Location_Type”WarningSurface – type of warning surface associated with ramp.Truncated DomeOtherNotes:- Domain: “Ramp_Location_Type”InstallDate – date the ramp was installedOwnedBy - designation of the entity that has ownership of the ADA ramp.PrivateCityNotes:- Domain: “Ramp_Owned_By”MaintainedBy - designation of the entity that is responsible for maintaining the ADA ramp.PrivateCityNotes:- Domain: “Ramp_Maintained_By”Condition – conditional status that describes the ADA ramp - this should be found in the Inspection Report.ConditionDate – date that the condition of the ADA ramp was inspected.Enabled – 1 or 0Attachment – static photo of the ramp.Inspection – InspectionDate – date the ADA ramp was last inspected. UniqueID - unique identifying value assigned to a feature, generally same as OBJECTID. Location – closest address to the ADA ramp’s location, full address - without ZIP code.Plan Link – file path to location where site plans for the corresponding ADA ramp is found, not applicable for all.created_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 points.SECTION 3Handling of Data and RecommendationsCondition (A)Ramp Width – 4 ft. or greaterWarning Surface – Truncated DomeMaterial Condition – Fair or BetterFair or Better – Limited or tight cracking, faulting (<1/4”), isolated spallingCondition (B)Ramp Width – > 3 ft. to < 4 ft. Warning Surface – Exposed Aggregate SurfaceMaterial Condition – PoorPoor – Moderate Cracking, faulting (1/4”-3/4”), moderate spallingCondition (C)Ramp Width – 3 ft. or lessWarning Surface – No detectable warning surfaceMaterial Condition – Very PoorVery Poor – Severe cracking, faulting (>3/4”), extensive spallingCondition (D)A curb ramp is needed but does not exist at the location to access an existing sidewalk where it crosses a curb.[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data]Condition (CE)Private or Commercial Entrances, City does not maintain[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.)------- Condition (CE – Commercial Entrance) – Added to keep track of ADA ramps not maintained by the city.- If ramp has truncated domes but no sidewalk leading to it, mark as condition A.B. Department Notes- Cityworks will need to track:Money, Labor and Equipment attributed to each ADA ramp.C. Unresolved QuestionsD. Other- N/A
Service Item Id: 2ab0d8ab0ff24b3e9454b000aec640e3
Copyright Text: The ADA Ramps data layer was created by Nate Rexrode in the Public Works Department of the City of Harrisonburg, on 3/1/2017. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg.
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 Systems Analyst at 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 Systems Analyst.SECTION 2Explanation of Attribute DataUniqueID - unique identifying value assigned to a feature, generally same as OBJECTID. SidewalkType – type of sidewalk material usedDecorativeBrickConcreteNotes:- Domain: “Sidewalk_Type”GrassBuffer – indicates grass buffer between sidewalk and street.YesNoNotes:- Domain: “Grass_Buffer”SnowRemovalResponsibility – party responsible for removing snowPublic WorksPrivateJMUContractorNotes:- Domain: “Sidewalk_Snow_Removal_Responsibility”Length – (feet) length of sidewalk.Width – (feet) width of sidewalk.InstallDate – date the sidewalk was installed.OwnedBy - designation of the entity that has ownership of the sidewalk.CityPrivateNotes:- Domain: “Sidewalk_Owned_By”MaintainedBy - designation of the entity that is responsible for maintaining the sidewalk.CityPrivateNotes:- Domain: “Sidewalk_Maintained_By”Condition – conditional status that describes the sidewalk - this should be found in the Inspection Report.ConditionDate – date that the condition of the sidewalk was inspected.LastInspectionDate – date the sidewalk was last inspected. Enabled – 1 or 0Attachment – static photo of the sidewalk.PlanLink – file path to location where site plans for the corresponding sidewalk is found, not applicable for all.InspectionLink - link to the City Works report form.Street – closest address to sidewalks location – without ZIP code.created_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 points.Shape.STLength() – default field, length of the featureSECTION 3Handling of Data and RecommendationsTitle ofHandlingTopic #1[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 #2[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 #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 ofHandlingTopic #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.)------8/27/2018 – Sidewalks segments are now to be grouped into block-lengths, or from street intersection to street intersection. This does not include driveway or commercial entrances, if a segment is divided by these features then both segments on either side of the feature are to be merged together. Segments should end on the corner of an adjoining street intersection. Additionally, segments on the other side of the road should be included in the feature, if there is a segment on the opposite side of the street, within the length of the block, then the features should be merged together.B. Department Notes- N/AC. Unresolved Questions- N/AD. Other- N/A
Service Item Id: 2ab0d8ab0ff24b3e9454b000aec640e3
Copyright Text: The Sidewalks data layer was created by Alfredo Velasquez in the Public Works Department of the City of Harrisonburg, on 6/21/2017. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg.
Description: INDEXSection 1: Responsible PartiesSection 2: Explanation of Attribute DataSection 3: Handling of Data and RecommendationsSection 4: Additional ConsiderationsSECTION 1Responsible PartiesParties responsible for updating this layer:- The Systems Analyst at 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 Systems Analyst.SECTION 2Explanation of Attribute DataUniqueID - unique identifying value assigned to a feature, generally same as OBJECTID.ConstructionMaterial– material that the shared use path is constructed of.AsphaltStonePaver BrickConcreteNotes:- Domain: “Shared_Use_Paths_Construction_Material”Width– (feet) width of shared use paths.RejuvenatedDate– date of last maintenance. InstallDate– date the path was installed.OwnedBy- designation of the entity that has ownership of the shared use path.CityPrivateNotes:- Domain: “Shared_Use_Path_Owned_By”MaintainedBy- designation of the entity that is responsible for maintaining the shared use path.CityPrivateNotes:- Domain: “Shared_Use_Path_Maintained_By”Condition– conditional status that describes the shared use path - this should be found in the Inspection Report.ConditionDate– date that the condition of the path was inspected.Enabled– 1 or 0Attachment– static photo of the shared use path.PlanLink– file path to location where site plans for the corresponding path is found, not applicable for all.InspectionLink- link to the City Works report form.created_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.Shape.STLength()– default field, length of the feature.SECTION 3Handling of Data and RecommendationsTitle ofHandlingTopic #1[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 #1[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 #1[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 #1[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 #1[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 howand whythings 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.)------B. Department Notes- Cityworks will need to track:Money, Labor, and Equipment attributed to each shared use path.C. Unresolved QuestionsD. Other- N/A
Service Item Id: 2ab0d8ab0ff24b3e9454b000aec640e3
Copyright Text: The Shared Use Path data layer was created by Alfredo Velasquez in the Public Works Department of the City of Harrisonburg, on 7/12/2017. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg.