Giters

firetools / qgis2fds

An open source and free tool to export terrain elevation, landuse, and georeferencing to NIST FDS for computational fluid dynamics (CFD) wildfire or atmospheric pollutants dispersion simulations.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Some suggestions

mcgratta opened this issue · comments

commented

I have a few suggestions

  1. Is it possible for the Plugin Manager in QGIS to indicate what version of qgis2fds is installed. Currently, I see Version 1.0.1 from February, even tough a change was recently made. It would be helpful to somehow indicate the exact git hash or maintenance version.
  2. Look at this window
    image
    The path to the landuse type file points to my qgis2fds repository. If I send someone else my .qgz file, my specific folder information is included. Can we somehow not have this specific path locked in? I guess the larger question is can we minimize the inclusion of specific paths in the .qgz file. This could help new users get started faster.
  3. The qgis2fds pop-up window sometimes gets lost behind the larger QGIS window. Is there a way to prevent this? It sometimes seems as if we have lost contact.

We can discuss more at the next Friday meeting. These are just a few things that tripped us up today.

commented

  1. This is my fault, I fixed the #48 issue and forgot to bump the qgis2fds version to 1.0.2. It should be ok now.

  2. Yes. QGIS creates absolute paths by default. So, whenever I start working on a new case, I create a directory and copy the config files there (eg. Landfire.gov_F13.csv). Then I replace the default absolute path with a relative one ./Landfire.gov_F13.csv, relative to the path where I saved my .qgz file. All the example cases have relative paths.

  3. This is QGIS, rough on the edges... let me investigate a bit more on that. I probably should open an upstream QGIS issue on that.

I am on a field trip on Friday, I am not sure I am going to make it.

commented

To add to the list of suggestions:

  1. It would be nice to have more control of the mesh configuration and the Z domain extent. Just specifying the number of meshes would be good if we always just needed to run qgis2fds once and then make any necessary mods to the MESH lines. But I am finding that I need to run things many times to fine tune my setup. Then I have to adjust the MESH lines and Z extent each time.
commented

I added the git hash to my branch. You will need to install "gitpython" to the python environment which QGIS uses and add your git executable to the path QGIS uses. The commit won't show up if either of those are not found. You can test if you have the git environment set up correctly by typing "import git" into the python console in QGIS.

image