-
Notifications
You must be signed in to change notification settings - Fork 3
Home
José Gómez-Dans edited this page Feb 1, 2016
·
1 revision
This is just a note. I think we need one table to store the different download efforts, with individual tables for each sensor, where the actual products are stored. The basic structure of the tables follows
- Site (some name, e.g. Caaveiro ;-D)
- Location (a GML Polygon or somesuch)
- Centroid (A POINT)
- Start date
- End data (or None for continuous leeching)
- Storage directory
- Username
- Landsat data (ETM+ and/or LDCM)
- Sentinel2 data (YES/NO)
- Sentinel1 data (NO, product)
- MODIS products (NO, MYD09GA.006)
- Site (linked to site in the main table)
- Path
- Row
- Sensor
- Date
- Path to file
- Site
- Tile
- Product
- Date
- Path
- Site
- MGRS coordinates (maybe get this from the query if it's a pain getting a library to figure it out)
- Date
- Granule_id
- Cloudiness
TBD, really. But I'm guessing it's going to be product type or something like that