Initial support for AWFI, PAN10M and PAN5M included

[fredliporace]

This is my take on #6

It is already possible to select the CBERS sensor and visualize it. Most of the changes are in the sample client.

Todo

• [x] Update packaging to use the new rio-tiler and aws-sat-api-py. Currently using local packages.
• [x] Generate new path/row grids for the sensors.
• [x] Check the natural and false rgb for PAN10M.
• [x] Disable RGB selection for PAN5M (single panchromatic band).

PR references:

• https://github.com/mapbox/rio-tiler/pull/43
• https://github.com/RemotePixel/aws-sat-api-py/pull/3

[vincentsarago]

👋 @fredliporace thanks for all the work. I'll work on getting everything merged/deployed today

[fredliporace]

Hey @vincentsarago,

This completes the viewer update to show all sensors. The reference grids with scenes available for each sensor is updated when a new sensor is selected. Some remarks:

• The AWFI swath is very large, if we use the whole footprint for scene selection there will be a huge overlap that will make the scene selection confusing. I chose to show a smaller footprint (equivalent to a MUX scene) centered over the AWFI scene center.
• PAN5 and PAN10 scenes have a swath equivalent to half a MUX scene, but use the same path/row convention in scene identification.
• The datasets are being served from my mapbox account, I'll update them in a monthly basis. If you want I can make the geojson files available, or the scrips that generate them from the CSV files.
• A cbers-tiles endpoint is available in https://gk4ai2v1m3.execute-api.us-east-1.amazonaws.com/production/cbers for testing.

[vincentsarago]

The datasets are being served from my mapbox account, I'll update them in a monthly basis. If you want I can make the geojson files available, or the scrips that generate them from the CSV files.

This is great, as long as you make the tilesets public you can provide them and it shouldn't cost you anything (cost is linked to mapbox token). We could add the tilesets info in the readme.

Thanks for this update anyway ;-)

[fredliporace]

OK, will update the readme in a future PR. This closes #7