# Proposed Santiago, Putumayo building import

Status: draft for community consultation. No OSM upload is authorized or has
been performed.

## Goal and scope

Add missing building footprints within the 3.391 km² valid-data footprint of
the 29 November 2025 OpenAerialMap survey of Santiago, Putumayo, Colombia. The
active review queue contains 573 candidate features representing 724
provisional roof units. These figures describe a review workload, not a final
building count. Expanding the area or adding another feature type would require
a new consultation.

## Sources and licenses

- OpenAerialMap survey “Santiago Putumayo”: sole visual validation imagery,
  CC BY 4.0, contributed by Jorge Froilan Mallama Botina.
- `hotosm/dinov3s-buildings`: open building-segmentation model, used to produce
  candidate geometry from the OAM imagery.
- Microsoft Global Building Footprints: CDLA-Permissive-2.0, used for candidate
  geometry and corroboration.
- Live OpenStreetMap: used only for duplicate and conflation checks.
- IGAC and Google Open Buildings: excluded from queue processing and all
  shareable/import geometry.

The exact source URLs, versions, dates, hashes, and notices are recorded in
`source_manifest.json`. License compatibility and attribution will be confirmed
with the OSM community before the import proceeds.

## Preparation

1. Compare every candidate with the OAM imagery.
2. Keep an existing polygon only when its entire outline accurately matches the
   visible roof.
3. Correct or retrace inaccurate, merged, offset, or incomplete outlines.
4. Reject false positives and defer uncertain structures.
5. Re-query live OSM immediately before each batch and remove or conflate every
   overlap; proximity alone is never treated as a duplicate.
6. Run geometry checks for validity, self-intersections, unexpected overlaps,
   tiny parts, and outliers before upload.

No candidate is automatically accepted. The public reviewer stores decisions
locally and can export them by candidate ID for reproducible QA.

## OSM tagging

Accepted objects will normally receive `building=yes`. A more specific building
value will be used only when the imagery or another permitted source makes it
verifiable. Candidate IDs, model scores, and internal processing fields will
not be added as permanent OSM tags.

Proposed changeset metadata:

- comment: `Add reviewed buildings in Santiago, Putumayo`
- source: `OpenAerialMap; Microsoft Global Building Footprints`
- imagery_used: the exact Santiago OAM survey
- import documentation URL and review forum URL

## Accounts, batches, and QA

- Use a dedicated import account linked to the operator's normal OSM account
  and this plan.
- After community approval and the required review period, begin with a compact
  10–20-building test changeset.
- Ask the community to inspect that changeset before continuing.
- Later changesets will remain compact and contain at most 50 buildings.
- Pause immediately if reviewers identify a systematic geometry, conflation,
  licensing, or tagging problem.
- Track all candidate IDs, decisions, corrections, and resulting OSM changeset
  IDs in a public progress record.

## Reversion

Record every import changeset and keep each batch geographically compact. If a
systematic problem is found, stop the import, notify the forum thread, and
revert the affected complete changesets. Ask the Data Working Group or an
experienced local mapper for help if a clean revert is uncertain.

## Published materials

- Interactive full queue: https://rowan-cooper-selected-work.robrothepro.chatgpt.site/projects/santiago-building-screening/
- Methodology: `AI_BUILDING_OUTLINE_PIPELINE.md`
- Review protocol: `OSM_PILOT_PROTOCOL.md`
- Source manifest: `source_manifest.json`
- Queue summary: `review_queue_summary.json`
- Candidate GeoJSON: `review_queue.geojson`
- Processing source code: published beside the viewer as
  `docs/santiago_ai_pass.py` and `docs/build_review_queue.py`
- OSM Colombia discussion: to be added after the initial post

## Approval gate

Do not upload until the documentation is public, source-license questions are
resolved, the OSM Colombia community has had the formal review opportunity, at
least 14 days have passed after the complete import-review post, and all raised
concerns have been addressed.