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

[Bug] There's no "Extent Selection" in Impact Function Centric Wizard #1957

Closed
adisadit opened this issue May 25, 2015 · 3 comments
Closed

Comments

@adisadit
Copy link

Problem

I'm using Impact Function Centric Wizard (Building and Flood hazard) and didn't have any layer in my layer list. So after i select my hazard and exposure data from my directory, the next section is not the "Aggregation" and "Extent Selection" instead it appear Error message like this:
image
Which is really strange because i'm using training data that already in same datum and already intersect/overlap each other.
This error only appear if you don't have any layer in layer list and you decide to pick from your computer directory. If you already load your layer and use that layer for wizard, it didn't appear that kind of bug/

Step for producing this error

  • Open InaSAFE Impact Function Centric Wizard
  • Select Structure with Flood Hazard
  • Select the data from disk/directory

Operating System

I'm using QGIS 2.8 Wien and using both InaSAFE 3.0 (from repo) and InaSAFE 3.2 (from github)

@lucernae
Copy link
Collaborator

@adissadis can I have more specific information on what are the layer filenames which is used?

@adisadit
Copy link
Author

@lucernae i'm using building_osm_jakarta with hazard data using both flood_hkv_current_jakarta and flood_osm_bpbd18113_Jakarta

@ismailsunni
Copy link
Member

@borysiasty can you make sure that this won't happen in the new wizard?

The problem only occurs when the user select layer from disk. All is fine if the user select the layer from QGIS.

borysiasty added a commit that referenced this issue Jun 17, 2015
[IFCWizard] Fix test for layer overlap. Fixes #1957
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants