Licensing & Data Source Notices
CountyGISMaps packages are built for commercial, internal, and client-facing work. You can use purchased packages to create maps, reports, dashboards, applications, and analyses. What you cannot do is redistribute the raw package files, resell the raw data, or use the packages to build a competing raw-data or download service.
In Short
- Yes: commercial use, internal use, client deliverables, and derivative outputs
- No: raw-file redistribution, sublicensing, raw-data resale, and competing raw-data services
- Sometimes required: source attribution or provider notices for specific package contents
Overview
When you buy a CountyGISMaps package, you are buying a licensed compilation of source data, documentation, formatting, packaging, and value-added work. Our package license gives you broad rights to use that package in real commercial workflows. It does not erase or override upstream source restrictions where a provider requires attribution, notice, or special handling.
Many federal datasets in our packages are public domain or broadly public-use, but not every package component comes with the same source posture. That is why package docs include items such as README.txt, LICENSE.txt, PROVIDER_NOTICES.txt, and docs/DATA_GUIDE.md.
What You Can Do
- Use paid packages for internal business work
- Use paid packages in client services, consulting, and deliverables
- Create derivative maps, reports, models, dashboards, and applications
- Share package outputs within the licensed organization for normal internal use
- Use derived outputs commercially, including in reports, analysis, and customer work
What You Cannot Do
- Redistribute the raw package files as-is outside the licensed use case
- Resell the raw package data as a standalone product
- Sublicense the package or raw files to third parties without permission
- Strip provider notices, source notices, or embedded license materials where they apply
- Use the package to create, seed, or materially support a competing raw-data website, API, marketplace, or download service
Source-Specific Notices
| Source | In package? | Public domain? | Attribution / notice |
|---|---|---|---|
| U.S. Census Bureau | Yes | Generally yes | Citation recommended in public-facing work |
| NOAA | Yes | Generally yes | Citation recommended in reports, dashboards, and publications |
| NCES | Yes | Public / public-use | Citation recommended |
| Overture-derived places | Yes | Mixed / open | Preserve Overture and upstream notices for raw or near-raw redistribution of business_places or similar outputs |
| USPS-derived ZIP directory data | Yes | Treat conservatively | Do not assume public-domain status for raw USPS-derived ZIP directory content. Review USPS / PostalPro terms before republishing raw directory-style outputs |
| USGS / The National Map services | Sometimes / derived outputs | Yes | For derived map-service outputs include: “Map services and data available from U.S. Geological Survey, National Geospatial Program.” |
| USGS MRLC NLCD | Yes | Yes | Use the recommended USGS annual NLCD citation in publications and presentations |
For outputs derived from USGS The National Map services, include: “Map services and data available from U.S. Geological Survey, National Geospatial Program.”
Best Practices for Public Use
- Keep source credits visible in public-facing maps, dashboards, reports, and articles
- Preserve provider notices where package docs say they apply
- Avoid redistributing raw source extracts or near-raw package files unless permitted
- Check the package docs when using housing data, business places, ZIP directory content, or basemap-derived outputs publicly
Questions
If you are unsure whether a planned use is covered, contact us before distribution or launch.
See also Terms of Service and Use, Contact, and the package documentation included with your download.