geojson files used in geofiltering are stored and retrieved from opera-ancillaries S3 bucket in the dev account. These files are expected to not change often and should only be a handful of files necessary for historical processing campaigns.
We now have a new use-case during INT and PST activities where we want to create many (10+) of specific geojson files to aid for a specific use-case. These files aren't expected to be used in production. Only a few people have access to opera-ancillaries S3 bucket, by design, because these are ops-critical files.
So to aid the use-case of INT and PST, a simple code change would be for daac_data_subscriber to fall back to looking for geojson file in the current working directory if not found in S3. This would only work when the subscriber is run directly on a Mozart box or a user machine - would not work if running in a verdi worker. But I believe this will satisfy INT/PST needs with minimal development and testing time.
philipjyoon
commented
6 months ago
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
No response
Describe the feature request
geojson files used in geofiltering are stored and retrieved from
opera-ancillariesS3 bucket in the dev account. These files are expected to not change often and should only be a handful of files necessary for historical processing campaigns.We now have a new use-case during INT and PST activities where we want to create many (10+) of specific geojson files to aid for a specific use-case. These files aren't expected to be used in production. Only a few people have access to
opera-ancillariesS3 bucket, by design, because these are ops-critical files.So to aid the use-case of INT and PST, a simple code change would be for daac_data_subscriber to fall back to looking for geojson file in the current working directory if not found in S3. This would only work when the subscriber is run directly on a Mozart box or a user machine - would not work if running in a verdi worker. But I believe this will satisfy INT/PST needs with minimal development and testing time.