ArcGIS REST Services Directory Login | Get Token
Home > services > Test_DPW_Stormwater (FeatureServer) > Stormwater Manholes Help | API Reference
JSON

Layer: Stormwater Manholes (ID: 3)

View In:   ArcGIS Online Map Viewer

Name: Stormwater Manholes

Display Field: Type

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 GIS Technician at the Community Development office is responsible for entering new features into the dataset from site plans of recent construction projects in the City of Harrisonburg,- 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 DataType - type of manhole.Cast-In-Place ManholePrecast ManholeNotes:- Domain: “SW_Manhole_Type”Depth – depth of manholeLength – length of face of manholePipe1In - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe2In - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe3In - [Pipe size in inches] [Pipe type] – Ex: 36” CMP Pipe4In - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe5In - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe1Out - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe2Out - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe3Out - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe4Out - [Pipe size in inches] [Pipe type] – Ex: 36” CMPDrainstoMS4 – whether or not the asset drains into the city’s MS4 system.YesNoNotes:- Domain: “Drains_To_MS4”OwnedBy – owner of the manhole.CityOtherNotes:- Domain – “SW_Manhole_Owned_By”MaintainedBy – party responsible for maintaining the manhole.CityOtherNotes:- Domain – “SW_Manhole_Maintained_ByLastInspectionDate - date of the last inspection on the manholeCondition – conditional status that describes the manhole - this should be found in the Inspection Report.ConditionDate – date that the condition of the manhole was inspected.Enabled – 1 or 0 Attachment – static photo of the manhole.PlanLink – link to site plans for manhole.InspectionLink - this is the date of the site plan for the stormwater manhole.InstallDate – file path to location where site plans for the corresponding manhole is found.Status - status of manhole.Location – closest address to stormwater manholes location, full address - without ZIP code.NewDepth – New Depth of manhole.Unique_ID - unique identifying value assigned to a feature, generally same as OBJECTID.Shape – geometric shape of these features are pointsGlobalID - default editor tracking field, unique serial number for the feature.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.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.)------B. Department Notes - N/AC. Unresolved Questions-N/AD. Other- N/A

Copyright Text: The swMANHOLES data layer was created by Kathy Walker in the Department of Community Development in the City of Harrisonburg, on 7/13/2016. This information was created under the supervision of the Systems Analyst and in association with the GIS Technician at 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