1. Website: Croplands.org

2. User Authentication Full user authentication system with roles. User passwords hashed (one way encrypted) with a salt using modern encryption techniques.

3. Reference Data Database Storage accessible through an API http://www.croplands.org/api/fiel d_points http://www.croplands.org/api/fiel d_points – GET, PUT, PATCH, POST, DELETE etc… – geoJSON Format – Still determining what should require authentication, but… Reference Data History – Each change to a reference data location is logged. Who changed it? What changed? – Can undo changes.

4. Reference Data Structure Cropland – 0: Not Cropland – 1: Cropland Water Source – 0: Unknown – 1: Rainfed – 2: Irrigated Intensity – 0: Unknown – 1: Single – 2: Double – 3: Triple – 4: Continuous Crop Type – 0: Unknown – 1: Wheat – 2: Corn – 3: Rice – 4: Barley – 5: Soybean – 6: Pulses – 7: Cotton – 8: Potatoes – 20: Other Still need definitions!

5. Google Earth Engine Python Access Working – Bitbucket git repository – Web API Example: Extracting Modis NDVI Timeseries http://www.croplands.org/gee/time_series?lat=42.01&lng=- 95.60&date_start=2000-01-01&date_end=2015-01-01

6. Ideas / Challenges Can reference data be moved? – How far? 50m, 1km, unlimited – By who? Edit permissions – Who can edit? – Allow public to edit, but require review? Getting field size? – Allow users to draw polygon? – Show Modis/Landsat pixel bounds when placing reference data markers? Check for homogeneity with Google Earth Engine similar to retrieving time series information.

7. Publishing Data LPDAAC – in progress Google Earth Engine – starting