ArcGIS REST Services Directory Login
JSON

Layer: Original_Townsite (ID: 10)

Name: Original_Townsite

Display Field: SUB_NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: FieldsOBJECTID*: A number that is automatically assigned to each feature upon creation in ArcGISSUB_NAME:The name given to a subdivision. No names are allowed to have special characters: use letters and numbers only (replace '&' with 'and' and '#' with 'No'). Otherwise, names are to match those given at the top of the plat. Duplicated because ACCELA uses it. Do not Remove either one!REPLAT:Whether or not the subdivision in question is a replatPLANNING_NO: The planning number associated with a given subdivision, used to locate relevent files in the Development Services Center file room.SubNum:The number assigned to a given subdivision at the conclusion of the planning acceptance, normally given when the mylar copy is hung in the file room. Reason for duplication currently unknown. Do NOT remove unless it can be verified unnecessary. RECORD_DATE: The date a subdivision was recorded by the County ClerkREC_NO: The reception number recorded by the County Clerk for the subdivisionNOTES: Additional notes not accounted for in other fields. Miscellaneous informationSEC: The section in which the the majority of the subdivision is located.T_R: The township range in which the majority of the subdivision is located. Use the abbreviation TXN RYW where x is the township and y is the range. Duplicated field because ACCELA uses it. Do not Remove either one!OrdinanceDoc: The ordinance document number associated with the subdivision, if any.created_user: The name of the user who added the subdivision, automatically generated. Relatively new, so empty for most existing subdivisions.created_date: The date the subdivision was added to ArcGIS, automatically generated. There are no entries before 1 - 16 - 2018last_edited_user:The name of the person who last edited the subdivision and/or its informationlast_edited_date:The date the subdivision and/or its information was last edited.Annexation_Name: The name of the annexation associated with the subdivision, if any. OBLink:A link that leads to the subdivision document(s) in the OnBase digital storage system.LINKtoOnBaseWeb:This link allows the subdivision to be accessed through the COL's newer webmaps. T_R: The township range in which the majority of the subdivision is located. This field has a drop-down (domain) for the ranges. Duplicated field because ACCELA uses it. Do not Remove either one!SUBDIVISION_NAME: The name given to a subdivision. No names are allowed to have special characters: use letters and numbers only (replace '&' with 'and' and '#' with 'No'). Otherwise, names are to match those given at the top of the plat. Duplicated because ACCELA uses it. Do not Remove either one!SUB_NO: The number assigned to a given subdivision at the conclusion of the planning acceptance, normally given when the mylar copy is hung in the file room. Reason for duplication currently unknown. Do NOT remove unless it can be verified unnecessary.Shape*: Defines the feature type, assigned automatically.Shape.STAREA():Area of a specific feature, as calculated by ArcGISShape.STLength(): Length of a specific feature, as calculated by ArcGIS

Service Item Id: 997f07d0f54e467fa5007c8a4f12de6d

Copyright Text:

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON

Min Scale: 0

Max Scale: 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:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
Supported Operations:   Query   Query Attachments   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata