Description: APN: Assessor Parcel NumberASMT: Assessment numberREALUSE: Assessor Real Use CodePrimary code "C" = CommercialPrimary code "A" or "P" = AgriculturalAll other Primary codes = ResidentialDESCRIPTION: Open description field for notes regarding address, if anyDIR: Directional prefix for site address. N, S, E, or WHOUSE NUMBER: Site address numberSTREET NAME: Site address street nameSTREET TYPE: Site address street suffixUNIT: Unit number, if anyCITY: Site address city locationZIP: Site address zip codeNUMBER OF UNITS: The number of units. 0 is assigned to metersADDRESS TYPE: 1. Single Family Residence2. Residential 2-3 unit3. Condo4. Mobile Home5. Apartment6. Commercial7. Second Unit8. Meter9. Cell Tower10. TentativeLOT: Legal lot numberLEGAL: Recorded documentADDRESS: Concatenated site address field created from DIR, HOUSE NUMBER, STREET NAME and STREET TYPE fieldsDATE EDITED: Internal attributeGlobalID: Internal attributeINCORPORATED: Internal attribute for tracking County or City addressesADDRESS_ID: Unique ID for database purposes.X_COORDINATE: X coordinate in State Plane.Y_COORDINATE: Y coordinate in State Plane.LAT_COORDINATE: Lattitude coordinate. LONG_COORDINATE: Longitude coordinate.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Field Definition:GEOID10 = "Census tract identifier; a concatenation of 2010 Census state FIPS code, county FIPS code, and census tract code"CAC_NAME = Community Name. Derived from Community Advisory Councils RCIT GIS layer. Census Areas not within a CAC are identified as NONE. DATA_SOURCE = CES 3.0 | CEVA | OVERLAP CES 3.0/CEVA CalEnviroscreen 3.0 (CES) represents a 2018 statewide analysis from the California Office of Environmental Health Hazard Assessment (OEHHA). Source Link: https://oehha.ca.gov/calenviroscreenCumulative Environmental Vulnerabilities Assessment (CEVA) represents data from the Center for Regional Change at UC Davis. Their effors encompassed a County wide study and the report was published in June, 2013. Report Link: https://regionalchange.ucdavis.edu/report/revealing-invisible-coachella-valleyThe Environmental Justice Communities attribute information for Riverside County derived from the efforts of State and university research and analysis. Note, only attribute information from these sources were used. For spatial reference, census tract and census block group polygons were derived from the Census Bureau as released to the public in the form of TIGER/Line Shapefiles. Source Link: https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-line-file.html
Definition Expression: N/A
Copyright Text: US Census, California Office of Environmental Health Hazard Assessment (OEHHA) , Center for Regional Change UC Davis, RCIT, Riverside County Planning Department
Description: CITYNAME: City nameANNEXATION: Annexation numberLAFCO_NUM: Local Area Formation Commission numberRECORDED_DATE: Date of recordation for annexationINST_NUM: Recorders office instrument numberCITY_FIPS: Federal Information Processing Standard city numberMaintained by Stella Spadafora: 5/2015
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.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
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.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
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.
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.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
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.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
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.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
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.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: This feature class only contains PLUS cases and if a department name is part of the feature class name, only the set of cases created and maintained by that department are included in the feature class.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.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: This feature class only contains PLUS cases and if a department name is part of the feature class name, only the set of cases created and maintained by that department are included in the feature class.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.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [CASE_ID] CONCAT " - PA " CONCAT [PLANNING_AREA] Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: [255, 255, 190, 255] Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Value: Coachella Valley Stormwater Channel and Delta Conservation Area Label: Coachella Valley Stormwater Channel and Delta Conservation Area Description: Symbol:
Value: Indio Hills/Joshua Tree National Park Linkage Conservation Area Label: Indio Hills\Joshua Tree National Park Linkage Conservation Area Description: Symbol:
Description: Government Code 51175-89 directs the California Department of Forestry and Fire Protection (CAL FIRE) to identify areas of very high fire hazard severity zones within Local Responsibility Areas (LRA). Mapping of the areas, referred to as Very High Fire Hazard Severity Zones (VHFHSZ), is based on data and models of, potential fuels over a 30-50 year time horizon and their associated expected fire behavior, and expected burn probabilities to quantify the likelihood and nature of vegetation fire exposure (including firebrands) to buildings. Details on the project and specific modeling methodology can be found at http://frap.cdf.ca.gov/projects/hazard/methods.html. Local Responsibility Area VHFHSZ maps were initially developed in the mid-1990s and are now being updated based on improved science, mapping techniques, and data. This specific geographic information system dataset depicts final CAL FIRE recommendations for Very High FHSZs within the local jurisdiction. The process of finalizing these boundaries involved an extensive local review process, the details of which are available at http://frap.cdf.ca.gov/projects/hazard/btnet/ (click on "Continue as guest without logging in"). Local government has 120 days to designate, by ordinance, very high fire hazard severity zones within its jurisdiction after receiving the recommendation. Local government can add additional VHFHSZs. There is no requirement for local government to report their final action to CAL FIRE when the recommended zones are adopted. Consequently, users are directed to the appropriate local entity (county, city, fire department, or Fire Protection District) to determine the status of the local fire hazard severity zone ordinance. To display the areas of VHFHSZ recommended by CAL FIRE, simply display on the attribute HAZ_CLASS, as that has been filtered to represent only areas in the Very High Class, and only for areas that are in Local Responsibility Area (LRA) status.
Definition Expression: N/A
Copyright Text: CAL FIRE recoginzes the important contribution of various local government entities that contributed data, maps, and comments that were critical components of the FHSZ mapping process.
Description: Government Code 51175-89 directs the California Department of Forestry and Fire Protection (CAL FIRE) to identify areas of very high fire hazard severity zones within Local Responsibility Areas (LRA). Mapping of the areas, referred to as Very High Fire Hazard Severity Zones (VHFHSZ), is based on data and models of, potential fuels over a 30-50 year time horizon and their associated expected fire behavior, and expected burn probabilities to quantify the likelihood and nature of vegetation fire exposure (including firebrands) to buildings. Details on the project and specific modeling methodology can be found at http://frap.cdf.ca.gov/projects/hazard/methods.html. Local Responsibility Area VHFHSZ maps were initially developed in the mid-1990s and are now being updated based on improved science, mapping techniques, and data. This specific geographic information system dataset depicts final CAL FIRE recommendations for Very High FHSZs within the local jurisdiction. The process of finalizing these boundaries involved an extensive local review process, the details of which are available at http://frap.cdf.ca.gov/projects/hazard/btnet/ (click on "Continue as guest without logging in"). Local government has 120 days to designate, by ordinance, very high fire hazard severity zones within its jurisdiction after receiving the recommendation. Local government can add additional VHFHSZs. There is no requirement for local government to report their final action to CAL FIRE when the recommended zones are adopted. Consequently, users are directed to the appropriate local entity (county, city, fire department, or Fire Protection District) to determine the status of the local fire hazard severity zone ordinance. To display the areas of VHFHSZ recommended by CAL FIRE, simply display on the attribute HAZ_CLASS, as that has been filtered to represent only areas in the Very High Class, and only for areas that are in Local Responsibility Area (LRA) status.
Definition Expression: N/A
Copyright Text: CAL FIRE recoginzes the important contribution of various local government entities that contributed data, maps, and comments that were critical components of the FHSZ mapping process.
Description: The General Plan provides new land use designations for all parcels in the unincorporated area of Riverside County. While delivery of this data was received by the County at this time, please be advised that GIS has NOT OFFICIALLY VERIFIED the data or PERFORMED ADEQUATE QUALITY CONTROL VALIDATION for ACCURACY or DISCREPANCIES. In addition, consistency review is planned for comparison of current Zoning classifications with General Plan designations. Until completion of this review, please be aware that discrepancies can occur on any parcel. *The data now reflects the current (05/06/13) city boundaries, March Joint Powers Authority landuse designations have been removed. Please contact MJPA for landuse information. ***Please use the cartographic representations (Landuse, Overlay, Foundation Component) within this data layer for all map products*** Maintained by Stella Spadafora 07/2016
Value: TEMECULA VALLEY WINE COUNTRY POLICY AREA - EQUESTRIAN DISTRICT Label: TEMECULA VALLEY WINE COUNTRY POLICY AREA - EQUESTRIAN DISTRICT Description: Symbol:
Value: TEMECULA VALLEY WINE COUNTRY POLICY AREA - RESIDENTIAL DISTRICT Label: TEMECULA VALLEY WINE COUNTRY POLICY AREA - RESIDENTIAL DISTRICT Description: Symbol:
Value: TEMECULA VALLEY WINE COUNTRY POLICY AREA - WINERY DISTRICT Label: TEMECULA VALLEY WINE COUNTRY POLICY AREA - WINERY DISTRICT Description: Symbol:
Description: This feature class was derived from the LMSACTIVITIES_BUILDINGSAFTEY feature class and the SPECIFIC_PLAN feature class.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:LMS_KEY - The unique key value within the LMS system. In this feature class it is not unique for Specific Plan Planning Areas.CASENAME - The format a user would input to the LMS system to find the caseCASE_TYPE - The main type of the case, which can be either SP or TR.STATUS - The status of the case. These cases are all approved cases, even if the LMS system does not have that status.CATEGORY - PLNG is the category for all these cases.DEPARTMENT - PLANNING is the Department for all these cases.APPLIED_DATE - The application date for the case expressed as a number in the format YYYYMMDD.APPROVED_DATE - The approved date for the case expressed as a number in the format YYYYMMDD.COMPLETED_DATE - The completed date for the case expressed as a number in the format YYYYMMDD.EXPIRED_DATE - The expiration date for the case expressed as a number in the format YYYYMMDD.CASE_TYPE_DESC - The human readable description of the Case TypeCASE_DESC - A brief description of what the case was designed to do.CONSTRUCTION - The code for the case type.LOCATION - A description of the case locationTRACT - The numeric portion of a Tract number. Only used with Tracts. This corresponds to the same field in PARCEL_ASSESSORS.SUB_NAME - The title of a Tract. Only used with Tracts. This corresponds to the same field in PARCEL_ASSESSORS.SP_NUMBER - The base number assigned a Specifc Plan. Used with both Specific Plans and Tracts (to indicate the Tract is within the Specifc Plan).SP_NAME - The Specific Plan name. Used with both Specific Plans and Tracts (to indicate the Tract is within the Specifc Plan).ADOPTED_DATE - The original adoption date of the Specific Plan or an Amendment adoption date. Only used for Specific Plans.PLANNING_AREA - The Planning Area designation for the portion of the Specific Plan within the boundary. Only used for Specific Plans.SPLU_DESCRIPTION - The Specific Plan Land Use Description as stated in the Specific Plan document. These designations vary from plan to plan and are not standardized.LAND_USE_STANDARDIZED - The standard Land Use Designation codes used by the General Plan that best represents the SPLU_DESCRIPTION.MINIMUM_LOT_SIZE_SQ_FT - The minimum lot size permitted by the Planning Area or Tract, always expressed in square feet.ACRES - The GIS calculated Acreage of the feature boundary, not the acreage identified in the Specific Plan document or Tract description.MIN_DENSITY - The minimum desity permitted within the Planning Area.MAX_DENSITY -The maximum desity permitted within the Planning Area.EXPECTED_UNITS - The number of residential units expected to be built within the Planning Area or Tract. This may be more or less than the Approved Units authorized if the recorded maps had more or less residential lots than the original Planning authorization.APPROVED_UNITS - The number of units authorized by the original Planning approvak of the case,PRE_LMS_UNITS - The building permti units that must have been built before the LMS system could track building permits.PERMIT_FINAL_UNITS - The number of LMS hounsing units counted from BRS cases within the LMS system.PERMIT_FINAL_UNITS - The number of LMS housing units counted from BRS cases within the LMS system that have a status of FINAL.TOTAL_FINAL_UNITS - The sum of the PRE_LMS_UNITS and PERMIT_FINAL_UNITS.PERCENT_FINAL - The percent of build out of the TOTAL_FINAL_UNITS relative to the EXPECTED_UNITS.PERMIT_ISSUED_UNITS - The number of LMS housing units counted from BRS cases within the LMS system that have a status of ISSUED.TOTAL_ISSUED_UNITS - The sum of the PRE_LMS_UNITS, PERMIT_FINAL_UNITS and PERMIT_ISSUED_UNITS.PERCENT_ISSUED - The percent of build out of the TOTAL_ISSUED_UNITS relative to the EXPECTED_UNITS.PERMIT_ACTIVE_UNITS - The number of LMS hounsing units counted from BRS cases within the LMS system that have a Status of APPLIED, PLANCK, or PCAPPR.TOTAL_ACTIVE_UNITS - The sum of the PRE_LMS_UNITS, PERMIT_FINAL_UNITS, PERMIT_ISSUED_UNITS and PERMIT_ACTIVE_UNITS.PERCENT_ACTIVE - The percent of build out of the TOTAL_ACTIVE_UNITS relative to the EXPECTED_UNITSSUPERVISORIAL_DISTRICT - The number of the Supervisorial Distrct in which the case is located.RECORDED_NOTES - Notes concerning the recordation status of the Tract map or of residential tracts within the Specific Plan. The notes are not determined by Planning Area, but only for the entire Specific Plan.
Description: This data set of line features represent Riverside County's recorded street centerlines.This data set was designed to carry out functions of the Transportation department and is not a true street network layer. Centerlines do not have complete "connectivity" due to the fact that this layer is primarily roads that have been recorded but does not necessarily contain all roads. OBJECTID - Internal feature number. STNAME - Recorded name of the centerline. TYPE - Used to classify roads, primarily by surface type. Description of the codes found in the attribute "TYPE" TYPE DESCRIPTION C01 Federal Aid Interstate C02 State Highways C03 F.A.U. Maintained C04 F.A.S. Maintained C05 Paved Surface Maintained C06 Paved Surface (Traveled) C07 Graveled Surface Maintained C08 Graveled Surface (Traveled) C09 Dirt Surface Maintained C10 Dirt Surface (Traveled) C11 Accepted For Public Use C12 Non-County/Accepted for P.U. C13 Non-County road C14 Vacated C15 Abandon C16 Maintained F.A.U./Non-County C17 Maintained F.A.S./Non-County C18 Maintained Paved/Accepted C19 Maintained Paved/Non-County C20 Maintained Paved/Vacated C21 Maintained Gravel/Accepted C22 Maintained Gravel/Non-County C23 Maintained Gravel/Vacated C24 Maintained Dirt/Accepted C25 Maintained Dirt/Non-County C26 Maintained Dirt/Vacated C27 Accepted/Vacated C28 Maintained Under Contract C29 City Road C30 Paved Maintained/Dirt Maintained C31 Dedicated and Accepted/CFD Maintained W01 Maintained for City W02 Maintained for City/Non-County W03 Maintained for City/Non-County (Reversed) W04 Maintained for City/Accepted W05 F.A.U. Maintained/Maintained for City W06 Dirt Surface Maintained/Maintained for City W07 Paved Surface Maintained/Maintained for City W08 Graveled Surface Maintained/Maintained for City Z01 Traffic Division Modeling Connectivity Use Only (The "W" series within the TYPE field were initially created for the City of Wildomar, but have had their application expanded to include any Centerline where the County maintains the road for a City - typically for a limited period after a City's incorporation. The "W" will continue as a convention to make it easy to distinguish such roads from roads normally maintained by the County, even though it is understood that the "W" will lose its initial association with the City of Wildomar over time.). GENPLANTYPE - General Plan Classification of the Road. Not corrected for the RCLIS 2003 updated at thsi time. Description of the codes found in the attribute "GENPLANTYPE" GENPLANTYPE SYMBOL DESCRIPTION 01 101 FREEWAY 02 201 EXPRESSWAY 03 301 URBAN ARTERIAL 04 304 URBAN ARTERIAL (PROPOSED) 05 401 ARTERIAL 06 404 ARTERIAL (PROPOSED) 07 501 MOUNTAIN ARTERIAL 08 504 MOUNTAIN ARTERIAL (PROPOSED) 09 13 MAJOR 10 16 MAJOR (PROPOSED) 11 21 SECONDARY 12 24 SECONDARY (PROPOSED) 13 801 SPECIFIC PLAN ROAD 14 804 SPECIFIC PLAN ROAD (PROPOSED) 15 25 SCENIC ROUTE 16 28 SCENIC ROUTE (PROPOSED) (PROPOSED) indicates that the road is part of the "General PLan Alignment" but does not currently exist as a legal centerline. This type of centerline will be stored in the CENTERLINEREF data set. DIRECTION - Represents the direction of traffic flow. Presently not supported. NAMEID - Numerical representation of the recorded street name. Unique STNAME and NAMEID values are tracked in the STNMS table. RDNUMBER - Used by the Transportation Department to identify county maintained roads. Used for accounting purposes. SEGNUMBER - Used in combination with the RDNUMBER to uniquely identify an individual centerline, segment, or length. No longer supported. FLAG - Indicates whether or not an arc will be used in a street network data set. Presently not used because there is no street network data set. L_F_ADD - The starting address for the left side of the street. L_T_ADD - The ending address for the left side of the street. R_F_ADD - The starting address for the right side of the street. R_T_ADD - The ending address for the right side of the street. PRE_DIR - The street direction prefix. Example: 'E' for east. STREET_NAME - The base legal street name of the centerline. Example: "MAIN". STREET_TYPE - The Street Name Type abbreviation. Example: 'ST' for street. Valid values for the STREET_TYPE field are: ' ' - ' ' (No Type is a space) AVE - AVENUE BLVD - BOULEVARD CIR - CIRCLE CT - COURT CV - COVE DR - DRIVE EXPY - EXPRESSWAY FWY - FREEWAY HWY - HIGHWAY LN - LANE LOOP - LOOP PATH - PATH PKWY - PARKWAY PL - PLACE PT - POINT RD - ROAD SQ - SQUARE ST- STREET TER - TERRACE TRL - TRAIL WALK - WALK WAY - WAY SUF_DIR - The street direction suffix. Example: "N' for north. TRACT - The tract map number in which the centerline can be found. MODIFIED - Modified Date CREATED - Created Date SOURCE_NOTES - References to legal documentation related to the Centerline found during research, including such things as recordation histroy, name change history, and acceptance for or termination of maintenance information, FULL_NAME - Name used to construct ROUTE_NAME field values. Used to detect changes in the STNAME value. AREA_PLAN_ABBREVIATION - Abbreviated Area Plan Name used to create ROUTE_NAME Valid values for AREA_PLAN_ABBREVIATION are: DESCN - Desert Center ECDES - East County/Desert ECVAP - Eastern Coachella Valley Plan ELSIN - Lake Elsinore EVALE - Eastvale HIGHG - Highgrove HVWIN - Harvest Valley/Winchester JURUP - Jurupa LAKEV - Lakeview/Nuevo LMATH - Lake Mathews MARCH - March MEADV - Mead Valley PASS - Pass Area PVERD - Palo Verde Valley RECHE - Reche Canyon REMAP - REMAP (Riverside Extended Mountain Area Plan) RIVER - Riverside/Corona/Norco SANJA - San Jacinto Valley SBCO - San Bernardino County SUNCI - Sun City/Menifee Valley SWAP - Southwest Area Plan TEMES - Temescal Valley WCVAP - Western Coachella Valley Area Plan SUBROUTE - Optional Identifier used to build ROUTE_NAME to separate branches or distiguish discontinuous portions of a street within an area plan that are unlikely to ever form a continuous route. ROUTE_NAME - Primary field used to construct a Linear Referencing derivative of the Centerlines layer. THis values is a component of ROUTE_ALT1 and ROUTE_ALT2 and is overriden by those fields when they have values. ROUTE_DIR1 - Used with ROUTE_NAME to build values for ROUTE_ALT1 when there is a value assigned. ROUTE_ALT1 - First Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Norh or East. ROUTE_DIR2 - Used with ROUTE_NAME to build values for ROUTE_ALT2 when there is a value assigned. ROUTE_ALT2 - Second Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Souh or West. BUILD_PRIORITY - Used to create Linear Referenced Routes. Sets the corner from which to build routes. Valuid values for BUILD_PRIORITY are: UL - Upper Left (Default) LL - Lower Left UR - Upper Right LR - Lower Right LINE_LINK - Geometric ID of Centerline arc. Made up of the From X/Y coordinate, the To X/Y coordinate and the Length. Used to detect geometric changes to an existing Centerline. CL_ID - Duplicate of OBJECTID. USed for detecting newly added segments to the network each week or to relate and join exported versions of CENTERLINES back to the original CENTERLINE feature class.
Definition Expression: N/A
Copyright Text: If you need additional information about CENTERLINES, please contact the Transportation Department at 951-955-6880 or on the web at http://www.tlma.co.riverside.ca.us/trans/office.shtm
Description: This data set of line features represent Riverside County's recorded street centerlines.This data set was designed to carry out functions of the Transportation department and is not a true street network layer. Centerlines do not have complete "connectivity" due to the fact that this layer is primarily roads that have been recorded but does not necessarily contain all roads. OBJECTID - Internal feature number. STNAME - Recorded name of the centerline. TYPE - Used to classify roads, primarily by surface type. Description of the codes found in the attribute "TYPE" TYPE DESCRIPTION C01 Federal Aid Interstate C02 State Highways C03 F.A.U. Maintained C04 F.A.S. Maintained C05 Paved Surface Maintained C06 Paved Surface (Traveled) C07 Graveled Surface Maintained C08 Graveled Surface (Traveled) C09 Dirt Surface Maintained C10 Dirt Surface (Traveled) C11 Accepted For Public Use C12 Non-County/Accepted for P.U. C13 Non-County road C14 Vacated C15 Abandon C16 Maintained F.A.U./Non-County C17 Maintained F.A.S./Non-County C18 Maintained Paved/Accepted C19 Maintained Paved/Non-County C20 Maintained Paved/Vacated C21 Maintained Gravel/Accepted C22 Maintained Gravel/Non-County C23 Maintained Gravel/Vacated C24 Maintained Dirt/Accepted C25 Maintained Dirt/Non-County C26 Maintained Dirt/Vacated C27 Accepted/Vacated C28 Maintained Under Contract C29 City Road C30 Paved Maintained/Dirt Maintained C31 Dedicated and Accepted/CFD Maintained W01 Maintained for City W02 Maintained for City/Non-County W03 Maintained for City/Non-County (Reversed) W04 Maintained for City/Accepted W05 F.A.U. Maintained/Maintained for City W06 Dirt Surface Maintained/Maintained for City W07 Paved Surface Maintained/Maintained for City W08 Graveled Surface Maintained/Maintained for City Z01 Traffic Division Modeling Connectivity Use Only (The "W" series within the TYPE field were initially created for the City of Wildomar, but have had their application expanded to include any Centerline where the County maintains the road for a City - typically for a limited period after a City's incorporation. The "W" will continue as a convention to make it easy to distinguish such roads from roads normally maintained by the County, even though it is understood that the "W" will lose its initial association with the City of Wildomar over time.). GENPLANTYPE - General Plan Classification of the Road. Not corrected for the RCLIS 2003 updated at thsi time. Description of the codes found in the attribute "GENPLANTYPE" GENPLANTYPE SYMBOL DESCRIPTION 01 101 FREEWAY 02 201 EXPRESSWAY 03 301 URBAN ARTERIAL 04 304 URBAN ARTERIAL (PROPOSED) 05 401 ARTERIAL 06 404 ARTERIAL (PROPOSED) 07 501 MOUNTAIN ARTERIAL 08 504 MOUNTAIN ARTERIAL (PROPOSED) 09 13 MAJOR 10 16 MAJOR (PROPOSED) 11 21 SECONDARY 12 24 SECONDARY (PROPOSED) 13 801 SPECIFIC PLAN ROAD 14 804 SPECIFIC PLAN ROAD (PROPOSED) 15 25 SCENIC ROUTE 16 28 SCENIC ROUTE (PROPOSED) (PROPOSED) indicates that the road is part of the "General PLan Alignment" but does not currently exist as a legal centerline. This type of centerline will be stored in the CENTERLINEREF data set. DIRECTION - Represents the direction of traffic flow. Presently not supported. NAMEID - Numerical representation of the recorded street name. Unique STNAME and NAMEID values are tracked in the STNMS table. RDNUMBER - Used by the Transportation Department to identify county maintained roads. Used for accounting purposes. SEGNUMBER - Used in combination with the RDNUMBER to uniquely identify an individual centerline, segment, or length. No longer supported. FLAG - Indicates whether or not an arc will be used in a street network data set. Presently not used because there is no street network data set. L_F_ADD - The starting address for the left side of the street. L_T_ADD - The ending address for the left side of the street. R_F_ADD - The starting address for the right side of the street. R_T_ADD - The ending address for the right side of the street. PRE_DIR - The street direction prefix. Example: 'E' for east. STREET_NAME - The base legal street name of the centerline. Example: "MAIN". STREET_TYPE - The Street Name Type abbreviation. Example: 'ST' for street. Valid values for the STREET_TYPE field are: ' ' - ' ' (No Type is a space) AVE - AVENUE BLVD - BOULEVARD CIR - CIRCLE CT - COURT CV - COVE DR - DRIVE EXPY - EXPRESSWAY FWY - FREEWAY HWY - HIGHWAY LN - LANE LOOP - LOOP PATH - PATH PKWY - PARKWAY PL - PLACE PT - POINT RD - ROAD SQ - SQUARE ST- STREET TER - TERRACE TRL - TRAIL WALK - WALK WAY - WAY SUF_DIR - The street direction suffix. Example: "N' for north. TRACT - The tract map number in which the centerline can be found. MODIFIED - Modified Date CREATED - Created Date SOURCE_NOTES - References to legal documentation related to the Centerline found during research, including such things as recordation histroy, name change history, and acceptance for or termination of maintenance information, FULL_NAME - Name used to construct ROUTE_NAME field values. Used to detect changes in the STNAME value. AREA_PLAN_ABBREVIATION - Abbreviated Area Plan Name used to create ROUTE_NAME Valid values for AREA_PLAN_ABBREVIATION are: DESCN - Desert Center ECDES - East County/Desert ECVAP - Eastern Coachella Valley Plan ELSIN - Lake Elsinore EVALE - Eastvale HIGHG - Highgrove HVWIN - Harvest Valley/Winchester JURUP - Jurupa LAKEV - Lakeview/Nuevo LMATH - Lake Mathews MARCH - March MEADV - Mead Valley PASS - Pass Area PVERD - Palo Verde Valley RECHE - Reche Canyon REMAP - REMAP (Riverside Extended Mountain Area Plan) RIVER - Riverside/Corona/Norco SANJA - San Jacinto Valley SBCO - San Bernardino County SUNCI - Sun City/Menifee Valley SWAP - Southwest Area Plan TEMES - Temescal Valley WCVAP - Western Coachella Valley Area Plan SUBROUTE - Optional Identifier used to build ROUTE_NAME to separate branches or distiguish discontinuous portions of a street within an area plan that are unlikely to ever form a continuous route. ROUTE_NAME - Primary field used to construct a Linear Referencing derivative of the Centerlines layer. THis values is a component of ROUTE_ALT1 and ROUTE_ALT2 and is overriden by those fields when they have values. ROUTE_DIR1 - Used with ROUTE_NAME to build values for ROUTE_ALT1 when there is a value assigned. ROUTE_ALT1 - First Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Norh or East. ROUTE_DIR2 - Used with ROUTE_NAME to build values for ROUTE_ALT2 when there is a value assigned. ROUTE_ALT2 - Second Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Souh or West. BUILD_PRIORITY - Used to create Linear Referenced Routes. Sets the corner from which to build routes. Valuid values for BUILD_PRIORITY are: UL - Upper Left (Default) LL - Lower Left UR - Upper Right LR - Lower Right LINE_LINK - Geometric ID of Centerline arc. Made up of the From X/Y coordinate, the To X/Y coordinate and the Length. Used to detect geometric changes to an existing Centerline. CL_ID - Duplicate of OBJECTID. USed for detecting newly added segments to the network each week or to relate and join exported versions of CENTERLINES back to the original CENTERLINE feature class.
Definition Expression: N/A
Copyright Text: If you need additional information about CENTERLINES, please contact the Transportation Department at 951-955-6880 or on the web at http://www.tlma.co.riverside.ca.us/trans/office.shtm
Description: This data set of line features represent Riverside County's recorded street centerlines.This data set was designed to carry out functions of the Transportation department and is not a true street network layer. Centerlines do not have complete "connectivity" due to the fact that this layer is primarily roads that have been recorded but does not necessarily contain all roads. OBJECTID - Internal feature number. STNAME - Recorded name of the centerline. TYPE - Used to classify roads, primarily by surface type. Description of the codes found in the attribute "TYPE" TYPE DESCRIPTION C01 Federal Aid Interstate C02 State Highways C03 F.A.U. Maintained C04 F.A.S. Maintained C05 Paved Surface Maintained C06 Paved Surface (Traveled) C07 Graveled Surface Maintained C08 Graveled Surface (Traveled) C09 Dirt Surface Maintained C10 Dirt Surface (Traveled) C11 Accepted For Public Use C12 Non-County/Accepted for P.U. C13 Non-County road C14 Vacated C15 Abandon C16 Maintained F.A.U./Non-County C17 Maintained F.A.S./Non-County C18 Maintained Paved/Accepted C19 Maintained Paved/Non-County C20 Maintained Paved/Vacated C21 Maintained Gravel/Accepted C22 Maintained Gravel/Non-County C23 Maintained Gravel/Vacated C24 Maintained Dirt/Accepted C25 Maintained Dirt/Non-County C26 Maintained Dirt/Vacated C27 Accepted/Vacated C28 Maintained Under Contract C29 City Road C30 Paved Maintained/Dirt Maintained C31 Dedicated and Accepted/CFD Maintained W01 Maintained for City W02 Maintained for City/Non-County W03 Maintained for City/Non-County (Reversed) W04 Maintained for City/Accepted W05 F.A.U. Maintained/Maintained for City W06 Dirt Surface Maintained/Maintained for City W07 Paved Surface Maintained/Maintained for City W08 Graveled Surface Maintained/Maintained for City Z01 Traffic Division Modeling Connectivity Use Only (The "W" series within the TYPE field were initially created for the City of Wildomar, but have had their application expanded to include any Centerline where the County maintains the road for a City - typically for a limited period after a City's incorporation. The "W" will continue as a convention to make it easy to distinguish such roads from roads normally maintained by the County, even though it is understood that the "W" will lose its initial association with the City of Wildomar over time.). GENPLANTYPE - General Plan Classification of the Road. Not corrected for the RCLIS 2003 updated at thsi time. Description of the codes found in the attribute "GENPLANTYPE" GENPLANTYPE SYMBOL DESCRIPTION 01 101 FREEWAY 02 201 EXPRESSWAY 03 301 URBAN ARTERIAL 04 304 URBAN ARTERIAL (PROPOSED) 05 401 ARTERIAL 06 404 ARTERIAL (PROPOSED) 07 501 MOUNTAIN ARTERIAL 08 504 MOUNTAIN ARTERIAL (PROPOSED) 09 13 MAJOR 10 16 MAJOR (PROPOSED) 11 21 SECONDARY 12 24 SECONDARY (PROPOSED) 13 801 SPECIFIC PLAN ROAD 14 804 SPECIFIC PLAN ROAD (PROPOSED) 15 25 SCENIC ROUTE 16 28 SCENIC ROUTE (PROPOSED) (PROPOSED) indicates that the road is part of the "General PLan Alignment" but does not currently exist as a legal centerline. This type of centerline will be stored in the CENTERLINEREF data set. DIRECTION - Represents the direction of traffic flow. Presently not supported. NAMEID - Numerical representation of the recorded street name. Unique STNAME and NAMEID values are tracked in the STNMS table. RDNUMBER - Used by the Transportation Department to identify county maintained roads. Used for accounting purposes. SEGNUMBER - Used in combination with the RDNUMBER to uniquely identify an individual centerline, segment, or length. No longer supported. FLAG - Indicates whether or not an arc will be used in a street network data set. Presently not used because there is no street network data set. L_F_ADD - The starting address for the left side of the street. L_T_ADD - The ending address for the left side of the street. R_F_ADD - The starting address for the right side of the street. R_T_ADD - The ending address for the right side of the street. PRE_DIR - The street direction prefix. Example: 'E' for east. STREET_NAME - The base legal street name of the centerline. Example: "MAIN". STREET_TYPE - The Street Name Type abbreviation. Example: 'ST' for street. Valid values for the STREET_TYPE field are: ' ' - ' ' (No Type is a space) AVE - AVENUE BLVD - BOULEVARD CIR - CIRCLE CT - COURT CV - COVE DR - DRIVE EXPY - EXPRESSWAY FWY - FREEWAY HWY - HIGHWAY LN - LANE LOOP - LOOP PATH - PATH PKWY - PARKWAY PL - PLACE PT - POINT RD - ROAD SQ - SQUARE ST- STREET TER - TERRACE TRL - TRAIL WALK - WALK WAY - WAY SUF_DIR - The street direction suffix. Example: "N' for north. TRACT - The tract map number in which the centerline can be found. MODIFIED - Modified Date CREATED - Created Date SOURCE_NOTES - References to legal documentation related to the Centerline found during research, including such things as recordation histroy, name change history, and acceptance for or termination of maintenance information, FULL_NAME - Name used to construct ROUTE_NAME field values. Used to detect changes in the STNAME value. AREA_PLAN_ABBREVIATION - Abbreviated Area Plan Name used to create ROUTE_NAME Valid values for AREA_PLAN_ABBREVIATION are: DESCN - Desert Center ECDES - East County/Desert ECVAP - Eastern Coachella Valley Plan ELSIN - Lake Elsinore EVALE - Eastvale HIGHG - Highgrove HVWIN - Harvest Valley/Winchester JURUP - Jurupa LAKEV - Lakeview/Nuevo LMATH - Lake Mathews MARCH - March MEADV - Mead Valley PASS - Pass Area PVERD - Palo Verde Valley RECHE - Reche Canyon REMAP - REMAP (Riverside Extended Mountain Area Plan) RIVER - Riverside/Corona/Norco SANJA - San Jacinto Valley SBCO - San Bernardino County SUNCI - Sun City/Menifee Valley SWAP - Southwest Area Plan TEMES - Temescal Valley WCVAP - Western Coachella Valley Area Plan SUBROUTE - Optional Identifier used to build ROUTE_NAME to separate branches or distiguish discontinuous portions of a street within an area plan that are unlikely to ever form a continuous route. ROUTE_NAME - Primary field used to construct a Linear Referencing derivative of the Centerlines layer. THis values is a component of ROUTE_ALT1 and ROUTE_ALT2 and is overriden by those fields when they have values. ROUTE_DIR1 - Used with ROUTE_NAME to build values for ROUTE_ALT1 when there is a value assigned. ROUTE_ALT1 - First Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Norh or East. ROUTE_DIR2 - Used with ROUTE_NAME to build values for ROUTE_ALT2 when there is a value assigned. ROUTE_ALT2 - Second Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Souh or West. BUILD_PRIORITY - Used to create Linear Referenced Routes. Sets the corner from which to build routes. Valuid values for BUILD_PRIORITY are: UL - Upper Left (Default) LL - Lower Left UR - Upper Right LR - Lower Right LINE_LINK - Geometric ID of Centerline arc. Made up of the From X/Y coordinate, the To X/Y coordinate and the Length. Used to detect geometric changes to an existing Centerline. CL_ID - Duplicate of OBJECTID. USed for detecting newly added segments to the network each week or to relate and join exported versions of CENTERLINES back to the original CENTERLINE feature class.
Definition Expression: N/A
Copyright Text: If you need additional information about CENTERLINES, please contact the Transportation Department at 951-955-6880 or on the web at http://www.tlma.co.riverside.ca.us/trans/office.shtm
Description: Approved General Plan Circulation Element as adopted by the Board of Supervisors, October 7, 2003. This dataset represents the ultimate right of way of Riverside County's Integrated Plan Circulation Element.
Definition Expression: N/A
Copyright Text: Transportation TLMA Riverside County
Description: Show area covered based on specification listed in Ordinance No. 655Zones based on radii listed in Ord No. 655 at 15 and 45 miles centered on Mt. Palomar Observatory.