PublicWorks/Parking_Lot_Decks (FeatureServer)

View In: ArcGIS JavaScript ArcGIS Online Map Viewer

Service Description: <div style='text-align:Left;'><div><div>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.<ul><li>Deck</li><li>Lot</li><li>Other</li></ul>Notes:- 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.<ul><li>City</li><li>Private</li></ul>Notes:- Domain: “Parking_Owned_By”MaintainedBy - designation of the entity that is responsible for maintaining the deck/lot.<ul><li>City</li><li>Private</li></ul>Notes:- 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 Recommendations<table><tbody><tr><td>Title ofHandlingTopic #1</td><td>[Brief advice/description of how to address a specific component of/issue related to the data.]</td><td>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </td></tr><tr><td>Title ofHandlingTopic #2</td><td>[Brief advice/description of how to address a specific component of/issue related to the data.]</td><td>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </td></tr><tr><td>Title ofHandlingTopic #3</td><td>[Brief advice/description of how to address a specific component of/issue related to the data.]</td><td>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </td></tr><tr><td>Title ofHandlingTopic #4</td><td>[Brief advice/description of how to address a specific component of/issue related to the data.]</td><td>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </td></tr><tr><td>Title ofHandling Topic #5</td><td>[Brief advice/description of how to address a specific component of/issue related to the data.]</td><td>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </td></tr></tbody></table>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 </div></div></div>

All Layers and Tables

Has Versioned Data: true

MaxRecordCount: 2000

Supported Query Formats: JSON

Supports Query Data Elements: true

Layers:

Parking Lot Decks (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 - 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

Service Item Id: c6b486bc5a2a4e7eb523b8e0029b8f58

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.

Spatial Reference: 102746 (2283) LatestVCSWkid(0)

Initial Extent:

Full Extent:

Units: esriFeet

Document Info:

Enable Z Defaults: false

Supports ApplyEdits With Global Ids: false

Support True Curves : true

Only Allow TrueCurve Updates By TrueCurveClients : true

Supports Return Service Edits Option : true

Supports Dynamic Layers: false

Child Resources: Info Uploads Query Data Elements Relationships

Supported Operations: Query Query Contingent Values QueryDomains Apply Edits Extract Changes