Fire data processing: Automatically update data before running reports, if needed

[lbross]

The fire data processing steps could take a long time so we don't want to generate the data every time we run the reports. But we do want to make sure we have the most current data available. TBD if this is optional with a checkbox on the report UI or if we always do it.

NIFC: We have established procedures for getting the most recent year from the service. As part of the NIFC data creation, we will record the max date in the BAGIS analysis.xml parameter file at the AOI level. If the service date exceeds the max date in the analysis.xml, we will regenerate the polygon layer from the service date and 30 preceding years. This could result in some of the oldest records purging off if they are outside the 30 year window.

MTBS: We have established procedures for getting the most recent year from the image service names on the server. If the server image service names are more recent than the aoi image layer names, we will clip the new layers to the aoi. Do we want to delete aoi image layers that are outside the 30 year window?

[jdduh]

For MTBS, if there is a mechanism to check the presence of previously-clipped images before reclipping the imageservices, then we can just leave the clipped images in the aoi without deleting them.

[lbross]

@jdduh: Do you want to add this mtbs mechanism to the data processing step? I think we could do this in the initial implementation without too much trouble. Do you want a checkbox to override this in case of bad data or do we want it to always work this way?

[jdduh]

Yes, please create a checkbox "Overwrite existing MTBS rasters in AOI" with it checked by default. I assume that the tool will overwrite nifc data each time the tool is executed.