Geometry parcel recalculating #381

Closed
opened 9 months ago by mpeltriaux · 1 comments
Owner

Status quo

In case of errors on linked services, the parcel calculation might fail, leading to a never-ending spinner on the spatial reference box.

There should be some sort of recalculation being triggered somehow.

Improvement

Each time a client requests the parcels of a geometry using the GeomParcelsView, certain checks are done to differ between states like in-the-making or no-results. However, since the background process (in celery) can not be watched by the view class directly, we need to extent the Geometry model in a way, that we can directly see whether the process of calculating is still running.

If the process is "still running" but a certain time has passed, we can assume the process died in one or another way. In this case the GeomParcelsView shall trigger the calculation again.

# Status quo In case of errors on linked services, the parcel calculation might fail, leading to a never-ending spinner on the spatial reference box. There should be some sort of recalculation being triggered somehow. # Improvement Each time a client requests the parcels of a geometry using the `GeomParcelsView`, certain checks are done to differ between states like in-the-making or no-results. However, since the background process (in celery) can not be watched by the view class directly, we need to extent the `Geometry` model in a way, that we can directly see whether the process of calculating is still running. If the process is "still running" but a certain time has passed, we can assume the process died in one or another way. In this case the `GeomParcelsView` shall trigger the calculation again.
mpeltriaux added the
enhancement
label 9 months ago
mpeltriaux self-assigned this 9 months ago
mpeltriaux referenced this issue from a commit 9 months ago
mpeltriaux added reference geom_parcel_improvements 8 months ago
Poster
Owner

Merged in #384

# Merged in #384
mpeltriaux closed this issue 8 months ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: IT-Naturschutz/konova#381
Loading…
There is no content yet.