This dataset contains shapefile boundaries for CA State, counties and places from the US Census Bureau's 2023 MAF/TIGER database. Current geography in the 2023 TIGER/Line Shapefiles generally reflects the boundaries of governmental units in effect as of January 1, 2023.
Download high-quality, up-to-date United States shapefile boundaries (SHP, projection system SRID 4326). Our United States Shapefile Database offers comprehensive boundary data for spatial analysis, including administrative areas and geographic boundaries. This dataset contains accurate and up-to-date information on all administrative divisions, zip codes, cities, and geographic boundaries, making it an invaluable resource for various applications such as geographic analysis, map and visualization, reporting and business intelligence (BI), master data management, logistics and supply chain management, and sales and marketing. Our location data packages are available in various formats, including Shapefile, GeoJSON, KML, ASC, DAT, CSV, and GML, optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more. Companies choose our location databases for their enterprise-grade service, reduction in integration time and cost by 30%, and weekly updates to ensure the highest quality.
This city boundary shapefile was extracted from Esri Data and Maps for ArcGIS 2014 - U.S. Populated Place Areas. This shapefile can be joined to 500 Cities city-level Data (GIS Friendly Format) in a geographic information system (GIS) to make city-level maps.
This dataset is a compilation of county parcel data from Minnesota counties that have opted-in for their parcel data to be included in this dataset.
It includes the following 55 counties that have opted-in as of the publication date of this dataset: Aitkin, Anoka, Becker, Benton, Big Stone, Carlton, Carver, Cass, Chippewa, Chisago, Clay, Clearwater, Cook, Crow Wing, Dakota, Douglas, Fillmore, Grant, Hennepin, Houston, Isanti, Itasca, Jackson, Koochiching, Lac qui Parle, Lake, Lyon, Marshall, McLeod, Mille Lacs, Morrison, Mower, Murray, Norman, Olmsted, Otter Tail, Pennington, Pipestone, Polk, Pope, Ramsey, Renville, Rice, Saint Louis, Scott, Sherburne, Stearns, Stevens, Traverse, Waseca, Washington, Wilkin, Winona, Wright, and Yellow Medicine.
If you represent a county not included in this dataset and would like to opt-in, please contact Heather Albrecht (Heather.Albrecht@hennepin.us), co-chair of the Minnesota Geospatial Advisory Council (GAC)’s Parcels and Land Records Committee's Open Data Subcommittee. County parcel data does not need to be in the GAC parcel data standard to be included. MnGeo will map the county fields to the GAC standard.
County parcel data records have been assembled into a single dataset with a common coordinate system (UTM Zone 15) and common attribute schema. The county parcel data attributes have been mapped to the GAC parcel data standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html
This compiled parcel dataset was created using Python code developed by Minnesota state agency GIS professionals, and represents a best effort to map individual county source file attributes into the common attribute schema of the GAC parcel data standard. The attributes from counties are mapped to the most appropriate destination column. In some cases, the county source files included attributes that were not mapped to the GAC standard. Additionally, some county attribute fields were parsed and mapped to multiple GAC standard fields, such as a single line address. Each quarter, MnGeo provides a text file to counties that shows how county fields are mapped to the GAC standard. Additionally, this text file shows the fields that are not mapped to the standard and those that are parsed. If a county shares changes to how their data should be mapped, MnGeo updates the compilation. If you represent a county and would like to update how MnGeo is mapping your county attribute fields to this compiled dataset, please contact us.
This dataset is a snapshot of parcel data, and the source date of the county data may vary. Users should consult County websites to see the most up-to-date and complete parcel data.
There have been recent changes in date/time fields, and their processing, introduced by our software vendor. In some cases, this has resulted in date fields being empty. We are aware of the issue and are working to correct it for future parcel data releases.
The State of Minnesota makes no representation or warranties, express or implied, with respect to the use or reuse of data provided herewith, regardless of its format or the means of its transmission. THE DATA IS PROVIDED “AS IS” WITH NO GUARANTEE OR REPRESENTATION ABOUT THE ACCURACY, CURRENCY, SUITABILITY, PERFORMANCE, MECHANTABILITY, RELIABILITY OR FITINESS OF THIS DATA FOR ANY PARTICULAR PURPOSE. This dataset is NOT suitable for accurate boundary determination. Contact a licensed land surveyor if you have questions about boundary determinations.
DOWNLOAD NOTES: This dataset is only provided in Esri File Geodatabase and OGC GeoPackage formats. A shapefile is not available because the size of the dataset exceeds the limit for that format. The distribution version of the fgdb is compressed to help reduce the data footprint. QGIS users should consider using the Geopackage format for better results.
https://www.ontario.ca/page/open-government-licence-ontariohttps://www.ontario.ca/page/open-government-licence-ontario
The Ontario Watershed Boundaries (OWB) collection represents the authoritative watershed boundaries for Ontario. The data is based on a framework similar to the Atlas of Canada Fundamental Drainage Areas and the United States Watershed Boundary Dataset, however it adopts a more stringent scientific approach to watershed delineation. The Ontario Watershed Boundaries (OWB) collection includes five data classes:OWB Main (OWB) (Download: Shapefile | File Geodatabase | Open Data Service | QGIS Layer )all watershed levels from primary to quaternary, and level 5 and 6 watersheds for select areas of the province;OWB Primary (OWBPRIM) (Download: SHP | FGDB | ODS | QLR-Diverted Flow | QLR-Natural Flow)all primary watersheds or major drainage areas (WSCMDA) in the Canadian classification;OWB Secondary (OWBSEC) (Download: SHP | FGDB | ODS | QLR*)all secondary watersheds or sub drainage areas (WSCSDA);OWB Tertiary (OWBTERT) (Download: SHP | FGDB | ODS | QLR*)all tertiary watersheds or sub-sub drainage areas (WSCSSDA);OWB Quaternary (OWBQUAT) (Download: SHP | FGDB | ODS | QLR)all quaternary watersheds or 6-digit drainage areas (WSC6).*Display issues in QGIS are currently being investigated for these services. See the RSS feed below for details.IMPORTANT NOTE: The OWB data replaces the following data classes:Provincial Watersheds, HistoricalAdditional DocumentationUser Guide for Ontario Watershed Boundaries (Word)Watershed Delineation Principles and Guidelines for Ontario (Word) Atlas of Canada 1,000,000 National Frameworks Data, Hydrology - Fundamental Drainage Areas United States Geological Survey Watershed Boundary Dataset (Website)
Status Completed: Production of the data has been completed
Maintenance and Update Frequency Irregular: data is updated in intervals that are uneven in duration - usually after the completion of major updates to source data (e.g. OIH), but could also include spot updates and expansion of the dataset over time based on user needs. RSS FeedFollow our feed to get the latest announcements and developments concerning our watersheds. Visit our feed at the bottom of our ArcGIS Online OWB page.
Contact Ontario Ministry of Natural Resources - Geospatial Ontario, geospatial@ontario.ca
Not seeing a result you expected?
Learn how you can add new datasets to our index.
This dataset contains shapefile boundaries for CA State, counties and places from the US Census Bureau's 2023 MAF/TIGER database. Current geography in the 2023 TIGER/Line Shapefiles generally reflects the boundaries of governmental units in effect as of January 1, 2023.