ArcGIS REST Services Directory Login
JSON

Layer: gis.PLANNING.Annexations (ID: 0)

Name: gis.PLANNING.Annexations

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: FieldsOBJECTID_1*: A number that is automatically assigned to each feature upon creation by ArcGISFILE_ROOM_:Alias "Planning_No". This is the planning annexation number. It can be used to locate files related to the annexation in the DSC's File RoomFILE_NUMBE: Alias "Annex_Map_No". This is the number of the corresponding annexation map in the small vertical file near the file room manager's desk in the DSC's File Room. Not every entry has one, because not every annexation has a map hanging in our file room.ORDINANCE_: The number of the ordinance, if any, associated with the annexationRECEPTION_:The reception number recorded by the County Clerk for the annexationADOPTION_D: The date an annexation was adopted into the cityGRID_ID: An id used to locate the annexation on the map outside of the File Room in the south side of the DSC building.Shape*: Defines the feature type. To properly represent annexations, use 'Polygon'Update_: The date the annexation was last updated.Sig_changes: Whether or not the changes made during the update qualified as 'significant'.SubMapNum: On occasion, an area is subdivided and annexed at nearly the same time. In such cases, the subdivision plat also stands in as the annexation map. When that happens, this entry gets filled out and can be used to identify the plat.NAME: The name given to the annexation.LINKtoSIRE: A link to the annexation documentation for the old digital storage system. Primarily used to construct the current webmap.INDEX_NUM: An index number used to locate the annexation on the map outside of the File Room in the south side of the DSC building.LINKtoSIRE2: A link to the annexation documentation for the old digital storage system. Primarily used to construct the current webmap.YEAR: The year a given annexation was adopted into the citySbdu: Unknown, unused. (marked for deletion. Remove when possible)OrdinanceDoc: An obsolete field awaiting deletion. In order to find the Annexation Ordinance, go to the Annexation's OnBase link.created_user: The name of the user who added the annexation. Most are emptycreated_date: The date the annexation was added to ArcGIS. There are no entries from before 11 - 29 - 2016last_edited_user: The name of the person who last edited the annexation and/or its informationlast_edited_date: The date the annexation and/or its information was last edited.On Base Link: A link that leads to the annexation document in the OnBase digital storage system.Township_Range: The township range in which the majority of the annexation is located.Section:The section in which the majority of the annexation is located. SHAPE.area: Area of the specific feature, as calculated by ArcGISSHAPE.len: Length of the specific features, as calculated by ArcGIS

Service Item Id: fc74a75611f443e2ac4bc38f4a3fef78

Copyright Text:

Default Visibility: true

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