Permissions:
Only certain user roles can view and edit data in Settings.
NPWS users can only see Impact Analysis inputs and can edit their own inputs.
Only RMP admin can download geospatial data for sensitive categories.
Input name | Description | File type | Field format | Can you change the default? | Can you override the default in a project ? | Location in RMP |
NetCDF weather | NetCDF data incorporates how weather changes geospatially over time. NetCDF weather is a package of multiple files. | A .ZIP file containing multiple NetCDF files in a .gz file or individual NetCDF files an .nc file | Requires the following format: *_Curing_SFC.nc *_Sky_SFC.nc *_DF_SFC.nc *_T_SFC.nc *_RH_SFC.nc *_WindOnHour_Mag_SFC.nc *_Wind_Dir_SFC.nc (edited) | N/A | N/A | Default input Open run > Inputs > Weather library |
Point data weather | Weather data recorded at a specific geographic location (point) and applied to a broader area. Point weather can be a single file or a package of multiple files. | .xlsx | Requires the following format:
Note: The data is applied to an ignition point using the Weather_Id field. | N/A | N/A | Default input Open run > Inputs > Weather library |
How NetCDF integration works in the RMP
You can upload NetCDF weather inputs to the RMP weather library as a weather day. For information on how to add Weather days, see Add a weather day to the weather library.
File manipulation when uploading
The RMP will validate that the NetCDF compressed zip file has the right structure, and will update it if needed.
There are no changes made to uploaded NetCDF files during the upload process.
Visualising NetCDF files
NetCDF files are stored within the Geoserver for visualisation—the files will be down sampled for performance if needed. You can visualise the following parts of NetCDF files:
Relative Humidity
Temperature
Wind Speed
Wind Direction
NetCDF in Phoenix
The following Phoenix processes happen at run time and do not change the raw NetCDF files.
File naming conventions
Phoenix will accept the following files with these specific naming conventions (any deviation from the below suffix to the file names will not be read by Phoenix):
netcdfFileList.Add("_Curing_SFC.nc");
netcdfFileList.Add("_Sky_SFC.nc");
netcdfFileList.Add("_DF_SFC.nc");
netcdfFileList.Add("_T_SFC.nc");
netcdfFileList.Add("_RH_SFC.nc"); netcdfFileList.Add("_WindOnHour_Mag_SFC.nc"); netcdfFileList.Add("_Wind_Dir_SFC.nc"); netcdfFileList.Add("_Wind_Dir_SPOT.nc"); netcdfFileList.Add("_Wind_Mag_SPOT.nc");Code from Phoenix
Not all these files are required for Phoenix to run.
Expected units
The following table shows the units Phoenix requires for each NetCDF types:
NetCDF type | Phoenix Hardcoded Units |
Temperature Unit | C |
Wind On Hour Magnitude Unit | knots (kts,kt,knots,knot) or kmh |
Wind Magnitude Spot Unit | knots (kts,kt,knots,knot) or kmh |
Curing Unit | % |
Drought Factor | DF |
Relative Humidity | % |
Wind Direction | degrees_north |
Wind Direction Spot | degrees_north |
Start time manipulation
Phoenix requires the date of NetCDF data to cover the modelled start and end times.
Uploaded NetCDF data requires the start date as the prefix of the uploaded compressed zip file name, for example 20191112_AM_Extreme.zip
The current running job has the Phoenix modelled date, for example 2027-01-01T11:00:00+11:00.
The RMP compares the NetCDF date and the Phoenix date to calculate the number of days between the start date and the modelled date, for example 2607.
The NetCDF files are time-shifted by the number of days to match the time when Phoenix will process the NetCDF data. Phoenix manages the conversion between the NetCDF UTC time and the Phoenix modelled date, which includes the timezone information.
Wind on the hour magnitude manipulation
Phoenix will attempt to read the wind magnitude unit value in the NetCDF file and convert the values to Kmh. It uses the following conversion multiplier between Knots and Kmh:
this.dblConversionFactor = 1.85198479488;
Code from Phoenix
Phoenix will not always be able to read the wind magnitude units from the NetCDF file. RMP handles this by checking the units in the wind magnitude file and making any necessary conversions from Knots to Kmh. RMP uses the same conversion factor from Knots to Kmh.