Appearance
Attribution and Credits
InsightMaps is built with open-source tools, commercial mapping technology, and public data sources. Proper attribution is required by law and helps credit the organizations that make this service possible.
How to Attribute InsightMaps Outputs
When sharing maps, screenshots, or analysis results from InsightMaps, include the following attributions:
Required Attribution Text
Powered by Esri | Data: [Data Source Names] | Created with InsightMapsExample:
Powered by Esri | Data: Tasmanian Government (LIST), Geoscience Australia | Created with InsightMapsWhere to Include Attribution
- Printed Maps: Bottom margin or legend area
- Digital Maps: On-screen text or image caption
- Reports: Footer or data sources section
- Social Media: In post caption or image text
- Presentations: On each slide containing map content
Mapping Technology Credits
Esri ArcGIS
InsightMaps uses the ArcGIS Maps SDK for JavaScript for map display and interaction.
Required Attribution: "Powered by Esri" must be displayed prominently on all maps and map-based outputs.
License: Maps are subject to Esri's Terms of Use
In-App Attribution: The map view includes automatic attribution in the bottom-right corner. Do not remove this attribution.
ArcGIS Licensing Model
The ArcGIS Maps SDK for JavaScript itself carries no license fee. Costs only arise when your application consumes Esri-hosted services (basemaps, geocoding, routing) beyond the free monthly thresholds. If the SDK is pointed at your own data sources (tile servers, GeoJSON, WMS/WMTS, ArcGIS Enterprise), there are no per-transaction charges from Esri.
Important: Even when not consuming Esri services, all obligations under the Esri Master License Agreement still apply — including "Powered by Esri" attribution, no SDK modification, and no wrapping under copyleft licenses.
Free Tier (ArcGIS Location Platform)
Every ArcGIS Location Platform account — free to create, no credit card required — includes monthly service allowances:
| Service | Free Monthly Allowance | Pay-as-You-Go Overage |
|---|---|---|
| Basemap tiles (vector/raster/static) | 2,000,000 tiles | $0.15 per 1,000 tiles |
| Basemap sessions (Oct 2025+) | 1,000 sessions (up to 12 hrs each) | $4 per 1,000 sessions |
| Geocoding (not stored) | 20,000 requests | $0.50 per 1,000 |
| Geocoding (stored/batch) | No free tier | $4 per 1,000 |
| Simple routing | 20,000 routes | $0.50 per 1,000 |
| Service areas | 5,000 requests | $50 per 1,000 |
| Places search | 500 requests | $8 per 1,000 |
| Elevation | 50,000 points | $1 per 1,000 |
| Feature storage | 250 MB | $0.0044/MB |
| Tile/file storage | 250 MB | $0.00012/MB |
If usage stays within these limits, there is no charge. If limits are exceeded without pay-as-you-go billing enabled, services are disabled until the next billing cycle — no surprise charges. Commercial use is explicitly permitted on the free tier.
Session-based pricing (introduced October 2025) offers an alternative to per-tile billing: one flat fee per session covers unlimited tile loads during that session, making costs more predictable for high-traffic apps.
Advanced services like optimized routing ($50/1,000), fleet routing ($100/1,000), data enrichment ($1/1,000 attributes), and spatial analysis ($0.10/1,000 features) have no free tier and require pay-as-you-go to be activated.
Licensing Paths for Commercial Use
Esri offers three paths for commercial deployment:
- ArcGIS Location Platform — The primary path for new developers. Free account with metered pay-as-you-go billing in USD. No annual commitments or termination fees. Commercial deployment permitted on the free tier.
- ArcGIS Online (Organizational Subscription) — Annual credit-based model with named user licenses (Viewer, Creator, Professional). Basemap layers and non-stored geocoding do not consume credits under ArcGIS Online.
- ArcGIS Enterprise — Self-hosted infrastructure. The SDK works with your own ArcGIS Server services without API keys or per-transaction costs. A traditional software license negotiated directly with Esri.
SDK-Only Use (No Esri Services)
If your application uses the ArcGIS Maps SDK but connects only to your own data sources or third-party ArcGIS servers (e.g., government servers), no API key is required and no usage limits apply. Attribution ("Powered by Esri") and all MLA obligations still apply.
June 2024 Transition
In June 2024, Esri deprecated the ArcGIS Developer Subscription and consolidated developer offerings under ArcGIS Location Platform. The old free "Essentials" plan had been limited to non-commercial use — the new Location Platform accounts removed this restriction, allowing commercial deployment even on the free tier.
Legacy API Key Retirement (June 2026)
API keys created before June 2024 entered "mature support" and will be fully retired in June 2026. New API key credentials offer improved security with configurable expiration, referrer URL restrictions, service-specific scoping, and key rotation. All applications should migrate to the new credential system before the deadline.
Master License Agreement (MLA) Restrictions
The Esri Master License Agreement (E204) governs all use of the ArcGIS Maps SDK. Key restrictions:
- Code integrity: You cannot modify, decompile, reverse-engineer, or disassemble the SDK. You can use and redistribute it without modification, but cannot create derivative works of the SDK itself.
- Open-source contamination: You cannot combine or subject the SDK to open-source licenses (such as GPL) that would require the Esri code to be disclosed in source form, licensed for derivative works, or redistributed at no charge.
- AI/ML restrictions: You cannot use Esri data (basemaps, geocoding results, etc.) outside of the Software and Online Services to train artificial intelligence or machine learning systems.
- Redistribution: You can build and sell applications ("Value-Added Applications") that use the SDK, but you cannot package and resell the SDK itself or provide third parties direct access to Esri products so they can build their own GIS applications.
- Trial/educational licenses: Trial licenses are for testing only (not commercial), educational licenses are solely for educational purposes with no revenue generation, and grant program licenses are noncommercial only.
For the full terms, see the Esri Master License Agreement.
Note: Esri licensing terms, pricing, and free tier limits change periodically. The information above reflects terms as of early 2026. Always verify current terms directly at developers.arcgis.com or by contacting Esri. For commercial distribution questions, contact Esri Sales or Esri Australia for region-specific guidance. This is not legal advice.
Calcite Design System
User interface components are built with Esri's Calcite Design System.
License: Apache License 2.0
Data Source Credits
InsightMaps aggregates geospatial data from multiple sources. Each data layer has its own license and attribution requirements.
Australian Federal Government
Common Sources:
- Geoscience Australia - National mapping and geoscience data
- Australian Bureau of Statistics - Census and boundary data
- Bureau of Meteorology - Weather and climate data
Typical License: Creative Commons Attribution 4.0 International (CC BY 4.0)
Attribution Format:
Data Source: [Agency Name], Australian Government
License: CC BY 4.0Example:
Data Source: Geoscience Australia, Australian Government
License: CC BY 4.0
Accessed: February 2026State and Territory Government Data
Each Australian state and territory publishes geospatial data under open licenses:
| State/Territory | Data Portal | Common License |
|---|---|---|
| Tasmania | data.thelist.tas.gov.au | CC BY 3.0 AU |
| Victoria | data.vic.gov.au | CC BY 4.0 |
| Queensland | data.qld.gov.au | CC BY 4.0 |
| South Australia | data.sa.gov.au | CC BY 4.0 |
| New South Wales | data.nsw.gov.au | CC BY 4.0 |
| Western Australia | data.wa.gov.au | CC BY 4.0 |
| Northern Territory | data.nt.gov.au | Varies |
| ACT | data.act.gov.au | CC BY 4.0 |
Attribution Format:
Data Source: [Agency/Department Name], [State] Government
License: Creative Commons Attribution [version]
Accessed: [Date]Example (Tasmania):
Data Source: Land Information System Tasmania (LIST), Tasmanian Government
License: Creative Commons Attribution 3.0 Australia (CC BY 3.0 AU)
Accessed: February 2026Local Council Data
Some datasets come from local government councils. Each council may have different terms:
- Check the specific council's open data policy
- Attribution is typically required
- Commercial use may require permission
Contact the relevant council if you're unsure about their data terms.
Third-Party ArcGIS Services
InsightMaps may connect to third-party ArcGIS Server endpoints operated by government agencies or other organizations:
- Data ownership remains with the original provider
- Attribution requirements are set by the data provider
- Access terms may change over time
When using layers from InsightMaps, check the layer metadata for specific attribution requirements.
Creative Commons License Requirements
Most Australian government data is licensed under Creative Commons Attribution (CC BY) licenses. When using CC BY data, you must:
- ✅ Give appropriate credit to the original creator
- ✅ Provide a link to the license (e.g., https://creativecommons.org/licenses/by/4.0/)
- ✅ Indicate if changes were made (e.g., data filtered, styled, or combined)
- ❌ Do not suggest endorsement by the data provider
Derivative Work Examples:
- "Original data from [Source] modified by applying filters for residential zoning"
- "Map combines data from [Source A] and [Source B], styled for presentation"
- "Analysis based on [Source] data, aggregated to regional level"
Example CC BY Attribution
Based on data from Geoscience Australia (CC BY 4.0)
Available at: https://data.gov.au
Data filtered and styled for InsightMaps analysisOpen Source Software
InsightMaps uses several open-source libraries and tools. Key acknowledgments:
| Library | License | Purpose |
|---|---|---|
| Vue.js | MIT | Frontend framework |
| TypeScript | Apache 2.0 | Type-safe development |
| Vite | MIT | Build tool |
| Tailwind CSS | MIT | Styling framework |
| Calcite Components | Apache 2.0 | UI components |
For a complete list of dependencies, see the package.json file in the source code.
Important Notes
Data Ownership
- All data remains owned by the original providers
- InsightMaps does not claim ownership of any third-party data
- Using data through InsightMaps does not transfer ownership rights
No Endorsement
- Data providers do not endorse InsightMaps or any outputs created with the service
- Do not suggest that government agencies or other data providers endorse your use of their data
Terms Can Change
- Data licenses and attribution requirements can change over time
- Review current terms before distributing outputs
- Check data provider websites for the latest license information
Verify Before Important Use
For critical projects (publications, legal documents, commercial products):
- Verify current license terms with the data provider
- Confirm attribution requirements
- Check if additional permissions are needed
- Keep records of license versions and access dates
Commercial Use
Attribution requirements apply equally to commercial and non-commercial use. Commercial users should:
- Verify that data licenses permit commercial use (most CC BY licenses do)
- Keep records of data sources and attribution for compliance audits
- Review data provider terms for any additional commercial restrictions
Copyright Concerns
If you believe content using InsightMaps violates copyright:
- Review our Terms of Use for DMCA procedures
- Contact [email protected] for takedown requests
- Include specific details about the infringing content
Getting Help with Attribution
If you're unsure about attribution requirements:
- Check the layer metadata in InsightMaps for specific attribution text
- Visit the data provider's website for their attribution guidelines
- Contact the data provider directly for clarification
- Email us at [email protected] if you need help identifying data sources
Quick Attribution Checklist
Before sharing InsightMaps outputs:
- [ ] "Powered by Esri" is visible
- [ ] All data sources are credited by name
- [ ] License types are mentioned (e.g., CC BY 4.0)
- [ ] No claim of data ownership is made
- [ ] No suggestion of provider endorsement
- [ ] Attribution is clearly readable
- [ ] Links to licenses are included (where practical)
Last updated: March 7, 2026