Name: Commercial Use - Assessor

Display Field: CORRIDOR

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: NOTE: This comes originally from layers within ..DRP_ADVANCE_PLANNING\housing_element\layers\small_lot_subdivisions\Small_Lot_Subdivisions_Commercial_Analysis_2016.gdb. The numbers below refer to iterative layers, and the bold numbered step refers to this layer.These layers analyse the parcels (exported on 12/19/16) and whether they have commercial zoning and whether they have Assessor Commercial Uses. The purpose of these layers is to help identify where the Commercial Corridors are and it was done through buffering and dissolving. They were classified as follows corridors based on how many adjacent parcels there were in each cluster - good corridors have a lot of adjacent parcels within 50 feet of each other.Selected parcels within the four communities and a 500 foot buffer around each community (has Assessor Use Code). Exported on 12/19/16.Centroids from Layer 2.Parcels dissolved by blocks. DONE IN FIRST DRAFT OF ANALYSIS - NOT CONTINUED AS IT WAS DECIDED TO USE BUFFERING / DISSOLVINGSpatial Joined Centroids with Blocks so that Block ID could be transferred back to parcels. DONE IN FIRST DRAFT OF ANALYSIS - NOT CONTINUED AS IT WAS DECIDED TO USE BUFFERING / DISSOLVINGUsed Layer 5 to code Layer 2 and dissolve on block ID and Use Code. DONE IN FIRST DRAFT OF ANALYSIS - NOT CONTINUED AS IT WAS DECIDED TO USE BUFFERING / DISSOLVINGSelected out Assessor Use Types for Commercial, then buffered by 50 feet and dissolved the buffers. The dissolved buffers were used to select the parcels from Layer 2 and these were dissolved into multi-part polygons. Then these were categorized as to whether they were commercial corridors (good to low quality), commercial areas (not corridors but significant areas), then whether they were non-corridors. The parcel count and area of each multi-part polygon was used to determine corridors in the 1st pass, then a more subjective judgement was used in the second pass.

Copyright Text:

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 72224

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:

XMin: 6463889.318749994
YMin: 1787325.1599999964
XMax: 6524263.219999999
YMax: 1846187.5199999958
Spatial Reference: 102645  (2229)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSBackwardDiagonal
Color: [0, 0, 0, 255]
Outline:
Style: esriSLSSolid
Color: [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

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• SUM_Shape_Area ( type: esriFieldTypeDouble, alias: SUM_Shape_Area )
• ACRES ( type: esriFieldTypeDouble, alias: ACRES )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• GROUP_ID ( type: esriFieldTypeInteger, alias: GROUP_ID )
• COUNT_GIS_ID ( type: esriFieldTypeInteger, alias: COUNT_GIS_ID )
• CORRIDOR ( type: esriFieldTypeString, alias: CORRIDOR, length: 100 )
• Acre_Ranges ( type: esriFieldTypeString, alias: Acre_Ranges, length: 50 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )

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

  Iteminfo   Thumbnail   Metadata