-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Postnord data download fails when trying to push git changes #2
Comments
Hi Johan, Cool that you're interested in the project! May I ask if you're trying to reuse the data and what for? I'm always curious about reuses! 😃 You are right, something is wrong with this script. I just applied a quick fix by changing the time the script is run (now 1 hour after the other one). This project in't active now but the goal was to create voronoi polygons for the areas of each postcode. If you're interested, it could be a cool technical challenge. |
Hey, Sounds like an interesting challenge! What's the intended use case for that? I mean, I'm not entirely sure how well it would map to exactly what streets fall into each postcode.. I guess voronoi polygons would be a reasonable estimation of the relative size of the areas covered though, for making comparisons across different parts of the country? 🤔 Anyhow, I actually ended up here because I was looking for a way to keep an updated list of all valid postcodes, perhaps on a weekly or monthly basis. It was nice to see that the PostNord API can be used with just the first three digits, to fetch a whole subset of postcodes at once. That certainly reduces the number of API calls one has to make! |
The use case is to have an open alternative to the monopoly of postnummerservice. Postcode information is open data in many country and it should be in Sweden too. Maybe you've heard of Postnummerupproret, a project from @peterk and @kodapan. It was the same idea but using OSM to gather data. Some info I gathered while investigating for this project:
|
It seems the Postnord job fails pretty much all the time:
This is probably because the OSM data download finishes first, and has already pushed a new commit to the repo, causing the Postnord push to fail due to being behind:
It's probably easy to fix by just following the suggestion and doing a "git pull" (on both jobs to be safe I guess), or one could set the jobs up to run sequentially in GitHub Actions instead.
The text was updated successfully, but these errors were encountered: