Service Description: The places dataset was designed to create a comprehensive location database of places and things that are not easily attributable to an address. They represent points of interest, mile makers, historical sites, significant community land marks, businesses by type, etc. This dataset is not designed to be a replacement for specific business driven layers that track and maintain the locations of specific features such as as road assets, capital improvements, etc. This is a generic reference layer for both cartographic and geocoding reference.
Service ItemId: 08433f58c6d44e0389f729b4360c5f89
Has Versioned Data: false
Max Record Count: 2000
Supported query Formats: JSON
Supports applyEdits with GlobalIds: False
Supports Shared Templates: True
All Layers and Tables
Layers:
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.
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:
XMin: 5982340.41928156
YMin: 1944784.77513857
XMax: 6704048.12450219
YMax: 2152581.63969942
Spatial Reference: 102646 (2230)
Full Extent:
XMin: 6050432.78057334
YMin: 1776414.17714334
XMax: 6987078.50012593
YMax: 2258558.99467592
Spatial Reference: 102646 (2230)
Units: esriFeet
Child Resources:
Info
SharedTemplates
Supported Operations:
Query
ConvertFormat
Get Estimates