You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I add nodes/routes to a node network I want to check if there are any mistakes so I can fix them quickly.
However, the update cycle is about 8 hours, so likely doesn't include my latest changes.
I would like changes to be automatically incorporated (like #368 ) or a button I can click to trigger the analysis again.
I think manual re-analysis is easier to implement while work on #368 continues.
To prevent DOS, it is smart to add two conditions on triggering the re-analysis:
User must be logged in with an OSM account
Last analysis is at least 5 minutes ago
The text was updated successfully, but these errors were encountered:
@spaanse dankjewel voor deze suggestie en jou inspanningen bij het in kaart brengen van nieuwe knooppuntroutes (ik volg jouw avonturen een beetje via het forum)
The node network analysis already processes all changes automatically. Most of the time the impact of your changes should be visible in knooppuntnet within 5 or 10 minutes.
So all pages under following urls should be near up-to-date all the time:
However, yesterday (October 4th) around 10:16 a problem started with the process of getting the data from OpenStreetMap into knooppuntnet. The replication became very very slow until it stopped completely. This is why you did not see your updates. At this moment replication is working again, and the database is slowly catching up. The database should be up-to-date again later today.
The automatic update does not work yet for the monitoring functionality:
When I add nodes/routes to a node network I want to check if there are any mistakes so I can fix them quickly.
However, the update cycle is about 8 hours, so likely doesn't include my latest changes.
I would like changes to be automatically incorporated (like #368 ) or a button I can click to trigger the analysis again.
I think manual re-analysis is easier to implement while work on #368 continues.
To prevent DOS, it is smart to add two conditions on triggering the re-analysis:
The text was updated successfully, but these errors were encountered: