Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN STYLE="font-weight:bold;">DEV </SPAN><SPAN>- The group layer supports the Land Use Services SalesForce Implementation.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>These 2021 Assignment Boundaries were created for the purpose of supporting and assigning Fire Hazard Abatement inspections in San Bernardino County in 2021. These boundaries were first used for production FHA field inspections starting in March of 2021. They differ from prior years' assignment boundaries because - in 2021 - all "Valley" assignment areas were re-drawn to follow assessor book boundaries to aid in the FHA team's warrant process.</SPAN><SPAN /><SPAN /></P><P><SPAN /></P><P><SPAN>Valley assignment areas were re-drawn by Swarna Keshavan, reviewed/adjusted by Lindsay King, and finally reviewed and approved by Andres Diaz.</SPAN></P><P><SPAN /><SPAN /><SPAN /></P><P><SPAN>- It was updated on March 13, 2021 to fix an area of overlap containing about 20 parcels between the 1200-SBOVL and 1200-H1 areas.</SPAN></P><P><SPAN>- It was updated on March 22, 2021 to add a new field: WITHIN_FHA, with the value calculated to "Yes" for all records. This change was made to support the use of this layer in a SalesForce application built by the vendor Incapsulate.</SPAN></P><P><SPAN>- It was updated on June 16, 2021 to reflect the change in the City of Fontana boundary after an annexation by the city. As a result, a portion of the 0239-DE2 assignment area was removed, and the remaining areas were split into 0239-DE2 and 0239-DE3.</SPAN></P><P><SPAN /></P><P><SPAN>This feature class is publised as a hosted feature services on ArcGIS Online as item id:ab7a3bab6c60406d83d75a4699b98641.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><TABLE><TBODY><TR><TD><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>FIELD NAME</SPAN></SPAN></P></TD><TD><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Comment</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>OBJECTID</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Unique Identifier</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>TEXT2</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN>The Current Community Plan (if available)/Zoning- minimum parcel size for the polygon</SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Shape_Leng</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Shape Length</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Shape_Area</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Shape Area</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>GPA_CYCLE</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Intended for amendment date to the zoning of the polygon</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>ORDINANCE</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Intended for the ordinance number for the change in zoning for the polygon</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>QUAD</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Intended for the Quad sheet reference, to identify the zoning's within the quad sheet boundary for the hard copy print outs.</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>TEXT1</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>The Previous Zoning for the polygon</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>TEXT3</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>City/Town label for the polygon</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>CommunityPlan</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Intended for the Community plan area label for the polygon</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>LUD</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Because TEXT2 was a breviation of the community plan area and the zoning, for some reason this field was created to show just the zoning.</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>MinParcelSize</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Intended to identify the minimum lot size for a specific zoning type.</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>City</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>City/Town label for the polygon</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Web1</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>This was intended to translate the acronyms of TEXT 2. I have a python scrypt that I run when updating the online zoning map that auto calculates this field each time I run a update which is why it is showing nothing at the moment.</SPAN></SPAN></P></TD></TR></TBODY></TABLE><P><SPAN /></P></DIV></DIV></DIV>
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: 8 Font Family: Times New Roman 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: 10 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 0.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [CITY_NAME] Use Coded Values: false Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 36 Font Family: Candara Font Style: normal Font Weight: normal Font Decoration: none