Open Landmarks / Contribute
Bring a place
you know.
A good contribution is recognizable, correctly placed and inexpensive to render. How you make it is up to you.
Choose your tools
Model in Blender by hand, use procedural scripts, or use AI assistance. You do not need the original author's generator, an AI subscription or access to a private service. Submit an editable Blender source and two GLBs. Disclose AI assistance and other third-party inputs in the metadata.
Keep the architecture, lose the weight
Prioritize the silhouette, major roof forms, openings and structural rhythm. Aim for fewer than 8,000 triangles, six materials and six draw calls; each GLB must be at most 250 kB before compression. V1 uses opaque, texture-free materials, static triangles and applied transforms. Include a genuinely simpler LOD when it preserves the silhouette.
Prepare a submission
- Copy the metadata template into
collection/your-landmark/asset.json. - Add
detail.glb,low.glb,source.blend.gz,spatial-source.jsonand a smallpreview.webp. - Record the OSM IDs, versions, geometry and timestamp; list reference authors, source pages and licenses. Do not copy imagery from commercial maps.
- Run
npm cithennpm run validate. Fill in exact byte counts and SHA-256 hashes. Existing submissions are complete examples. - Submit a pull request to the collection repository once it is published. Keep the review state pending; maintainers approve the exact content revision.
The repository is being prepared for publication. Downloads and the submission format are available here now.
What gets reviewed
Automated checks cover glTF validity, hashes, size budgets, transforms, normals, triangles, materials and declared 3D bounds. A maintainer also checks footprint fit, architectural identity, multiple camera angles, lightness, night lighting, basemap overlap and licensing. Passing the validator alone does not approve a model.
What you agree to share
Your original artistic contribution is offered under CC BY 4.0; OSM-derived spatial data remains under ODbL 1.0. Provide editable source and provenance alongside the exports. You can keep your production tools private, provided you can grant the submitted rights and meet the source-data obligations. Read the full component policy.