California Land Ownership Public

<p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>This dataset was updated May, 2026. This is a hosted view for the public of the California Land Ownership layer.&nbsp;</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>This ownership dataset was generated primarily from CPAD data, which already tracks the majority of ownership information in California. CPAD is utilized without any snapping or clipping to FRA/SRA/LRA. CPAD has some important data gaps, so additional data sources are used to supplement the CPAD data. Currently this includes the most currently available data from BIA, DOD, and FWS. Additional sources may be added in subsequent versions. Decision rules were developed to identify priority layers in areas of overlap.</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>The current process for compiling the data sources includes:</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>* Clipping input datasets to the California boundary</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>* Filtering the FWS data on the Primary Interest field to exclude lands that are managed by but not owned by FWS (ex: Leases, Easements, etc)</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>* Supplementing the BIA Pacific Region Surface Trust lands data with the Western Region portion of the LAR dataset which extends into California.</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>* Filtering the BIA data on the Trust Status field to exclude areas that represent mineral rights only.</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>* Filtering the CPAD data on the Ownership Level field to exclude areas that are Privately owned (ex: HOAs)</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>* In the case of overlap, sources were prioritized as follows: FWS &gt; BIA &gt; CPAD &gt; DOD</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>* As an exception to the above, DOD lands on FRA which overlapped with CPAD lands that were incorrectly coded as non-Federal were treated as an override, such that the DOD designation could win out over CPAD.</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>In addition to this ownership dataset, a supplemental _source dataset is available which designates the source that was used to determine the ownership in this dataset.</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>Starting in 2022, the ownership dataset was compiled using a new methodology. Previous versions attempted to match federal ownership boundaries to the FRA footprint, and used a manual process for checking and tracking Federal ownership changes within the FRA, with CPAD ownership information only being used for SRA and LRA lands. The manual portion of that process was proving difficult to maintain, and the new method (described below) was developed in order to decrease the manual workload, and increase accountability by using an automated process by which any final ownership designation could be traced back to a specific dataset.</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'><strong>Data Sources:</strong></span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>* GreenInfo Network's California Protected Areas Database (CPAD2025b).&nbsp;</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>* US Fish and Wildlife Service FWSInterest dataset (updated January, 2026). &nbsp;</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>* Department of Defense Military Bases dataset (updated April, 2026).&nbsp;</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>* Bureau of Indian Affairs, Pacific Region, Surface Trust and Pacific Region Office (PRO) land boundaries data (2026) via Ronald Lodgepole&nbsp;</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>* Bureau of Indian Affairs, Land Area Representations (LAR) and BIA Regions datasets (updated Oct 2019)</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'><strong>Data Gaps &amp; Changes:</strong></span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>Known gaps include several BOR, ACE and Navy lands which were not included in CPAD nor the DOD MIRTA dataset, and topology issues within the individual input datasets (ex: CPAD). Our hope for future versions is to refine the process by pulling in additional data sources to fill in some of those data gaps. Additionally, any feedback received about missing or inaccurate data can be taken back to the appropriate source data where appropriate, so fixes can occur in the source data, instead of just in this dataset.</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>26_1: The BIA input data added datasets from newer tribal land allotments not included in previous ownership datasets. DOD and FWS were also added to with topology errors near Tijuana Slough adjusted. The DOD input appeared to shift in the original source, causing minor topology errors.</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>25_1: The CPAD Input dataset was amended to merge large gaps in certain areas of the state known to be erroneous, such as Yosemite National Park, and to eliminate overalps from the original input. The FWS input dataset was updated in February of 2025, and the DOD input dataset was updated in October of 2024. The BIA input dataset was the same as was used for the previous ownership version.</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>24_1: Input datasets this year included numerous changes since the previous version, particularly the CPAD and DOD inputs. Of particular note was the re-addition of Camp Pendleton to the DOD input dataset, which is reflected in this version of the ownership dataset. We were unable to obtain an updated input for tribral data, so the previous inputs was used for this version.</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>23_1: A few discrepancies were discovered between data changes that occurred in CPAD when compared with parcel data. These issues will be taken to CPAD for clarification for future updates, but for ownership23_1 it reflects the data as it was coded in CPAD at the time. In addition, there was a change in the DOD input data between last year and this year, with the removal of Camp Pendleton. An inquiry was sent for clarification on this change, but for ownership23_1 it reflects the data per the DOD input dataset.</span></p><p><span style='background-color:white; color:#141414; font-family:&quot;Arial&quot;,sans-serif;'>22_1 : represents an initial version of ownership with a new methodology which was developed under a short timeframe. A comparison with previous versions of ownership highlighted the some data gaps with the current version. Some of these known gaps include several BOR, ACE and Navy lands which were not included in CPAD nor the DOD MIRTA dataset. Our hope for future versions is to refine the process by pulling in additional data sources to fill in some of those data gaps. In addition, any topological errors (like overlaps or gaps) that exist in the input datasets may thus carry over to the ownership dataset. Ideally, any feedback received about missing or inaccurate data can be taken back to the relevant source data where appropriate, so fixes can occur in the source data, instead of just in this dataset.</span></p>