Norway states partially obsolete, partially missing

Abierto
#814 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
38/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
json, python
Área
data

Línea de trabajo

The outdated data is in nor.geojson, the Norwegian boundary file in the boundary date pack. Start by finding where the pack is built or loaded in the repository and how the state names are matched. The source for the post-2024 Norwegian county polygons and the missing Trøndelag and Møre og Romsdal entries is not in the payload, so confirm it with a maintainer first. Done means the file reflects the 1 January 2024 regions and both missing states load.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area: geo-data improvement
Current State

I have boundary date pack version 47.

  • The Norwegian state polygons describe how the states were before 1. januar 2024.
  • Two Norwegian states are missing from the file nor.geojson (‘Trøndelag’ and ‘Møre og Romsdal’). These two states were the only Norwegian states that, at the time, contained a non-English letter. I am not sure if that is relevant, but it’s the only thing that is ‘special’ with these two states compared to the other states.
Proposed Improvement
  • Update the boundary data with the new polygons as of 1. januar 2024.
Expected Benefits
  • Up-to-date polygons are obviously more useful than outdated ones.
Environment

OS: Windows 11 Enterprise Version 23H2
OS Build: 22631.7517
Processor: 12th Gen Intel(R) Core(TM) i7-12850HX 2.10 GHz
RAM: 64.0 GB

OpenSAK v1.18.0 beta 3

Lenguaje dominante
Python
Estrellas
37
Forks
17
Merge medio
21 h 5 min
PR fusionados (30 d)
131

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenSAK-Org/OpenSAK

Todos los issues de OpenSAK-Org/OpenSAK

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.