Skip to content
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

How to compute many indicator/topic combinations for a lot of input geometries? #592

Open
matthiasschaub opened this issue Jun 20, 2023 · 1 comment
Labels
brainstorming Idea for a potential new feature or adaption that still needs further discussion

Comments

@matthiasschaub
Copy link
Collaborator

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.

@matthiasschaub 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
@matthiasschaub matthiasschaub added the brainstorming Idea for a potential new feature or adaption that still needs further discussion label Jun 20, 2023
@hn437
Copy link
Contributor

hn437 commented Jun 27, 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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
brainstorming Idea for a potential new feature or adaption that still needs further discussion
Projects
None yet
Development

No branches or pull requests

2 participants