Contains:World HillshadeWorld Street Map (with Relief) - Base LayerLarge Scale International Boundaries (v11.3)World Street Map (with Relief) - LabelsDoS Country Labels DoS Country LabelsCountry (admin 0) labels that have been vetted for compliance with foreign policy and legal requirements. These labels are part of the US Federal Government Basemap, which contains the borders and place names that have been vetted for compliance with foreign policy and legal requirements.Source: DoS Country Labels - Overview (arcgis.com)Large Scale International BoundariesVersion 11.3Release Date: December 19, 2023DownloadFor more information on the LSIB click here: https://geodata.state.gov/ A direct link to the data is available here: https://data.geodata.state.gov/LSIB.zipAn ISO-compliant version of the LSIB metadata (in ISO 19139 format) is here: https://geodata.state.gov/geonetwork/srv/eng/catalog.search#/metadata/3bdb81a0-c1b9-439a-a0b1-85dac30c59b2 Direct inquiries to internationalboundaries@state.govOverviewThe Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. The current edition is version 11.3 (published 19 December 2023). The 11.3 release contains updates to boundary lines and data refinements enabling reuse of the dataset. These data and generalized derivatives are the only international boundary lines approved for U.S. Government use. The contents of this dataset reflect U.S. Government policy on international boundary alignment, political recognition, and dispute status. They do not necessarily reflect de facto limits of control.National Geospatial Data AssetThis dataset is a National Geospatial Data Asset managed by the Department of State on behalf of the Federal Geographic Data Committee's International Boundaries Theme.DetailsSources for these data include treaties, relevant maps, and data from boundary commissions and national mapping agencies. Where available and applicable, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery process involves analysis of satellite imagery and elevation data. Due to the limitations of source materials and processing techniques, most lines are within 100 meters of their true position on the ground.Attribute StructureThe dataset uses thefollowing attributes:Attribute NameCC1COUNTRY1CC2COUNTRY2RANKSTATUSLABELNOTES These attributes are logically linked:Linked AttributesCC1COUNTRY1CC2COUNTRY2RANKSTATUS These attributes have external sources:Attribute NameExternal Data SourceCC1GENCCOUNTRY1DoS ListsCC2GENCCOUNTRY2DoS ListsThe eight attributes listed above describe the boundary lines contained within the LSIB dataset in both a human and machine-readable fashion. Other attributes in the release include "FID", "Shape", and "Shape_Leng" are components of the shapefile format and do not form an intrinsic part of the LSIB."CC1" and "CC2" fields are machine readable fields which contain political entity codes. These codes are derived from the Geopolitical Entities, Names, and Codes Standard (GENC) Edition 3 Update 18. The dataset uses the GENC two-character codes. The code ‘Q2’, which is not in GENC, denotes a line in the LSIB representing a boundary associated with an area not contained within the GENC standard.The "COUNTRY1" and "COUNTRY2" fields contain human-readable text corresponding to the name of the political entity. These names are names approved by the U.S. Board on Geographic Names (BGN) as incorporated in the list of Independent States in the World and the list of Dependencies and Areas of Special Sovereignty maintained by the Department of State. To ensure the greatest compatibility, names are presented without diacritics and certain names are rendered using commonly accepted cartographic abbreviations. Names for lines associated with the code ‘Q2’ are descriptive and are not necessarily BGN-approved. Names rendered in all CAPITAL LETTERS are names of independent states. Other names are those associated with dependencies, areas of special sovereignty, or are otherwise presented for the convenience of the user.The following fields are an intrinsic part of the LSIB dataset and do not rely on external sources:Attribute NameMandatoryContains NullsRANKYesNoSTATUSYesNoLABELNoYesNOTESNoYesNeither the "RANK" nor "STATUS" field contains null values; the "LABEL" and "NOTES" fields do.The "RANK" field is a numeric, machine-readable expression of the "STATUS" field. Collectively, these fields encode the views of the United States Government on the political status of the boundary line.Attribute NameValueRANK123STATUSInternational BoundaryOther Line of International Separation Special Line A value of "1" in the "RANK" field corresponds to an "International Boundary" value in the "STATUS" field. Values of "2" and "3" correspond to "Other Line of International Separation" and "Special Line", respectively.The "LABEL" field contains required text necessarily to describe the line segment. The "LABEL" field is used when the line segment is displayed on maps or other forms of cartographic visualizations. This includes most interactive products. The requirement to incorporate the contents of the "LABEL" field on these products is scale dependent. If a label is legible at the scale of a given static product a proper use of this dataset would encourage the application of that label. Using the contents of the "COUNTRY1" and "COUNTRY2" fields in the generation of a line segment label is not required. The "STATUS" field is not a line labeling field but does contain the preferred description for the three LSIB line types when lines are incorporated into a map legend. Using the "CC1", "CC2", or "RANK" fields for labeling purposes is prohibited.The "NOTES" field contains an explanation of any applicable special circumstances modifying the lines. This information can pertain to the origins of the boundary lines, any limitations regarding the purpose of the lines, or the original source of the line. Use of the "NOTES" field for labeling purposes is prohibited.External Data SourcesGeopolitical Entities, Names, and Codes Registry: https://nsgreg.nga.mil/GENC-overview.jspU.S. Department of State List of Independent States in the World: https://www.state.gov/independent-states-in-the-world/U.S. Department of State List of Dependencies and Areas of Special Sovereignty: https://www.state.gov/dependencies-and-areas-of-special-sovereignty/The source for the U.S.—Canada international boundary (NGDAID97) is the International Boundary Commission: https://www.internationalboundarycommission.org/en/maps-coordinates/coordinates.phpThe source for the “International Boundary between the United States of America and the United States of Mexico” (NGDAID82) is the International Boundary and Water Commission: https://catalog.data.gov/dataset?q=usibwcCartographic UsageCartographic usage of the LSIB requires a visual differentiation between the three categories of boundaries. Specifically, this differentiation must be between:- International Boundaries (Rank 1);- Other Lines of International Separation (Rank 2); and- Special Lines (Rank 3).Rank 1 lines must be the most visually prominent. Rank 2 lines must be less visually prominent than Rank 1 lines. Rank 3 lines must be shown in a manner visually subordinate to Ranks 1 and 2. Where scale permits, Rank 2 and 3 lines must be labeled in accordance with the “Label” field. Data marked with a Rank 2 or 3 designation does not necessarily correspond to a disputed boundary.Additional cartographic information can be found in Guidance Bulletins (https://hiu.state.gov/data/cartographic_guidance_bulletins/) published by the Office of the Geographer and Global Issues.ContactDirect inquiries to internationalboundaries@state.gov.CreditsThe lines in the LSIB dataset are the product of decades of collaboration between geographers at the Department of State and the National Geospatial-Intelligence Agency with contributions from the Central Intelligence Agency and the UK Defence Geographic Centre.Attribution is welcome: U.S. Department of State, Office of the Geographer and Global Issues.Changes from Prior ReleaseThe 11.3 release is the third update in the version 11 series.This version of the LSIB contains changes and accuracy refinements for the following line segments. These changes reflect improvements in spatial accuracy derived from newly available source materials, an ongoing review process, or the publication of new treaties or agreements. Notable changes to lines include:• AFGHANISTAN / IRAN• ALBANIA / GREECE• ALBANIA / KOSOVO• ALBANIA/MONTENEGRO• ALBANIA / NORTH MACEDONIA• ALGERIA / MOROCCO• ARGENTINA / BOLIVIA• ARGENTINA / CHILE• BELARUS / POLAND• BOLIVIA / PARAGUAY• BRAZIL / GUYANA• BRAZIL / VENEZUELA• BRAZIL / French Guiana (FR.)• BRAZIL / SURINAME• CAMBODIA / LAOS• CAMBODIA / VIETNAM• CAMEROON / CHAD• CAMEROON / NIGERIA• CHINA / INDIA• CHINA / NORTH KOREA• CHINA / Aksai Chin• COLOMBIA / VENEZUELA• CONGO, DEM. REP. OF THE / UGANDA• CZECHIA / GERMANY• EGYPT / LIBYA• ESTONIA / RUSSIA• French Guiana (FR.) / SURINAME• GREECE / NORTH MACEDONIA• GUYANA / VENEZUELA• INDIA / Aksai Chin• KAZAKHSTAN / RUSSIA• KOSOVO / MONTENEGRO• KOSOVO / SERBIA• LAOS / VIETNAM• LATVIA / LITHUANIA• MEXICO / UNITED STATES• MONTENEGRO / SERBIA• MOROCCO / SPAIN• POLAND / RUSSIA• ROMANIA / UKRAINEVersions 11.0 and 11.1 were updates to boundary lines. Like this version, they also contained topology fixes, land boundary terminus refinements, and tripoint adjustments. Version 11.2 corrected a few errors in the attribute data and ensured that CC1 and CC2 attributes are in alignment with an updated version of the Geopolitical Entities, Names, and Codes (GENC) Standard, specifically Edition 3 Update 17.LayersLarge_Scale_International_BoundariesTerms of
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Alquist-Priolo Earthquake Fault Zoning Act (1972) and the Seismic Hazards Mapping Act (1990) direct the State Geologist to delineate regulatory "Zones of Required Investigation" to reduce the threat to public health and safety and to minimize the loss of life and property posed by earthquake-triggered ground failures. Cities and counties affected by the zones must regulate certain development "projects" within them. These Acts also require sellers of real property (and their agents) within a mapped hazard zone to disclose at the time of sale that the property lies within such a zone.
NOTE: Fault Evaluation Reports are available for those areas covered by a Regulatory Map however there are reports available for areas outside the Regulatory map boundary. For a complete set of maps available for purchase on CD please contact the CGS Library.
The official tax maps for the City of New York are maintained by the DEPARTMENT OF FINANCE Tax Map Office. Tax maps show the lot lines, the block and lot numbers, the street names, lot dimensions, and easements. Please see the following link for additional documentation- https://github.com/CityOfNewYork/nyc-geo-metadata/blob/master/Metadata/Metadata_DigitalTaxMap.md
Spreadsheets and graphs are powerful tools that make data come alive and tell a story. Now, use maps to see the story from another perspective. ArcGIS Maps for Office enables Microsoft Excel and PowerPoint users worldwide to ask location-related questions of data, get powerful insights, and make the best decisions. You can:Map your spreadsheet data – whether you want to see customer locations, ZIP code aggregations, custom sales territories and more – you can see it all.Add geographic context to your spreadsheet data and communicate these insights via interactive maps in PowerPoint.Gain insight into demographic, spending, behavior, and landscape information, among many more.Use the authoritative content on the ArcGIS platform to supplement your location data and add context to the locations in your spreadsheet.Securely share your maps with colleagues and stakeholders.Bring the power of the ArcGIS platform into your spreadsheets and presentations. To use ArcGIS Maps for Office you need an ArcGIS Online paid or trial subscription or a Portal for ArcGIS Named User License and Microsoft Office 2010, 2013, or 2016. Visit the online documentation for information on how to use this app.
Government Land Office maps (GLOs) are a result of the effort to survey all United States public lands before settlement. Starting in 1812 land was divided into square six mile blocks called townships, then subdivided into sections and ranges. Each subdivided area was surveyed and given its own map or GLO. During this process surveyors were required to indicate cultural resources such as roads and Indian trails and standardized symbols were used to represent geographic features. These GLOs are now maintained by the Bureau of Land Management as part of the official Land Status and Cadastral Survey records. As land was divided into parcels of individual ownership additional cadastral survey maps were created over time. For this reason there are often multiple GLOs or "cadastral survey maps" for one township / range, generally numbered one through four. For this seamless GLO layer, DAHP focused solely on the more historical GLOs which were usually listed as image number one or two for that specific township / range in the BLM Cadastral Survey records. In some cases no GLOs were available for review. Such areas included National Forest Lands, National Parks, Indian Reservations, and remote wilderness areas.
This website lists popular maps such as atlases for hunting and fishing and map resources such as a map index, mobile apps, and web and data services.
NOTICE TO PROVISIONAL 2023 LAND USE DATA USERS: Please note that on December 6, 2024 the Department of Water Resources (DWR) published the Provisional 2023 Statewide Crop Mapping dataset. The link for the shapefile format of the data mistakenly linked to the wrong dataset. The link was updated with the appropriate data on January 27, 2025. If you downloaded the Provisional 2023 Statewide Crop Mapping dataset in shapefile format between December 6, 2024 and January 27, we encourage you to redownload the data. The Map Service and Geodatabase formats were correct as posted on December 06, 2024.
Thank you for your interest in DWR land use datasets.
The California Department of Water Resources (DWR) has been collecting land use data throughout the state and using it to develop agricultural water use estimates for statewide and regional planning purposes, including water use projections, water use efficiency evaluations, groundwater model developments, climate change mitigation and adaptations, and water transfers. These data are essential for regional analysis and decision making, which has become increasingly important as DWR and other state agencies seek to address resource management issues, regulatory compliances, environmental impacts, ecosystem services, urban and economic development, and other issues. Increased availability of digital satellite imagery, aerial photography, and new analytical tools make remote sensing-based land use surveys possible at a field scale that is comparable to that of DWR’s historical on the ground field surveys. Current technologies allow accurate large-scale crop and land use identifications to be performed at desired time increments and make possible more frequent and comprehensive statewide land use information. Responding to this need, DWR sought expertise and support for identifying crop types and other land uses and quantifying crop acreages statewide using remotely sensed imagery and associated analytical techniques. Currently, Statewide Crop Maps are available for the Water Years 2014, 2016, 2018- 2022 and PROVISIONALLY for 2023.
Historic County Land Use Surveys spanning 1986 - 2015 may also be accessed using the CADWR Land Use Data Viewer: https://gis.water.ca.gov/app/CADWRLandUseViewer.
For Regional Land Use Surveys follow: https://data.cnra.ca.gov/dataset/region-land-use-surveys.
For County Land Use Surveys follow: https://data.cnra.ca.gov/dataset/county-land-use-surveys.
For a collection of ArcGIS Web Applications that provide information on the DWR Land Use Program and our data products in various formats, visit the DWR Land Use Gallery: https://storymaps.arcgis.com/collections/dd14ceff7d754e85ab9c7ec84fb8790a.
Recommended citation for DWR land use data: California Department of Water Resources. (Water Year for the data). Statewide Crop Mapping—California Natural Resources Agency Open Data. Retrieved “Month Day, YEAR,” from https://data.cnra.ca.gov/dataset/statewide-crop-mapping.
The documentation below is in reference to this items placement in the NM Supply Chain Data Hub. The documentation is of use to understanding the source of this item, and how to reproduce it for updatesTitle: OSE POD Locations Web-MapItem Type: URLSummary: GIS for Administering New Mexico's Water Resources. OSE POD Locations web-map. Source: Office of the State EngineerNotes: Prepared by: Uploaded by EMcRae_NMCDCSource: Office of the State EngineerFeature Service: https://nmcdc.maps.arcgis.com/home/item.html?id=9f5da56ad3734f90b8395cf4a41b07b4UID: 68,44Data Requested: water, water rights for agriculture, availability of waterMethod of Acquisition: Public map created and maintained by the Office of the State EngineerDate Acquired: May 2022Priority rank as Identified in 2022 (scale of 1 being the highest priority, to 11 being the lowest priority): 3Tags: PENDING
Spatial coverage index compiled by East View Geospatial of set "Bolivia Political Maps by Department". Source data from IGMB (publisher). Type: Thematic - Transportation. Scale: Varies. Region: South America.
[Metadata] Description: Agricultural Land Use Maps (ALUM) for islands of Kauai, Oahu, Maui, Molokai, Lanai and Hawaii as of 1978-1980. Sources: State Department of Agriculture; Hawaii Statewide GIS Program, Office of Planning. Note: August, 2018 - Corrected one incorrect record, removed coded value attribute domain.For more information on data sources and methodologies used, please refer to complete metadata at https://files.hawaii.gov/dbedt/op/gis/data/alum.pdf or contact Hawaii Statewide GIS Program, Office of Planning and Sustainable Development, State of Hawaii; PO Box 2359, Honolulu, HI 96804; (808) 587-2846; email: gis@hawaii.gov; Website: https://planning.hawaii.gov/gis.
The Digital Geologic-GIS Map of Vicksburg National Military Park, Mississippi and Louisiana is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (vick_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (vick_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (vick_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (vick_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (vick_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (vick_geology_metadata_faq.pdf). Please read the vick_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Mississippi State University, Department of Geosciences. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (vick_geology_metadata.txt or vick_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).
This web map created by the Colorado Governor's Office of Information Technology GIS team, serves as a basemap specific to the state of Colorado. The basemap includes general layers such as counties, municipalities, roads, waterbodies, state parks, national forests, national wilderness areas, and trails.Layers:Layer descriptions and sources can be found below. Layers have been modified to only represent features within Colorado and are not up to date. Layers last updated February 23, 2023. Colorado State Extent: Description: “This layer provides generalized boundaries for the 50 States and the District of Columbia.” Notes: This layer was filtered to only include the State of ColoradoSource: Esri Living Atlas USA States Generalized Boundaries Feature LayerState Wildlife Areas:Description: “This data was created by the CPW GIS Unit. Property boundaries are created by dissolving CDOWParcels by the property name, and property type and appending State Park boundaries designated as having public access. All parcel data correspond to legal transactions made by the CPW Real Estate Unit. The boundaries of the CDOW Parcels were digitized using metes and bounds, BLM's GCDB dataset, the PLSS dataset (where the GCDB dataset was unavailable) and using existing digital data on the boundaries.” Notes: The state wildlife areas layer in this basemap is filtered from the CPW Managed Properties (public access only) layer from this feature layer hosted in ArcGIS Online Source: Colorado Parks and Wildlife CPW Admin Data Feature LayerMunicipal Boundaries:Description: "Boundaries data from the State Demography Office of Colorado Municipalities provided by the Department of Local Affairs (DOLA)"Source: Colorado Information Marketplace Municipal Boundaries in ColoradoCounties:Description: “This layer presents the USA 2020 Census County (or County Equivalent) boundaries of the United States in the 50 states and the District of Columbia. It is updated annually as County (or County Equivalent) boundaries change. The geography is sources from US Census Bureau 2020 TIGER FGDB (National Sub-State) and edited using TIGER Hydrology to add a detailed coastline for cartographic purposes. Geography last updated May 2022.” Notes: This layer was filtered to only include counties in the State of ColoradoSource: Esri USA Census Counties Feature LayerInterstates:Description: Authoritative data from the Colorado Department of Transportation representing Highways Notes: Interstates are filtered by route sign from this CDOT Highways layer Source: Colorado Department of Transportation Highways REST EndpointU.S. Highways:Description: Authoritative data from the Colorado Department of Transportation representing Highways Notes: U.S. Highways are filtered by route sign from this CDOT Highways layer Source: Colorado Department of Transportation Highways REST EndpointState Highways:Description: Authoritative data from the Colorado Department of Transportation representing Highways Notes: State Highways are filtered by route sign from this CDOT Highways layer Source: Colorado Department of Transportation Highways REST EndpointMajor Roads:Description: Authoritative data from the Colorado Department of Transportation representing major roads Source: Colorado Department of Transportation Major Roads REST EndpointLocal Roads:Description: Authoritative data from the Colorado Department of Transportation representing local roads Source: Colorado Department of Transportation Local Roads REST EndpointRail Lines:Description: Authoritative data from the Colorado Department of Transportation representing rail lines Source: Colorado Department of Transportation Rail Lines REST EndpointCOTREX Trails:Description: “The Colorado Trail System, now titled the Colorado Trail Explorer (COTREX), endeavors to map every trail in the state of Colorado. Currently their are nearly 40,000 miles of trails mapped. Trails come from a variety of sources (USFS, BLM, local parks & recreation departments, local governments). Responsibility for accuracy of the data rests with the source.These data were last updated on 2/5/2019” Source: Colorado Parks and Wildlife CPW Admin Data Feature LayerNHD Waterbodies:Description: “The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.”Notes: This layer was filtered to only include waterbodies in the State of ColoradoSource: National Hydrography Dataset Plus Version 2.1 Feature LayerNHD Flowlines:Description: “The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.”Notes: This layer was filtered to only include flowline features in the State of ColoradoSource: National Hydrography Dataset Plus Version 2.1 Feature LayerState Parks:Description: “This data was created by the CPW GIS Unit. Property boundaries are created by dissolving CDOWParcels by the property name, and property type and appending State Park boundaries designated as having public access. All parcel data correspond to legal transactions made by the CPW Real Estate Unit. The boundaries of the CDOW Parcels were digitized using metes and bounds, BLM's GCDB dataset, the PLSS dataset (where the GCDB dataset was unavailable) and using existing digital data on the boundaries.” Notes: The state parks layer in this basemap is filtered from the CPW Managed Properties (public access only) layer from this feature layer Source: Colorado Parks and Wildlife CPW Admin Data Feature LayerDenver Parks:Description: "This dataset should be used as a reference to locate parks, golf courses, and recreation centers managed by the Department of Parks and Recreation in the City and County of Denver. Data is based on parcel ownership and does not include other areas maintained by the department such as medians and parkways. The data should be used for planning and design purposes and cartographic purposes only."Source: City and County of Denver Parks REST EndpointNational Wilderness Areas:Description: “A parcel of Forest Service land congressionally designated as wilderness such as National Wilderness Area.”Notes: This layer was filtered to only include National Wilderness Areas in the State of ColoradoSource: United States Department of Agriculture National Wilderness Areas REST EndpointNational Forests: Description: “A depiction of the boundaries encompassing the National Forest System (NFS) lands within the original proclaimed National Forests, along with subsequent Executive Orders, Proclamations, Public Laws, Public Land Orders, Secretary of Agriculture Orders, and Secretary of Interior Orders creating modifications thereto, along with lands added to the NFS which have taken on the status of 'reserved from the public domain' under the General Exchange Act. The following area types are included: National Forest, Experimental Area, Experimental Forest, Experimental Range, Land Utilization Project, National Grassland, Purchase Unit, and Special Management Area.”Notes: This layer was filtered to only include National Forests in the State of ColoradoSource: United States Department of Agriculture Original Proclaimed National Forests REST Endpoint
The National Transit Map - Agencies dataset was compiled on June 02, 2025 from the Bureau of Transportation Statistics (BTS) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The National Transit Map (NTM) is a nationwide catalog of fixed-guideway and fixed-route transit service in America. It is compiled using General Transit Feed Specification (GTFS) Schedule data. The GTFS Schedule documentation is available at, https://gtfs.org/schedule/. The NTM Agencies dataset represents the physical addresses of participating transit agencies. Regarding data coverage and licenses, starting in Report Year 2023, the Federal Transit Administration (FTA) has required National Transit Database (NTD) Reporters to submit General Transit Feed Specification (GTFS) data. Reporters will submit GTFS during their reporting period, which is determined by their fiscal year end date. All GTFS data submitted to the NTD will enter the public domain. Prior to the GTFS requirement, transit agencies voluntarily participated in the NTM and granted the U.S. Department of Transportation (USDOT) a Creative Commons Attribution 3.0 United States (CC-BY-3.0) license. The CC-BY-3.0 license is available at, https://creativecommons.org/licenses/by/3.0/us/legalcode. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529047
Minnesota's original public land survey plat maps were created between 1848 and 1907 during the first government land survey of the state by the U.S. Surveyor General's Office. This collection of more than 3,600 maps includes later General Land Office (GLO) and Bureau of Land Management maps up through 2001. Scanned images of the maps are available in several digital formats and most have been georeferenced.
The survey plat maps, and the accompanying survey field notes, serve as the fundamental legal records for real estate in Minnesota; all property titles and descriptions stem from them. They also are an essential resource for surveyors and provide a record of the state's physical geography prior to European settlement. Finally, they testify to many years of hard work by the surveying community, often under very challenging conditions.
The deteriorating physical condition of the older maps (drawn on paper, linen, and other similar materials) and the need to provide wider public access to the maps, made handling the original records increasingly impractical. To meet this challenge, the Office of the Secretary of State (SOS), the State Archives of the Minnesota Historical Society (MHS), the Minnesota Department of Transportation (MnDOT), MnGeo and the Minnesota Association of County Surveyors collaborated in a digitization project which produced high quality (800 dpi), 24-bit color images of the maps in standard TIFF, JPEG and PDF formats - nearly 1.5 terabytes of data. Funding was provided by MnDOT.
In 2010-11, most of the JPEG plat map images were georeferenced. The intent was to locate the plat images to coincide with statewide geographic data without appreciably altering (warping) the image. This increases the value of the images in mapping software where they can be used as a background layer.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
ECM Community Support Services tables for a Quarterly Implementation Report. Including the County and Plan Details for both ECM and Community Support.
This Medi-Cal Enhanced Care Management (ECM) and Community Supports Calendar Year Quarterly Implementation Report provides a comprehensive overview of ECM and Community Supports implementation in the programs' first year. It includes data at the state, county, and plan levels on total members served, utilization, and provider networks.
ECM is a statewide MCP benefit that provides person-centered, community-based care management to the highest need members. The Department of Health Care Services (DHCS) and its MCP partners began implementing ECM in phases by Populations of Focus (POFs), with the first three POFs launching statewide in CY 2022.
Community Supports are services that address members’ health-related social needs and help them avoid higher, costlier levels of care. Although it is optional for MCPs to offer these services, every Medi-Cal MCP offered Community Supports in 2022, and at least two Community Supports services were offered and available in every county by the end of the year.
DOUGLAS COUNTY SURVEY/GISGIS PARCEL MAPPING GUIDELINES FOR PARCEL DISCREPANCIESIt is the intent of the Douglas County GIS Parcel Mapping to accurately identify the areas of land parcels to be valued and taxed 1. Discrepancies in areas• The Auditor/Assessor (tax) acreage areas started with the original US General Land Office (GLO) township plat maps created from the Public Land Survey (PLS) that was done between 1858 and 1871. The recovery of the PLS corners and the accurate location of these corners with GPS obtained coordinates has allowed for accurate section subdivisions, which results in accurate areas for parcels based on legal descriptions, which may be significantly different than the original areas. (See Example 2)• Any parcel bordering a meandered lake and/or a water boundary will likely have a disparity of area between the Auditor/Assessor acreages and the GIS acreages because of the inaccuracy of the original GLO meander lines from which the original areas were determined. Water lines are not able to be drafted to the same accuracy as the normal parcel lines. The water lines are usually just sketched on a survey and their dimensions are not generally given on a land record. The water boundaries of our GIS parcels are located from aerial photography. This is a subjective determination based on the interpretation by the Survey/GIS technician of what is water. Some lakes fluctuate significantly and the areas of all parcels bordering water are subject to constant change. In these cases the ordinary high water line (OHW) is attempted to be identified. Use of 2-foot contours will be made, if available. (See Example 1)• Some land records do not accurately report the area described in the land description and the description area is ignored. (See Example 3)• The parcel mapping has made every attempt to map the parcels based on available survey information as surveyed and located on the ground. This may conflict with some record legal descriptions.Solutions• If an actual survey by a licensed Land Surveyor is available, it will be utilized for the tax acreage.• If the Auditor/Assessor finds a discrepancy between the tax and GIS areas, they will request a review by the County Survey/GIS department.• As a starting guideline, the County Survey/GIS department will identify all parcels that differ in tax area versus GIS parcel area of 10 % or more and a difference of at least 5 acres. (This could be expanded later after the initial review.)• Each of these identified parcels will be reviewed individually by the County Survey/GIS department to determine the reason for the discrepancy and a recommendation will be made by the County Survey/GIS department to the Auditor/Assessor if the change should be made or not.• If a change is to be made to the tax area, a letter will be sent to the taxpayer informing them that their area will be changed during the next tax cycle, which could affect their property valuation. This letter will originate from the Auditor/Assessor with explanation from the County Survey/GIS department. 2. Gaps and Overlaps• Land descriptions for adjoining parcels sometimes overlap or leave a gap between them.o In these instances the Survey/GIS technician has to make a decision where to place this boundary. A number of circumstances are reviewed to facilitate this decision as these dilemmas are usually decided on a case by case basis. All effort will be made to not leave a gap, but sometimes this is not possible and the gap will be shown with “unknown” ownership. (Note: The County does not have the authority to change boundaries!)o Some of the circumstances reviewed are: Which parcel had the initial legal description? Does the physical occupation of the parcel line as shown on the air photo more closely fit one of the described parcels? Interpretation of the intent of the legal description. Is the legal description surveyable?Note: These overlaps will be shown on the GIS map with a dashed “survey line” and accompanying text for the line not used for the parcel boundary. 3. Parcel lines that do not match location of buildings Structures on parcels do not always lie within the boundaries of the parcel. This may be a circumstance of building without the benefit of a survey or of misinterpreting these boundaries. The parcel lines should be shown accurately as surveyed and/or described regardless of the location of structures on the ground. NOTE: The GIS mapping is not a survey, but is an interpretation of parcel boundaries predicated upon resources available to the County Survey/GIS department.Gary Stevenson Page 1 7/21/2017Example 1Example 2A Example 2B Example 3
CPD Maps includes data on the locations of existing CDBG, HOME, public housing and other HUD-funded community assets, so that users can view past investments geographically when considering various strategies for future funding. CPD Maps offers a large amount of data in a way that is easy to access. The website allows grantees and the general public to easily search, query, and display information to identify trends and analyze the needs of their community.
National Center for Veterans and Analysis Statistics Population Maps are a compilation of facts related to the count of Veterans at multiple geographies.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
HCAI Emergency Operations Center Application for Earthquakes, Fires, PSPS.
Several different government offices have published the Daily weather maps over its history. The publication has also gone by different names over time. The U.S. Signal Office began publication of the maps as the War Department maps on Jan. 1, 1871. When the government transferred control of the weather service to the newly-created Weather Bureau in 1891 the title changed to the Department of Agriculture weather map. In 1913 the title became simply Daily weather map. Eventually, in 1969, the Weather Bureau began publishing a weekly compilation of the daily maps with the title Daily weather maps (Weekly series). The the principal charts are the Surface Weather Map, the 500 Millibar Height Contours Chart, the Highest and Lowest Temperatures chart and the Precipitation Areas and Amounts chart. This library contains a very small subset of this series: 11Sep1928-31Dec1928, 01Jan1959-30Jun1959, and 06Jan1997-04Jan1998.
Contains:World HillshadeWorld Street Map (with Relief) - Base LayerLarge Scale International Boundaries (v11.3)World Street Map (with Relief) - LabelsDoS Country Labels DoS Country LabelsCountry (admin 0) labels that have been vetted for compliance with foreign policy and legal requirements. These labels are part of the US Federal Government Basemap, which contains the borders and place names that have been vetted for compliance with foreign policy and legal requirements.Source: DoS Country Labels - Overview (arcgis.com)Large Scale International BoundariesVersion 11.3Release Date: December 19, 2023DownloadFor more information on the LSIB click here: https://geodata.state.gov/ A direct link to the data is available here: https://data.geodata.state.gov/LSIB.zipAn ISO-compliant version of the LSIB metadata (in ISO 19139 format) is here: https://geodata.state.gov/geonetwork/srv/eng/catalog.search#/metadata/3bdb81a0-c1b9-439a-a0b1-85dac30c59b2 Direct inquiries to internationalboundaries@state.govOverviewThe Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. The current edition is version 11.3 (published 19 December 2023). The 11.3 release contains updates to boundary lines and data refinements enabling reuse of the dataset. These data and generalized derivatives are the only international boundary lines approved for U.S. Government use. The contents of this dataset reflect U.S. Government policy on international boundary alignment, political recognition, and dispute status. They do not necessarily reflect de facto limits of control.National Geospatial Data AssetThis dataset is a National Geospatial Data Asset managed by the Department of State on behalf of the Federal Geographic Data Committee's International Boundaries Theme.DetailsSources for these data include treaties, relevant maps, and data from boundary commissions and national mapping agencies. Where available and applicable, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery process involves analysis of satellite imagery and elevation data. Due to the limitations of source materials and processing techniques, most lines are within 100 meters of their true position on the ground.Attribute StructureThe dataset uses thefollowing attributes:Attribute NameCC1COUNTRY1CC2COUNTRY2RANKSTATUSLABELNOTES These attributes are logically linked:Linked AttributesCC1COUNTRY1CC2COUNTRY2RANKSTATUS These attributes have external sources:Attribute NameExternal Data SourceCC1GENCCOUNTRY1DoS ListsCC2GENCCOUNTRY2DoS ListsThe eight attributes listed above describe the boundary lines contained within the LSIB dataset in both a human and machine-readable fashion. Other attributes in the release include "FID", "Shape", and "Shape_Leng" are components of the shapefile format and do not form an intrinsic part of the LSIB."CC1" and "CC2" fields are machine readable fields which contain political entity codes. These codes are derived from the Geopolitical Entities, Names, and Codes Standard (GENC) Edition 3 Update 18. The dataset uses the GENC two-character codes. The code ‘Q2’, which is not in GENC, denotes a line in the LSIB representing a boundary associated with an area not contained within the GENC standard.The "COUNTRY1" and "COUNTRY2" fields contain human-readable text corresponding to the name of the political entity. These names are names approved by the U.S. Board on Geographic Names (BGN) as incorporated in the list of Independent States in the World and the list of Dependencies and Areas of Special Sovereignty maintained by the Department of State. To ensure the greatest compatibility, names are presented without diacritics and certain names are rendered using commonly accepted cartographic abbreviations. Names for lines associated with the code ‘Q2’ are descriptive and are not necessarily BGN-approved. Names rendered in all CAPITAL LETTERS are names of independent states. Other names are those associated with dependencies, areas of special sovereignty, or are otherwise presented for the convenience of the user.The following fields are an intrinsic part of the LSIB dataset and do not rely on external sources:Attribute NameMandatoryContains NullsRANKYesNoSTATUSYesNoLABELNoYesNOTESNoYesNeither the "RANK" nor "STATUS" field contains null values; the "LABEL" and "NOTES" fields do.The "RANK" field is a numeric, machine-readable expression of the "STATUS" field. Collectively, these fields encode the views of the United States Government on the political status of the boundary line.Attribute NameValueRANK123STATUSInternational BoundaryOther Line of International Separation Special Line A value of "1" in the "RANK" field corresponds to an "International Boundary" value in the "STATUS" field. Values of "2" and "3" correspond to "Other Line of International Separation" and "Special Line", respectively.The "LABEL" field contains required text necessarily to describe the line segment. The "LABEL" field is used when the line segment is displayed on maps or other forms of cartographic visualizations. This includes most interactive products. The requirement to incorporate the contents of the "LABEL" field on these products is scale dependent. If a label is legible at the scale of a given static product a proper use of this dataset would encourage the application of that label. Using the contents of the "COUNTRY1" and "COUNTRY2" fields in the generation of a line segment label is not required. The "STATUS" field is not a line labeling field but does contain the preferred description for the three LSIB line types when lines are incorporated into a map legend. Using the "CC1", "CC2", or "RANK" fields for labeling purposes is prohibited.The "NOTES" field contains an explanation of any applicable special circumstances modifying the lines. This information can pertain to the origins of the boundary lines, any limitations regarding the purpose of the lines, or the original source of the line. Use of the "NOTES" field for labeling purposes is prohibited.External Data SourcesGeopolitical Entities, Names, and Codes Registry: https://nsgreg.nga.mil/GENC-overview.jspU.S. Department of State List of Independent States in the World: https://www.state.gov/independent-states-in-the-world/U.S. Department of State List of Dependencies and Areas of Special Sovereignty: https://www.state.gov/dependencies-and-areas-of-special-sovereignty/The source for the U.S.—Canada international boundary (NGDAID97) is the International Boundary Commission: https://www.internationalboundarycommission.org/en/maps-coordinates/coordinates.phpThe source for the “International Boundary between the United States of America and the United States of Mexico” (NGDAID82) is the International Boundary and Water Commission: https://catalog.data.gov/dataset?q=usibwcCartographic UsageCartographic usage of the LSIB requires a visual differentiation between the three categories of boundaries. Specifically, this differentiation must be between:- International Boundaries (Rank 1);- Other Lines of International Separation (Rank 2); and- Special Lines (Rank 3).Rank 1 lines must be the most visually prominent. Rank 2 lines must be less visually prominent than Rank 1 lines. Rank 3 lines must be shown in a manner visually subordinate to Ranks 1 and 2. Where scale permits, Rank 2 and 3 lines must be labeled in accordance with the “Label” field. Data marked with a Rank 2 or 3 designation does not necessarily correspond to a disputed boundary.Additional cartographic information can be found in Guidance Bulletins (https://hiu.state.gov/data/cartographic_guidance_bulletins/) published by the Office of the Geographer and Global Issues.ContactDirect inquiries to internationalboundaries@state.gov.CreditsThe lines in the LSIB dataset are the product of decades of collaboration between geographers at the Department of State and the National Geospatial-Intelligence Agency with contributions from the Central Intelligence Agency and the UK Defence Geographic Centre.Attribution is welcome: U.S. Department of State, Office of the Geographer and Global Issues.Changes from Prior ReleaseThe 11.3 release is the third update in the version 11 series.This version of the LSIB contains changes and accuracy refinements for the following line segments. These changes reflect improvements in spatial accuracy derived from newly available source materials, an ongoing review process, or the publication of new treaties or agreements. Notable changes to lines include:• AFGHANISTAN / IRAN• ALBANIA / GREECE• ALBANIA / KOSOVO• ALBANIA/MONTENEGRO• ALBANIA / NORTH MACEDONIA• ALGERIA / MOROCCO• ARGENTINA / BOLIVIA• ARGENTINA / CHILE• BELARUS / POLAND• BOLIVIA / PARAGUAY• BRAZIL / GUYANA• BRAZIL / VENEZUELA• BRAZIL / French Guiana (FR.)• BRAZIL / SURINAME• CAMBODIA / LAOS• CAMBODIA / VIETNAM• CAMEROON / CHAD• CAMEROON / NIGERIA• CHINA / INDIA• CHINA / NORTH KOREA• CHINA / Aksai Chin• COLOMBIA / VENEZUELA• CONGO, DEM. REP. OF THE / UGANDA• CZECHIA / GERMANY• EGYPT / LIBYA• ESTONIA / RUSSIA• French Guiana (FR.) / SURINAME• GREECE / NORTH MACEDONIA• GUYANA / VENEZUELA• INDIA / Aksai Chin• KAZAKHSTAN / RUSSIA• KOSOVO / MONTENEGRO• KOSOVO / SERBIA• LAOS / VIETNAM• LATVIA / LITHUANIA• MEXICO / UNITED STATES• MONTENEGRO / SERBIA• MOROCCO / SPAIN• POLAND / RUSSIA• ROMANIA / UKRAINEVersions 11.0 and 11.1 were updates to boundary lines. Like this version, they also contained topology fixes, land boundary terminus refinements, and tripoint adjustments. Version 11.2 corrected a few errors in the attribute data and ensured that CC1 and CC2 attributes are in alignment with an updated version of the Geopolitical Entities, Names, and Codes (GENC) Standard, specifically Edition 3 Update 17.LayersLarge_Scale_International_BoundariesTerms of