Google Earth Engine integration notebook

[kevinlacaille]

This notebook outlines how to integrate Planet with Google Earth Engine (GEE) using Planet's service account and the Orders API. There will be a follow up notebook, which will outline how to integrate with GEE using a custom service account.

Closes #210

[lobugliop]

Looks good, I was able to run this locally. Just some small comments

[lobugliop]

#nit might be nice to have the GEE delivery options as consts at the top of the notebook

[kevinlacaille]

If this were a regular script I would 100% do this, but I fear that would be a little inconsistent with how we typically lay out our notebooks. Thoughts on this @mkshah605?

[mkshah605]

I'd be open to it! It might make sense so users can easily change their credentials. It's similar to how I laid out this Subscriptions notebook, where people can define their bucket and gcs key in cell #2. Definitely open to your thoughts!

[kevinlacaille]

I've thought about it and we only use the project and collection names a single time, just in this cell, and it feels a bit unnecessary to define these as constants. @mkshah605, it makes sense in your subscriptions notebook, as you use bucket and gcs_key more than once in your notebook, but in this case I seem to justify creating two more variables. Are you opposed to leaving them as is?

[mkshah605]

yes that makes sense. I am good with leaving them in here

[samroy-pl]

This notebook is well set up to interact directly with the Python SDK as expected, this is not backward compatible, and maybe we need to include the SDK version information needed somewhere on the notebook.

Change cell 1 to this

# Order and Delivery to Google Earth Engine

In this notebook we're going to cover how to order data using the [Orders API](https://developers.planet.com/apis/orders/) and deliver it to [Google Earth Engine (GEE)](https://earthengine.google.com/) using [Planet’s GEE Delivery integration](https://developers.planet.com/docs/integrations/gee/).

This example demonstrates how to:
1. Define the data to be ordered
2. Build a cloud delivery configuration object (`delivery_config`), which tells the Orders API where to deliver the data
3. Build an order request to be sent off to the Orders API, `iowa_order`
4. Create the order and have it deliver to your GEE project

**Prerequisites:** 
- Planet python SDK 2.0 installed and initialized in your environment(**This notebook is not compatible with earlier version of the Planet SDK**)
- An AOI - `iowa_aoi`
- Item ID(s) - `iowa_images`
- A GEE project with EE API enabled - `planet-devrel-dev`
- A pre-existing GEE [ImageCollection](https://developers.google.com/earth-engine/guides/ic_creating) - `gee-integration-testing`
- An account with a download quota. Not sure if you have download quota? Please [get in touch](https://www.planet.com/contact-sales/).

Images might be delivered while the script polls for status to change to success, but images might be delivered to Earth Engine collection during the wait time, so I would include that information

[kevinlacaille]

Note that only clipping and harmonization are the only two tools that are compatible with GEE in cell 15.