[FEATURE] please put the spatial and temporal paramters, and start and end dates into the output filenames

[admahood]

It used to be like this, I don't know why this was changed. This is really important.

should be something like

fired_<area_of_interest>_<events/daily>_<area_of_interest>_s<s>_t<t>_from<YYYYDOY>_to<YYYYDOY>.<gpkg/shp>

[pvn-a]

Is this still a priority to be addressed? If so, can I take a look at this (I don't see any commits to address this issue yet).

I took a look at it ... seems like regardless of whether we choose the input as shapefile/tiles/country, the outputs look like this

OLD [country, shapefile based inputs]
INFO - 2026-03-24 00:25:01,222 [model_classes.py:1400] : Saving daily geodataframe to /outputs/shapefiles/fired_firedpy_2020_to_2021_daily.gpkg
INFO - 2026-03-24 00:25:03,869 [model_classes.py:1411] : Writing full daily CSV file to /outputs/tables/fired_firedpy_2020_to_2021_daily.csv
INFO - 2026-03-24 00:25:05,664 [model_classes.py:1426] : Saving event-level geo to /outputs/shapefiles/fired_firedpy_2020_to_2021_events.gpkg
INFO - 2026-03-24 00:25:05,697 [model_classes.py:1437] : Writing full daily CSV file to /outputs/tables/fired_firedpy_2020_to_2021_events.csv
INFO - 2026-03-24 00:25:05,716 [create_readme.py:164] : Run summary written to /outputs/fired_firedpy_readme.txt.

Questions

• Do we need <area_of_interest> to appear twice in the filename?
• In the case of a shapefile input, the <area_of_interest> will be the filename of the shapefile right?
• Should we change the name of the readme.txt file as well?
• I don't see a framework yet for unit test cases. Should I write them for this feature regardless?

[admahood]

Yeah i think right now from new version, we can keep it the way it is, but add s<> and t<>