Document Puerto Rico urbanization semantics for address_levels (v2.0.0 / 2026-09-23.1)

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

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
38/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
documentation

Direzione di ricerca

Start from overture-schema-theme-addresses/src/overture/schema/addresses/address.py, especially the AddressLevel model and its country-dependent address_levels slots. Then trace the release 2026-09-23.1/schema v2.0.0 address configuration and source handling for NAD and OpenAddresses, looking for any URB/Urbnztn_PR role or omission. Done means the docs explicitly state whether Puerto Rico urbanization is encoded, its slot/index convention, unknown-slot handling, and any provider-specific behavior, or state that it is intentionally omitted.

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

Descrizione

external

Could you point to the authoritative Puerto Rico address hierarchy and contributor conversion contract used by the addresses theme in release 2026-09-23.1 (schema v2.0.0)?

The selected AddressLevel model defines country-dependent ordered slots and preserves unknown positions, but does not identify a Puerto Rico urbanization role. A generic US locality example or the separate divisions-theme Puerto Rico rule would not establish that address role.

Specifically, a documentation/configuration pointer would help resolve:

  1. Whether and how this release represents Puerto Rico in country, separately from jurisdiction/coverage assumptions.
  2. Whether USPS-style urbanization is encoded in address_levels, and the exact slot/index convention and hierarchy distinguishing it from municipality, barrio, sector, other area name and postal city.
  3. Whether the rule differs by sources.provider/resource/version, including NAD and OpenAddresses, and any contributor-specific renaming or omission of URB/Urbnztn_PR.
  4. Required unknown/absent-slot and ambiguity handling, and the release-applicable converter/configuration revision or specification.
  5. If urbanization is not encoded for this release, an explicit omission statement would also resolve the documentation gap. We will not infer it from the last nonempty slot or postal_city.

No address records, personal data or private implementation details are requested; a public field/role contract or configuration pointer is sufficient. This is a schema/lineage question, not a request for license clearance or a deployment approval.

Lingua principale
Python
Stelle
220
Fork
22
Merge medio
2g 20h
PR unite (30g)
19

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 OvertureMaps/schema

Tutte le issue di OvertureMaps/schema

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.