So far a previous map request could be chosen for re-render, but only with the very same settings as originally chosen.
Now there’s finally a “Reedit” button along with the “Recreate” one, allowing you to chose an existing map and then going through the edit dialogs with the original choices being pre-selected, but changeable.
Disclaimer: this is still work in progress, it works well for geographic area selection, but there is only limited support for maps based on a chosen administrative area, and any uploaded files will no longer be present.
Several things that happened after the July server update, but never got mentioned yet:
map list and detail pages now show the map queue a map job is assigned to, and lists can be filtered by queue
on file upload you can now choose “delete after render”, and even preserved uploads will eventually be purged after a year max.
while a map is rendered more detailed status updates than just “rendering” will be shown, giving some insight into rendering progress
individual rendered files are displayed as soon as they are ready, and not just after all files have completely been generated
multi colored GPX tracks now also work in the multi page format
an Umap overlay style regression introduced by the earlier rewrite has been fixed, markers are now shown using correct style information again
OpenStreetMap Carto default map style has been upgraded from version 5.2.0 to current 5.7.0 release
as the v5.7 database schema is no loner fully backwards compatible with all the other stiles there are now two planet databases in parallel, one for Openstreetmap cart, and one for all the other styles
After running the current machine for almost two and a half years now I decided it was time for an operating system update and some cleanups, including a fresh OSM data re-import. While I was on it I also switched from Ubuntu to Debain, as I had already done for my development / test VMs for a while now.
The migration is mostly complete now, things currently still missing are:
* The local Weblate translation instance is not back yet. I’m not sure what the actual problem is here and need to read myself into the topic once more, this may take another week or two. * The OpenArdenneStyle and some of the OpenOrienteeringMap styles are still disabled for now due to problems, these should be back by the end of the week latest * Some of the images in this blog got lost (I would like to blame WordPress, but have to confess that it was completely my fault after all)
If you find any other problem that I may not be aware of yet please do not hesitate to get in touch with me via email@example.com
There have been two incidents where rendering stopped for several hours this weekend (see the yellow curve in the monitoring graph), and it could hardly happen at a worse time, wit me traveling and attending FOSDEM in Brussels.
I hope to have identified the root cause so that it should not happen again, and even if it does I’d get aware of it earlier, now that I’m back at home again …
So far only two types of indexes were supported: the classic street index with a fixed predefined set of additional points of interest added, and the custom map marker index only available via the alternative neighborhood POI frontend.
Soon it will be possible to choose from a variety of different indexes retrieved from the OSM database for different use cases, e.g. the first additional index being a healthcare index showing clinics, doctors, pharmacies etc.
This will not really be visible, but after several years of just trying to keep this project alive and adding some new stuff here and there it’s now become overdue to show the code base some more love and do an overall cleanup.
I’m aiming for:
improving the comment situation in general
making sure all functions and methods have proper docstrings
converting existing docstrings to NumPi format
removing dead / unused code
replacing the old test code with proper unit and integration tests
Starting with the OCitysMap code, and then the Django web frontend and API code later.
This code base has gone through a few hands, and I never really was a “Python Guy”, only really having learned Python “on the go”, so lots of this cleanup will actually be about improving code added by my earlier self when I was in sort of a “Python Brogrammer” state and didn’t know better yet.