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

Analysis completed with no impact layer #528

Open
lucernae opened this issue Mar 19, 2019 · 4 comments
Open

Analysis completed with no impact layer #528

lucernae opened this issue Mar 19, 2019 · 4 comments

Comments

@lucernae
Copy link
Collaborator

lucernae commented Mar 19, 2019

Some analysis like this:

https://geonode.ingc.gov.mz/geosafe/analysis/219

Has completed with no impact layer.
But, since we already implemented Task Diagnostics, when the task completed, we can be sure that the task itself returned with no errors. Which means, possibly there is something wrong with the data.

Possible cause:

  • The analysis has completed but since there are no impact, the impact layer is empty.
  • The hazard or exposures have some misconfiguration in the InaSAFE keywords. Some info might be doesn't match up, which causes InaSAFE doesn't found the geometry/features affected and returned no impact layer
@gubuntu
Copy link
Contributor

gubuntu commented Mar 19, 2019

in at least one case this is because the hazard layer has InaSAFE 5 keywords instead of 4.4

@lucernae lucernae self-assigned this Mar 19, 2019
@lucernae lucernae added the bug label Mar 19, 2019
@lucernae
Copy link
Collaborator Author

Yeah, currently trying to download the layer to know the actual issue

@gubuntu
Copy link
Contributor

gubuntu commented Mar 19, 2019

just look at the metadata detail

@lucernae
Copy link
Collaborator Author

For this particular layer, it turns out that this layer: https://geonode.ingc.gov.mz/geosafe/analysis/219 has no metadata upload (xml).
Not sure how this happens in the first place, but I just reupload the metadata, fix the upload session for this particular layer so it can have xml file, fix the extent to be consistent with metadata from the admin page, then rerun analysis.
All analysis that uses this as its exposure layer now runs fine.
So this is just data problem. I think we can close this.

The reason why the original impact analysis return None is because the exposure layer doesn't have keywords (as a file), so the analysis completed (no features), but no impact layer produced (zero analysis).

I think we can close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants