Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Downloaded from </SPAN><A href="https://gis.yolocounty.org:443/ext/rest/services/GISViewer/CommunityResources/FeatureServer/0" STYLE="text-decoration:underline;"><SPAN>Yolo County Rest Services</SPAN></A><SPAN>.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: Disclaimer
The information on these maps is based on the most current information available to Yolo County Geographic Information Systems. The County of Yolo does not warrant its accuracy or suitability for any particular purpose. The information on these maps is not intended to replace engineering, financial or primary records research
Maps & Data: Issues/Usage/Interpretation
Whether on paper or electronic, all maps are merely abstractions. A map is an attempt to represent some aspect of reality for some specific purpose. No single map is perfect for all purposes.
The maps and data presented here are aggregated from a wide variety of sources. Care has been taken to integrate these various data sources as well as possible. However, each agency providing data may have their own internal standards for accuracy and timeliness that may affect the degree to which the various data sources agree with each other.
Thus you may find that parcel lines (from the Assessor's office) may not line up exactly with flood data (derived from FEMA maps) or census boundaries (derived from US Census maps) or with aerial photography, et cetera. Each of these data sources may be considered on their own, for their own purposes, but comparisons among them may not be directly possible, and some manual interpretation may be necessary.
Maps are also created with specific scales in mind that may limit their accuracy. For example, map data intended to be presented at a county-wide scale may have been simplified or created in a generalized manner such that fine details when zoomed in very close are not available. For example, state-wide soils data will not be accurate down to a specific parcel level of detail.
There are also timing issues to contend with, as each data source may not be updated with the same frequency. Even among the Assessor's office, the data from their mapping department (parcel lines) and their data entry department (textual parcel information) may not be updated concurrently. Thus for recently modified parcels you may find discrepancies in the data.
The maps presented here represent an ongoing process of data creation - they will never be finished. The underlying data is constantly changing. Every attempt has been made to keep the data as current and accurate as possible, but these maps cannot be considered an authoritative source of data.
Color: [16, 114, 186, 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: 6 Font Family: Montserrat Medium Font Style: normal Font Weight: normal Font Decoration: none
Type
(
type: esriFieldTypeString, alias: Type, length: 255
, Coded Values:
[Idea about walking: Idea about walking]
, [Idea about biking: Idea about biking]
, [General comment: General comment]
, ...1 more...
)
Type
(
type: esriFieldTypeString, alias: Type, length: 255
, Coded Values:
[Idea about walking: Idea about walking]
, [Idea about biking: Idea about biking]
, [General comment: General comment]
)
Description: Calculate Transit Service Frequency
Time window field prefix: AM
Start date and time: 10/28/2023 6:00:00 AM
Duration: 180.0 minutes
Counting departures
Time window field prefix: Midday
Start date and time: 10/28/2023 11:00:00 PM
Duration: 120.0 minutes
Counting departures
Time window field prefix: PM
Start date and time: 10/28/2023 3:45:35 PM
Duration: 180.0 minutes
Counting departures
Description: Calculate Transit Service Frequency
Time window field prefix: AM
Start date and time: 10/24/2023 6:00:00 AM
Duration: 180.0 minutes
Counting departures
Time window field prefix: Midday
Start date and time: 10/24/2023 11:00:00 PM
Duration: 120.0 minutes
Counting departures
Time window field prefix: PM
Start date and time: 10/24/2023 3:45:35 PM
Duration: 180.0 minutes
Counting departures
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The bicycle amenities that are viewable are:</SPAN></P><UL><LI><P><SPAN>Bike Parking</SPAN></P></LI><LI><P><SPAN>Bike Repair Stations</SPAN></P></LI></UL><P><SPAN>This data is downloaded from Open Street map and was filtered by "bicycle" and "amenity" fields.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Lines originated from the Yolo County Centerline data. The data was collected using the SACOG Existing Regional Bike Facilities for the bike lanes. The Street Width, Bike Lane Width, Speed Limit, and Bike Lane Blockage was hand collected by Fehr & Peers staff.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Lines originated from the Yolo County Centerline data with a 40 foot copy parallel. The data was collected using aerial imagery and assigned the attributes by Fehr & Peers staff. </SPAN></P><P><SPAN>Data collection was done in early October 2023.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Downloaded from the </SPAN><A href="https://yodata-yolo.opendata.arcgis.com:443/datasets/f6321ba62a574a60b429f21133836bc6_2/about" STYLE="text-decoration:underline;"><SPAN>Yolo County GIS Open Data Portal</SPAN></A><SPAN>.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: Disclaimer
The information on these maps is based on the most current information available to Yolo County Geographic Information Systems. The County of Yolo does not warrant its accuracy or suitability for any particular purpose. The information on these maps is not intended to replace engineering, financial or primary records research
Maps & Data: Issues/Usage/Interpretation
Whether on paper or electronic, all maps are merely abstractions. A map is an attempt to represent some aspect of reality for some specific purpose. No single map is perfect for all purposes.
The maps and data presented here are aggregated from a wide variety of sources. Care has been taken to integrate these various data sources as well as possible. However, each agency providing data may have their own internal standards for accuracy and timeliness that may affect the degree to which the various data sources agree with each other.
Thus you may find that parcel lines (from the Assessor's office) may not line up exactly with flood data (derived from FEMA maps) or census boundaries (derived from US Census maps) or with aerial photography, et cetera. Each of these data sources may be considered on their own, for their own purposes, but comparisons among them may not be directly possible, and some manual interpretation may be necessary.
Maps are also created with specific scales in mind that may limit their accuracy. For example, map data intended to be presented at a county-wide scale may have been simplified or created in a generalized manner such that fine details when zoomed in very close are not available. For example, state-wide soils data will not be accurate down to a specific parcel level of detail.
There are also timing issues to contend with, as each data source may not be updated with the same frequency. Even among the Assessor's office, the data from their mapping department (parcel lines) and their data entry department (textual parcel information) may not be updated concurrently. Thus for recently modified parcels you may find discrepancies in the data.
The maps presented here represent an ongoing process of data creation - they will never be finished. The underlying data is constantly changing. Every attempt has been made to keep the data as current and accurate as possible, but these maps cannot be considered an authoritative source of data.
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>This data is downloaded from Open Street map and was filtered by "bicycle".</SPAN></P></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Data was downloaded from the </SPAN><A href="https://tims.berkeley.edu:443/tools/query/index.php?clear=true" STYLE="text-decoration:underline;"><SPAN>Transportation Injury Mapping System</SPAN></A><SPAN>. </SPAN></P><P STYLE="text-indent:20;"><SPAN>Date: 01/01/2018 to 12/31/2022. </SPAN></P><P STYLE="text-indent:20;"><SPAN>County: Yolo</SPAN></P><P STYLE="text-indent:20;"><SPAN>City: All</SPAN></P><P><SPAN>(2021 - 2022 is provisional and subject to change.)</SPAN></P></DIV></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: Source - Transportation Injury Mapping System
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><A href="https://data.sacog.org:443/datasets/SACOG::regional-existing-bike-facilities-2019/about" STYLE="text-decoration:underline;"><SPAN>Existing Regional Bicycle and Pedestrian Facilities</SPAN></A></P><P><SPAN>In the past, updates to the Regional Bike Facilities layers were biennial, to coincide with updates of the Regional Bicycle, Pedestrian, and Trails Master Plan. Going forward, updates will take place annually, though major projects will be added as they are opened, if needed.</SPAN></P><P><SPAN>The Regional Bicycle, Pedestrian, and Trails Master Plan envisions a complete transportation system that supports healthy living and active communities where bicycling and walking are viable and popular travel choices in a comprehensive, safe, and convenient network. The existing bike facilities layer is a comprehensive layer of bikeways built and administered by local agencies throughout the region. This data reflects current bicycle & pedestrian facilities in order to help guide the development of a seamless and integrated regional bikeway network. On-street facilities are aligned to the Regional Centerline; off-street facilities have been added from jurisdiction submissions or digitized using imagery.</SPAN></P><P><SPAN>Line segments represent transportation facilities for pedestrian and/or bicycle use. The "class" field signifies level of use in the design.</SPAN></P><P><SPAN>Class 1 designates a hard-surface multi-use trail suitable for bicycle and foot traffic. It is separate from facilities for motor vehicle traffic and meets CalTrans standards for width, signage, and surface.</SPAN></P><P><SPAN>Class 2 designates an on-street lane for bicycles only. Lanes have striping and other markings to separate them from motor vehicle traffic. There are versions of class 2 lanes that are separated from traffic with painted areas for added security and visibility for riders.</SPAN></P><P><SPAN>Class 3 designates an on-street route for bicycles only. Routes are marked by signage only; cyclists are expected to ride with the flow of traffic.</SPAN></P><P><SPAN>Class 4 designates a buffered bike lane. Buffered bike lanes have have striping and other markings to designate them for bicycle traffic, but also by some form of upright buffer to separate them from motor vehicle traffic. Possible buffers include curbs, planters, parked cars, and pylons. A bike lane separated by paint only is a class 2, not a class 4.</SPAN></P><P><SPAN>Class 0 is a SACOG-created designation to indicate informal trails of local or regional importance. The large majority of these are unpaved trails bridging gaps between other facilities, but some may be paved trails that do not meet the CalTrans width requirements for inclusion as a class 1 facility.</SPAN></P><P><SPAN>Updates will occur on a rolling basis as we review plans and learn about new bike/ped facilities built.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: Source - Sacramento Area Council of Governments Open Data Portal
Description: <DIV STYLE="text-align:Left;"><P><SPAN>This layer is GTFS data downloaded as a CSV from:</SPAN></P><P><A href="http://iportal.sacrt.com:80/GTFS/SRTD/google_transit.zip" target="_blank" STYLE="text-decoration:underline;"><SPAN>http://iportal.sacrt.com/GTFS/SRTD/google_transit.zip</SPAN></A></P></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This layer is GTFS data downloaded as a CSV from:</SPAN></P><P><A href="http://iportal.sacrt.com:80/GTFS/SRTD/google_transit.zip" STYLE="text-decoration:underline;"><SPAN>http://iportal.sacrt.com/GTFS/SRTD/google_transit.zip</SPAN></A></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This layer is GTFS data downloaded as a CSV from:</SPAN></P><P><A href="https://unitrans.ucdavis.edu:443/media/gtfs/Unitrans_GTFS.zip" STYLE="text-decoration:underline;"><SPAN>https://unitrans.ucdavis.edu/media/gtfs/Unitrans_GTFS.zip</SPAN></A></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This layer is GTFS data downloaded as a CSV from:</SPAN></P><P><A href="https://unitrans.ucdavis.edu:443/media/gtfs/Unitrans_GTFS.zip" STYLE="text-decoration:underline;"><SPAN>https://unitrans.ucdavis.edu/media/gtfs/Unitrans_GTFS.zip</SPAN></A></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>This layers was downloaded from the </SPAN><A href="https://data-usdot.opendata.arcgis.com:443/datasets/amtrak-stations/explore?location=38.423549%2C-121.731608%2C10.51" target="_blank" STYLE="text-decoration:underline;"><SPAN>U.S. Department of Transportation Open Data Portal</SPAN></A><SPAN>.</SPAN></P></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>This layers was downloaded from the </SPAN><A href="https://data-usdot.opendata.arcgis.com:443/datasets/usdot::amtrak-routes/explore?location=37.512705%2C-96.584950%2C10.51" target="_blank" STYLE="text-decoration:underline;"><SPAN>U.S. Department of Transportation Open Data Portal</SPAN></A><SPAN>.</SPAN></P></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This layer is GTFS data downloaded as a CSV from:</SPAN></P><P><A href="http://www.yolobus.com:80/GTFS/google_transit.zip" STYLE="text-decoration:underline;"><SPAN>http://www.yolobus.com/GTFS/google_transit.zip</SPAN></A></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This layer is GTFS data downloaded as a CSV from:</SPAN></P><P><A href="http://www.yolobus.com:80/GTFS/google_transit.zip" STYLE="text-decoration:underline;"><SPAN>http://www.yolobus.com/GTFS/google_transit.zip</SPAN></A></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This school points data was downloaded from the </SPAN><A href="https://data-cdegis.opendata.arcgis.com:443/datasets/CDEGIS::california-schools-2022-23/explore?location=36.818710%2C-119.500000%2C7.00&showTable=true" STYLE="text-decoration:underline;"><SPAN>California Department of Education Open GIS Data</SPAN></A><SPAN>.</SPAN></P><P><SPAN>The Free or Reduced-Price meal (FRPM) Data was exported from the </SPAN><A href="https://www.cde.ca.gov:443/ds/ad/filessp.asp" STYLE="text-decoration:underline;"><SPAN>California Department of Education website</SPAN></A><SPAN>.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Downloaded from </SPAN><A href="https://gis.yolocounty.org:443/ext/rest/services/GISViewer/CommunityResources/FeatureServer/0" STYLE="text-decoration:underline;"><SPAN>Yolo County Rest Services</SPAN></A><SPAN>.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: Disclaimer
The information on these maps is based on the most current information available to Yolo County Geographic Information Systems. The County of Yolo does not warrant its accuracy or suitability for any particular purpose. The information on these maps is not intended to replace engineering, financial or primary records research
Maps & Data: Issues/Usage/Interpretation
Whether on paper or electronic, all maps are merely abstractions. A map is an attempt to represent some aspect of reality for some specific purpose. No single map is perfect for all purposes.
The maps and data presented here are aggregated from a wide variety of sources. Care has been taken to integrate these various data sources as well as possible. However, each agency providing data may have their own internal standards for accuracy and timeliness that may affect the degree to which the various data sources agree with each other.
Thus you may find that parcel lines (from the Assessor's office) may not line up exactly with flood data (derived from FEMA maps) or census boundaries (derived from US Census maps) or with aerial photography, et cetera. Each of these data sources may be considered on their own, for their own purposes, but comparisons among them may not be directly possible, and some manual interpretation may be necessary.
Maps are also created with specific scales in mind that may limit their accuracy. For example, map data intended to be presented at a county-wide scale may have been simplified or created in a generalized manner such that fine details when zoomed in very close are not available. For example, state-wide soils data will not be accurate down to a specific parcel level of detail.
There are also timing issues to contend with, as each data source may not be updated with the same frequency. Even among the Assessor's office, the data from their mapping department (parcel lines) and their data entry department (textual parcel information) may not be updated concurrently. Thus for recently modified parcels you may find discrepancies in the data.
The maps presented here represent an ongoing process of data creation - they will never be finished. The underlying data is constantly changing. Every attempt has been made to keep the data as current and accurate as possible, but these maps cannot be considered an authoritative source of data.
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Downloaded from </SPAN><A href="https://gis.yolocounty.org:443/ext/rest/services/GISViewer/Infrastructure/FeatureServer/12" STYLE="text-decoration:underline;"><SPAN>Yolo County Rest Services</SPAN></A><SPAN>.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: Disclaimer
The information on these maps is based on the most current information available to Yolo County Geographic Information Systems. The County of Yolo does not warrant its accuracy or suitability for any particular purpose. The information on these maps is not intended to replace engineering, financial or primary records research
Maps & Data: Issues/Usage/Interpretation
Whether on paper or electronic, all maps are merely abstractions. A map is an attempt to represent some aspect of reality for some specific purpose. No single map is perfect for all purposes.
The maps and data presented here are aggregated from a wide variety of sources. Care has been taken to integrate these various data sources as well as possible. However, each agency providing data may have their own internal standards for accuracy and timeliness that may affect the degree to which the various data sources agree with each other.
Thus you may find that parcel lines (from the Assessor's office) may not line up exactly with flood data (derived from FEMA maps) or census boundaries (derived from US Census maps) or with aerial photography, et cetera. Each of these data sources may be considered on their own, for their own purposes, but comparisons among them may not be directly possible, and some manual interpretation may be necessary.
Maps are also created with specific scales in mind that may limit their accuracy. For example, map data intended to be presented at a county-wide scale may have been simplified or created in a generalized manner such that fine details when zoomed in very close are not available. For example, state-wide soils data will not be accurate down to a specific parcel level of detail.
There are also timing issues to contend with, as each data source may not be updated with the same frequency. Even among the Assessor's office, the data from their mapping department (parcel lines) and their data entry department (textual parcel information) may not be updated concurrently. Thus for recently modified parcels you may find discrepancies in the data.
The maps presented here represent an ongoing process of data creation - they will never be finished. The underlying data is constantly changing. Every attempt has been made to keep the data as current and accurate as possible, but these maps cannot be considered an authoritative source of data.
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Downloaded from the </SPAN><A href="https://yodata-yolo.opendata.arcgis.com:443/datasets/31e1796adb4c41eeb9e677d4fea5e248_1/about" STYLE="text-decoration:underline;"><SPAN>Yolo County GIS Open Data Portal</SPAN></A><SPAN>.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: Disclaimer: The information on these maps is based on the most current information available to Yolo County Geographic Information Systems. The County of Yolo does not warrant its accuracy or suitability for any particular purpose. The information on these maps is not intended to replace engineering, financial or primary records researchMaps & Data: Issues/Usage/InterpretationWhether on paper or electronic, all maps are merely abstractions. A map is an attempt to represent some aspect of reality for some specific purpose. No single map is perfect for all purposes.The maps and data presented here are aggregated from a wide variety of sources. Care has been taken to integrate these various data sources as well as possible. However, each agency providing data may have their own internal standards for accuracy and timeliness that may affect the degree to which the various data sources agree with each other.Thus you may find that parcel lines (from the Assessor's office) may not line up exactly with flood data (derived from FEMA maps) or census boundaries (derived from US Census maps) or with aerial photography, et cetera. Each of these data sources may be considered on their own, for their own purposes, but comparisons among them may not be directly possible, and some manual interpretation may be necessary.Maps are also created with specific scales in mind that may limit their accuracy. For example, map data intended to be presented at a county-wide scale may have been simplified or created in a generalized manner such that fine details when zoomed in very close are not available. For example, state-wide soils data will not be accurate down to a specific parcel level of detail.There are also timing issues to contend with, as each data source may not be updated with the same frequency. Even among the Assessor's office, the data from their mapping department (parcel lines) and their data entry department (textual parcel information) may not be updated concurrently. Thus for recently modified parcels you may find discrepancies in the data.The maps presented here represent an ongoing process of data creation - they will never be finished. The underlying data is constantly changing. Every attempt has been made to keep the data as current and accurate as possible, but these maps cannot be considered an authoritative source of data.
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>Downloaded from the </SPAN><A href="https://yodata-yolo.opendata.arcgis.com:443/datasets/82843f878266491ebcfcdd291290fe4c_4/about" target="_blank" STYLE="text-decoration:underline;"><SPAN>Yolo County GIS Open Data Portal</SPAN></A><SPAN>.</SPAN></P></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: Disclaimer
The information on these maps is based on the most current information available to Yolo County Geographic Information Systems. The County of Yolo does not warrant its accuracy or suitability for any particular purpose. The information on these maps is not intended to replace engineering, financial or primary records research
Maps & Data: Issues/Usage/Interpretation
Whether on paper or electronic, all maps are merely abstractions. A map is an attempt to represent some aspect of reality for some specific purpose. No single map is perfect for all purposes.
The maps and data presented here are aggregated from a wide variety of sources. Care has been taken to integrate these various data sources as well as possible. However, each agency providing data may have their own internal standards for accuracy and timeliness that may affect the degree to which the various data sources agree with each other.
Thus you may find that parcel lines (from the Assessor's office) may not line up exactly with flood data (derived from FEMA maps) or census boundaries (derived from US Census maps) or with aerial photography, et cetera. Each of these data sources may be considered on their own, for their own purposes, but comparisons among them may not be directly possible, and some manual interpretation may be necessary.
Maps are also created with specific scales in mind that may limit their accuracy. For example, map data intended to be presented at a county-wide scale may have been simplified or created in a generalized manner such that fine details when zoomed in very close are not available. For example, state-wide soils data will not be accurate down to a specific parcel level of detail.
There are also timing issues to contend with, as each data source may not be updated with the same frequency. Even among the Assessor's office, the data from their mapping department (parcel lines) and their data entry department (textual parcel information) may not be updated concurrently. Thus for recently modified parcels you may find discrepancies in the data.
The maps presented here represent an ongoing process of data creation - they will never be finished. The underlying data is constantly changing. Every attempt has been made to keep the data as current and accurate as possible, but these maps cannot be considered an authoritative source of data.
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Downloaded from the </SPAN><A href="https://yodata-yolo.opendata.arcgis.com:443/datasets/f6321ba62a574a60b429f21133836bc6_2/about" STYLE="text-decoration:underline;"><SPAN>Yolo County GIS Open Data Portal</SPAN></A><SPAN>.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: Disclaimer
The information on these maps is based on the most current information available to Yolo County Geographic Information Systems. The County of Yolo does not warrant its accuracy or suitability for any particular purpose. The information on these maps is not intended to replace engineering, financial or primary records research
Maps & Data: Issues/Usage/Interpretation
Whether on paper or electronic, all maps are merely abstractions. A map is an attempt to represent some aspect of reality for some specific purpose. No single map is perfect for all purposes.
The maps and data presented here are aggregated from a wide variety of sources. Care has been taken to integrate these various data sources as well as possible. However, each agency providing data may have their own internal standards for accuracy and timeliness that may affect the degree to which the various data sources agree with each other.
Thus you may find that parcel lines (from the Assessor's office) may not line up exactly with flood data (derived from FEMA maps) or census boundaries (derived from US Census maps) or with aerial photography, et cetera. Each of these data sources may be considered on their own, for their own purposes, but comparisons among them may not be directly possible, and some manual interpretation may be necessary.
Maps are also created with specific scales in mind that may limit their accuracy. For example, map data intended to be presented at a county-wide scale may have been simplified or created in a generalized manner such that fine details when zoomed in very close are not available. For example, state-wide soils data will not be accurate down to a specific parcel level of detail.
There are also timing issues to contend with, as each data source may not be updated with the same frequency. Even among the Assessor's office, the data from their mapping department (parcel lines) and their data entry department (textual parcel information) may not be updated concurrently. Thus for recently modified parcels you may find discrepancies in the data.
The maps presented here represent an ongoing process of data creation - they will never be finished. The underlying data is constantly changing. Every attempt has been made to keep the data as current and accurate as possible, but these maps cannot be considered an authoritative source of data.
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>Downloaded from the </SPAN><A href="https://yodata-yolo.opendata.arcgis.com:443/datasets/e1b1a6c82e3141959ea4e166a6c372a7_15/about" target="_blank" STYLE="text-decoration:underline;"><SPAN>Yolo County GIS Open Data Portal</SPAN></A><SPAN>.</SPAN></P></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: Disclaimer: The information on these maps is based on the most current information available to Yolo County Geographic Information Systems. The County of Yolo does not warrant its accuracy or suitability for any particular purpose. The information on these maps is not intended to replace engineering, financial or primary records researchMaps & Data: Issues/Usage/InterpretationWhether on paper or electronic, all maps are merely abstractions. A map is an attempt to represent some aspect of reality for some specific purpose. No single map is perfect for all purposes.The maps and data presented here are aggregated from a wide variety of sources. Care has been taken to integrate these various data sources as well as possible. However, each agency providing data may have their own internal standards for accuracy and timeliness that may affect the degree to which the various data sources agree with each other.Thus you may find that parcel lines (from the Assessor's office) may not line up exactly with flood data (derived from FEMA maps) or census boundaries (derived from US Census maps) or with aerial photography, et cetera. Each of these data sources may be considered on their own, for their own purposes, but comparisons among them may not be directly possible, and some manual interpretation may be necessary.Maps are also created with specific scales in mind that may limit their accuracy. For example, map data intended to be presented at a county-wide scale may have been simplified or created in a generalized manner such that fine details when zoomed in very close are not available. For example, state-wide soils data will not be accurate down to a specific parcel level of detail.There are also timing issues to contend with, as each data source may not be updated with the same frequency. Even among the Assessor's office, the data from their mapping department (parcel lines) and their data entry department (textual parcel information) may not be updated concurrently. Thus for recently modified parcels you may find discrepancies in the data.The maps presented here represent an ongoing process of data creation - they will never be finished. The underlying data is constantly changing. Every attempt has been made to keep the data as current and accurate as possible, but these maps cannot be considered an authoritative source of data.
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Downloaded from the </SPAN><A href="https://data.sacog.org:443/datasets/SACOG::rivers/about" STYLE="text-decoration:underline;"><SPAN>SACOG GIS Open Data Portal</SPAN></A><SPAN>.</SPAN></P><P><SPAN>Updated April 2018.</SPAN></P><P><SPAN>Downloaded September 2023.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: SACOG provides data as a public service. These data are provided "as-is." While every effort has been made to ensure the accuracy or correctness of these data, SACOG makes no warranty, expressed or implied, as to its accuracy or correctness and expressly disclaims liability for the accuracy thereof. In no event shall SACOG become liable to users of these data, or any other party, for any loss or damages, consequential or otherwise, including but not limited to time, money, or goodwill, arising from the use, operation or modification of the data. In using these data, users further agree to indemnify, defend, and hold harmless SACOG for any and all liability of any nature arising out of or resulting from the lack of accuracy or correctness of the data, or the use of the data. Users will not distribute these data to other potential users. Instead they will refer those users to SACOG for an independent dataset and documentation. To assist SACOG in the maintenance of the data, users should provide SACOG's GIS staff information concerning errors or discrepancies found in using the data.
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>This traffic volumes feature class containing Traffic Volumes (also known as Traffic Counts) on California state highway network created from AADT excel spreadsheet file maintained by Caltrans, Division of Traffic Operations. Annual average daily traffic is the total volume for the year divided by 365 days. The traffic count year is from October 1st through September 30th. Very few locations in California are actually counted continuously. Traffic Counting is generally performed by electronic counting instruments moved from location throughout the State in a program of continuous traffic count sampling. The resulting counts are adjusted to an estimate of annual average daily traffic by compensating for seasonal influence, weekly variation and other variables which may be present. Annual ADT is necessary for presenting a statewide picture of traffic flow, evaluating traffic trends, computing accident rates, planning and designing highways and other purposes.</SPAN></P><P><SPAN>Downloaded from </SPAN><A href="https://gisdata-caltrans.opendata.arcgis.com:443/datasets/d8833219913c44358f2a9a71bda57f76_0/about" target="_blank" STYLE="text-decoration:underline;"><SPAN>Caltrans GIS Open Data Portal</SPAN></A><SPAN>.</SPAN></P></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: Source - California Department of Transportation(Caltrans)
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Downloaded from the </SPAN><A href="https://yodata-yolo.opendata.arcgis.com:443/datasets/40849bb0db4e4135ad102acd5b504bae_0/about" STYLE="text-decoration:underline;"><SPAN>Yolo County GIS Open Data Portal</SPAN></A><SPAN>.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Data was downloaded from the </SPAN><A href="https://map.healthyplacesindex.org:443/?redirect=false" STYLE="text-decoration:underline;"><SPAN>California Healthy Places Index created by the Public Health Alliance of Southern California</SPAN></A><SPAN>. Data was exported a CSV and was joined to 2022 Census Tract polygons.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: Source - California Healthy Places Index, developed by the Public Health Alliance of Southern California.
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Data was downloaded from the </SPAN><A href="https://www.ers.usda.gov:443/data-products/food-access-research-atlas/download-the-data/" STYLE="text-decoration:underline;"><SPAN>U.S. Department of Agriculture's Food Access Research Atlas</SPAN></A><SPAN>. Data is from 2019 and was last updated 4/27/2021. Data was exported as an excel sheet and joined to census tract polygons. The census polygons are from 2010 as instructed by the original data website's instructions.</SPAN></P><P><SPAN>A data dictionary can be downloaded from the above website.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 1d34b334f336425fbfe84567af6e636c
Copyright Text: Data Source - U.s Department of Agriculture Economic Research Service
Polygon Source - Census Bureau's Cartographic Boundary Files