ArcGIS REST Services Directory Login | Get Token
JSON

Layer: Wall (BWL) Permits (ID: 36)

Parent Layer: PLUS Cases by Type (Modified)

Name: Wall (BWL) Permits

Display Field: CASE_ID

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: This featire class only contains permits administered by the Building and Safety Department.This feature class is updated by a python script each morning from the previous day's building permits. The script is named BRS_UPDATE.py and is located in the //agency/agencydfs/Tran/Files/rfairhur/Python_Scripts directory. The original data is stored in the Plus_Conversion_Data.gdb file geodatabase in the //agency/agencydfs/Tran/Files/rfairhur/Layers/Plus_Conversion_Data directory.The fields in this feature class are:APN: Assessor parcel number(s) associated with each permitCASE_ID: PLUS permit numberCASE_DESCR: Description of permitted activityCASE_MODULE: The PLUS module in which the case located. All permits in this feature class are in the PERMIT module.CASE_TYPE: The PLUS case type category of the caseCASE_WORK_CLASS: The PLUS work class subcategory of the caseDEPARTMENT: County department issuing permit. For this feature class, all permits have a value of BLD for the Building and Safety Department.CASE_STATUS: The PLUS permit statusAPPLIED_DATE: Date of permit applicationAPPROVED_DATE: Date of permit approvalCOMPLETED_DATE: Date of permitted activity completionEXPIRED_DATE: Date of permit expirationRECORDED_PAGE: The Recorder's book and page number location of the recorded map that created the APNSUBDIVISION_NAME: The Subdivision Name of the recorded map, either per the Assessors or per the Tract/Lot field converted from LMS as of 11/30/2017.LOT: The Assessors Lot field value for the APNBLOCK: The Assessors Block field value for the APNBUILDING_COUNT: The number of buildings covered by the permitUNIT_COUNT: The number of residential, commmercial or industrial units covered by the permit as assigned by the Building and Safety Department.FLOOR_COUNT: The number of floors in the building covered by the permitHEIGHT: The height of the (tallest) building covered by the permitFCC_CODE: Internal attributeBLD_TRACT: The Tract that created or will create the lot the building permit is located withinBLD_LOT: The Lot of the BLD_TRACT that contains or will contain the building permitNEW_APN: When available, the new APN used to replace the shape of the permit after maps have recorded.UNIT_STATS_COUNT: The TRANS_PLUS_RESIDENTIAL_PERMITS_STATS feature class uses this column of unit counts for the statistics it summarizes. This field is primarily maintained for counting BRS permits primary dwelling units, and excludes permits for Second Units, Casitas, Pool Houes, Guest Quarters and duplicate unit values on any multi-parcel permit from being countedLOCATION: General location of permitted activityMODEL_NUMBER: When available, the Model or Plan number of the residential permit. Parsed from CASE_DESCR when available.

Definition Expression: N/A

Copyright Text:

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, AMF, geoJSON

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

Can Modify Layer: false

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   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata