[FireSTARR Feature Request]: Assume timezone based on longitude if not specified

[jordan-evens]

Contact Details

No response

What would you like to see in the tool?

Since timezone is only used for determining when to use overnight ffmc, it's kind of confusing to have to specify it. All the inputs/outputs are in local time, so we don't need an exact time for converting anything.

If sunrise/sunset is super important then --tz can be used, but generally just offsetting by 1 hour per 15 degrees is probably fine - especially since the whole idea of overnight ffmc threshold is manufactured based on experience and not actually backed by anything published.

This would allow recent versions to be drop-in replacements for e.g. bp3+

[BadgerOnABike]

I think this makes sense to me.

Out of curiosity does FireSTARR maintain the date field as a date time coming in that would have the UTC declination still attached?

Could do a check between the weather and the fire to make sure the TZs are the same if the TZ exists in the weather data as a sanity check? Though I suppose if someone was running a scenario with weather from somewhere else that could be a problem... So treating it as local at all times makes sense there.