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
The workflow should handle errors gracefully (Write to disk and continue).
The input: ?
The output should be useful: Should be possible to be opened in QGIS.
The text was updated successfully, but these errors were encountered:
matthiasschaub
changed the title
Define a workflow to compute indicator/topic combinations for input geometries
How to compute many indicator/topic combinations for a lot of input geometries?
Jun 20, 2023
From what I've learned from the oqt-for-food-envs project:
Input:
I allowed multiple files holding multiple features. That way you could have a file per Region and each region can consist of multiple parts. Therefore, you can choose features with a better suited area size to calculate for.
As I wanted to add further information on my side, I imported the features on my side and sent them to OQT as single features. I added a check if the data is in WGS84 and if not an automated reprojection as first step, otherwise the "further information" is may calculated only for the OQT analysis to fail afterwards
Workflow:
Due to the metadata request bug, the request should be repeated twice if the return is a 500 Internal Server Error. Therefore, the result should be checked as soon as it comes back to allow that
An async calculation of reports for 5 NUTS-3 regions could easily be carried out and saves lot's of time. Definitely recommend this, but as bullet above stays, check result immediately after return and may repeat. Number of simoultanious calculations should be checked and could may be increased
Output:
Visualization in QGIS can be really helpful. Therefore, you may want to add the resulting class as an attribute by itself
In order to work with the attribute table in QGIS you should not save the html return/svg figure as attribute to the feature. QGIS can handle those long fields quite bad, therefore, scrolling sideways takes very long as it tries to load those fields (>1min for bavarian NUTS-3 regions)
The workflow should handle errors gracefully (Write to disk and continue).
The input: ?
The output should be useful: Should be possible to be opened in QGIS.
The text was updated successfully, but these errors were encountered: