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 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.- The Street Division Superintendent at the Public Works Department is responsible for updating and maintaining paving schedule spreadsheet(s)/information.SECTION 2Explanation of Attribute DataUniqueID - 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 - OBJECTIDRoadName– name of the individual road segment identified in the paving schedule.Lanes - number of traffic lanes in segment.SpeedLimit– speed limit in mph of the segment.StreetClassification– VDOT classification of StreetPrincipal ArterialMinor ArterialMajor CollectorMinor CollectorLocalNon-VDOT StreetAlleyNotes:- Domain: “Street_Classification”StreetDesignation– Whether street is NHS or Non-NHSNHSNon-NHSNotes:- Domain: “Street_Designation”BikeLanes– Does the street have bike lanes along segment?YesNoNotes:- Domain: “Street_Bike_Lanes”CenterTurnLane– whether or not there is a center turn lane in the segment.YesNoNotes:- Domain: “Center_Turn_Lane”Length– (feet) the total length or the street featureInstallDate- this is the year that the street segment was last paved.VDOTConditionAssesment– VDOT CCI rating value.VCADate– date of the VDOT Condition Assesment.LastInspectionDate- date of the last inspection on the street.Condition– conditional status that describes the street - this should be found in the Inspection Report.ConditionDate– date that the condition that the street was inspected.Enabled– 1 or 0Attachment– static photo of the street.Plan Link– file path to location where site plans for the corresponding street is found.InspectionsLink- link to the City Works report form.Location – closest address to street ‘s location, full address - without ZIP code.PlanDate – date of the site plan where the corresponding street is found.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 polyline.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 #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 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 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.)------- N/AB. Department Notes- N/AC. Unresolved Questions- N/AD. Other- N/A
Copyright Text: The Streets data layer was created by Nate Rexrode in the Public Works Department of the City of Harrisonburg, on 5/1/2017. This information was created under the supervision of the Systems Analyst and in association with the GIS Administrator for 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 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 DataUniqueID - 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 - OBJECTIDGeneratorNumber – number assigned to a particular generator.Fuel Type – material that the generator is constructed of.PropaneNatural GasNotes:- Domain: “Generator_Fuel_Type”Wattage– (Watts) a measure of electrical power.InstallDate– date the path was installed.MaintainedBy- designation of the entity that is responsible for maintaining the shared use path.LastInspectionDate– date when the generator was last inspected.Condition– conditional status that describes the generator - this should be found in the Inspection Report.ConditionDate– date that the condition of the generator was inspected.Enabled– 1 or 0Attachment– static photo of the generator.PlanLink– file path to location where site plans for the corresponding generator 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.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 #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 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 NotesC. Unresolved QuestionsD. Other- N/A
Copyright Text: The Generators data layer was created by Nate Rexrode in the Public Works Department of the City of Harrisonburg, in 2017. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg.
Default Visibility: false
MaxRecordCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 0.0
Max Scale: 0.0
Supports Advanced Queries: true
Supports Statistics: true
Has Labels: false
Can Modify Layer: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports Datum Transformation: true
Extent:
XMin: NaN
YMin: NaN
XMax: NaN
YMax: NaN
Spatial Reference: 102746
(2283)
LatestVCSWkid(0)
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 DataUniqueID - 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 - OBJECTIDSidewalkType – 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
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 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 DataLength – (feet) the total length or the curb featureInstallDate - this is the year that the curb was physically installed.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.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.CurbType – type of curb that the line represents.CurbCurb and GutterNotes:- Domain: “Curb_Type_1”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 polyline.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 #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 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.)------- Initial Planning: Image below shows how curb segments will be defined. 8/27/2018 – Curb 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- Cityworks will need to track:Last Inspection DateConditionLast Maintenance DateSchedule MaintenanceC. Unresolved Questions- Geometric Network & Drains to MS4?D. Other- N/A
Copyright Text: The Curbs data layer was created by Alfredo Gutierrez Velasquez in the Public Works Department of the City of Harrisonburg, on 6/1/2016. 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 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 DataLocationType – location of the ramp on the street.BlendedDirectionalNotes:- 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 DomeExposed AggregateOtherNotes:- Domain: “Ramp_Location_Type”Dome Color – Color of truncated domes.RedGreyNotes:- Domain: “stDomeColor”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”VDOT_Function_Condition - VDOT rated condition of rampA - Fully FunctionalB - Adequately FunctionalC - Some FunctionalityD - Ramp NeededNA - Not NeededCE - Commercial EntranceNotes:- Domain: “VDOT_Function Condition”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. 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 - OBJECTIDLocation – 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
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 1Responsible 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 DataUniqueID - 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 - OBJECTIDConstructionMaterial– 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
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.
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 DataUniqueID - 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 - OBJECTIDName – ParkingAreaType – is it a parking lot or parking deck.DeckLotOtherNotes:- Domain: “Parking_Area_Type”InstallDate - this is the year that the parking lot/deck was physically installed.OwnedBy - designation of the entity that has ownership of the deck/lot.CityPrivateNotes:- Domain: “Parking_Owned_By”MaintainedBy - designation of the entity that is responsible for maintaining the deck/lot.CityPrivateNotes:- Domain: “Parking_Maintained_By”Location – closest address to deck/lots location, full address - without ZIP code.Condition – conditional status that describes the deck/lot - this should be found in the Inspection Report.ConditionDate – date that the condition of the deck/lot was inspected.Enabled – 1 or 0Attachment – static photo of the deck/lot.Plan Link – file path to location where site plans for the corresponding deck/lot is found.InspectionLink - link to the City Works report form - full path name.ParkingSpaces – total number of parking spaces in the deck/lot.ADA Spaces – total number of disability parking spaces.TenHrParkingSpaces – total number of 10-hour parking spaces.TwoHrParkingSpaces – total number of 2-hour parking spaces.OneHrParkingSpaces – total number of 1-hour parking spaces.ThirtyMin ParkingSpaces – total number of 30-minute parking spaces.LeasedSpaces – total number of leased/resident parking spaces.GovParkingSpaces – total number of government parking spaces.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 polygons.Shape.STArea() – default field, area of the polygon.Shape.STLength() – default field, length of the polygon.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 #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 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.)------- N/A B. Department Notes- N/A C. Unresolved Questions- N/AD. Other- N/A
Copyright Text: The Parking Lots and Decks data layer was created by Alfredo Velasquez in the Public Works Department of the City of Harrisonburg, on 7/5/2018. 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.
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 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 DataUniqueID - 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 - OBJECTIDCityROW– shows if the mowing area is in the city Right of Way.YesNoNotes:- Domain: “Mowing_Areas_CityROW”CityProperty– shows if the mowing area is on a city owned propertyYesNoNotes:- Domain: “Mowing_Areas-CityProperty”Condition– conditional status that describes the mowing area - this should be found in the Inspection Report.ConditionDate– date that the condition of the mowing area was inspected.Enabled– 1 or 0Attachment– static photo of the mowing area.Plan Link– file path to location where site plans for the corresponding mowing area is found, not applicable for all.InspectionLink- link to the City Works report form.Location – closest address to mowing area’s location, full address - without ZIP code.Acres – acreage of mowing areaSize – size of mowing area in acrescreated_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 polygons.Shape.STArea() – default field, area of the polygon.Shape.STLength()– default field, length of the polygon.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 #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 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 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 mowing area.How many times per year each mowing area was mowed.C. Unresolved QuestionsD. Other- N/A
Copyright Text: The mowing areas data layer was created by Nate Rexrode in the Public Works Department of the City of Harrisonburg, on 2/15/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 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 DataUniqueID - 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 - OBJECTIDSpacerType – buffer material between post and rail.PlasticWoodMetalNotes:- Domain: “Guardrail_Spacer_Type”EndTreatent – collision end type on end of guardrail.AttenuatorStandardOtherNotes:- Domain: “Guardrail_End_Treatment”PostType – material composition of the support posts for the segment.WoodMetalNotes:- Domain: Guardrail_Post_Type”InstallDate – date of guardrail’s installation.OwnedBy - designation of the entity that has ownership of the guardrail.CityPrivateNotes:- Domain: “Guardrail_Owned_By”MaintainedBy - designation of the entity that is responsible for maintaining the guardrail.CityPrivateNotes:- Domain: “Guardrail_Maintained_By”Condition – conditional status that describes the curb - this should be found in the Inspection Report.ConditionDate – date that the condition of the guardrail was inspected.Enabled – 1 or 0Inspection – ?InspectionDate - date of the last inspection on the guardrail.Attachment – static photo of the guardrail.Plan Link – file path to location where site plans for the corresponding guardrail is found.InspectionsLink - link to the City Works report form.Location – closest address to guardrail ‘s location, full address - without ZIP code.PlanDate – date of the site plan where the corresponding guardrail is found.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 polyline.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 #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 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.)------- N/AB. Department Notes- N/AC. Unresolved Questions- N/AD. Other- N/A
Copyright Text: The Guardrails data layer was created by Alfredo Gutierrez Velasquez in the Public Works Department of the City of Harrisonburg, on 7/31/2016. 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 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 DataUniqueID - 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 - OBJECTIDMaterial– material that fence is constructed ofChain LinkWoven WireSplit RailNotes:- Domain: “Fence_Material”Length–(feet) length of fence.Height– (feet) height of fence.BarbWire– does the fence have barbed wire on itYesNoNotes:- Domain: “Fence_Barb_Wire”InstallDate– date the fence was installed.OwnedBy- designation of the entity that has ownership of the fence.CityPrivateNotes:- Domain: “Fence_Owned_By”MaintainedBy- designation of the entity that is responsible for maintaining the fence.CityPrivateNotes:- Domain: “Fence_Maintained_By”Condition– conditional status that describes the fence - this should be found in the Inspection Report.ConditionDate– date that the condition of the fence was inspected.Enabled– 1 or 0Attachment– static photo of the fence.PlanLink– file path to location where site plans for the corresponding fence 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 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 #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 fence.C. Unresolved QuestionsD. Other- N/A
Copyright Text: The Fence data layer was created by Alfredo Velasquez in the Public Works Department of the City of Harrisonburg, on 7/25/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 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 DataType – type of Retaining Wall.RubbleLandscaping StonePoured ConcreteDecorative ConcreteMSENotes:- Domain: “Retaining_Wall_Type”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 - OBJECTIDDimensions – dimensions of the retaining wall in (sq.ft.)RailInstalled – is there a rail on the Retaining Wall?YesNoNotes:- Domain: “Retaining_Wall_Rail”StepsPresent – Are there steps present on the Retaining Wall?YesNoNotes:- Domain: “Retaining_Wall_Steps”Location – closest address to retaining wall‘s location, full address - without ZIP code.InstallDate – date of retaining wall’s installation.OwnedBy - designation of the entity that has ownership of the retaining wall.CityPrivateNotes:- Domain: “Retaining_Wall_Owned_By”MaintainedBy - designation of the entity that is responsible for maintaining the retaining wall.CityPrivateNotes:- Domain: “Retaining_Wall_Maintained_By”Condition – conditional status that describes the retaining wall - this should be found in the Inspection Report.ConditionDate – date that the condition of the retaining wall was inspected.Enabled – 1 or 0Attachment – static photo of the retaining wall.Plan Link – file path to location where site plans for the corresponding retaining wall is found.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 polyline.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 #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 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.)------- N/AB. Department Notes- N/AC. Unresolved Questions- N/AD. Other- N/A
Copyright Text: The Retaining Walls data layer was created by Alfredo Gutierrez Velasquez in the Public Works Department of the City of Harrisonburg, on 7/31/2016. 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 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 DataUniqueID - 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 - OBJECTIDFacility Name – name of facility.Dimensions (sq. ft.) – square footage of building.InstallDate – date of facilities installation.OwnedBy - designation of the entity that has ownership of the facility.CityOtherNotes:- Domain: “Facility_Owned_By”MaintainedBy - designation of the entity that is responsible for maintaining the facility.CityOtherNotes:- Domain: “Facility_Maintained_By”Enabled – 1 or 0Attachment – static photo of the facility.Plan Link – file path to location where site plans for the corresponding facility 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 polygons.Shape.STArea() – default field, area of polygon.Shape.STLength() – default field, length of the polygon.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 #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 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.)------- N/AB. Department Notes- N/AC. Unresolved Questions- N/AD. Other- N/A
Copyright Text: The City Facilities data layer was created by Nate Rexrode in the Public Works Department of the City of Harrisonburg, in 2016. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg.