Publish v2 catalog regions from the Public API's own region reference files
Los mantenedores suelen responder en 3 días
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 38/100
Línea de trabajo
Start by locating the v2 region publication code and the certified data release inputs that provide row filters and weight matrices; the issue does not name specific files or tests. Check how the current PolicyEngine.py region registry feeds /v2/regions, then trace how region reference files should select households. Done means publication uses repository-owned references, rejects unavailable selectors, and omits US places that cannot run.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What
The Public API should publish the regions of each v2 catalog version from region reference files it keeps in its own repository, one per country, instead of copying PolicyEngine.py's region registry.
Each file should list every region's code, label, type, parent and US state, the value that selects its households, and the v1 identifier it replaces (for example country/ni and constituency/Aldershot). Publication should then give each region its dataset and filter from the certified data release that PolicyEngine.py ships:
- US states and congressional districts, and UK nations: a row filter (a column and a value).
- UK constituencies and local authorities: the release's weight matrix and the region's row code in it.
It should refuse to publish a region the data cannot select, and leave out regions that cannot run yet (US places).
Why
- Today
/v2/regionslists only the regions PolicyEngine.py's registry exposes: 5 UK regions, and 333 US places that would calculate national figures if run as listed. - UK constituencies and local authorities are missing, and are known in v1 by name rather than by ONS code.
- The registry's region lists and filters change with each PolicyEngine.py release, and nothing checks them against the data.
With reference files owned by the Public API, the catalog lists all 1,015 UK regions by ONS code, uses "United States" and "United Kingdom" as the national labels, and fails loudly when a filter column or matrix row is missing.
- Lenguaje dominante
- Python
- Estrellas
- 18
- Forks
- 33
- Merge medio
- 2 d 18 h
- PR fusionados (30 d)
- 36
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de PolicyEngine/policyengine-api
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
PolicyEngine/policyengine-api#3911 ·
Los mantenedores suelen responder en 3 días
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
PolicyEngine/policyengine-api#3910 ·
Los mantenedores suelen responder en 3 días
-
Remove the v1 user routes and keep complete simulation and report results finalPosiblemente ocupada @MaxGhenis la tomó hoy. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
PolicyEngine/policyengine-api#4028 ·
Los mantenedores suelen responder en 3 días
-
Store the metadata v3 reads in the v2 catalog, from PolicyEngine.py's public recordsPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
PolicyEngine/policyengine-api#4022 ·
Los mantenedores suelen responder en 3 días
-
Remove the routes only the legacy site used, check health at /health, and stop serving Canada, Nigeria and IsraelPosiblemente ocupada @anth-volk la tomó hace 1 día. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
PolicyEngine/policyengine-api#4016 ·
Los mantenedores suelen responder en 3 días
Todos los issues de PolicyEngine/policyengine-api
Issues similares
-
[Resource]: LoreAbiertoresource-submission validation-passed
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
hesreallyhim/awesome-claude-code#3234 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
openminion/openminion#376 ·
Los mantenedores suelen responder en 1 día
-
Type: ☹︎ Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
posit-dev/great-tables#1028 ·
Los mantenedores suelen responder en 1 día
-
integration: apple_tv
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
home-assistant/core#188282 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
A "since" range is worded as a career: "the past two seasons" says "regular season career (2025 on)"AbiertoP4: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
jeffknupp/association#538 ·