Establish contribution flow for reverse-geocoding polygons in OpenSAK-Data

Aperta
  • Qualcosa non va?
#776 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
json
Ambito
data, documentation

Direzione di ricerca

The work is a new CONTRIBUTING.md in the OpenSAK-Data repo, not code. Use the existing translation contribution process as the model, and confirm the ODbL attribution wording with maintainers before drafting. Done means the file covers the listed points: polygon file format, naming, licensing consent, PR flow and manual review. Optional GeoJSON CI checks are out of scope for the first pass.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: geo-data feature
Image
Problem Statement

Charles Suprin reached out on Facebook offering Bermuda parish polygons generated with the ConvertOSMtoPolygon script, which would bring OpenSAK's reverse-geocoding data more in line with project-gc. Currently several Bermuda parishes are missing from our data (see attached map comparison — the white/empty areas).

We currently have no defined process for accepting this kind of community contribution, even though the demand exists and the value (more accurate, more complete reverse-geocoding coverage) is clear.

Proposed Solution

Define and document a lightweight contribution flow for OpenSAK-Data, similar in spirit to our existing translation contribution process.

Proposed scope
Write a CONTRIBUTING.md (or similar) for the OpenSAK-Data repo describing:
Expected file format/structure for polygon submissions
Naming conventions
ODbL licensing consent/attribution requirements for submitted data
PR-based submission process (PR can be opened by the contributor, Fabio, or Allan)
Optional: basic CI validation on PRs (valid GeoJSON syntax, no self-intersecting polygons, naming convention check)
Manual review/vetting step before merge (at least initially — no automated acceptance)
Out of scope (tracked separately)
Any in-app feature to let users load/run their own local polygon files (see #777)

Lingua principale
Python
Stelle
37
Fork
17
Merge medio
16h 7m
PR unite (30g)
128

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenSAK-Org/OpenSAK

Tutte le issue di OpenSAK-Org/OpenSAK

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.