Name: Shopping_Centers

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>Point layer to show the location of areas and specific features such as buildings, mile markers, and mountain tops </SPAN></SPAN></P><P><SPAN><SPAN>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.</SPAN></SPAN></P><P><SPAN><SPAN>In PLACES_CASINOS fields were added named ADDR and CITYNM and calculated equal to existing fields ADDRESS and CITY to facilitate the appending process.</SPAN></SPAN></P><P><SPAN><SPAN>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.</SPAN></SPAN></P><P><SPAN><SPAN>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.</SPAN></SPAN></P><P><SPAN><SPAN>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.</SPAN></SPAN></P></DIV></DIV></DIV>

Service Item Id: 6af4c9e3ccca45639fcb9fe0b0801b19

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.

Default Visibility: false

MaxRecordCount: 2000

MaxSelectionCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.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:

XMin: -1.3055095464830847E7
YMin: 3834673.7848378695
XMax: -1.3017481678830773E7
YMax: 3899854.240704759
Spatial Reference: 102100  (3857)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSMSCircle
Color: [165, 129, 56, 255]
Size: 4.0
Angle: 0.0
XOffset: 0
YOffset: 0
Outline:
[0, 0, 0, 255] Width: 0
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• NAME ( type: esriFieldTypeString, alias: NAME, length: 200 )
• ADDR ( type: esriFieldTypeString, alias: ADDR, length: 75 )
• CITYNM ( type: esriFieldTypeString, alias: CITYNM, length: 16 )
• TYPE ( type: esriFieldTypeString, alias: TYPE, length: 254 )
• DESCRIP ( type: esriFieldTypeString, alias: DESCRIP, length: 254 )
• FEA_SRC ( type: esriFieldTypeString, alias: FEA_SRC, length: 35 )
• COMMUNITYN ( type: esriFieldTypeString, alias: COMMUNITYN, length: 35 )
• SCALE ( type: esriFieldTypeInteger, alias: SCALE )
• EDIT_REASO ( type: esriFieldTypeInteger, alias: EDIT_REASO )
• CREATOR ( type: esriFieldTypeString, alias: CREATOR, length: 254 )
• CREATED ( type: esriFieldTypeDate, alias: CREATED, length: 8 )
• EDITOR ( type: esriFieldTypeString, alias: EDITOR, length: 254 )
• EDITED ( type: esriFieldTypeDate, alias: EDITED, length: 8 )
• Primary_Di ( type: esriFieldTypeInteger, alias: Primary_Di )
• Zipcode ( type: esriFieldTypeInteger, alias: Zipcode )
• Longitude ( type: esriFieldTypeDouble, alias: Longitude )
• Latitude ( type: esriFieldTypeDouble, alias: Latitude )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata