1. How licensing works
2. Per-order attribution
attribution.json file at the root listing:- Every upstream source used to produce the bundle.
- The license each source carries.
- The required attribution string for that license.
3. No downstream restrictions
Mantle Place does not, through these terms or any other policy, attempt to contractually restrict any downstream redistribution rights granted to you by the upstream licenses.
What you do with your bundle is bounded by the upstream licenses, not by us. If a source license permits commercial reuse, that permission travels with your bundle. If a source license requires share-alike, that obligation travels too.
4. Produced Works & vector layers (ODbL architecture)
Most Mantle Place outputs (rasterized basemaps, meshed terrain, extruded building massing, and baked deliverables) are architected to qualify as Produced Works under the Open Database License (ODbL), not as Derivative Databases. In practical terms:
- Those outputs are computed from the upstream database, not a redistribution of the database itself.
- The ODbL Share-Alike clause applies to Derivative Databases. A Produced Work is not a Derivative Database, so downstream rendering of those outputs is not required to be open-sourced.
The exception is the structured vector layers in your bundle's Vector/ folder (building footprints, roads, water, land use, and land cover as GeoPackage, GeoJSON, Shapefile, and FlatGeobuf). These are licensed to you as a database under the ODbL:
- Attribution is always required, exactly as listed in your bundle.
- If you adapt that vector data and redistribute it as a database, the ODbL share-alike obligation applies to the redistributed database.
- Renders, meshes, and other Produced Works you create from those layers are not subject to share-alike.
5. Your responsibilities
- Including the attribution strings from
attribution.jsonin any user-facing surface where attribution is required. - Honoring source-specific obligations (e.g., ODbL share-alike where it applies, CC-BY attribution requirements, terms attached to public-domain corrections).
- Verifying that your downstream use is compatible with the upstream licenses listed in your bundle.