Google Map Engine Can export images to Map Engine from Earth Engine Can Import Back into Earth Engine with Asset Id Can serve layers as WMS

Displaying Maps to Public Mapsengine WMS Layers Javascript Map API to Load WMS over Baselayers Available on the web: Development Location: usgs-gfsad.herokuapp.com Open Source Python Based Webserver with Flask Framework Leaflet.js Mapping Library Exception: Maps Engine

Data Collection and Verification Load Existing Data into Map and Allow Verification Pull Data from Google Earth Engine at Regular Intervals Allow Users to Submit New Data Points Large Amounts of Data Can Be Sent to Justin Validation of Form Entry to Ensure Consistency of Data

Data Storage Sample Data Vector Photos Raster Layers Maps Engine Table Accessible via Google API, Google Maps Engine, Google Earth Engine, Custom API Endpoint, Download Url Photos Amazon S3 ? Other Storage? Raster Layers Maps Engine Accessible via WMS Layer, Google Maps Engine, Google Earth Engine

Future: Google Earth Engine Automatically Run Algorithm in Google Earth Engine Cloud as New Vector Classification Data is Available Export Raster to Google Maps Engine for Publishing

Next Steps Continued Refactoring and Unitests of Client Side and Server Side Code Finish Implementation of Form Photos Upload/Insert CSV/Shapefile/? Upload Filtering/Custom Icons for Sample Data User Login System Catching Rate Limit Errors for API

Next Steps Cont. Mobile App for Field Data Collection Accuracy issues? Distributed Tasks Pull Data from Earth Engine for Sample Location Check for Streetview Image Data Points: Filter Good from Bad Daily Backup and Versioning of Sample Data via SQL Database and Basic File Storage

Discussion Standard Schema for Sample Data Valid vs Invalid Data and Reviewing Restricted Access for Some Tasks via Login Downloadable in geoJSON, csv, other? Filtering Good Sample Points from Bad