MODIS api docs notes

default no clouds

aggregate by country

/{ISO} # return one number, representing all time; also include start/end date fields {'IDN':'40,50', 'startdate':'2006-01-01', 'enddate':'2006-02-16', 'tres':'16', sres='500'}

/{ISO}?dateformat=seconds # ditto, but with unix epoch seconds instead of human readable {'IDN':'40,50', 'startdate':'2006-01-01', 'enddate':'2006-02-16', 'tres':'16', sres='500'}

simple things should be simple

complex things should be possible

all queries should be based on WGS84 latlon

I want a pixel TS

seconds should be for midnight the morning of a given date

ndvi/sres/tres/2000/12/1/lat/lon/json/ {lat:1.00833333, lon:110.00833333, sres:500, tres:16, data:{2,1,2,3,4,2,2,4,5,8}, start:12342345, stop:212341234}

{metadata{lat:1.00833333, lon:110.00833333, sres:500, tres:16, start:12342345, stop:212341234}, data:{2,1,2,3,4,2,2,4,5,8}}

I want a pixel TS with all cloudy/bad pixels replaced with nodata = -1

ndvi/sres/tres/lat/lon/dropcloudy/ {lat:1.00833333, lon:110.00833333, sres:500, tres:16, data:{2,1,-1,3,4,2,-1,4,5,8}}

?color=red&state=running&location=park

I want all data for a country

we don't want to send it all at once - huge, lots of bandwidth

but I want something like this:

/iso/ndvi/sres/tres/query=count

this gives

/iso/ndvi/sres/tres/query=vals,next

I want a graph of a pixel TS

use google charts?

ndvi/sres/tres/lat/lon/python/ ndvi/sres/tres/lat/lon/human/

how do we deal with cloud cover?

make people deal with them themselves?

I want a bbox TS - should this be a raster?

ndvi/sres/tres/lat/lon/geotiff/ ndvi/sres/tres/ul/lr/json/

I want a TS for a geographic area