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.
GNU General Public License v3.0
17 stars 13 forks source link

How to set qgis2fds to NOT shift coordinates during FDS code generation? #95

Open donish-getstand opened 3 days ago

donish-getstand commented 3 days ago

I am generating FDS code from a digital terrain map (UTM 10 N) using the :

processing.run("Export to NIST FDS:Export terrain", {
    'chid': CHID,
    'fds_path': OUTPUT_PATH,
    'extent': EXTENT,
    'pixel_size': 1,
    'origin': None,
    'dem_layer': INPUT_FILE,
    'landuse_layer': None,
    'landuse_type_filepath': '',
    'fire_layer': None,
    'wind_filepath': '',
    'tex_layer': None,
    'tex_pixel_size': 10,
    'nmesh': NUMBER_OF_MESHES,
    'cell_size': CELL_SIZE,
    'export_obst': True,
    'debug': False
})

But, qgis2fds centers the data based on the EXTENT's centroid. How do I adjust the settings so that all of the coordinates (x,y,z in UTM 10 N) are preserved when going to fds?

I've tried put (0, 0) and (500000, 0), which is the origin for UTM 10N in for the 'origin' parameter, but with no luck. The x, y, and even z coordinates experiences a shift.

Any help would be greatly appreciated!

emanuelegissi commented 17 hours ago

Hi Donish, this is an interesting request. Let me take a look at it. I am very busy these days, it is going to take some time. Emanuele

Il giorno sab 16 nov 2024 alle ore 17:36 donish-getstand < @.***> ha scritto:

I am generating FDS code from a digital terrain map (UTM 10 N) using the :

processing.run("Export to NIST FDS:Export terrain", { 'chid': CHID, 'fds_path': OUTPUT_PATH, 'extent': EXTENT, 'pixel_size': 1, 'origin': None, 'dem_layer': INPUT_FILE, 'landuse_layer': None, 'landuse_type_filepath': '', 'fire_layer': None, 'wind_filepath': '', 'tex_layer': None, 'tex_pixel_size': 10, 'nmesh': NUMBER_OF_MESHES, 'cell_size': CELL_SIZE, 'export_obst': True, 'debug': False })

But, qgis2fds centers the data based on the EXTENT's centroid. How do I adjust the settings so that all of the coordinates (x,y,z in UTM 10 N) are preserved when going to fds?

I've tried put (0, 0) and (500000, 0), which is the origin for UTM 10N in for the 'origin' parameter, but with no luck. The x, y, and even z coordinates experiences a shift.

Any help would be greatly appreciated!

— Reply to this email directly, view it on GitHub https://github.com/firetools/qgis2fds/issues/95, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACXMVY77NFHE7CSCPBRZ46D2A5YCJAVCNFSM6AAAAABR47FOA6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGY3DINJZHE3TINQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

-- "When old people used to wish each other peace, we didn't understand the meaning of this word. Now we really understand." [Natalia Balasynovych, mayor of Vasilkiv, Ukraine 2022]

donish-getstand commented 9 hours ago

Hi Emanuele,

Thanks for taking the time to look at this issue! I did play around with the parameter values for 'origin' but I couldnt figure out how to nullify any coordinate shift; it feels like there should be an easy answer, but maybe not. Any help on this matter would be greatly appreciated!