ArcGIS REST Services Directory Login | Get Token
JSON

Layer: Places (ID: 0)

Name: Places

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Five layers of place data was combined to make this single layer into a single layer; those of: PLACES (Was SANGIS.PLACES renamed PLACES_OLD); SHERIFF_PLACE_NAMES (Sheriff's place name file for dispatch);PLACES_SG SANDAG Places layer; PLACE_NAMES (Geographic Names Information System /GNIS, assumed); PLACES_CASINOS Casinos.In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.PLACES and PLACES_SG initially contained MULTIPOINT features; TOOLBOX Feature to Point was used to make the features POINT. The working layers were then called PLACES_SG_FeatureToPoint and PLACES_OLD_FeatureToPoint.In the PLACES layer 3 fields were widened for consistency with similarly named fields in other layers. NAME was widened from 32 to 200; ADDR was widened from 32 to 75; TYPE was widened from 20 to 254. After 2 versions the layer was named PLACES_OLD_FeatureToPoint2. PLACES_OLD_FeatureToPoint2 (which was originally PLACES) was copied to a feature class named PLACES_COMBINED. The other 4 feature classes were then appended with the NOTEST option. The name of the original layers where each point resided is in an added field FEA_SRC.The geodatabase was then copied, renamed PLACES_OUTPUT_20100730 and unneeded intermediate results were deleted.The final result is the feature class PLACES_COMBINED in the geodatabase PLACES_OUTPUT_20100730.For the most part, the attribute fields align with the original 5 datasets that were used to create Places. However, some fields were deleted, as they did not apply to the other datasets. Other fields were assigned an attribute domain. These include: CityNm, CommunityNm, EntityType, and Fea_Src. The CityNm is comprised of the 18 incorporated cities within the County, as well as S.D. County. CommunityNm was a field that was added, since data entered under the CityNm field were actually communities. This domain includes 184 community and neighborhood names. The EntityType domain was taken directly from Bing's entity types and descriptions. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.

Copyright Text: County of San Diego, Planning and Development Services, LUEG-GIS Service, SANDAG, San Diego County Sheriff, U.S. Board on Geographic Names

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