ArcGIS REST Services Directory
JSON

Layer: DrinkingWaterSystems (ID:1)

View In:   Map Viewer

Name: DrinkingWaterSystems

Display Field: WDNAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: Graphic Standards: For districts outside of Tulare County, the data is presented 'as'is' - no effort was made to reconcile overlaps, gaps, or other inconsistancies.For districts within Tulare County, the following rules apply:Tulare County GIS data is 'parcel oriented' ... generally, boundaries are adjustred to coincide with parcel lines (creating consistent error)Parcels within and near to the City of Visalia are 'surveyor accurate' ... accurate to within 3" (more precise that areial photos)Parcels within the 'valley' portion of Tulare County are accurate to within 40'Parcels in the Foothills and Mountains can have significent spatial errorFor collections of small parcels, boundaries are adjusted to correspond to parcel lines, even though that boundary may be offset from 'true position' (as indicated by areial photos)For developments on large parcels, boundaries are adjusted to correspond to aerial photosBoundary vertices were 'snapped' to PARCELS, with sufficient number of points such that the boundary line (line weight 2) would completely obscure the source PARCEL lines, when viewed at 1:5000 scaleDistrict Naming ConventionsDistrict names have been 'standardized' in order to make sorting names useful and to keep district names unique, and to record any special relationship between district. Examples:'Improvement District # 1' is ambiguous ... there are many such districts in the state.... 'ImpD # 1 (C.S.D. of Three Rivers); is unique. The name indicates that this district was spawned by the Community Service District of Three Rivers.'County Water Works # 1' is ambiguous ... there are many such districts in the state.... 'CWW (Tulare) # 1 (Alpaugh)' is unique. The name indicates that this district was spawned by the County of Tulare to serve the community of Alpaugh.

Copyright Text:

Min. Scale: 0

Max. Scale: 0

Default Visibility: true

Max Record Count: 2000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

HasZ: false

HasM: false

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field: GlobalID

Type ID Field: sysTYPE

Fields:
Types:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 11/8/2018 12:26:08 AM

Schema Last Edit Date: 11/8/2018 12:26:08 AM

Data Last Edit Date: 11/8/2018 12:26:08 AM

Supported Operations:   Query   Query Top Features   Query Analytic   Query Bins   Generate Renderer   Validate SQL   Get Estimates   ConvertFormat