Description: Address point feature class is actively undergoing edits and is updated on a daily basis. It follows the CalOES schema and has additional fields as required by Solano County, Geographic Technologies Group (GTG) (data stewards), and Bradshaw Consulting Services (BCS) (data host).Fields:Site_NGUID - Site NENA Globally Unique IDAPN - APNFullAddress - Full Address FullAddr_Label_Abbrv - Abbreviated LabelFullAddr_Label - Full Address LabelGTG_Flag - GTG Flag field to categorize anomaliesGTG_Notes - GTG Notes field to describe anomalyAddNum_Pre - Address Number PrefixAdd_Number - Address NumberAddNum_Suf - Address Number SuffixSt_PreMod - Street Name Pre ModifierSt_PreDir - Street Name Pre DirectionalSt_PreTyp - Street Name Pre TypeSt_PreSep - Street Name Pre Type SeparatorSt_Name - Street NameSt_PosType - Street Name Post TypeSt_PosDir - Street Name Post DirectionalSt_PosMod - Street Name Post ModifierDiscrpAgID - Discrepancy Agency IDDateUpdate - Date UpdateEffective - Effective DateExpire - Expiration DateCountry - CountryState - StateCounty - CountyAddDataURI - Additional Data URIInc_Muni - Incorporated MunicipalityUninc_Comm - Unincorporated CommunityNbrhd_Comm - Neighborhood CommunityLSt_PreDir - Legacy Street Pre DirectionalLSt_Name - Legacy Street NameLSt_Type - Legacy Street Post TypeLSt_PosDir - Legacy Street Post DirectionalESN - ESNMSAGComm - MSAG Community NamePost_Comm - Postal Community NamePost_Code - Postal CodePost_Code4 - ZIP Plus 4Building - BuildingFloor - FloorUnit - UnitRoom - RoomSeat - SeatAddtl_Loc - Additional Location InformationLandmkName - Complete Landmark NameMile_Post - Mile PostPlace_Type - Place TypePlacement - Placement MethodLong - LongitudeLat - LatitudeElev - ElevationGC_Exception - GC QC Exception Codecreated_user - Editor tracking (who created the data)created_date - Editor tracking (when was the data created)last_edited_user - Editor tracking (who last edited the data)last_edited_date - Editor tracking (when was the data last edited)GlobalID - Unique Global IDADDRESS_ID - BCS Address IDSEGMENT_ID - BCS Segment ID associated with address pointNAME_ID - BCS Name IDSIDE - BCS Side of segment the address point falls alongANOMALY - BCS Anomaly trackerUNIT_NUM - BCS Unit Number (no description)UNIT_TYPE - BCS Unit Description (no number)
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: This data is maintained by Geographic Technologies Group under the guidance of Solano County.
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: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: Road centerline feature class is actively undergoing edits and is updated nightly. It is actively undergoing edits and is updated on a monthly basis. It follows the CalOES schema and has additional fields as required by Solano County, Geographic Technologies Group (GTG) (data stewards), and Bradshaw Consulting Services (BCS) (data host).Note: "Updated" field in Item Description may not be accurate.Fields:RCL_NGUID - Road Centerline NENA Globally Unique IDFullAddress - Full Address FullAddr_Label_Abbrv - Abbreviated LabelFullAddr_Label - Full Address LabelRoadOwner - Road OwnerRoadClass - Road ClassGTG_Flag - GTG Flag field to categorize anomaliesGTG_Notes - GTG Notes field to describe anomalyAdNumPre_L - Left Address Number PrefixAdNumPre_R - Right Address Number PrefixFromAddr_L - Left From AddressToAddr_L - Left To AddressFromAddr_R - Right From AddressToAddr_R - Right To AddressParity_L - Parity LeftParity_R - Parity RightSt_PreMod - Street Name Pre ModifierSt_PreDir - Street Name Pre DirectionalSt_PreTyp - Street Name Pre TypeSt_PreSep - Street Name Type SeparatorSt_Name - Street NameSt_PosType - Street Name Post TypeSt_PosDir - Street Name Post DirectionalSt_PosMod - Street Name Post ModifierLSt_PreDir - Legacy Street Name Pre DirectionalLSt_Name - Legacy Street NameLSt_Type - Legacy Street Name TypeLSt_PosDir - Legacy Street Name Post DirectionalESN_L - ESN LeftESN_R - ESN RightMSAGComm_L - MSAG Community Name LeftMSAGComm_R - MSAG Community Name RightCountry_L - Country LeftCountry_R - Country RightState_L - State LeftState_R - State RightCounty_L - County LeftCounty_R - County RightIncMuni_L - Incorporated Municipality LeftIncMuni_R - Incorporated Municipality RightUnincCom_L - Unincorporated Community LeftUnincCom_R - Unincorporated Community RightNbrhdCom_L - Neighborhood Community LeftNbrhdCom_R - Neighborhood Community RightPostCode_L - Postal Code LeftPostCode_R - Postal Code RightPostComm_L - Postal Community Name LeftPostComm_R - Postal Community Name RightOneWay - One-WaySpeedLimit - Speed LimitValid_L - Validation LeftValid_R - Validation RightDiscrpAgID - Discrepancy Agency IDDateUpdate - Date UpdatedEffective - Effective DateExpire - Expiration DateGC_Exception - GC QC Exception Codecreated_user - Editor tracking (who created the data)created_date - Editor tracking (when was the data created)last_edited_user - Editor tracking (who last edited the data)last_edited_date - Editor tracking (when was the data last edited)GlobalID - Unique Global IDSEGMENT_ID - BCS Segment IDNAME_ID - BCS Name IDANOMALY - BCS Anomaly trackerfromElev - BCS from elevation measuretoElev - BCS to elevation measurefromToCost - BCS from-to cost measuretoFromCost - BCS to-from cost measure
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: This data is maintained by Geographic Technologies Group under the guidance of Solano County.
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: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 10000.0 Max. Scale: 0.0 Label Placement: esriServerLinePlacementCenterAlong Label Expression: N/A Use Coded Values: true Symbol:
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: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 30000.0 Max. Scale: 10000.0 Label Placement: esriServerLinePlacementCenterAlong Label Expression: N/A Use Coded Values: true Symbol:
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: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
postcomm_l
(
type: esriFieldTypeString, alias: Postal Community Name Left, length: 40
, Coded Values:
[Benicia: Benicia]
, [Dixon: Dixon]
, [Fairfield: Fairfield]
, ...4 more...
)
postcomm_r
(
type: esriFieldTypeString, alias: Postal Community Name Right, length: 40
, Coded Values:
[Benicia: Benicia]
, [Dixon: Dixon]
, [Fairfield: Fairfield]
, ...4 more...
)
oneway
(
type: esriFieldTypeString, alias: One-Way, length: 2
, Coded Values:
[TF: One-way traveling from TO node to FROM node]
, [B: Travel in both directions allowed]
, [FT: One-way traveling from FROM node to TO node]
)
Description: Parcel feature class was created on 9/4/24 from stakeholder feedback on Parcels_REGIS.Fields:lowparceli - APN Number for lot of multiunit dwellingsparcelid- APN Numberfloororder - Building Floorc_user - Created Userc_date - Created Datelast_edit - Last Edited Userlast_edate - Last Edited Dategtg_review - Notes on Parcel Reviewgtg_notes - Notes from GTG Teamcountynote - Solano County GIS Staff Notesdata_note - Data Notestaxmapno - Number of the tax map associated with the parcelgis_acre - Measured Acreage Value Xcentroid - X Centroid Value Ycentroid - Y Centroid Value taxmaplink - Link to Tax Map propurl - Link to Property Characteristics asmtnum – PIN rollyear - Current Tax Roll Year acres - Recorded Acreage Value lotsize – Lot Size Square Footage usecode - Use Code use_desc - Use Code Description subdiv – Subdivision Name qclass – Quality Class yrblt - Year Built status – PIN Status valland - Land Value valimp – Improvement Value valtv – Trees & Vine Value valfme – Fixed Machinery & Equipment Value valpp – Personal Property Value valpen – Penalty Value assessee – Owner of Recordaddr1 – Owner address 1addr2 – Owner address 2addr3 – Owner address 3addr4 – Owner address 4addr5 – Owner address 5city - Owner address City Name state - Owner address State Name addrzip – Owner address Zip Code situs – Site Addresssitenum – Site Number siteroad – Site Street Name p_address – Site Number & Street sitecity – Site City Name unitbldg – Site Unit/Building wa – Williamson Act (YS/NO) wa_status – Williamson Act Status Code wacontno – Williamson Act Contract Number wa_prime – Total Prime Acreage noprimacre – Total Nonprime Acreage exacre – Total Excluded Acreage p_create - Parcel Creation Date p_inactive - Parcel Inactivation Date firs_floor - First Floor Area sec_floor - Second Floor Area thir_floor - Third Area other_area - Other Area garage - Garage Area total_area - Total Area stories - Number of Stories bedroom - Number of Bedrooms bathroom - Number of Bathrooms dining - Dining Room (Space, YS, NO) family - Family Room (Space, YS, NO) other_room - Number of Other Rooms utility - Utility Room (Space, YS, NO) rooms - Total Rooms Countfireplc – Fireplace (Space, YS, NO, 1, 2…) hvac - HVAC Code pool – Swimming Pool (Space, YS, NO) solar - Solar (Space, YS, NO) tac - TAG tac_city – TAG City Name govt_owned – Govt Owned hotype – Home Owner Exemption Type fund_fire – Fire District desc_fire - Fire District Description f_school - School District d_school – School District Description fund_water – Water District desc_water – Water District Description f_air_board – Air Board District d_air_board - Air Board District Description f_soil_cons - Soil Conservation District d_soil_cons – Soil Conservation District Description acre_diff - Acreage Difference
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: This data is maintained by Geographic Technologies Group under the guidance of Solano County. All parcels are based on the Solano County Tax Maps. If there are discrepancies, Tax Map is considered authority. However, Tax Map is not a legal document.
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: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: Fire Hazard Severity Zone (FHSZ) classifications and map, as mandated by California law and implemented by the State Fire Marshal. The latest FHSZ map, issued on September 29, 2023, was formally adopted on January 31, 2024, and became effective on April 1, 2024. It delineates lands within state responsibility areas into three fire hazard levels: moderate, high, and very high. These designations are determined based on an array of factors such as fuel loading, slope, fire weather, and wind patterns that contribute to wildfire spread.Developed through a science-based model, the FHSZ assessments consider fire history, potential fuel sources, predicted fire behavior, terrain, and typical fire weather conditions, aiming for a predictive outlook over 30 to 50 years. Unlike risk evaluations, these hazard classifications do not account for mitigative actions like home hardening, wildfire history, or fuel reduction efforts but focus on inherent physical conditions that influence fire likelihood and potential intensity.The FHSZs serve several purposes: they are used to designate areas where California’s wildland urban interface building codes apply to new buildings; they can be a factor in real estate disclosure; and local governments consider fire hazard severity in the safety elements of their general plans. Moderate, high, and very high FHSZs are found in areas where the State has financial responsibility for fire protection and prevention (SRA). Only very high FHSZs are found in Local Responsibility Areas (LRAs).Regulatory adherence mandates that this classification system and its accompanying maps follow the procedures set by the Administrative Procedures Act, transitioning from Title 14, Section 1280.01 to Title 19, Section 2201 of the California Code of Regulations. This shift signifies an administrative update without altering the geographic portrayal of FHSZs. The updated regulations are integral to enhancing wildfire preparedness and mitigation strategies across California, rooted in rigorous evaluation and a comprehensive understanding of fire behavior and hazards.Fields:sra - SRA: Classifications for State Responsibility Area (SRA)fhsz - FHSZ: Classifications from Moderate, High, Very High fhsz_description - FHSZ_Description matching classification as 1, 2, 3Data Uploaded 4/15/2024, DMachado, Solano County Department of Information Technology
Description: <div style="text-align:Left;"> <div> <div> <p><span>These data were significantly updated in coordination with LAFCO in 2021. Changes to the city boundary have significant impact on many other data layers which at this time may not have been adjusted to match the new city boundary.</span></p> <p><span>Data Quality</span></p> <p><span>These data reflect an approximation of the city boundary and any dispute over the actual boundary must be resolved by looking at the original source documentation. Only a Professional Land Surveyor should be relied upon for final determination of any specific boundary. There are two known areas which are disputed. One is the boundary along Ramsey Road between Fairfield and unincorporated Solano County. The second area is south of Illinois Street in Fairfield.</span></p> <table border="1"> <tbody><tr> <th>Field</th> <th>Description</th> </tr> <tr> <td>Name</td> <td>City Name</td> </tr> <tr> <td>Agency</td> <td>Proper City Name</td> </tr> </tbody></table> <p><span>Date last updated: 05/22/2024 - Resolved geometry at City of Vallejo and City of Benicia northwestern edge</span></p> <p><span>Uploaded to Solano County GIS Portal 05/22/2024 by GIS Services Team, Solano County Department of Information Technology</span></p> <p><span></span></p> </div> </div></div>
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: Data is owned by LAFCO for Solano County. Changes, edits, and revisions to the same are made by Solano County Department of Information Technology GIS Team by LAFCO authorization.
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: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: The Solano County Department of Resource Management, Environmental Health Services Division is the Certified Unified Program Agency (CUPA) for all cities and unincorporated areas within Solano County. The legislation that developed the CUPA was created by the State Legislature to minimize the number of inspections and different fees for businesses that use hazardous materials and dispose of hazardous wastes. The laws and regulations pertaining to the use and disposal of hazardous materials and hazardous wastes are in the California Health and Safety Code, Chapters 6.5, 6.67, 6.7, 6.75, 6.95, & 6.11 and the California Code of Regulations, Title 19, Title 22, Title 23, & Title 27 found in Health and Safety Code and California Code of Regulations. The public can review information on all the facilities subject to these programs within Solano County and throughout California at CalEPA Regulated Site Portal. Data received 04/21/2023 by Christopher Ambrose, Supervising Hazardous Materials Specialist, Solano County Department of Resource Management Data updated 04/27/2023 bconrad, Department of Information Technology
Description: The Solano County Local Enforcement Agency (LEA) is responsible for enforcement of solid waste laws and regulations in Solano County. LEA reports to CalRecycle for issues regarding solid waste.Created for Environmental Health division of Resource Management by DoIT, September 2024
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: Data was created via a collaboration between the Department of Information Technology (DoIT) and the Department of Resource Management. Approval criteria was set by Jeffrey Bell in the RM department.
Local Enforcement Agency (LEA) Details: Solano County (48-AA)
Solano County
Department of Resource Management 675 Texas St Ste 5500
Fairfield, CA 94533
Phone
(707) 784-6765
FAX
(707) 784-4805
Certifications
A, B, C, D
Source: https://www2.calrecycle.ca.gov/SolidWaste/LEA/Details/58
Description: The Solano County Board of Supervisors consists of five supervisorial districts. District 1 consists of approximately one half of the City of Vallejo in the northern section. District 2 includes the City of Benicia, approximately one half of the City of Vallejo in the southern section, Cordelia, and Green Valley. District 3 is made up of portions of the City of Suisun and a large portion of the City of Fairfield. District 4 includes a large part of the City of Vacaville, the City of Dixon and the City of Rio Vista. District 5 includes a portion of the eastern section of the City of Suisun, the northern section of Fairfield, a portion of the eastern part of the City of Vacaville, the City of Rio Vista, and the Elmira area.
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: 18 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: ***** BACKGROUND *****In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata.A dataset named cnty24k97_1 was made available (approximately 2004) through the California Department of Forestry and Fire Protection - Fire and Resource Assessment Program (CDF - FRAP) and the California Spatial Information Library (CaSIL). In late 2006, the Department of Fish and Game (DFG) reviewed cnty24k97_1. Comparisons were made to a high-quality 100K dataset (co100a/county100k from the former Teale Data Center GIS Solutions Group) and legal boundary descriptions from ( http://www.leginfo.ca.gov ). The cnty24k97_1 dataset was missing Anacapa and Santa Barbara islands. DFG added the missing islands using previously-digitized coastline data (coastn27 of State Lands Commission origin), corrected a few county boundaries, built region topology, added additional attributes, and renamed the dataset to county24k.In 2007, the California Mapping Coordinating Committee (CMCC) requested that the California Department of Forestry and Fire Protection (CAL FIRE) resume stewardship of the statewide county boundaries data. CAL FIRE adopted the changes made by DFG and collected additional suggestions for the county data from DFG, DOC, and local government agencies. CAL FIRE incorporated these suggestions into the latest revision, which has was renamed cnty24k09_1.***** THIS VERSION*****This version of the county dataset was created as a result of an effort to improve the coastal linework. It uses the previous interior linework from the cnty24k13_1 data, but replaces the coastal linework (including islands and inlets) based on NOAA's ERMA coastal dataset (which used NAIP 2010). In addition to the improved linework, additional coding was added to differentiate inlets and bays, islands, and manmade structures such as piers and breakers. Note that some of this coding may not be featured in this specific dataset.This dataset is one of several available datasets that were created as a group designed to work in topological sync with each other. These "paired" datasets include a full county dataset (cnty15_1_full), a basic state dataset (state15_1), an ocean dataset (ocean15_1), and country/state datasets (both full and neighbor-only - cntrystate15_1_full and cntrystate15_1_neighbor, respectively). Further details about these paired datasets can be found in their respective metadata.This specific dataset represents the basic (ie simplified) county dataset without the extra coding that can be found in the "full" dataset. In this dataset, all bays (plus bay islands and constructed features) are merged into the mainland, and coastal features (such as islands and constructed features) are not included.In November 2015, the dataset was adjusted to include a change in the Yuba-Placer county boundary from 2010 that was not yet included in the 14_1 version of the dataset (ord No 5546-B). This change constitutes the diffrence between the 15_1 and 14_1 versions of this dataset.Last Edited by DMachado per Tax Map 014701. Published by DMachado on 06/10/24
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: U.S. Bureau of Reclamation, California Department of Conservation, California Department of Fish and Game, California Department of Forestry and Fire Protection, National Oceanic and Atmospheric Administration, Solano DoIT
Description: The County has adopted community standards in the form of the General Plan and Zoning Ordinance to promote the safety, welfare and orderly development of the County. The construction of any building, and the occupancy or use of that building, must be designed and constructed to meet these community standards. These standards vary depending on what is proposed and where the building is located.Zoning districts are established to promote compatible patterns of land use within the zoning jurisdiction of the City and to establish site development regulations and performance standards appropriate to the purposes of each district and their respective uses. The Zoning Maps assign each piece of property to a "zone" which specifies how the land may be used. The Zoning Ordinance establishes uses allowed in each zone and standards that must be met within each zone. If a landowner proposes a use that is not allowed in that zone, a change of zone, or a Rezone, must occur. A Rezone also requires a public hearing and County Board of Supervisors' approval. Once a Rezone is approved, it remains with the land until any future rezones are approved.Purpose of Zoning Plan:A zoning plan is adopted to provide a precise plan for residential, commercial, industrial, agricultural, public, and other land uses in the County in order to:A. Protect the established character and social and economic values of agricultural, residential, commercial, industrial, recreational, and other areas within the County which have developed in a healthy and orderly manner;B. Encourage beneficial development of those areas which have grown with conflicting or uneconomic patterns of use; andC. Assist in providing a definite and publicly approved plan of development to guide, control and stimulate the future growth of the County in accordance with the need of the County and in proper relation to other land use areas in the region.More information is available at https://www.solanocounty.com/depts/rm/planning/faq.asp or contact County of Solano, Department of Resource Management Planning Services Division at 707-784-6765.Data layer updated 12/28/2023 by DMachado. Update included A-20 zoned parcels adjacent to TAFB. Updated data layer includes LAFCO Resolution No. 2023-15, 2023-16, 2023-17 for City of FairfieldData layer uploaded 02/24/2024 by BConrad. Updated data layer includes BOS Ordinance NO. 2024: AN ORDINANCE AMENDING CHAPTER 28, SECTION 28.11 ZONING MAP NO. 12-N, OF THE SOLANO COUNTY CODE TO REZONE A 24.42-ACRE SITE LOCATED AT 2316 ROCKVILLE ROAD (APN:0027-200-150) FROM AGRICULTURE TOURIST CENTER (ATC), NEIGHBORHOOD COMMERCIAL, AND SUISUN VALLEY AGRICULTURE (A-SV-20) TO ATC AND A-SV-20 (Solano Landing Z-22-04)Data layer updated and uploaded 06/24/24 by DMachado to account for Policy Plan and Travis Reserve Overlay
Description: The General Plan is the guide for both land development and conservation in the unincorporated portions of the county. It contains the policy framework necessary to fulfill the community’s vision for Solano County in 2030; a sustainable place with a thriving environment and an economy that maintains social equity. This theme of sustainability is carried throughout the plan in its goals, policies, and programs. The General Plan is the guide for both development and conservation within the unincorporated county through 2030. Under California law, every county and city must adopt a comprehensive, long-term general plan to direct physical development within its jurisdiction. General plans serve as a blueprint for future development and conservation efforts, with goals and policies providing a solid basis for future decisions related to land use, development, and conservation. The General Plan is the primary document used by the County to regulate land use under California law. Zoning and development codes, specific plans, and individual public and private development proposals must be consistent with General Plan goals, policies, and standards. More information is available at https://www.solanocounty.com/depts/rm/planning/faq.asp or contact County of Solano, Department of Resource Management Planning Services Division at 707-784-6765.Updated 04/02/2024, BConrad, Solano County Department of Information TechnologyUpdated 06/24/24, DMachado to account for Overlays within the service
Description: This feature class depicts the boundaries of the Solano County Cemetery Districts and their Proposed Spheres of Influence. Solano County Has four public cemetery districts that operate nine cemeteries. The County Board of Supervisors appoints a Board of Trustees to govern each district.Cemetery Districts:Winters Joint Cemetery DistrictSilveyville Cemetery DistrictVacaville/Elmira Cemetery DistrictSolano Cemetery DistrictRio Vista-Montezuma CemeteryCemetery Districts Spheres of Influence:Winters Cemetery District Sphere of InfluenceSolano Cemetery District Sphere of InfluenceVacaville/Elmira Cemetery District Sphere of InfluenceData source: Solano LAFCO - Local Agency Formation Commissionhttp://www.solanolafco.com/maps.htmData accessed: 04/2024Last updated in Solano County Portal: 2023Date published in source: 2010Uploaded to Solano County GIS Portal, GIS Services Team, Solano County Department of Information Technology. Updated BConrad, 05/30/2024 based on annexation documentation received from LAFCO 04/03/2024.Fields - Alias - DescriptionCemetery_d - Districts - Name of boundary areaacres -- calculated acreage for the polygonsqmi -- calculated acreage for the polygon
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: Solano LAFCO - Local Agency Formation Commission
https://www.solanolafco.com/
Description: This dataset was created based upon a shapefile from an unknown source. Between 2001 and 2007, an effort was made to correct the dataset although it was not complete. Property boundaries with one shared line (autocomplete polygon) were updated based on parcel maps from the Solano County Assessor-Recorder’s Office that were available to Suisun RCD staff at the time. If some or all of the Assessor’s property maps were missing for a property, then boundaries may not be correct. There was no attempt to correct properties without shared line boundaries (not corrected with autocomplete polygon). Boundaries and club names are based upon the last update in March 2007 and thus may be out of date (with the exception of Overlook as stated below). In August 2015, the boundary of 635 Blacklock was updated based upon DWR Real Estate Branch’s assessment that the tidal berms are DWR property. Properties 604, 606, and 605 (only along Arnold Slough) were modified with the assumption that the tidal berms are within the respective ownerships. All bolygons were edited based upon the 2012 mosaic aerial for all of Suisun Marsh. The fields for Status_1 and restoration status were also updated.In April 2016, the boundary of property 322 was updated based upon Wetlands and Water Resources, Inc. boundary data within the Draft Restoration Plan dated March 2013. Property boundaries were also updated for 329 and 330 using the maps in the appraisals. All three property boundaries were also interpreted using the 2012 Suisun Marsh mosaic aerial. The 322 boundary was surveyed by DWR. That data has an incompatible projection and coordinate system and was not incorporated into this dataset due to time constraints. The 322 DWR survey data can be requested from the Suisun Resource Conservation District and is saved at \\nasdes\marsh3\data_GIS\Overlook_club\WWR. In June 2023, this dataset was topologically corrected to remove remaining overlaps and incidental gaps by Suisun Resource Conservation District staff.Geometry calculations are based upon NAD1983 UTM Zone 10N (original projection).For more information on this dataset, please contact Kristin Garrison at the Department of Water Resources and/or the Suisun Resource Conservation District.Shapefile was given to the Solano County Department of Information Technology on 5/29/2024. This shapefile was reprojected into NAD1983 California State Plane (2011) Zone II US Feet and converted into a feature class within the Boundaries_LAFCO feature dataset in June 2024. Fields:FID (Object ID)Shape (Geometry)ID (Long)NAME (Text)Type (Text)Ownership (Text)Label (Text)Notes (Text)Acres (Long)Shape_Leng (Double)Shape_Area (Double).
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: Suisun Resource Conservation District
Website: https://suisunrcd.org/
Address: 2544 Grizzly Island Road, Suisun City, CA 94585
Phone: 707-425-9302
Description: This dataset represents the legal boundary of the Solano Resource Conservation District. Data was originally created in WGS 1984 Web Mercator (auxiliary sphere); however, it has been reprojected into NAD 1983 (2011) California State Plane Zone II by Solano County GIS.Dataset created on 5/13/2022 by Solano Resource Conservation District.Dataset received by Solano County DoIT GIS on 5/29/2024.
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: Solano Resource Conservation District
Website: https://www.solanorcd.org/
Address: 1170 N Lincoln St., Ste 110, Dixon, CA 95620
Phone: 707-678-1655 ext. 101
Description: This dataset represents the legal boundary of the Dixon Resource Conservation District. Dixon RCD is located within both Solano and Yolo County. Data was originally created in NAD 1983 UTM Zone 10N; however this dataset has been reprojected into NAD 1983 (2011) California State Plane Zone II by Solano County GIS. For more information about this dataset, please contact the DRCD.Dataset created: 4/4/2003Dataset received by Solano County DoIT GIS Team on 5/30/2024.
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: Dixon Resource Conservation District
Website: https://www.dixonrcd.org/
Address: 1170 N. Lincoln St., Ste 110, Dixon, CA 95620
Phone: 707-678-1655
Description: These boundaries represent the Garbage Service Areas within Solano County. They are represented nominally by edge-alignment to the decennial census blocks within the County. Some boundaries deviate in instances where the garbage service providers identified boundaries circa 2008 that were retained as of March 2023. This dataset is considering a an approved product by the Resource Management team as of February 2024. Last updated February 2024.
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: Data was created via a collaboration between the Department of Information Technology (DoIT) and the Department of Resource Management. Approval criteria was set by Narcisa Untal for the RM department.
Description: Boundaries of various types of public agencies with responsibilities that include in part or primarily flood control, system maintenance, and improvement. Useful for locating a flood management agency, or identifying a responsible entity.In California, there are a variety of political entities that are granted self-taxation powers under various California codes in order to perform the basic goal of flood management within an area. This dataset compiles many of the various datasets together to provide the information in one location. It also includes districts that are no longer active political/management entities for archival or historical purposes. The primary type of flood agency in California are known as reclamation districts, and so represent the majority of the records in this database. The quality of the boundary accuracy is highly variable, due to a variety of reasons, including the fact that the original legal boundaries are frequently tied to Swamp Land Survey boundaries that themselves are poorly located by modern mapping standards. This set of boundary delineations represents the latest in a series of nearly 20 significant revisions primarily by DWR Delta Levees Program between 2000-2017 to a dataset first produced by Office of Emergency Services during the 1997 floods. The accuracy and completeness of the data are therefore higher in the Delta than elsewhere. The Division of Flood Management then stored the boundaries in their levee geodatabase that feeds the web mapping application known as FERIX. To produce this final dataset, in 2018 the Division of Engineering Geodetic Branch merged the data used by FERIX, along with other datasets used by the Delta Levees Program, and normalized the attribute table.
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: Access Constraints: Other Constraints
Use Constraints: DWR makes no warranties or guarantees —either expressed or implied — as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data.
Data Set Credit: California Department of Water Resources. Contact: gis@water.ca.gov
Description: Parcel feature class was created on 9/4/24.Fields:lowparceli - APN Number for lot of multiunit dwellingsparcelid- APN Numberfloororder - Building Floorc_user - Created Userc_date - Created Datelast_edit - Last Edited Userlast_edate - Last Edited Dategtg_review - Notes on Parcel Reviewgtg_notes - Notes from GTG Teamcountynote - Solano County GIS Staff Notesdata_note - Data Notestaxmapno - Number of the tax map associated with the parcelgis_acre - Measured Acreage Value Xcentroid - X Centroid Value Ycentroid - Y Centroid Value taxmaplink - Link to Tax Map propurl - Link to Property Characteristics asmtnum – PIN rollyear - Current Tax Roll Year acres - Recorded Acreage Value lotsize – Lot Size Square Footage usecode - Use Code use_desc - Use Code Description subdiv – Subdivision Name qclass – Quality Class yrblt - Year Built status – PIN Status valland - Land Value valimp – Improvement Value valtv – Trees & Vine Value valfme – Fixed Machinery & Equipment Value valpp – Personal Property Value valpen – Penalty Value assessee – Owner of Recordaddr1 – Owner address 1addr2 – Owner address 2addr3 – Owner address 3addr4 – Owner address 4addr5 – Owner address 5city - Owner address City Name state - Owner address State Name addrzip – Owner address Zip Code situs – Site Addresssitenum – Site Number siteroad – Site Street Name p_address – Site Number & Street sitecity – Site City Name unitbldg – Site Unit/Building wa – Williamson Act (YS/NO) wa_status – Williamson Act Status Code wacontno – Williamson Act Contract Number wa_prime – Total Prime Acreage noprimacre – Total Nonprime Acreage exacre – Total Excluded Acreage p_create - Parcel Creation Date p_inactive - Parcel Inactivation Date firs_floor - First Floor Area sec_floor - Second Floor Area thir_floor - Third Area other_area - Other Area garage - Garage Area total_area - Total Area stories - Number of Stories bedroom - Number of Bedrooms bathroom - Number of Bathrooms dining - Dining Room (Space, YS, NO) family - Family Room (Space, YS, NO) other_room - Number of Other Rooms utility - Utility Room (Space, YS, NO) rooms - Total Rooms Countfireplc – Fireplace (Space, YS, NO, 1, 2…) hvac - HVAC Code pool – Swimming Pool (Space, YS, NO) solar - Solar (Space, YS, NO) tac - TAG tac_city – TAG City Name govt_owned – Govt Owned hotype – Home Owner Exemption Type fund_fire – Fire District desc_fire - Fire District Description f_school - School District d_school – School District Description fund_water – Water District desc_water – Water District Description f_air_board – Air Board District d_air_board - Air Board District Description f_soil_cons - Soil Conservation District d_soil_cons – Soil Conservation District Description acre_diff - Acreage Differencezone1 - Zone 1zone2 - Zone 2zone3 - Zone 3tzperc - Total Zone Percenttzcheck - Total Zone 100%class1 - General Plan Class 1class2 - General Plan Class 2class3 - General Plan Class 3gptperc - Total GP Percentgptcheck - Total GP 100%supd - Supervisor Districtsupdch - Supervisor District Splitstasd - State Districtstasch - State Distrcit Splitsend - Senate Districtsendch - Senate District Splitcond - Congressional Districtcondch - Congressional District Splitfiresra - Wildfire State Responsibility Area
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: This data is maintained by Geographic Technologies Group under the guidance of Solano County. All parcels are based on the Solano County Tax Maps. If there are discrepancies, Tax Map is considered authority. However, Tax Map is not a legal document.
Description: Primary and Secondary Management Areas of the Suisun Marsh as described in the BCDC's Suisun Marsh Protection Plan.A shapefile depiction of BCDC's Primary and Secondary Management Areas of the Suisun Marsh. Data was developed to assist with cartographic depiction of the Marsh and therefore should not be used for jurisdictional purposes.Please see Supplemental information for updates. This data is a depiction of the Primary Management Area of the Suisun Marsh generated by the San Francisco Bay Conservation and Development Commission (BCDC). It is only a graphic depiction of the Primary Management Area and does not reflect the actual jurisdiction of BCDC. Per the Suisun Marsh Preservation Act, the "Suisun Marsh" or "marsh" means water covered areas, tidal marsh, diked-off wetlands, seasonal marshes, lowland grasslands, upland grasslands and cultivated lands specified on the map identified in Section 16 of that chapter of the Statutes of the 1977-78 Regular Session enacting this division. It includes both the primary and secondary management areas as shown on the Suisun Marsh Protection Plan Map and includes the entire right-of-way of any state highway that is designated as a portion of the boundary of the marsh. For additional information on BCDC's jurisdiction see the San Francisco Bay Plan, the Suisun Marsh Protection Plan and the Suisun Marsh Act. All information can be found at www.bcdc.ca.gov. Data based on map "Boundaries of the Suisun Marsh" in the Suisun Marsh Protection Plan, SFBCDC, 1976.Data extracted 09/26/2023Data last updated 11/09/2021Source: https://data-bcdc.opendata.arcgis.com/datasets/BCDC::suisun-marsh-protection-plan-management-areas/about
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: Todd Hallenbeck
San Francisco Bay Conservation & Development Commission
Description: Nut Tree Airport is a general aviation (GA) airport located in Vacaville CA roughly halfway between San Francisco and Sacramento. The Airport is located on the I-80 corridor and has easy access to both Interstates 80 and 505.The Airport consists of 286 acres and receives approximately 102,700 aircraft operations each year. The Airport is home to 201 based aircraft and has 117 hangars and other various commercial office spaces. The Airport’s 4,700 foot long runway can accommodate a variety of aircraft from single engine to twins to small/medium sized business jets.Nut Tree Airport Master Plan Noise Contours:The 1988 Airport/Land Use Compatibility Plan (ALUCP) includes supporting policies related to aircraft noise. The California Code of Regulations, Title 21, Subchapter 6 indicates that the State of California prohibits four land use types to be located within the 65 decibel (dB) Community Noise Equivalent Level (CNEL) exposure level, which include public and private schools, places of public worship, residential dwellings, and hospitals. In order to enforce these noise regulations, each airport is required to develop a noise exposure map delineating the 65 dB CNEL noise contour location. Noise policies described in the 1988 ALUCP indicates that the maximum CNEL which shall be considered normally acceptable for residential areas in the vicinity of Nut Tree Airport is 60 rather than 6511. Also, the 2007 City of Vacaville General Plan and the Vacaville Municipal code have also adopted the 60 dB CNEL noise level as the residential compatibility threshold. The noise contours illustrated in the 2007 General Plan are based upon the 1993 Nut Tree Airport Master Plan 2011 future noise contours. These contours were anticipated to be incorporated into the 1988 ALUCP; however, the 2007 General Plan indicates that the 1988 ALUCP has not been amended to incorporate the 1993 Nut Tree Airport Master Plan noise contours. As stated above, the State of California restricts the four incompatible land uses within the 65 CNEL exposure level. Further analysis and potential recommendations for changes to adopted noise contours will be included in later chapters of the Master Plan. The 2011 55, 60, and 65 CNEL noise contours based upon the 1993 Master Plan are presented in the mapping data. It is important to note that these 2011 noise contours are based on a forecast included in the 1993 Airport Master Plan of 180,000 annual aircraft operations. Actual 2009 aircraft operations were estimated to be 101,500.
Description: Nut Tree Airport is a general aviation (GA) airport located in Vacaville CA roughly halfway between San Francisco and Sacramento. The Airport is located on the I-80 corridor and has easy access to both Interstates 80 and 505.The Airport consists of 286 acres and receives approximately 102,700 aircraft operations each year. The Airport is home to 201 based aircraft and has 117 hangars and other various commercial office spaces. The Airport’s 4,700 foot long runway can accommodate a variety of aircraft from single engine to twins to small/medium sized business jets.Nut Tree Airport Master Plan Nut Tree Airport/Land Use Compatibility Plan:The 1988 ALUCP defines the airport compatible land use zones around the Airport as Airport Land Use Compatibility Zones. New development in these zones must be compatible with the plan. The six compatibility zones, the associated impact element, maximum densities, and required percentage of open space are described in the Nut Tree Airport Master Plan Airport Land Use Compatibility Criteria. The 1988 ALUCP also includes supporting policies related to aircraft noise, airspace protection, and aircraft overflights.Following the completion of the Development Concepts and Alternatives Analysis chapter of the Airport Master Plan, a review of the 1988 airport land use zones and compatibility criteria will be completed to determine if changes are necessary. The land use zones and compatibility will also be reviewed to determine consistency with the latest California Airport Land Use Planning Handbook, published in January of 2002. It is also important to note that any recommended changes to the 1988 airport land use zones and compatibility criteria should be considered and incorporated into both the City of Vacaville and the Solano County General Plans, as well as in the Vacaville Municipal Code. Zone A: Clear Zone or Primary SurfaceZone B: Inner Approach/Departure ZoneZone C: Outer Approach/Departure Zone or Adjacent to RunwayZone D: Extended Approach/Departure ZoneZone E: Adjacent to Runway or Final ApproachZone F: Other Airport Environment
Description: Rio Vista Airport Land Use Compatibility Plan (ALUCP)Rio Vista Airport features six safety zones, numbered 1 through 6. A series of criteria is provided that reflect the specific requirements and regulations for each safety zone. General Standards describe the specific requirements for densities and intensities for each zone. Noise Criteria provide the development limitations within each zone based on the noise contours from the Airport. Safety Criteria explain the particular land uses that are not permitted or may require ALUC review. Airspace Protection Criteria discuss specific requirements for development based on 14 CFR Part 77 imaginary surfaces at the Airport. Finally, Avigation Easement Dedication describes the avigation easement requirements for parcels located within Safety Zones 1, 2, 3.Safety Zone 1 consists of the two Rio Vista runways, together with immediately adjoining areas within the runway protection zones (RPZs). The dimensions of the RPZs are set in accordance with FAA criteria.Safety Zone 2 comprises the inner approach and departure areas immediately beyond and surrounding Safety Zone 1. Typically, residential uses are restricted, apart from infill within already developed areas. Non-residential uses that include agriculture, non-group recreational uses (that result in minimal concentrations of people), storage of low-hazard materials, low-intensity light industrial land uses, and auto, aircraft, and marine repair services are all normally allowed within this zone.Safety Zone 3 contains the areas where aircraft turn as they approach or depart the runway. Uses allowed in this safety zone include greenhouses, low-hazard materials storage, mini-storage, warehouses, light industrial uses, and vehicle repair services, as well as uses allowed in Safety Zone 2. Very low residential densities and low-intensity offices and commercial uses are permitted within this zone, while uses with higher concentrations of people and children are prohibited.Safety Zone 4 covers the outer approach and departure surfaces for the Airport and extends beyond Safety Zone 2. Normally, restaurants, retail, and industrial uses are allowed in this zone, as well as uses that are allowed in Safety Zone 3. Higher intensity retail uses and offices are to be avoided in this zone, while buildings and uses that result in larger assemblages of people and children are prohibited.Safety Zone 5 is the sideline zone that runs outside and parallel to Runways 15-33 and 7-25. Normally, all uses permitted in Zone 4 and common aviation-related activities are allowed, provided they satisfy FAA height and airspace protection criteria. Uses limited in Safety Zone 3 are also limited in Zone 5. All residential uses are to be prohibited unless they are airport related; and higher-intensity non-residential uses that result in higher assemblages of people, including children, are prohibited.Safety Zone 6 comprises the traffic pattern zone and Inner WHA Boundary for the Airport. This larger zone covers regular traffic patterns and entry routes to and exit routes from the Airport. The 55 dB CNEL contour is located within Safety Zone 6. While residential uses in this zone are only restricted in relation to noise and overflight impacts, no other prohibitions exist within this zone. However, outdoor stadiums and similar uses that would result in very high intensities of people should be avoided
Description: Rio Vista Airport Land Use Compatibility Plan (ALUCP)Section 2.2 Geographic Scope The Airport Influence Area (AIA) is comprised of portions of Solano County and the city of Rio Vista that surround the Airport, and encompasses Safety Zones 1 through 6, the Airport’s 2035 noise contours, the Airport’s Title 14 Code of Federal Regulations (CFR) Part 77 surfaces, the Airport’s overflight notification area, and the Inner and Outer Wildlife Hazard Analysis (WHA) areas.Section 5.8 Wildlife HazardsThis data depicts two wildlife hazard zones, the Inner Wildlife Hazard Analysis (WHA) Boundary and the Outer WHA Boundary, which contain specific development requirements. The Inner WHA Boundary is coterminous with the Traffic Pattern Boundary as represented by Safety Zone 6. The Outer WHA Boundary is located five miles from the farthest edge of the Airport’s Air Operations Area (AOA), which the Federal Aviation Administration (FAA) recommends for any hazardous wildlife attractant if the attractant could cause hazardous wildlife movement into or across the approach or departure airspace. FAA Advisory Circular 150/5200-33B provides guidance for minimizing the risks that certain wildlife species pose to aircraft. The Inner WHA Boundary is based on the fact that Rio Vista Airport serves piston-powered aircraft. Together, these perimeters encompass all safety zones and present additional conditions on certain types of land uses that are known to attract wildlife that are hazardous to aircraft operations. See FAA Circular 150/5200-33B in Appendix G for specific land use details and restrictions, including a description of conflicting land uses. The ALUC shall apply the following Wildlife Hazard (WH) policies within the AIA. The following policies do not apply to existing land uses.WH-1 Known Wildlife Hazards in Solano County - Inner WHA Boundary:Within the Inner WHA Boundary, new or expanded land uses involving discretionary review that has the potential to attract wildlife and cause bird strikes are required to prepare a wildlife hazard analysis (WHA). Reviewing agencies shall prepare a WHA for projects that have the potential to attract wildlife that could cause bird strikes. Expansion of existing wildlife attractants includes newly created areas and increases in enhanced or restored areas. The WHA must demonstrate wildlife attractants that may pose hazards to aircraft in flight will be minimized.WH-2 Known Wildlife Hazards in Solano County - Outer WHA Boundary:Outside the Inner WHA Boundary but within the Outer WHA Boundary, as shown on Figure 8, any new or expanded land use involving discretionary review that has the potential to attract the movement of wildlife and cause bird strikes are required to prepare a WHA. Expansion of existing wildlife attractants includes newly created areas and increases in enhanced or restored areas. All reasonably feasible mitigation measures must be incorporated into the planned land use. The WHA must demonstrate wildlife movement that may pose hazards to aircraft in flight will be minimized.WH-3 Environmental Review Compliance:1. All discretionary projects located within the Inner WHA Boundary or Outer WHA Boundary are required to consider the potential for the project to attract hazardous wildlife, wildlife movement, or bird strike hazards as part of the environmental review process required by the California Environmental Quality Act (CEQA).2. Because biological and hazard impacts are required to be examined in the context of CEQA compliance, it is anticipated that most projects will develop the information necessary to prepare a WHA and demonstrate compliance with this Policy WH-3 as part of the CEQA process, and that separate documentation will not be needed. Proposed projects within the Inner WHA Boundary that have the potential to cause a significant adverse impact under Policy WH-1, with or without mitigation, shall be reviewed by the ALUC (including but not limited to projects requiring an environmental impact report, mitigated negative declaration, or equivalent document).Data source: Rio Vista Airport - Airport Land Use Compatibility Plan - Figure 2blobdload.aspx (solanocounty.com)chrome-extension://efaidnbmnnnibpcajpcglclefindmkaj/https://www.solanocounty.com/civicax/filebank/blobdload.aspx?BlobID=34763Last updated on source: May 10, 2018Date published in source: May 10, 2018Updated for Solano County GIS: 04/24/2024. Uploaded to Solano County GIS Portal, GIS Services Team, Solano County Department of Information Technology.
Description: Travis Air Force Base Land Use Compatibility PlanSection 4.1 Compatibility Zones EstablishedIn total, the Air Force Base features six compatibility zones, A, B1, B2, C, D, and E, as well as two overlay zones, the Assault Landing Zone (ALZ) Training Overlay Zone and the Height Review Overlay Zone. Each of the compatibility zones and overlay zones are generally described with tabular information relating to density and intensity requirements and additional zone-specific criteria. The Plan provides additional general, noise, safety, aircraft protection, and overflight regulations and supporting criteria that apply to each of the compatibility zones.Section 4.9 Height Review Overlay ZoneThe Height Review Overlay Zone covers locations where the terrain exceeds or comes within 35 feet of any of the Federal Aviation Regulation (FAR) Part 77 airspace protection surfaces for Travis AFB. The Height Review zone overlays portions of the other compatibility zones, and is generally located in portions of Cement Hill and the Vaca Mountains, to the northwest of Travis AFB and between the cities of Fairfield and Vacaville.
Description: Travis Air Force Base Land Use Compatibility PlanSection 4.1 Compatibility Zones EstablishedIn total, the Air Force Base features six compatibility zones, A, B1, B2, C, D, and E, as well as two overlay zones, the Assault Landing Zone (ALZ) Training Overlay Zone and the Height Review Overlay Zone. Each of the compatibility zones and overlay zones are generally described with tabular information relating to density and intensity requirements and additional zone-specific criteria. The Plan provides additional general, noise, safety, aircraft protection, and overflight regulations and supporting criteria that apply to each of the compatibility zones.Section 4.8 Assault Landing Zone Training Overlay Zone The ALZ is a short runway on the northeast end of the Travis AFB airfield complex that is used for the tactical arrival, departure, and landing training for C-17 aircraft and aircrews. This additional runway enables C-17 training operations to remain segregated from other aircraft operations. Based on the combat arrival and departure simulations that occur at a minimum elevation of 500 feet above ground level (AGL), the ALZ Training Overlay Zone has been developed to restrict the development of tall structures within this zone.
Description: In total, the Air Force Base features six compatibility zones, A, B1, B2, C, D, and E, as well as two overlay zones, the ALZ Training Overlay Zone and the Height Review Overlay Zone. Below, each of the compatibility zones and overlay zones are generally described with tabular information relating to density and intensity requirements and additional zone-specific criteria. These details are also summarized in Table 1. Following this section, the Plan provides additional general, noise, safety, aircraft protection, and overflight regulations and supporting criteria that apply to each of the compatibility zones.Figure 4 depicts two wildlife hazard zones, the Bird Strike Hazard Zone and the Outer Perimeter, which contain specific development requirements. The Bird Strike Hazard Zone is delineated by a radius 14,500 feet from the runway centerlines. The Outer Perimeter is located five miles from the farthest edge of the Air Force Base’s air operations area (AOA), which the FAA recommends for any hazardous wildlife attractant if the attractant could cause hazardous wildlife movement into or across the approach or departure airspace. FAA Advisory Circular 150/5200-33B provides guidance for minimizing the risks that certain wildlife species pose to aircraft. The Outer Perimeter is based on the fact that Travis AFB serves turbine powered aircraft. Together, these perimeters encompass portions of all compatibility zones and present additional conditions on certain types of land uses that are known to attract wildlife that are hazardous to aircraft operations. See FAA Circular 150/5200-33B in Appendix G for specific land use details and restrictions, including a description of conflicting land uses.
Description: In total, the Air Force Base features six compatibility zones, A, B1, B2, C, D, and E, as well as two overlay zones, the ALZ Training Overlay Zone and the Height Review Overlay Zone. Below, each of the compatibility zones and overlay zones are generally described with tabular information relating to density and intensity requirements and additional zone-specific criteria. These details are also summarized in Table 1. Following this section, the Plan provides additional general, noise, safety, aircraft protection, and overflight regulations and supporting criteria that apply to each of the compatibility zones.Figure 4 depicts two wildlife hazard zones, the Bird Strike Hazard Zone and the Outer Perimeter, which contain specific development requirements. The Bird Strike Hazard Zone is delineated by a radius 14,500 feet from the runway centerlines. The Outer Perimeter is located five miles from the farthest edge of the Air Force Base’s air operations area (AOA), which the FAA recommends for any hazardous wildlife attractant if the attractant could cause hazardous wildlife movement into or across the approach or departure airspace. FAA Advisory Circular 150/5200-33B provides guidance for minimizing the risks that certain wildlife species pose to aircraft. The Outer Perimeter is based on the fact that Travis AFB serves turbine powered aircraft. Together, these perimeters encompass portions of all compatibility zones and present additional conditions on certain types of land uses that are known to attract wildlife that are hazardous to aircraft operations. See FAA Circular 150/5200-33B in Appendix G for specific land use details and restrictions, including a description of conflicting land uses.
Description: Travis Air Force Base Land Use Compatibility PlanSection 4.1 Compatibility Zones EstablishedIn total, the Air Force Base features six compatibility zones, A, B1, B2, C, D, and E, as well as two overlay zones, the Assault Landing Zone (ALZ) Training Overlay Zone and the Height Review Overlay Zone. Each of the compatibility zones and overlay zones are generally described with tabular information relating to density and intensity requirements and additional zone-specific criteria. The Plan provides additional general, noise, safety, aircraft protection, and overflight regulations and supporting criteria that apply to each of the compatibility zones.Section 4.2 Compatibility Zone A Compatibility Zone A consists of the Travis AFB runways (the two existing major runways and the ALZ, together with immediately adjoining areas within the runway primary surface and clear zones. The dimensions are set in accordance with Federal Aviation Administration (FAA) and Air Force criteria.Section 4.3 Compatibility Zone B1 Compatibility Zone B1 comprises Accident Potential Zone I (APZ I) as defined by the Air Force. This is an area of substantial risk situated within 7,500 feet of the runway ends. It is also subject to potential noise levels in excess of 80 dB Community Noise Equivalent Level (CNEL).Section 4.4 Compatibility Zone B2Compatibility Zone B2 is comparable to Accident Potential Zone II (APZ II) as indicated in Air Force guidelines, but is expanded to encompass approach and departure flight tracks that are not aligned with the runway. High risk and potential noise levels in the 70-to-80-dB CNEL range are the major compatibility factors.
Description: Travis Air Force Base Land Use Compatibility PlanSection 4.1 Compatibility Zones EstablishedIn total, the Air Force Base features six compatibility zones, A, B1, B2, C, D, and E, as well as two overlay zones, the Assault Landing Zone (ALZ) Training Overlay Zone and the Height Review Overlay Zone. Each of the compatibility zones and overlay zones are generally described with tabular information relating to density and intensity requirements and additional zone-specific criteria. The Plan provides additional general, noise, safety, aircraft protection, and overflight regulations and supporting criteria that apply to each of the compatibility zones.Section 4.5 Compatibility Zone C Compatibility Zone C encompasses locations exposed to potential noise in excess of approximately 60 dB Community Noise Equivalent Level (CNEL) together with additional areas occasionally affected by concentrated numbers of low-altitude aircraft overflights. To the greatest extent practical, the boundaries are delineated so as to follow sections, lines, other geographic features, and fixed offset distances from the extended runway centerlines. Developed residential areas within existing city limits are excluded.
Description: Travis Air Force Base Land Use Compatibility PlanSection 4.1 Compatibility Zones EstablishedIn total, the Air Force Base features six compatibility zones, A, B1, B2, C, D, and E, as well as two overlay zones, the Assault Landing Zone (ALZ) Training Overlay Zone and the Height Review Overlay Zone. Each of the compatibility zones and overlay zones are generally described with tabular information relating to density and intensity requirements and additional zone-specific criteria. The Plan provides additional general, noise, safety, aircraft protection, and overflight regulations and supporting criteria that apply to each of the compatibility zones.Section 4.6 Compatibility Zone DCompatibility Zone D includes all other locations beneath any of the Travis AFB airspace protection surfaces delineated in accordance with Federal Aviation Regulation (FAR) Part 77 as well as areas subject to frequent aircraft overflight. Limitations on the height of structures and notice of aircraft overflights are the only compatibility factors within this zone.
Description: Travis Air Force Base Land Use Compatibility PlanSection 4.1 Compatibility Zones EstablishedIn total, the Air Force Base features six compatibility zones, A, B1, B2, C, D, and E, as well as two overlay zones, the Assault Landing Zone (ALZ) Training Overlay Zone and the Height Review Overlay Zone. Each of the compatibility zones and overlay zones are generally described with tabular information relating to density and intensity requirements and additional zone-specific criteria. The Plan provides additional general, noise, safety, aircraft protection, and overflight regulations and supporting criteria that apply to each of the compatibility zones.Section 4.7 Compatibility Zone E Compatibility Zone E includes the area located between Zone D and the Airport Influence Area (AIA) boundary, which is coterminous with the Solano County boundaries. Zone E requires Airport Land Use Commission (ALUC) review for all proposed buildings or structures that are 200 feet or higher above ground level (AGL). There is no limit on the types of land uses, densities, or intensities, although large stadiums and similar uses should be avoided in this compatibility zone.Last edited 04/15/24 by DMachado to accomodate TAFB Zone D without overlap at request of Solano County Planning Dept.
Description: Travis Air Force Base Land Use Compatibility Plan (LUCP)Section 2.2.2 Boundaries of Airport Influence Area The specific limits of the Travis AFB Airport Influence Area (AIA) are:(a) The AIA is comprised of the entirety of Solano County and Compatibility Zones A, B1, B2, C, D, and E, together with the Assault Landing Zone (ALZ) and Height Review Overlay Zones. This data depicts the compatibility zones and the AIA for Travis AFB; additionally, a description of each of the compatibility zones is located in Policy 4.1 (page 17). These compatibility zones also include some portions Contra Costa, Napa, Sacramento, and Yolo Counties.(b) For the portions of the AIA that extend into Contra Costa, Napa, Sacramento, and Yolo counties, these areas are advisory to the Airport Land Use Commissions (ALUCs) within those counties. This LUCP is not binding on any areas located outside Solano County.(c) Within the AIA, all proposed development with structures that are 200 feet above ground level (AGL) or greater in height shall be reviewed by the ALUC and shall be consistent with Land Use Compatibility Criteria.(d) The AIA is the same as the ALUC planning area as referred to in the Public Utilities Code, Section 21675.
Description: This map includes change areas for city boundaries and county line adjustments filed in accordance with Government Code 54900. The boundaries in this map are based on the State Board of Equalization's tax rate area maps for the assessment roll year specified in the COFILE field. The information is updated regularly within 10 business days of the most recent BOE acknowledgement date. Some differences may occur between actual recorded boundaries and boundary placement in the tax rate area GIS map. Tax rate area boundaries are representations of taxing jurisdictions for the purpose of determining property tax assessments and should not be used to determine precise city or county boundary line locations.BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number; CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance; RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES: additional clarifying information about the action.BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the BOE's 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: California State Board of Equalization, Tax Area Services Section, TASS@boe.ca.gov, (916) 274-3250
https://gis-calema.opendata.arcgis.com/datasets/CalEMA::boe-citycounty/about
Description: Data received from Vallejo Flood & Wastewater District representing their service boundary in GIS.Data received 06/24/24.Data uploaded by DMachado 06/25/24
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: Vallejo Flood & Wastewater District - 450 Ryder Street | Vallejo CA 94590
Description: This is the boundary representing the service area for the Fairfield Suisun Sewer District reported as of June 2024.Outlined as of 06/25/24.Uploaded by DMachado as of 06/25/24.
Service Item Id: 6c641ef079df41e985c56b6c853a7d1c
Copyright Text: Data is owned by FSSD for Solano County.