Data set that contains information on archaeological remains of the pre historic settlement of the Letolo valley on Savaii on Samoa. It is built in ArcMap from ESRI and is based on previously unpublished surveys made by the Peace Corps Volonteer Gregory Jackmond in 1976-78, and in a lesser degree on excavations made by Helene Martinsson Wallin and Paul Wallin. The settlement was in use from at least 1000 AD to about 1700- 1800. Since abandonment it has been covered by thick jungle. However by the time of the survey by Jackmond (1976-78) it was grazed by cattle and the remains was visible. The survey is at file at Auckland War Memorial Museum and has hitherto been unpublished. A copy of the survey has been accessed by Olof Håkansson through Martinsson Wallin and Wallin and as part of a Masters Thesis in Archeology at Uppsala University it has been digitised.

Olof Håkansson has built the data base structure in the software from ESRI, and digitised the data in 2015 to 2017. One of the aims of the Masters Thesis was to discuss hierarchies. To do this, subsets of the data have been displayed in various ways on maps. Another aim was to discuss archaeological methodology when working with spatial data, but the data in itself can be used without regard to the questions asked in the Masters Thesis. All data that was unclear has been removed in an effort to avoid errors being introduced. Even so, if there is mistakes in the data set it is to be blamed on the researcher, Olof Håkansson. A more comprehensive account of the aim, questions, purpose, method, as well the results of the research, is to be found in the Masters Thesis itself. Direkt link http://uu.diva-portal.org/smash/record.jsf?pid=diva2%3A1149265&dswid=9472

Purpose:

The purpose is to examine hierarchies in prehistoric Samoa. The purpose is further to make the produced data sets available for study.

Prehistoric remains of the settlement of Letolo on the Island of Savaii in Samoa in Polynesia

MCGD_Data_V2.2 contains all the data that we have collected on locations in modern China, plus a number of locations outside of China that we encounter frequently in historical sources on China. All further updates will appear under the name "MCGD_Data" with a time stamp (e.g., MCGD_Data2023-06-21)

You can also have access to this dataset and all the datasets that the ENP-China makes available on GitLab: https://gitlab.com/enpchina/IndexesEnp

Altogether there are 464,970 entries. The data include the name of locations and their variants in Chinese, pinyin, and any recorded transliteration; the name of the province in Chinese and in pinyin; Province ID; the latitude and longitude; the Name ID and Location ID, and NameID_Legacy. The Name IDs all start with H followed by seven digits. This is the internal ID system of MCGD (the NameID_Legacy column records the Name IDs in their original format depending on the source). Locations IDs that start with "DH" are data points extracted from China Historical GIS (Harvard University); those that start with "D" are locations extracted from the data points in Geonames; those that have only digits (8 digits) are data points we have added from various map sources.

One of the main features of the MCGD Main Dataset is the systematic collection and compilation of place names from non-Chinese language historical sources. Locations were designated in transliteration systems that are hardly comprehensible today, which makes it very difficult to find the actual locations they correspond to. This dataset allows for the conversion from these obsolete transliterations to the current names and geocoordinates.

From June 2021 onward, we have adopted a different file naming system to keep track of versions. From MCGD_Data_V1 we have moved to MCGD_Data_V2. In June 2022, we introduced time stamps, which result in the following naming convention: MCGD_Data_YYYY.MM.DD.

UPDATES

MCGD_Data2025_02_28 includes a major change with the duplication of all the locations listed under Beijing, Shanghai, Tianjin, and Chongqing (北京, 上海, 天津, 重慶) and their listing under the name of the provinces to which they belonge origially before the creation of the four special municipalities after 1949. This is meant to facilitate the matching of data from historical sources. Each location has a unique NameID. Altogether there are 472,818 entries

MCGD_Data2025_02_27 inclues an update on locations extracted from Minguo zhengfu ge yuanhui keyuan yishang zhiyuanlu 國民政府各院部會科員以上職員錄 (Directory of staff members and above in the ministries and committees of the National Government). Nanjing: Guomin zhengfu wenguanchu yinzhuju 國民政府文官處印鑄局國民政府文官處印鑄局, 1944). We also made corrections in the Prov_Py and Prov_Zh columns as there were some misalignments between the pinyin name and the name in Chines characters. The file now includes 465,128 entries.

MCGD_Data2024_03_23 includes an update on locations in Taiwan from the Asia Directories. Altogether there are 465,603 entries (of which 187 place names without geocoordinates, labelled in the Lat Long columns as "Unknown").

MCGD_Data2023.12.22 contains all the data that we have collected on locations in China, whatever the period. Altogether there are 465,603 entries (of which 187 place names without geocoordinates, labelled in the Lat Long columns as "Unknown"). The dataset also includes locations outside of China for the purpose of matching such locations to the place names extracted from historical sources. For example, one may need to locate individuals born outside of China. Rather than maintaining two separate files, we made the decision to incorporate all the place names found in historical sources in the gazetteer. Such place names can easily be removed by selecting all the entries where the 'Province' data is missing.

The State Lands Commission has prepared the Significant Lands Inventory (report) for the California Legislature as a general identification and classification of those unconveyed State school lands and tide and submerged lands which possess significant environmental values. The publication incorporates evaluated and pertinent comments received on the initial draft report which was circulated statewide in February 1975.The absence of a particular digitized waterway in the dataset does not mean that the State does not claim ownership of that parcel or waterway, or that such specific parcel or waterway has no significant environmental values. This dataset is not intended to establish ownership, only to identify those parcels which possess significant environmental values. Staff was unable to physically inventory all of the considered lands; instead, the advice and participation of those with known environmental expertise was utilized as additional to staff survey.Tide and submerged lands are digitized in the WaterBody and WaterLine feature classes; WaterLines for coastal areas, WaterBody for inland areas. Tide and submerged lands under the jurisdiction of the State Lands Commission are those sovereign lands received from the Federal Government by virtue of California's admission to the Union on an equal footing with the original States. Such lands, and State interest therein, are generally the lands waterward of the ordinary high water mark of the Pacific Ocean (seaward to a three-mile limit); tidal bays, sloughs, estuaries; and, navigable lakes and streams within the State.School Lands are digitized in the SchoolLand feature class. State school lands under the jurisdiction of the Commission are largely composed of the 16th and 36th sections of each township. The Federal Government transferred these lands to the State in 1853, in order to establish a financial foundation for a public school system. In cases where the 16th and 36th sections were mineral in character, incomplete as to acreage total, or already claimed or granted by the Federal Government, the State was permitted to select other lands "in lieu" of the specific sections.The public trust of commerce, navigation and fisheries which the State retains on patented sovereign lands should also be considered included in this inventory. Wherever a waterway, or body of water, is listed or mapped, the common trust state interest in patented sovereign lands, if any, is also included.The State Lands Commission emphasized when it adopted this report at its December 1, 1975 meeting that all tide and submerged lands are significant by the nature of their public ownership. Only because of the methodology used for this report are all of these waterways not specifically listed in this inventory.It is the intent of the State Lands Commission that the Significant Lands Inventory be periodically updated. This dataset should be considered informational, to assist the Legislature, the Commission, and the public in considering the environmental aspects of a proposed project and the significant values to be protected therein.

OpenStreetMap (OSM) is a free, editable map & spatial database of the whole world. This dataset is an extract of OpenStreetMap data for French Polynesia in a GIS-friendly format.

The OSM data has been split into separate layers based on themes (buildings, roads, points of interest, etc), and it comes bundled with a QGIS project and styles, to help you get started with using the data in your maps. This OSM product will be updated weekly.

The goal is to increase awareness among Pacific GIS users of the richness of OpenStreetMap data in Pacific countries, as well as the gaps, so that they can take advantage of this free resource, become interested in contributing to OSM, and perhaps join the global OSM community.

OpenStreetMap data is open data, with a very permissive licence. You can download it and use it for any purpose you like, as long as you credit OpenStreetMap and its contributors. You don't have to pay anyone, or ask anyone's permission. When you download and use the data, you're granted permission to do that under the Open Database Licence (ODbL). The only conditions are that you Attribute, Share-Alike, and Keep open.

The required credit is “© OpenStreetMap contributors”. If you make a map, you should display this credit somewhere. If you provide the data to someone else, you should make sure the license accompanies the data

This dataset was updated May, 2025.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.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.The current process for compiling the data sources includes: Clipping input datasets to the California boundary 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) Supplementing the BIA Pacific Region Surface Trust lands data with the Western Region portion of the LAR dataset which extends into California. Filtering the BIA data on the Trust Status field to exclude areas that represent mineral rights only. Filtering the CPAD data on the Ownership Level field to exclude areas that are Privately owned (ex: HOAs) In the case of overlap, sources were prioritized as follows: FWS > BIA > CPAD > DOD 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.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. Data Sources: GreenInfo Network's California Protected Areas Database (CPAD2023a). https://www.calands.org/cpad/; https://www.calands.org/wp-content/uploads/2023/06/CPAD-2023a-Database-Manual.pdf US Fish and Wildlife Service FWSInterest dataset (updated December, 2023). https://gis-fws.opendata.arcgis.com/datasets/9c49bd03b8dc4b9188a8c84062792cff_0/explore Department of Defense Military Bases dataset (updated September 2023) https://catalog.data.gov/dataset/military-bases Bureau of Indian Affairs, Pacific Region, Surface Trust and Pacific Region Office (PRO) land boundaries data (2023) via John Mosley John.Mosley@bia.gov Bureau of Indian Affairs, Land Area Representations (LAR) and BIA Regions datasets (updated Oct 2019) https://biamaps.doi.gov/bogs/datadownload.html Data Gaps & Changes: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. 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.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 overlaps 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.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.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.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.

MCGD_Data_V2.1 contains all the data that we have collected on locations in modern China. Altogether there are 464,887 entries. The data include the name of locations and their variants in Chinese, pinyin, and any recorded transliteration; the name of the province in Chinese and in pinyin; Province ID; the latitude and longitude; the Name ID and Location ID, and NameID_Legacy. The Name IDs all start with H followed by seven digits. This is the internal ID system of MCGD (the NameID_Legacy column records the Name IDs in their original format depending on the source). Locations IDs that start with "DH" are data points extracted from China Historical GIS (Harvard University); those that start with "D" are locations extracted from the data points in Geonames; those that have only digits (8 digits) are data points we have added from various map sources. One of the main features of the MCGD Main Dataset is the systematic collection and compilation of place names from non-Chinese language historical sources. Locations were designated in transliteration systems that are hardly comprehensible today, which makes it very difficult to find the actual locations they correspond to. This dataset allows for the conversion from these obsolete transliterations to the current names and geocoordinates.

The CalFish Abundance Database contains a comprehensive collection of anadromous fisheries abundance information. Beginning in 1998, the Pacific States Marine Fisheries Commission, the California Department of Fish and Game, and the National Marine Fisheries Service, began a cooperative project aimed at collecting, archiving, and entering into standardized electronic formats, the wealth of information generated by fisheries resource management agencies and tribes throughout California.Extensive data are currently available for chinook, coho, and steelhead. Major data categories include adult abundance population estimates, actual fish and/or carcass counts, counts of fish collected at dams, weirs, or traps, and redd counts. Harvest data has been compiled for many streams, and hatchery return data has been compiled for the states mitigation facilities. A draft format has been developed for juvenile abundance and awaits final approval. This CalFish Abundance Database shapefile was generated from fully routed 1:100,000 hydrography. In a few cases streams had to be added to the hydrography dataset in order to provide a means to create shapefiles to represent abundance data associated with them. Streams added were digitized at no more than 1:24,000 scale based on stream line images portrayed in 1:24,000 Digital Raster Graphics (DRG).These features generally represent abundance counts resulting from stream surveys. The linear features in this layer typically represent the location for which abundance data records apply. This would be the reach or length of stream surveyed, or the stream sections for which a given population estimate applies. In some cases the actual stream section surveyed was not specified and linear features represent the entire stream. In many cases there are multiple datasets associated with the same length of stream, and so, linear features overlap. Please view the associated datasets for detail regarding specific features. In CalFish these are accessed through the "link" that is visible when performing an identify or query operation. A URL string is provided with each feature in the downloadable data which can also be used to access the underlying datasets.The coho data that is available via the CalFish website is actually linked directly to the StreamNet website where the database's tabular data is currently stored. Additional information about StreamNet may be downloaded at http://www.streamnet.org. Complete documentation for the StreamNet database may be accessed at http://http://www.streamnet.org/def.html

This dataset visualises the spatial distribution of the rental value in Amsterdam between 1647 and 1652. The source of rental value comes from the Verponding registration in Amsterdam. The verponding or the ‘Verpondings-quohieren van den 8sten penning’ was a tax in the Netherlands on the 8^th penny of the rental value of immovable property that had to be paid annually. In Amsterdam, the citywide verponding registration started in 1647 and continued into the early 19^th century. With the introduction of the cadastre system in 1810, the verponding came to an end.

The original tax registration is kept in the Amsterdam City Archives (Archief nr. 5044) and the four registration books transcribed in this dataset are Archief 5044, inventory 255, 273, 281, 284. The verponding was collected by districts (wijken). The tax collectors documented their collecting route by writing down the street or street-section names as they proceed. For each property, the collector wrote down the names of the owner and, if applicable, the renter (after ‘per’), and the estimated rental value of the property (in guilders). Next to the rental value was the tax charged (in guilders and stuivers). Below the owner/renter names and rental value were the records of tax payments by year.

This dataset digitises four registration books of the verponding between 1647 and 1652 in two ways. First, it transcribes the rental value of all real estate properties listed in the registrations. The names of the owners/renters are transcribed only selectively, focusing on the properties that exceeded an annual rental value of 300 guilders. These transcriptions can be found in Verponding1647-1652.csv. For a detailed introduction to the data, see Verponding1647-1652_data_introduction.txt.

Second, it geo-references the registrations based on the street names and the reconstruction of tax collectors’ travel routes in the verponding. The tax records are then plotted on the historical map of Amsterdam using the first cadaster of 1832 as a reference. Since the geo-reference is based on the street or street sections, the location of each record/house may not be the exact location but rather a close proximation of the possible locations based on the street names and the sequence of the records on the same street or street section. Therefore, this geo-referenced verponding can be used to visualise the rental value distribution in Amsterdam between 1647 and 1652. The preview below shows an extrapolation of rental values in Amsterdam. And for the geo-referenced GIS files, see Verponding_wijken.shp.

GIS specifications:

Coordination Reference System (CRS): Amersfoort/RD New (ESPG:28992)

Historical map tiles URL (From Amsterdam Time Machine)

NB: This verponding dataset is a provisional version. The georeferenced points and the name transcriptions might contain errors and need to be treated with caution.

Contributors

• Historical and archival research: Weixuan Li, Bart Reuvekamp
• Plotting of geo-referenced points: Bart Reuvekamp
• Spatial analysis: Weixuan Li
• Mapping software: QGIS
• Acknowledgements: Virtual Interiors project, Daan de Groot

Historic Fire Perimeter Dataset Feedback (arcgis.com)

Current criteria for data collection are as follows:

CAL FIRE (including contract counties) submit perimeters ≥10 acres in timber, ≥50 acres in brush, or ≥300 acres in grass, and/or ≥3 impacted residential or commercial structures, and/or caused ≥1 fatality.

All cooperating agencies submit perimeters ≥10 acres.

Version update:

Firep24_1 was released in April 2025. Five hundred forty-eight fires from the 2024 fire season were added to the database (2 from BIA, 56 from BLM, 197 from CAL FIRE, 193 from Contract Counties, 27 from LRA, 8 from NPS, 55 from USFS and 8 from USFW). Six perimeters were added from the 2025 fire season (as a special case due to an unusual January fire siege). Five duplicate fires were removed, and the 2023 Sage was replaced with a more accurate perimeter. There were 900 perimeters that received updated attribution (705 removed “FIRE” from the end of Fire Name field and 148 replaced Complex IRWIN ID with Complex local incident number for COMPLEX_ID field). The following fires were identified as meeting our collection criteria but are not included in this version and will hopefully be added in a future update: Addie (2024-CACND-002119), Alpaugh (2024-CACND-001715), South (2024-CATIA-001375). One perimeter is missing containment date that will be updated in the next release.

Cross checking CALFIRS reporting for new CAL FIRE submissions to ensure accuracy with cause class was added to the compilation process. The cause class domain description for “Powerline” was updated to “Electrical Power” to be more inclusive of cause reports.

Includes separate layers filtered by criteria as follows:

California Fire Perimeters (All): Unfiltered. The entire collection of wildfire perimeters in the database. It is scale dependent and starts displaying at the country level scale.

Recent Large Fire Perimeters (≥5000 acres): Filtered for wildfires greater or equal to 5,000 acres for the last 5 years of fires (2020-January 2025), symbolized with color by year and is scale dependent and starts displaying at the country level scale. Year-only labels for recent large fires.

California Fire Perimeters (1950+): Filtered for wildfires that started in 1950-January 2025. Symbolized by decade, and display starting at country level scale.

Detailed metadata is included in the following documents:

Wildland Fire Perimeters (Firep24_1) Metadata

See more information on our Living Atlas data release here:

CAL FIRE Historical Fire Perimeters Available in ArcGIS Living Atlas

For any questions, please contact the data steward:

Kim Wallin, GIS Specialist

CAL FIRE, Fire & Resource Assessment Program (FRAP)

kimberly.wallin@fire.ca.gov

Throughout the state, CAL FIRE has 21 operational units that are designed to address fire suppression over a certain geographic area. Each unit operates within their local jurisdiction and strives to fulfill the department's mission whether it be responding to all-risk emergencies, participating in fire safety education and educating homeowners on how to keep their property fire safe. In addition, CAL FIRE provides funding to six 'Contract Counties' (Kern, Los Angeles, Marin, Orange, Santa Barbara and Ventura) for fire protection services, including wages of suppression crews, lookouts, maintenance of fire fighting facilities, fire prevention assistants, pre-fire management positions, dispatch, special repairs, and administrative services. The Department's budget also provides for infrastructure improvements, and expanded fire fighting needs when fires grow beyond initial attack. Contract Counties are responsible for providing initial response to fires on SRA. When a wildland fire escapes this initial attack, CAL FIRE responds with fire fighting resources to assist the county.This service represents the latest official version of the CAL FIRE Administrative Units dataset, and is updated whenever a new version is released. As of May 2023, it represents cdfadmin23_1.

The FireOccurrence point layer represents ignition points, or points of origin, from which individual USFS wildland fires started. Data are maintained at the Forest/District level, or their equivalent, to track the occurrence and the origin of individual USFS wildland fires. Forests are working to include historical data, which may be incomplete.National USFS fire occurrence locations where wildland fires have historically occurred on National Forest System Lands and/or where protection is the responsibility of the US Forest Service. Knowing where wildland fire events have happened in the past is critical to land management efforts in the future.This data is utilized by fire & aviation staffs, land managers, land planners, and resource specialists on and around National Forest System Lands. The attributes included within the FireOccurrence point layer are needed to meet the needs of the US Forest Service, for data exchange between interagency data systems, to relate to the FirePerimeter polygon data layer and various fire data systems, and to track the locations of wildland fires.*This data has been updated to match 2021 National GIS Data Dictionary Standards.Metadata and DownloadsThis record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService CSV Shapefile GeoJSON KML For complete information, please visit https://data.gov.

This data set shows the centerlines of all public and some private roads within the state of Minnesota. Segments of pavement may have only one route or muitple routes traveling over them. One route will always be idenflied as primary and all attributes of these roadways signed to it. Other routes sharing the same pavement will be consisted co-incident or secendary and will not be a signed roadway attributes.

State highways are divided into segments called control sections for record keeping, maintenance, construction, and other administrative purposes. The four-digit control section number is composed of the two-number county code and an identifying two-digit number within that county. Control sections are revised due to jurisdictional transfers (typically from state to county) when new highway segments or entirely new state highways are built.

Routes State AID represent road centerlines for all state aid routes within the state of Minnesota.

Check other metadata records in this package for more information on routes centerlines.


Links to ESRI Feature Services:

Coincident Routes in Minnesota: Coincident Routes

MnDOT Control Sections: MnDOT Control Sections

MnDOT Roadway Routes in Minnesota: MnDOT Roadway Routes

Primary Routes in Minnesota: Primary Routes

State Aid Routes in Minnesota: State Aid Routes

Trunk Highways in Minnesota: Trunk Highways

Bus Stops in York. *Please note that the data published within this dataset is a live API link to CYC's GIS server. Any changes made to the master copy of the data will be immediately reflected in the resources of this dataset.The date shown in the "Last Updated" field of each GIS resource reflects when the data was first published.

Alaska's commercial fisheries are managed using various regulatory areas (i.e., districts, sections, statistical areas, etc...). District, subdistrict, and section polygons are delineated based on regulatory descriptions found in 5 AAC 21.200 (Cook Inlet Area). Alaska Fish and Game Regulations as described in 5 AAC 21.200 (last electronic update 6/15/2024) covers the May 2024 through May 2027 or until a new book is available following the Board of Fisheries meetings.Statistical areas are largely not defined in regulation, but internally defined within ADF&G. Statistical areas included are used for salmon fisheries for reporting harvest within Upper Cook Inlet. Statistical areas are polygons that divide the waters of the State of Alaska and the adjacent Exclusive Economic Zone (EEZ) into small units for the purpose of reporting and analyzing fishery harvest. Each statistical area is identified by a unique 5-digit number. Salmon statistical areas can be divided by lines defined in ADF&G regulations, and further subdivided based on prominent landmarks or points of land. Each statistical area has a geometry start date attribute which ranges in this dataset for Southeast Alaska from 1963 to 2024. Over the years, there have been changes to statistical area shapes , codes, and names. If a statistical area is not included in this file, it may have been used historically and exist in another GIS file version. Please note spring troll statistical areas DO NOT use these statistical areas for recording harvest, but are separately defined each spring in an ADF&G Advisory Announcement. Please contact the Troll Fishery Biologists for additional info on spring troll statistical areas.This data set should NOT be used for navigation or for determining compliance with ADF&G Commercial Fishing Regulations. Please consult the ADF&G Salmon Commercial Fisheries Regulations for the official definitions of regulatory boundaries. NOTE: These data attempt to depict boundaries as used for management during a specific time period. In some cases, boundaries used in practice may differ from those described in regulations, reports, maps, and other aids.Data last updated September 2024.

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.

NEW!: Use the new Business Account Number lookup tool. SUMMARYThis dataset includes the locations of businesses that pay taxes to the City and County of San Francisco. Each registered business may have multiple locations and each location is a single row. The Treasurer & Tax Collector’s Office collects this data through business registration applications, account update/closure forms, and taxpayer filings. Business locations marked as “Administratively Closed” have not filed or communicated with TTX for 3 years, or were marked as closed following a notification from another City and County Department. The data is collected to help enforce the Business and Tax Regulations Code including, but not limited to: Article 6, Article 12, Article 12-A, and Article 12-A-1. http://sftreasurer.org/registration.HOW TO USE THIS DATASETSystem migration in 2014: When the City transitioned to a new system in 2014, only active business accounts were migrated. As a result, any businesses that had already closed by that point were not included in the current dataset.2018 account cleanup: In 2018, TTX did a major cleanup of dormant and unresponsive accounts and closed approximately 40,000 inactive businesses.To learn more about using this dataset watch this video.To update your listing or look up your BAN see this FAQ: Registered Business Locations ExplainerData pushed to ArcGIS Online on November 10, 2025 at 6:16 AM by SFGIS.Data from: https://data.sfgov.org/d/g8m3-pdisDescription of dataset columns:

 UniqueID
 Unique formula: @Value(ttxid)-@Value(certificate_number)


 Business Account Number
 Seven digit number assigned to registered business accounts


 Location Id
 Location identifier


 Ownership Name
 Business owner(s) name


 DBA Name
 Doing Business As Name or Location Name


 Street Address
 Business location street address


 City
 Business location city


 State
 Business location state


 Source Zipcode
 Business location zip code


 Business Start Date
 Start date of the business


 Business End Date
 End date of the business


 Location Start Date
 Start date at the location


 Location End Date
 End date at the location, if closed


 Administratively Closed
 Business locations marked as “Administratively Closed” have not filed or communicated with TTX for 3 years, or were marked as closed following a notification from another City and County Department.


 Mail Address
 Address for mailing


 Mail City
 Mailing address city



 Mail State
 Mailing address state



 Mail Zipcode
 Mailing address zipcode


 NAICS Code
 The North American Industry Classification System (NAICS) is a standard used by Federal statistical agencies for the purpose of collecting, analyzing and publishing statistical data related to the U.S. business economy. A subset of these are options on the business registration form used in the administration of the City and County's tax code. The registrant indicates the business activity on the City and County's tax registration forms.

See NAICS Codes tab in the attached data dictionary under About > Attachments.

 NAICS Code Description
 The Business Activity that the NAICS code maps on to ("Multiple" if there are multiple codes indicated for the business).


 NAICS Code Descriptions List
 A list of all NAICS code descriptions separated by semi-colon


 LIC Code
 The LIC code of the business, if multiple, separated by spaces


 LIC Code Description
 The LIC code description ("Multiple" if there are multiple codes for a business)


 LIC Code Descriptions List
 A list of all LIC code descriptions separated by semi-colon


 Parking Tax
 Whether or not this business pays the parking tax


 Transient Occupancy Tax
 Whether or not this business pays the transient occupancy tax


 Business Location
 The latitude and longitude of the business location for mapping purposes.


 Business Corridor
 The Business Corridor in which the the business location falls, if it is in one. Not all business locations are in a corridor.

Boundary reference: https://data.sfgov.org/d/h7xa-2xwk

 Neighborhoods - Analysis Boundaries
 The Analysis Neighborhood in which the business location falls. Not applicable outside of San Francisco.

Boundary reference: https://data.sfgov.org/d/p5b7-5n3h

 Supervisor District
 The Supervisor District in which the business location falls. Not applicable outside of San Francisco. Boundary reference: https://data.sfgov.org/d/xz9b-wyfc


 Community Benefit District
 The Community Benefit District in which the business location falls. Not applicable outside of San Francisco. Boundary reference: https://data.sfgov.org/d/c28a-f6gs


 data_as_of
 Timestamp the data was updated in the source system


 data_loaded_at
 Timestamp the data was loaded here (open data portal)


 SF Find Neighborhoods
 This column was automatically created in order to record in what polygon from the dataset 'SF Find Neighborhoods' (6qbp-sg9q) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Current Police Districts
 This column was automatically created in order to record in what polygon from the dataset 'Current Police Districts' (qgnn-b9vv) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Current Supervisor Districts
 This column was automatically created in order to record in what polygon from the dataset 'Current Supervisor Districts' (26cr-cadq) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Analysis Neighborhoods
 This column was automatically created in order to record in what polygon from the dataset 'Analysis Neighborhoods' (ajp5-b2md) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Neighborhoods
 This column was automatically created in order to record in what polygon from the dataset 'Neighborhoods' (jwn9-ihcz) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.

Note: If no description was provided by DataSF, the cell is left blank. See the source data for more information.

This point dataset represents the location of gaging stations in the Sacramento-San Joaquin Delta and Suisun Marsh that have historic and statistical hydrologic data, specifically various river stage data. Stages are given in NAVD88, units feet. Specific stages are given for peak stages, 100-year stages produced under 2 separate US Army Corps of Engineers hydrology reports from 1976 and 1992, the year of previous peak stages cited by the 1976 and 1992 reports, and approximate typical tidal values as approximately estimated based on long term data records. This 2023 version of this datset replaces the prior 2020 version, and should be used as a complete replacement. The underlying analyses did not change, but the USACE peak observed stage field names from the prior version were corrected and supplemental USACE 50- and 100-year stages were added accordingly. In addition, the vertical datum conversion used at specific gages was added. The vertical datum conversion is based on DWR survey and North Central Regional Office information that is maintained for each gage station. The stage data was compiled by Karen Tolentino, engineer with Delta Levees, and by Joel Dudas, Senior Engineer in DWR's Division of Engineering, based on a wide variety of sources, including the HYDSTRA database, various historic bulletins, raw data, station histories, and other information provided by DWR's North Central Region Office, USGS, and other misc sources. They also adjusted all data to approximate NAVD88-related stages. Observed data periods of record varied widely by station, but go back as far as 1905. All peak values were derived from start of records until up to May, 2017.The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standard version 3.5, dated April 12, 2023. DWR makes no warranties or guarantees —either expressed or implied — as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. Comments, problems, improvements, updates, or suggestions should be forwarded to GIS@water.ca.gov.

More MetadataThis Water Well layer was created in March 2010 to provide an easily accessiable spatial database of water wells only. It also provides additional attribute information on Status, Depth, etc.The original water well & pollution source layer was developed in 1988 by the County’s Environmental Health Department. Records were entered into a database from 40 years of historical paper files, which exhibited a wide range of completeness and accuracy. This was an on-going process until early 1996 at which time the layer was no longer maintained. In late 2000, the Department of Building and Development began a process of updating the layer by entering data from the permit files, which had accumulated since 1996.

Statewide Property Inventory started in 1989 per legislation 11011.15, to begin a pro-active approach to managing the State’s Real Property assets in a computerized format. Having the information in an electronic format makes it available to top level decision-makers considering options for the best use of these assets. The Statewide Property Inventory is mandated to capture detailed information on the following: land owned and leased by the state, structures owned and leased by the state, property the state leases to the private sector. Statewide Property Inventory was established in 1988 by legislative mandate. Leases were added in 2004 by executive order. Data is updated annually by the agencies. Point of Contact: Any questions should be referred to the SPIWeb@dgs.ca.gov

Note: The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services beginning in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.This dataset is regularly updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications. PurposeCounty boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This feature layer is for public use. Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal Buffers (this dataset)Without Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)State BoundaryWith Bay CutsWithout Bay Cuts Working with Coastal Buffers The dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except OFFSHORE and AREA_SQMI to get a version with the correct identifiers. Point of ContactCalifornia Department of Technology, Office of Digital Services, gis@state.ca.gov Field and Abbreviation DefinitionsCDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.CENSUS_GEOID: numeric geographic identifiers from the US Census BureauCENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or countyCENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead. Boundary AccuracyCounty boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections.Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel is in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor. CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information. CDTFA's source data notes the following about accuracy: City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties. In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose. SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon. Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these