Description: In early November, 2017 we were tasked with analysing how many mobile homes there are throughout the county by unincorporated area, and Supervisorial District. It was also requested to have Assessor data and zoning as well. The eGIS LAND_TYPES layer was used in combination with a downloaded table of addresses from the State of CA Housing and Community Development (website is here). There were significant errors in the LAND_TYPES layer and we used this opportunity to update the polygon boundaries and names using these geocoded points from the state (who ultimately got this info from various fire departments). The layers are listed below, and we informed eGIS of our update efforts so that the LAND_TYPES layer could be updated.DRP HelpDesk Ticket reference #334373Downloaded spreadhseet into support folder, and converted to a File GDB. Used CAMS and Google geocoders, and some manual updates to move points into LAND TYPES polygons. Some are marked as "to remove" since they couldn't be found, or they no longer exist. (Created 11/6/17)Land Types data, queried out from eGIS for Mobile Homes. Layer 1 was used to QC this layer. (Created 11/6/17)Spatial Join between layers 1 & 2. There are some cases where a polygon existed, but no point was represented from the geocoded points (JOIN_FID = -1). The NAME and DESCRIPTIO fields were updated with what was in the joined Geocoded points layer. SOURCE and DATE_UPDATED was also updated. (Created 11/6/17 - updated on 11/9/17 and exported to LAND_TYPES eGIS layer on that day)Clipped Layer 3 for Unincorporated. (Created 11/6/17)
Description: In early November, 2017 we were tasked with analysing how many mobile homes there are throughout the county by unincorporated area, and Supervisorial District. It was also requested to have Assessor data and zoning as well. The eGIS LAND_TYPES layer was used in combination with a downloaded table of addresses from the State of CA Housing and Community Development (website is here). There were significant errors in the LAND_TYPES layer and we used this opportunity to update the polygon boundaries and names using these geocoded points from the state (who ultimately got this info from various fire departments). The layers are listed below, and we informed eGIS of our update efforts so that the LAND_TYPES layer could be updated.DRP HelpDesk Ticket reference #334373Downloaded spreadhseet into support folder, and converted to a File GDB. Used CAMS and Google geocoders, and some manual updates to move points into LAND TYPES polygons. Some are marked as "to remove" since they couldn't be found, or they no longer exist. (Created 11/6/17)Land Types data, queried out from eGIS for Mobile Homes. Layer 1 was used to QC this layer. (Created 11/6/17)Spatial Join between layers 1 & 2. There are some cases where a polygon existed, but no point was represented from the geocoded points (JOIN_FID = -1). The NAME and DESCRIPTIO fields were updated with what was in the joined Geocoded points layer. SOURCE and DATE_UPDATED was also updated. (Created 11/6/17 - updated on 11/9/17 and exported to LAND_TYPES eGIS layer on that day)Clipped Layer 3 for Unincorporated. (Created 11/6/17)
Description: This is the LAHSA Homeless Counts data for 2018 and it was joined to the Census Tracts* GIS layer. The Countywide Statistical Areas were determined for each Census Tract by taking the centroid of each tract and doing a spatial join with the Countywide Statistical Areas. As a result, there are some tracts that may have a city name, but actually may be in some unincorporated territory (and vice versa). This problem exists because Census Tract boundaries don't always conform fully with city / unincorporated area boundaries. The percentage of city vs. unin for each tract is given in the "PCT_" fields. Cities of Glendale, Pasadena, and Long Beach did not have data available at the tract level, and as of 3/12/19, those areas are blank.Relates to HelpDesk tickets #583612 & 141048* NOTE: a couple of the census tracts had been updated in 2012 near Calabasas, so this had to be taken into account...the LAHSA data had previous Census Tracts - see metadata for eGIS Repository layer on that.UPDATE HISTORY:1/10/19 - updated to append historic counts (2016 - 2017). It was intended to also include 2015 counts, however, LAHSA used 2000 Census Tracts for that allocation - resulting in 599 tracts not joining. Was not used.3/12/13 - brought in to SDE.
Description: PRC 4201 - 4204 and Govt. Code 51175-89 direct the California Department of Forestry and Fire Protection (CAL FIRE) to map areas of significant fire hazards based on fuels, terrain, weather, and other relevant factors. These zones, referred to as Fire Hazard Severity Zones (FHSZ), define the application of various mitigation strategies to reduce risk associated with wildland fires. CAL FIRE is remapping Fire Hazard Severity Zones (FHSZ) for State Responsibility Areas (SRA) and Very High Fire Hazard Severity Zones (VHFHSZ) recommendations in Local Responsibility Areas (LRA) to provide updated map zones, based on new data, science, and technology. This specific dataset provides FHSZs within SRA lands only, and represents the proposed zones, subject to changes based on local hearings. A subsequent dataset release will provide the actual adopted zones. Maps of the proposed zones in SRA are available at: http://frap.cdf.ca.gov/projects/hazard/fhz.html More information about the project can be found at: http://frap.cdf.ca.gov/projects/hazard/hazard.htmlUPDATED - 3/5/15 by taking out any reference to Responsibility Area - that now is in a seperate, more updated layer. Per. Alfie Blanch, this layer should not have any reference to Federal, State, or Local Responsibility Areas. Also, internal slivers were filled in by doing a 'Gap topology analysis.'
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.
Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [HAZ_CLASS] CONCAT " Fire Hazard" Use Coded Values: true Symbol:
Color: [255, 255, 255, 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
Min. Scale: 40000.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [HAZ_CLASS] CONCAT " Fire Hazard" Use Coded Values: true Symbol:
Color: [255, 255, 255, 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
Min. Scale: 40000.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [HAZ_CLASS] CONCAT " Fire Hazard" Use Coded Values: true Symbol:
Color: [255, 255, 255, 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