Hosted/Places (FeatureServer)

View In: ArcGIS JavaScript ArcGIS Online Map Viewer

Service Description:

All Layers and Tables

Has Versioned Data: false

MaxRecordCount: 2000

Supported Query Formats: JSON

Supports Query Data Elements:

Layers:

Places (0)

Description: Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops Originally, five layers of place data were combined 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. The dataset has since been added to from numerous other point source datasets along with individual edits from a range of data sources.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 EntityType domain was taken directly from Bing's entity types and descriptions. It was then modifed to be more easily understood and simplified. The Fea_Src domain lists the 5 original data sources, plus Bing as a future data source.The dataset is updated and reviewed by SanGIS on the basis of updates received to other independent point source datasets (e.g. hospitals, schools, fire stations). The Fea_Src field may change from the original sources as data is reviewed and revised. Where duplication of features from the original place data are discovered they are consolidated into a single feature.

Service Item Id: d8958fee125c4df3813791a2b5dd9745

Copyright Text: Staff at San Diego Data Processing, students and department of planning and land use, staff at SanGIS, the San Diego Sheriff's department dispatchers, and several commercial and open source resources.

Spatial Reference: 102646 (2230)

Initial Extent:

Full Extent:

Units: esriFeet

Document Info:

N/A Enable Z Defaults: true

Supports ApplyEdits With Global Ids: false

Supports Dynamic Layers: false

Child Resources: Info Relationships

Supported Operations: Query Query Contingent Values Append