We don't want to have offline map packages, that are potentially large in size, sitting around forever -- at least, not without the user's input about wanting to extend their expiration date.
[ ] Figure out an optimal expiration date (proposal to start: 1 year from creation).
[ ] On the MapDashboard UI, add an option to extend the expiration date (e.g. by another year from when the user requests the extension).
[ ] Once the expiration date is passed, we need to figure out a way to (1) delete the files and (2) update the db table row to set status = EXPIRED. (I think it will be good to keep a record of expired maps, for future reference - e.g. to use the same bounds and style for another map request.)
We don't want to have offline map packages, that are potentially large in size, sitting around forever -- at least, not without the user's input about wanting to extend their expiration date.
MapDashboardUI, add an option to extend the expiration date (e.g. by another year from when the user requests the extension).status= EXPIRED. (I think it will be good to keep a record of expired maps, for future reference - e.g. to use the same bounds and style for another map request.)