Skip to content
José Gómez-Dans edited this page Feb 1, 2016 · 1 revision

The database structure

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

Main table

  1. Site (some name, e.g. Caaveiro ;-D)
  2. Location (a GML Polygon or somesuch)
  3. Centroid (A POINT)
  4. Start date
  5. End data (or None for continuous leeching)
  6. Storage directory
  7. Username
  8. Landsat data (ETM+ and/or LDCM)
  9. Sentinel2 data (YES/NO)
  10. Sentinel1 data (NO, product)
  11. MODIS products (NO, MYD09GA.006)

Landsat table

  1. Site (linked to site in the main table)
  2. Path
  3. Row
  4. Sensor
  5. Date
  6. Path to file

MODIS table

  1. Site
  2. Tile
  3. Product
  4. Date
  5. Path

Sentinel 2 table

  1. Site
  2. MGRS coordinates (maybe get this from the query if it's a pain getting a library to figure it out)
  3. Date
  4. Granule_id
  5. Cloudiness

Sentinel 1 table

TBD, really. But I'm guessing it's going to be product type or something like that

Clone this wiki locally