wri / gfw-raster-analysis-lambda

GFW Raster Analysis in AWS Lambda
8 stars 4 forks source link

Data Environment #40

Closed jterry64 closed 3 years ago

jterry64 commented 3 years ago

Refactored to separate hardcoding of the data lake. Instead, you now have to send your "data environment" to the lambda, which includes all layers, their source URIs, grids, etc. You can also derive new layers from source layers using numpy expressions. The idea here is for data API to generate this from the assets table and send it to the lambda, so you lambda is automatically in sync with the available layers on the API.

Pull request checklist

Please check if your PR fulfills the following requirements:

Pull request type

Please check the type of change your PR introduces:

What is the current behavior?

All URIs to data lake are hardcoded, as well as layer metadata.

What is the new behavior?

Does this introduce a breaking change?

I will remove support for layers ending in "isoweek" from the SQL API - must now use "isoweek(date)"

jterry64 commented 3 years ago

@thomas-maschler fixed all your comments. I'll probably just keep this feature branch up while I work in on the gfw-data-api side, so I don't break staging.

thomas-maschler commented 3 years ago

Looks good