 image id  usgs/gfsad1000_v0  usgs/gfsad1000_v1  expected to be added to google earth...

Download  Image Id  USGS/GFSAD1000_V0  USGS/GFSAD1000_V1  Expected to be added to Google Earth Data Catalog with the week. Demo in EE JavaScript Playground

Post on 27-Dec-2015

214 views

Category:

Documents

1 download

Embed Size (px)

TRANSCRIPT

  • Slide 1
  • Image Id USGS/GFSAD1000_V0 USGS/GFSAD1000_V1 Expected to be added to Google Earth Data Catalog with the week. Demo in EE JavaScript Playground https://ee-api.appspot.com/bcc16fd7f270840482b323dde37c2956 Note: There are no legends or class colors as Earth Engine expects the user of the data to reference supporting information. Earth Engine is an analysis tool and is not for displaying results. Google Earth Engine Dataset
  • Slide 2
  • LP DAAC The timeline from test to operational is extremely variable, depending on resources, external dependencies, and the products themselves. Supporting information can be reviewed at: http://e4ftl01.cr.usgs.gov/GFSAD/lpdaacgfsad30/ http://e4ftl01.cr.usgs.gov/GFSAD/lpdaacgfsad30/
  • Slide 3
  • USGS Website Almost there I have my AFS account, can view files, but just need write privileges. Had a discussion about hosting some project work/documentation/products on non-USGS or.gov domains and the conclusion was it does not matter.
  • Slide 4
  • Croplands App New JavaScript Framework Building Barebones Custom Charting Library Still Refactoring Database Structure Redesign of Application with Additional Tools and an Improved Interface
  • Slide 5
  • New JavaScript Framework Switching to Angularjs, an Open Source JavaScript Framework Easier to Extend and Modify Maintains Separation of Data Model, Web View, and App Controller Allows Greater Ability for Testing
  • Slide 6
  • SVG Charting Library Building a Custom Scalable Vector Graphic Charting Library with Angularjs The currently available options have limitations for this particular application. Bar charts and line charts Primary reason is to reduce memory usage and latency when dealing with a significant amount of data.
  • Slide 7
  • Database Structure More Effectively Differentiating Data By Year Fixed Naming Inconsistencies Still Working on History Table Need to Modify Unit Tests
  • Slide 8
  • Web App Changes Improved Zoom Controls with Zoom to World Opacity Controls for Layers Improved Loading and Working Interface for User Ability to Select Rectangular Area of Map Select Markers and Get Histogram of Classes Query Google Earth Engine for Area per Class in Our Data Products (Still Writing EE Scripts) Working out the best interface for users to provide information by year. And more features in the works: photos, comments, etc.
  • Slide 9
  • Latest Screenshot

Recommended

View more >