This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads shapefile includes all features within the MTS Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in the MTS that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

This map feeds into a web app that allows a user to examine the known status of structures damaged by the wildfire. If a structure point does not appear on the map it may still have been impacted by the fire. Specific addresses can be searched for in the search bar. Use the imagery and topographic basemaps and photos to positively identify a structure. Photos may only be available for damaged and destroyed structures.For more information about the wildfire response efforts, visit the CAL FIRE incident page.

This shapefile contains tax rate area (TRA) boundaries in Fresno County for the specified assessment roll year. Boundary alignment is based on the 2023 county parcel map. A tax rate area (TRA) is a geographic area within the jurisdiction of a unique combination of cities, schools, and revenue districts that utilize the regular city or county assessment roll, per Government Code 54900. Each TRA is assigned a six-digit numeric identifier, referred to as a TRA number. TRA = tax rate area number

The 1994 Fresno County land use survey data set was developed by DWR through its Division of Planning and Local Assistance (DPLA). The data was gathered using aerial photography and extensive field visits, the land use boundaries and attributes were digitized, and the resultant data went through standard quality control procedures before finalizing. The land uses that were gathered were detailed agricultural land uses, and lesser detailed urban and native vegetation land uses. The data was gathered and digitized by staff of DWR’s San Joaquin District. Quality control procedures were performed jointly by staff at DWR’s DPLA headquarters and San Joaquin District. Important Points about Using this Data Set: 1. The land use boundaries were hand drawn directly on USGS quad maps and then digitized. They were drawn to depict observable areas of the same land use. They were not drawn to represent legal parcel (ownership) boundaries, or meant to be used as parcel boundaries. 2. This survey was a "snapshot" in time. The indicated land use attributes of each delineated area (polygon) were based upon what the surveyor saw in the field at that time, and, to an extent possible, whatever additional information the aerial photography might provide. For example, the surveyor might have seen a cropped field in the photograph, and the field visit showed a field of corn, so the field was given a corn attribute. In another field, the photograph might have shown a crop that was golden in color (indicating grain prior to harvest), and the field visit showed newly planted corn. This field would be given an attribute showing a double crop, grain followed by corn. The DWR land use attribute structure allows for up to three crops per delineated area (polygon). In the cases where there were crops grown before the survey took place, the surveyor may or may not have been able to detect them from the field or the photographs. For crops planted after the survey date, the surveyor could not account for these crops. Thus, although the data is very accurate for that point in time, it may not be an accurate determination of what was grown in the fields for the whole year. If the area being surveyed does have double or multicropping systems, it is likely that there are more crops grown than could be surveyed with a "snapshot". 3. If the data is to be brought into a GIS for analysis of cropped (or planted) acreage, two things must be understood: a. The acreage of each field delineated is the gross area of the field. The amount of actual planted and irrigated acreage will always be less than the gross acreage, because of ditches, farm roads, other roads, farmsteads, etc. Thus, a delineated corn field may have a GIS calculated acreage of 40 acres but will have a smaller cropped (or net) acreage, maybe 38 acres. b. Double and multicropping must be taken into account. A delineated field of 40 acres might have been cropped first with grain, then with corn, and coded as such. To estimate actual cropped acres, the two crops are added together (38 acres of grain and 38 acres of corn) which results in a total of 76 acres of net crop (or planted) acres. 4. Water source and irrigation method information was not collected for this survey. 5. Not all land use codes will be represented in the survey.

The 2000 Fresno County land use survey data set was developed by DWR through its Division of Planning and Local Assistance (DPLA). The data was gathered using aerial photography and extensive field visits, the land use boundaries and attributes were digitized, and the resultant data went through standard quality control procedures before finalizing. The land uses that were gathered were detailed agricultural land uses, and lesser detailed urban and native vegetation land uses. The data was gathered and digitized by staff of DWR’s San Joaquin District. Quality control procedures were performed jointly by staff at DWR’s DPLA headquarters and San Joaquin District. The finalized data include a shapefile of central and western Fresno County (land use vector data) and JPG files (raster data from aerial imagery). Important Points about Using this Data Set: 1. The land use boundaries were either drawn on-screen using developed photoquads, or hand drawn directly on USGS quad maps and then digitized. They were drawn to depict observable areas of the same land use. They were not drawn to represent legal parcel (ownership) boundaries, or meant to be used as parcel boundaries. 2. This survey was a "snapshot" in time. The indicated land use attributes of each delineated area (polygon) were based upon what the surveyor saw in the field at that time, and, to the extent possible, whatever additional information the aerial photography might provide. For example, the surveyor might have seen a cropped field in the photograph, and the field visit showed a field of corn, so the field was given a corn attribute. In another field, the photograph might have shown a crop that was golden in color (indicating grain prior to harvest), and the field visit showed newly planted corn. This field would be given an attribute showing a double crop, grain followed by corn. The DWR land use attribute structure allows for up to three crops per delineated area (polygon). In the cases where there were crops grown before the survey took place, the surveyor may or may not have been able to detect them from the field or the photographs. For crops planted after the survey date, the surveyor could not account for these crops. Thus, although the data is very accurate for that point in time, it may not be an accurate determination of what was grown in the fields for the whole year. If the area being surveyed does have double or multicropping systems, it is likely that there are more crops grown than could be surveyed with a "snapshot". 3. If the data is to be brought into a GIS for analysis of cropped (or planted) acreage, two things must be understood: a. The acreage of each field delineated is the gross area of the field. The amount of actual planted and irrigated acreage will always be less than the gross acreage, because of ditches, farm roads, other roads, farmsteads, etc. Thus, a delineated corn field may have a GIS calculated acreage of 40 acres but will have a smaller cropped (or net) acreage, maybe 38 acres. b. Double and multicropping must be taken into account. A delineated field of 40 acres might have been cropped first with grain, then with corn, and coded as such. To estimate actual cropped acres, the two crops are added together (38 acres of grain and 38 acres of corn) which results in a total of 76 acres of net crop (or planted) acres. 4. If the data is compared to the previous digital survey (i.e. the two coverages intersected for change detection determination) there will be land use changes that may be unexpected. The linework was created independently, so even if a field’s physical boundary hasn’t changed between surveys, the lines may differ due to difference in digitizing. Numerous thin polygons (with very little area) will result. A result could be UV1 (paved roads) to F1 (cotton). In reality, paved roads are not converted to cotton fields, but these small polygons would be created due to the differences in digitizing the linework for each survey. Additionally, this kind of comparison may yield polygons of significant size with unexpected changes. These changes will almost always involve non-cropped land, mainly U (urban), UR1 (single family homes on 1 – 5 acres), UV (urban vacant), NV (native vegetation), and I1 (land not cropped that year, but cropped within the past three years). The unexpected results (such as U to NV, or UR1 to NV) occur mainly because of interpretation of those non-cropped land uses with aerial imagery. Newer surveys or well funded surveys have had the advantage of using improved quality (higher resolution) imagery or additional labor, where more accurate identification of land use is possible, and more accurate linework is created. For example, an older survey may have a large polygon identified as UR, where the actual land use was a mixture of houses and vacant land. A newer survey may have, for that same area, delineated separately those land uses into smaller polygons. The result of an intersection would include changes from UR to UV (which is normally an unlikely change). It is important to understand that the main purpose of DWR performing land use surveys is to aid in development of agricultural water use data. Thus, given our goals and budget, our emphasis is on obtaining accurate agricultural land uses with less emphasis on obtaining accurate non-agricultural land uses (urban and native areas). 5. Water source information was not collected for this survey. 6. Not all land use codes will be represented in the survey.

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.Traffic Census Program Page

This layer is a snapshot of stream gages from the fall of 2020. It is the product of an attempt to compile a comprehensive, geospatial list of long-term stream gages whose data is publicly available. Initially, the layer will consist of USGS and CDEC gages. Over time, local (county, municipal, etc.) gages will be added. This layer is not claimed to be authoritative. In cases where this layer and the data maintained by the source entity differ, this layer always defers to the source entity. For analysis purposes, the gage point locations have been altered by SWRCB to coincide with the corresponding line features in the National Hydrography Dataset (NHD) Medium Resolution. The original point locations can be found "x" and "y" fields of the layer's attribute table.For questions, contact the SWRCB Division of Water Rights: DWR@waterboards.ca.gov.Data dictionary:

Field Name Description Data Type

SiteID Site ID Text

SiteName Site Name Text

Operator Agency or entity which operates the gage Text

DataSource The agency or entity which publishes the data online (source not exclusive) Text

SiteStatus Is the site, in general, active or inactive? Text - Active or Inactive

Stage_YN Did the gage report stage at any time? Text - Y or N or U

Stage_POR Stage period of record in days (if a site had multiple stage sensors or duration codes, then the max POR was used) Integer

Stage_Status Status of stage reporting (active/inactive) Text

Stage_RealTime Is/was stage reported hourly or more frequently? Text - Y or N

Flow_YN Did the gage report flow at any time? Text - Y or N or U

Flow_POR Flow period of record in days (if a site had multiple flow sensors or duration codes, then the max POR was used) Integer

Flow_Status Status of flow reporting (active/inactive) Text

Flow_RealTime Is/was flow reported hourly or more frequently? Text - Y or N

WatQual_YN Did the gage report one or more water quality parameters at any time? Includes parameters such as water chemistry, dissolved oxygen, and turbidity, but not temperature Text - Y or N or U

WatQual_POR Water quality period of record in days (if a site had multiple water quality sensors or duration codes, then the max POR was used) Integer

WatQual_Status Status of water quality reporting (active/inactive) Text

WatQual_RealTime Is/was water quality reported hourly or more frequently? Text - Y or N

Temp_YN Did the gage report water temperature at any time? Text - Y or N or U

Temp_POR Temperature period of record in days (if a site had multiple temperature sensors or duration codes, then the max POR was used) Integer

Temp_Status Status of temperature reporting (active/inactive) Text

Temp_RealTime Is/was temperature reported hourly or more frequently? Text - Y or N

FloodMgmt Primary purpose of gage is flood management Text - Y or N

EcosysMgmt Primary purpose of gage is ecosystem management (flow and water quality) Text - Y or N

GrdwtrMgmt Primary purpose of gage is groundwater management Text - Y or N

PubSafety Primary purpose of gage is public safety Text - Y or N

WtrSupply Primary purpose of gage is water supply (municipal or agricultural) Text - Y or N

Ref_GagesII Is the gage site considered a reference site in Gages II dataset? Text - Y or N

StrmOrder Strahler stream order Integer

UCDStrmClass UCD eFlows stream classification Text

StreamType Type of water conveyance the gage is measuring (e.g. Stream/River, Canal/Ditch, Artificial Path, etc.) Text

TotDASqKM Total drainage area in square kilometers Double

TotDASqMi Total drainage area in square miles Double

GNISID_MedRes GNIS (Geographic Names Information System) identification number of the NHD line segment the gage is on (from the NHD Medium Resolution dataset) Text

RchCd_MedRes Reach Code identification number of the NHD line segment the gage is on (from the NHD Medium Resolution dataset) Text

COMID_MedRes COM ID (common identifier) of the NHD line segment the gage is on (from the NHD Medium Resolution dataset) Text

WebLink Web address to access each gage's data Text

x_orig X coordinate as provided by source entity (NAD83 CA Teale Albers meters) Double

y_orig Y coordinate as provided by source entity (NAD83 CA Teale Albers meters) Double

WtrshdNm_HUC8 Name of containing HUC8 watershed Text

HUC8 Containing HUC 8 (Hydrologic Unit Code 8) identifier Text

WtrshdNm_HUC10 Name of containing HUC10 watershed Text

HUC10 Containing HUC 10 (Hydrologic Unit Code 10) identifier Text

WtrshdNm_HUC12 Name of containing HUC12 watershed Text

HUC12 Containing HUC 12 (Hydrologic Unit Code 12) identifier Text

GageGap_Status Status of Gage for Gage Gap Analysis (e.g. Well-Gaged, AWG = Almost Well-Gaged, or Exclude) Text

Infrastructure Gage is suspected of being located on infrastructure Text - Y or N

ReactivateSF Gage is a candidate for reactivation Text - Y or N

Priority_Reactivate Reactivation priority based on gage metadata alone (e.g. period_of_record, parameter status, end-date and other factors, but not including based on gage gap or management criteria) Text

AddFlow_2Stage Upgrade candidate: gage is actively reporting stage, potential upgrade to flow and stage Text - Y or N

AddFlow_2WQ Upgrade candidate: gage is actively reporting water quality or temperature data, but not flow and/or stage. Text - Y or N

AddTelemetry Upgrade candidate: gage is actively reporting stage and/or flow, but not in real-time Text - Y or N

AddTemp_2Flow Upgrade candidate: gage is actively reporting stage and/or flow, but not water temperature Text - Y or N