Add StreetComplete as a downstream mapping tool

[spwoodcock]

What StreetComplete exposes for integration now

1. geo:lat,lon?z=zoom intent: moves the camera to a point. That's it for location.
2. streetcomplete://s?... URL scheme: configures which quest types are enabled (for mapping parties). No geometry parameters.
3. Nothing else. No API, no ContentProvider, no way to receive polygons/GeoJSON, no bounding box parameter, no result callback.

What we could achieve right now

• The absolute best-case today: generate a geo: intent that opens StreetComplete centered on the task centroid.
• The user then just uses SC normally with no task boundary awareness.
• This is essentially a "launch the app at a location" button, not an integration.
• There's also no coordination, no task tracking, no boundary enforcement.

What would need to change for feasible integration

At a minimum: area restriction via intent, to accept a polygon/bbox and only show quests within it.
Bonus: some callback or webhook when quests are answered within the area, to update our mapping status (not essential).

These would be feature requests for StreetComplete, and the maintainers have historically kept the app deliberately simple and opinionated, avoiding mission creep: a tall order to be honest, but we could try.

[linear]

TECH-1110

[spwoodcock]

We could also consider targetting https://github.com/Helium314/SCEE, a fork of StreetComplete, with some more advanced config options.

SCEE added a "Custom Geometry" display feature in v60.1:

• Loads a GeoJSON file and renders it on the map: polygons get a semi-transparent fill + outline
• Supports name property for labeling
• Toggle on/off in Display Settings

Realistic workflow

1. User creates a project in Field-TM, selects "SCEE" as the mapping tool
2. Field-TM generates a GeoJSON file of their task area polygon
3. User downloads the GeoJSON to their phone (via QR code link, direct download, etc.)
4. User opens SCEE → Settings → Display Settings → Custom Geometry → selects the file
5. The task boundary appears on the map as a purple overlay
6. User maps quests within that boundary

Far from ideal, but workable (manual loading, no area enforcement, no completion tracking, uses a fork of StreetComplete...).

Closing for now.