snippet:
|
Solano County Boundary feature class is used for cartographic purposes, for generating statistical data, and for clipping data. Sourced from DoIT ArcGIS Online. |
summary:
|
Solano County Boundary feature class is used for cartographic purposes, for generating statistical data, and for clipping data. Sourced from DoIT ArcGIS Online. |
accessInformation:
|
U.S. Bureau of Reclamation,California Department of Tax and Fee Administration, Board of Equalization, California Department of Conservation, California Department of Fish and Game, California Department of Forestry and Fire Protection, National Oceanic and Atmospheric Administration, Solano DoIT |
thumbnail:
|
|
maxScale:
|
5000 |
typeKeywords:
|
[] |
description:
|
<DIV STYLE="text-align:Left;"><P><SPAN>***** BACKGROUND *****</SPAN></P><P><SPAN /></P><P><SPAN>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.</SPAN></P><P><SPAN /></P><P><SPAN>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 ( https://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.</SPAN></P><P><SPAN /></P><P><SPAN>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.</SPAN></P><P><SPAN /></P><P><SPAN>***** THIS VERSION*****</SPAN></P><P><SPAN /></P><P><SPAN>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.</SPAN></P><P><SPAN /></P><P><SPAN>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.</SPAN></P><P><SPAN /></P><P><SPAN>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.</SPAN></P><P><SPAN /></P><P><SPAN>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.</SPAN></P><P><SPAN /></P><P><SPAN>Edited by DMachado 7/22/2024 based on Resource Management, Surveying division review of 0147-010-080 and boundary overlap in that area. Area edited manually based on comparison to associated tax map for that APN.</SPAN></P><P><SPAN /></P><P><SPAN>Edited by DMachado 9/20/2024 to more closely align to the Board of Equalization data available from the California Department of Tax and Fee Administration, as published to the CA State GeoPortal: https://gis.data.ca.gov/datasets/CDTFA::boe-citycounty-1/about</SPAN></P></DIV> |
licenseInfo:
|
<DIV STYLE="text-align:Left;"><P><SPAN>DISCLAIMER :</SPAN></P><P><SPAN /></P><P><SPAN>The State of California and the Department of Forestry and Fire Protection make no representations or warranties regarding the accuracy of data or maps. The user will not seek to hold the State or the Department liable under any circumstances for any damages with respect to any claim by the user or any third party on account of or arising from the use of data or maps.</SPAN></P><P><SPAN /></P><P><SPAN>OTHER LIMITATIONS :</SPAN></P><P><SPAN /></P><P><SPAN>There are no restrictions on distribution of the data by users. However, users are encouraged to refer others to the Department of Forestry and Fire Protection to acquire the data, in case updated data become available. The user will cite the California Department of Forestry and Fire Protection as the original source of the data, but will clearly denote cases where the original data have been altered, updated, or in any way changed from the original condition.</SPAN></P><P><SPAN /></P><P><SPAN>Disclaimer: By using this data, the user acknowledges that it is possible that errors and omissions will occur in data input or programming done by the County or for the County to provide the GIS layers and/or other data in the form desired. The user further understands and agrees that it is possible that errors and omissions will occur in record keeping processes, especially when large numbers of records are developed and maintained, and that data may not meet the user's standards as to accuracy or completeness. Notwithstanding, the user agrees to take the data “as is”, fully expecting that there may be errors and omissions associated with the data. The user further understands and agrees that the County makes absolutely no warranty whatsoever, whether expressed or implied, as to the accuracy, thoroughness, value, quality, validity, merchantability, suitability, condition or fitness for a particular purpose of the data or any programming used to obtain the data, nor as to whether the data is error-free, up-to-date, complete or based upon accurate or meaningful facts. This data layer was made using Solano County GIS files with varying degrees of scale, accuracy, precision, correctness, and alignment and therefore cannot be used for situations requiring survey grade measurement. Solano County disclaims liability for any loss that may result from the use of its data and user accepts any and all risks associated with using this data. User acknowledges data limitations and accepts responsibility for data based judgments.</SPAN></P></DIV> |
catalogPath:
|
|
title:
|
County_Boundary |
type:
|
|
url:
|
|
tags:
|
["government","county boundaries","county boundary","county line","county","counties","boundary","border","borders","boundaries","location"] |
culture:
|
en-US |
portalUrl:
|
|
name:
|
|
guid:
|
|
minScale:
|
150000000 |
spatialReference:
|
|