ArcGIS REST Services Directory Login
Home > services > PublicWorks > Thermo (FeatureServer) > Thermo API Reference
JSON

Layer: Thermo (ID: 0)

View In:   ArcGIS Online Map Viewer

Name: Thermo

Display Field: Thermo_Marking

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 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 DataThermo_Marking – type of thermo marking.Left Turn ArrowRight Turn ArrowCombo ArrowStop BarCrosswalk4 in White4 in Yellow6 in White6 in YellowContrast ThermoRR CrossingHash Mark8 ft SCHOOL10 ft SCHOOLYield SymbolsBicycle SymbolSharrow (Share The Road)STOP LettersStraight Arrow12 in WhiteNotes:- Domain: “Thermo_Marking”Date_Installed – date the asset was installed.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.Location – closest address to the intersection’s location, full address - without ZIP code.Condition – conditional status that describes the cabinet.Enable – 1 or 0UniqueID - unique identifying value assigned to a feature, generally same as OBJECTID. Reinstall_Date – if the cabinet was removed and then reinstalled, the date of its re-installation.Shape – geometric shape of these features are points.GlobalID - default editor tracking field, unique serial number for 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 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

Service Item Id: 1e7925e019f14d2e9b1a7274e739cfaa

Copyright Text: The Thermoplastic Markings data layer was created by Alfredo Velasquez in the Public Works Department of the City of Harrisonburg, on 1/1/2018. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg. Asset Creator: Alfredo Gutierrez Velasquez (PW) Asset Editor: Asset Manager (PW) & Systems Analyst (PW) Asset Information: PW Traffic Engineering

Default Visibility: true

MaxRecordCount: 5000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 72223.819286

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: false

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

Child Resources:   Field Groups   Contingent Values

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   Update Metadata