RTB Maps is a cloud-based electronic Atlas. We used ArGIS 10 for Desktop with Spatial Analysis Extension, ArcGIS 10 for Server on-premise, ArcGIS API for Javascript, IIS web services based on .NET, and ArcGIS Online combining data on the cloud with data and applications on our local server to develop an Atlas that brings together many of the map themes related to development of roots, tubers and banana crops. The Atlas is structured to allow our participating scientists to understand the distribution of the crops and observe the spatial distribution of many of the obstacles to production of these crops. The Atlas also includes an application to allow our partners to evaluate the importance of different factors when setting priorities for research and development. The application uses weighted overlay analysis within a multi-criteria decision analysis framework to rate the importance of factors when establishing geographic priorities for research and development.Datasets of crop distribution maps, agroecology maps, biotic and abiotic constraints to crop production, poverty maps and other demographic indicators are used as a key inputs to multi-objective criteria analysis.Further metadata/references can be found here: http://gisweb.ciat.cgiar.org/RTBmaps/DataAvailability_RTBMaps.htmlDISCLAIMER, ACKNOWLEDGMENTS AND PERMISSIONS:This service is provided by Roots, Tubers and Bananas CGIAR Research Program as a public service. Use of this service to retrieve information constitutes your awareness and agreement to the following conditions of use.This online resource displays GIS data and query tools subject to continuous updates and adjustments. The GIS data has been taken from various, mostly public, sources and is supplied in good faith.RTBMaps GIS Data Disclaimer• The data used to show the Base Maps is supplied by ESRI.• The data used to show the photos over the map is supplied by Flickr.• The data used to show the videos over the map is supplied by Youtube.• The population map is supplied to us by CIESIN, Columbia University and CIAT.• The Accessibility map is provided by Global Environment Monitoring Unit - Joint Research Centre of the European Commission. Accessibility maps are made for a specific purpose and they cannot be used as a generic dataset to represent "the accessibility" for a given study area.• Harvested area and yield for banana, cassava, potato, sweet potato and yam for the year 200, is provided by EarthSat (University of Minnesota’s Institute on the Environment-Global Landscapes initiative and McGill University’s Land Use and the Global Environment lab). Dataset from Monfreda C., Ramankutty N., and Foley J.A. 2008.• Agroecology dataset: global edapho-climatic zones for cassava based on mean growing season, temperature, number of dry season months, daily temperature range and seasonality. Dataset from CIAT (Carter et al. 1992)• Demography indicators: Total and Rural Population from Center for International Earth Science Information Network (CIESIN) and CIAT 2004.• The FGGD prevalence of stunting map is a global raster datalayer with a resolution of 5 arc-minutes. The percentage of stunted children under five years old is reported according to the lowest available sub-national administrative units: all pixels within the unit boundaries will have the same value. Data have been compiled by FAO from different sources: Demographic and Health Surveys (DHS), UNICEF MICS, WHO Global Database on Child Growth and Malnutrition, and national surveys. Data provided by FAO – GIS Unit 2007.• Poverty dataset: Global poverty headcount and absolute number of poor. Number of people living on less than $1.25 or $2.00 per day. Dataset from IFPRI and CIATTHE RTBMAPS GROUP MAKES NO WARRANTIES OR GUARANTEES, EITHER EXPRESSED OR IMPLIED AS TO THE COMPLETENESS, ACCURACY, OR CORRECTNESS OF THE DATA PORTRAYED IN THIS PRODUCT NOR ACCEPTS ANY LIABILITY, ARISING FROM ANY INCORRECT, INCOMPLETE OR MISLEADING INFORMATION CONTAINED THEREIN. ALL INFORMATION, DATA AND DATABASES ARE PROVIDED "AS IS" WITH NO WARRANTY, EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, FITNESS FOR A PARTICULAR PURPOSE. By accessing this website and/or data contained within the databases, you hereby release the RTB group and CGCenters, its employees, agents, contractors, sponsors and suppliers from any and all responsibility and liability associated with its use. In no event shall the RTB Group or its officers or employees be liable for any damages arising in any way out of the use of the website, or use of the information contained in the databases herein including, but not limited to the RTBMaps online Atlas product.APPLICATION DEVELOPMENT:• Desktop and web development - Ernesto Giron E. (GeoSpatial Consultant) e.giron.e@gmail.com• GIS Analyst - Elizabeth Barona. (Independent Consultant) barona.elizabeth@gmail.comCollaborators:Glenn Hyman, Bernardo Creamer, Jesus David Hoyos, Diana Carolina Giraldo Soroush Parsa, Jagath Shanthalal, Herlin Rodolfo Espinosa, Carlos Navarro, Jorge Cardona and Beatriz Vanessa Herrera at CIAT, Tunrayo Alabi and Joseph Rusike from IITA, Guy Hareau, Reinhard Simon, Henry Juarez, Ulrich Kleinwechter, Greg Forbes, Adam Sparks from CIP, and David Brown and Charles Staver from Bioversity International.Please note these services may be unavailable at times due to maintenance work.Please feel free to contact us with any questions or problems you may be having with RTBMaps.

Internal view of the parcel layer. This view contains all the attributes that can be seen by County employees.There are approximately 51,300 real property parcels in Napa County. Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. GIS parcel boundaries are maintained by the Information Technology Services GIS team. Assessor Parcel Maps are created and maintained by the Assessor Division Mapping Section. Each parcel has an Assessor Parcel Number (APN) that is its unique identifier. The APN is the link to various Napa County databases containing information such as owner name, situs address, property value, land use, zoning, flood data, and other related information. Data for this map service is sourced from the Napa County Parcels dataset which is updated nightly with any recent changes made by the mapping team. There may at times be a delay between when a document is recorded and when the new parcel boundary configuration and corresponding information is available in the online GIS parcel viewer.From 1850 to early 1900s assessor staff wrote the name of the property owner and the property value on map pages. They began using larger maps, called “tank maps” because of the large steel cabinet they were kept in, organized by school district (before unification) on which names and values were written. In the 1920s, the assessor kept large books of maps by road district on which names were written. In the 1950s, most county assessors contracted with the State Board of Equalization for board staff to draw standardized 11x17 inch maps following the provisions of Assessor Handbook 215. Maps were originally drawn on linen. By the 1980’s Assessor maps were being drawn on mylar rather than linen. In the early 1990s Napa County transitioned from drawing on mylar to creating maps in AutoCAD. When GIS arrived in Napa County in the mid-1990s, the AutoCAD images were copied over into the GIS parcel layer. Sidwell, an independent consultant, was then contracted by the Assessor’s Office to convert these APN files into the current seamless ArcGIS parcel fabric for the entire County. Beginning with the 2024-2025 assessment roll, the maps are being drawn directly in the parcel fabric layer.Parcels in the GIS parcel fabric are drawn according to the legal description using coordinate geometry (COGO) drawing tools and various reference data such as Public Lands Survey section boundaries and road centerlines. The legal descriptions are not defined by the GIS parcel fabric. Any changes made in the GIS parcel fabric via official records, filed maps, and other source documents are uploaded overnight. There is always at least a 6-month delay between when a document is recorded and when the new parcel configuration and corresponding information is available in the online parcel viewer for search or download.Parcel boundary accuracy can vary significantly, with errors ranging from a few feet to several hundred feet. These distortions are caused by several factors such as: the map projection - the error derived when a spherical coordinate system model is projected into a planar coordinate system using the local projected coordinate system; and the ground to grid conversion - the distortion between ground survey measurements and the virtual grid measurements. The aim of the parcel fabric is to construct a visual interpretation that is adequate for basic geographic understanding. This digital data is intended for illustration and demonstration purposes only and is not considered a legal resource, nor legally authoritative.SFAP & CFAP DISCLAIMER: Per the California Code, RTC 606. some legal parcels may have been combined for assessment purposes (CFAP) or separated for assessment purposes (SFAP) into multiple parcels for a variety of tax assessment reasons. SFAP and CFAP parcels are assigned their own APN number and primarily result from a parcel being split by a tax rate area boundary, due to a recorded land use lease, or by request of the property owner. Assessor parcel (APN) maps reflect when parcels have been separated or combined for assessment purposes, and are one legal entity. The goal of the GIS parcel fabric data is to distinguish the SFAP and CFAP parcel configurations from the legal configurations, to convey the legal parcel configurations. This workflow is in progress. Please be advised that while we endeavor to restore SFAP and CFAP parcels back to their legal configurations in the primary parcel fabric layer, SFAP and CFAP parcels may be distributed throughout the dataset. Parcels that have been restored to their legal configurations, do not reflect the SFAP or CFAP parcel configurations that correspond to the current property tax delineations. We intend for parcel reports and parcel data to capture when a parcel has been separated or combined for assessment purposes, however in some cases, information may not be available in GIS for the SFAP/CFAP status of a parcel configuration shown. For help or questions regarding a parcel’s SFAP/CFAP status, or property survey data, please visit Napa County’s Surveying Services or Property Mapping Information. For more information you can visit our website: When a Parcel is Not a Parcel | Napa County, CA

Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. Parcel boundaries in GIS are created and maintained by the Assessor’s Division Mapping section and Information Technology Services. There are approximately 51,300 real property parcels in Napa County. Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. GIS parcel boundaries are maintained by the Information Technology Services GIS team. Assessor Parcel Maps are created and maintained by the Assessor Division Mapping Section. Each parcel has an Assessor Parcel Number (APN) that is its unique identifier. The APN is the link to various Napa County databases containing information such as owner name, situs address, property value, land use, zoning, flood data, and other related information. Data for this map service is sourced from the Napa County Parcels dataset which is updated nightly with any recent changes made by the mapping team. There may at times be a delay between when a document is recorded and when the new parcel boundary configuration and corresponding information is available in the online GIS parcel viewer.From 1850 to early 1900s assessor staff wrote the name of the property owner and the property value on map pages. They began using larger maps, called “tank maps” because of the large steel cabinet they were kept in, organized by school district (before unification) on which names and values were written. In the 1920s, the assessor kept large books of maps by road district on which names were written. In the 1950s, most county assessors contracted with the State Board of Equalization for board staff to draw standardized 11x17 inch maps following the provisions of Assessor Handbook 215. Maps were originally drawn on linen. By the 1980’s Assessor maps were being drawn on mylar rather than linen. In the early 1990s Napa County transitioned from drawing on mylar to creating maps in AutoCAD. When GIS arrived in Napa County in the mid-1990s, the AutoCAD images were copied over into the GIS parcel layer. Sidwell, an independent consultant, was then contracted by the Assessor’s Office to convert these APN files into the current seamless ArcGIS parcel fabric for the entire County. Beginning with the 2024-2025 assessment roll, the maps are being drawn directly in the parcel fabric layer.Parcels in the GIS parcel fabric are drawn according to the legal description using coordinate geometry (COGO) drawing tools and various reference data such as Public Lands Survey section boundaries and road centerlines. The legal descriptions are not defined by the GIS parcel fabric. Any changes made in the GIS parcel fabric via official records, filed maps, and other source documents are uploaded overnight. There is always at least a 6-month delay between when a document is recorded and when the new parcel configuration and corresponding information is available in the online parcel viewer for search or download.Parcel boundary accuracy can vary significantly, with errors ranging from a few feet to several hundred feet. These distortions are caused by several factors such as: the map projection - the error derived when a spherical coordinate system model is projected into a planar coordinate system using the local projected coordinate system; and the ground to grid conversion - the distortion between ground survey measurements and the virtual grid measurements. The aim of the parcel fabric is to construct a visual interpretation that is adequate for basic geographic understanding. This digital data is intended for illustration and demonstration purposes only and is not considered a legal resource, nor legally authoritative.SFAP & CFAP DISCLAIMER: Per the California Code, RTC 606. some legal parcels may have been combined for assessment purposes (CFAP) or separated for assessment purposes (SFAP) into multiple parcels for a variety of tax assessment reasons. SFAP and CFAP parcels are assigned their own APN number and primarily result from a parcel being split by a tax rate area boundary, due to a recorded land use lease, or by request of the property owner. Assessor parcel (APN) maps reflect when parcels have been separated or combined for assessment purposes, and are one legal entity. The goal of the GIS parcel fabric data is to distinguish the SFAP and CFAP parcel configurations from the legal configurations, to convey the legal parcel configurations. This workflow is in progress. Please be advised that while we endeavor to restore SFAP and CFAP parcels back to their legal configurations in the primary parcel fabric layer, SFAP and CFAP parcels may be distributed throughout the dataset. Parcels that have been restored to their legal configurations, do not reflect the SFAP or CFAP parcel configurations that correspond to the current property tax delineations. We intend for parcel reports and parcel data to capture when a parcel has been separated or combined for assessment purposes, however in some cases, information may not be available in GIS for the SFAP/CFAP status of a parcel configuration shown. For help or questions regarding a parcel’s SFAP/CFAP status, or property survey data, please visit Napa County’s Surveying Services or Property Mapping Information. For more information you can visit our website: When a Parcel is Not a Parcel | Napa County, CA

Data last synced 07-11-2025 00:48. Data synced on a Daily interval.

MCCALL IMPACT ZONEMcCall Impact zone received from City of McCall GIS Department. As City Engineers for McCall, CH2MHill has been tasked to develop spatially accurate Zoning and Parcel information for the City Manager of Public Works, Roger Millar. We expect to use an official Geodedic survey in this data, and use as a baseline for an eventual City wide planning and development project. This Data being different from known past data, in that, we are combining City limits and urban renewal information with W/S/SD information. This information is not accurate for individual property owners, parcel by parcel.DONNELLY IMPACT ZONEDonnelly Impact zone received from independent GIS contractor Garrett Mapp (garrettmapp@gmail.com).CASCADE IMPACT ZONECascade Impact zone digitized manually by Valley County GIS Analyst based on a legal description and map provided by Surveyor John Russell. Boundary within Cascade reservoir may not be representative in that it is described as 1000 to 1320 feet distance from high water mark - however no high water mark spatial data was available at time of Cascade Impact Area digitization by Valley County GIS Analyst.

Analysis of ‘Census County Economically Distressed Areas 2018’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/0b289b5e-0507-424d-9f07-f8d2b11b9580 on 27 January 2022.

--- Dataset description provided by original source is as follows ---

This is a copy of the statewide Census County GIS Tiger file. It is used to determine if a county is EDA or not by adding ACS (American Community Survey) Median Household Income (MHI) and Population Density data at the county level. The IRWM web based DAC mapping tool uses this GIS layer. Every year this table gets updated after ACS publishes their updated estimates. Created by joining 2016 EDA table to 2010 block groups feature class. The TIGER/Line Files are shapefiles and related database files (.dbf) that 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) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, Census 2000 tabulation blocks 3001, 3002, 3003,.., 3999 within Census 2000 tract 1210.02 are also within BG 3 within that census tract. Census 2000 BGs generally contained between 600 and 3,000 people, with an optimum size of 1,500 people. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For Census 2000, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to these offshore, water-only areas not included in regularly numbered census tract areas.

--- Original source retains full ownership of the source dataset ---

Analysis of ‘Census County Disadvantaged Communities 2016’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/e0f429bf-3181-42bb-b0c7-58aa9187e6a9 on 12 February 2022.

--- Dataset description provided by original source is as follows ---

--- Original source retains full ownership of the source dataset ---

The North American Blue Carbon map shows the distribution of salt marsh, mangrove, and seagrass habitats in North America. Data were compiled from approximately 50 source datasets, including international (UNEP-WCMC), national (Conabio, US Geological Survey and the US National Wetlands Inventory), as well as state and provincial sources and information from individual investigators. This 2021 release represents the third update to the CEC’s mapping of blue carbon habitats, and was a priority within the Strengthening Adaptation Capacity in Marine Protected Areas project under the CEC’s 2019–2020 Operational Plan. Although this release presents the most comprehensive picture of North American blue carbon spatial distribution at the time of publication, many seagrass and salt marsh habitats have yet to be mapped and efforts to do so are ongoing, with several pending updates underway.

These data have been made publicly available from an authoritative source other than this Atlas and data should be obtained directly from that source for any re-use. See the original metadata from the authoritative source for more information about these data and use limitations.

The authoritative source of these data can be found at the following location: www.cec.org/north-american-environmental-atlas/north-american-blue-carbon-2021/

This dataset was created as part of a collaborative effort between the Mexican Carbon Program that conducted an exhaustive search for data updates or new datasets available, as well as coordinate three national workshops with Blue Carbon experts from Canada, the United States and Mexico to retrieve feedback on the best practices to map Blue Carbon ecosystems across North America; and the Commission for Environmental Cooperation that conducted the review and evaluation of the datasets collected, as well as the map integration process and cartographic refinement in collaboration with Ricardo Llamas (rllamas@comunidad.unam.mx) as independent geospatial consultant.

Analysis of ‘Census Block Group Economically Distressed Areas 2018’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/ac57065c-1179-421b-968f-e8010700189c on 12 February 2022.

--- Dataset description provided by original source is as follows ---

This is a copy of the statewide Census Block Group GIS Tiger file. It is used to determine if a block group (BG) is EDA or not by adding ACS (American Community Survey) Median Household Income (MHI) and Population Density data at the BG level. The IRWM web based DAC mapping tool uses this GIS layer. Every year this table gets updated after ACS publishes their updated estimates. Created by joining 2016 EDA table to 2010 block groups feature class. The TIGER/Line Files are shapefiles and related database files (.dbf) that 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) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, Census 2000 tabulation blocks 3001, 3002, 3003,.., 3999 within Census 2000 tract 1210.02 are also within BG 3 within that census tract. Census 2000 BGs generally contained between 600 and 3,000 people, with an optimum size of 1,500 people. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For Census 2000, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to these offshore, water-only areas not included in regularly numbered census tract areas.

--- Original source retains full ownership of the source dataset ---