WindNinja crashes with LCPs from WFDSS and FlamMap

[nwagenbrenner]

Tonja Opperman supplied an LCP from WFDSS for testing.

[nwagenbrenner]

Additional details from Chuck:

WFDSS, FlamMap, and IFTDSS all use the LANDFIRE Product Service (LFPS) to build landscapes created in a GeoTiff file format. The projection associated with those landscapes is in a localized Albers projection intended to keep the output product aligned with North and to keep the cell sizes constant. They are in a NAD83 Albers projection, with all the Parameters based on the landscape extent.

LFPS Links: https://lfps.usgs.gov/LFProductsServiceUserGuide.pdf

If Tonja ran DT WN and used the Domain Average Winds on the WFDSS landscape file, it would run in DTWN HOWEVER when attempting to open the KMZ of outputs into GoogleEarth it returns this error. A shapefile would load into QGis with points and the appropriate Attribute Table. This also happens when trying to use a landscape from FlamMap Get Landscape Utility for the same extent and LANDFIRE version. I could replicate all this myself.

AN issue became when attempting to use the WFDSS Geotiff landscape file in DT WN and initialize it from a weather model - i tried it using the WFDSS landscape file and the NOMADSHRR3km and Wind Ninja Crashed and closed immediately. So i wonder if the issue is that the Weather model grids are in WGS84 DD and they can't be warped or aligned with the GeoTiff Landscape file? OR i got lucky and picked a bad option for the weather? I was able to download the zip folder and open and select an hour in DT WN

My suggestions to Tonja, were
Use Wind Ninja in FlamMap which only has the Conservation of Mass Solver, then you can use the WFDSS landscape.

OR
if needed the full Conservation of Mass and Momentum Solver and or to initialize the WN run using a weather model, to use DT WN Download and specify "Landscape File" which is currently Landfire 2023 Ver 2.4.0, this is the same as currently available in in WFDSS.

I warned her that the projection of the landscape file from DT WN download would be in a UTM Zone, and that to use the DT WN fire behavior outputs in FlamMap she would need to use the same landscape she downloaded from DT WN in FlamMap as well to use the gridded wind products

[nwagenbrenner]

This may have to wait until 4.0.0. It has something to do with proj6 vs. proj4. Windows is still stuck on GDAL 2.x and proj4 due to our reliance on MSVC 2010 and gisinternals for gdal. With 4.0.0 we'll migrate to modern GDAL and proj6 via vspkg.

ERROR 6: No translation for Albers to PROJ.4 format is known.

Run 0 (warning): Exception caught during Google Earth file writing: failed to create coordinate transform, kmz creation failed