{"_id":"56c7647153cafe0d00a53d7e","__v":0,"initVersion":{"_id":"55faeacad0e22017005b8268","version":"1"},"project":"55faeacad0e22017005b8265","user":{"_id":"55fae9d4825d5f19001fa379","username":"","name":"Sherri Barksdale"},"hidden":false,"createdAt":"2016-02-19T18:52:33.985Z","fullscreen":false,"htmlmode":false,"html":"<h1> Get the latest platform updates from GBDX!</h1>\n\n<br />\n<br />\n \n\n<p>We're always improving the GBDX platform. Check back regularly for the latest release notes and updates. </p>\n<br />\n\n\n<a href=\"https://twitter.com/GBDXReleaseLog\" class=\"twitter-follow-button\">Follow @GBDXReleaseLog</a>","body":"#Get the latest platform updates\n\nCheck back here regularly for updates and release notes. \n\nFollow [@GBDXReleaseLog](http://twitter.com/GBDXReleaseLog) on Twitter.\n\n##July 26, 2017\n**New process**: Completed workflows that are more than 4 months old will be removed from the system. \n\n**When**:  This process will be implemented on or shortly after **Thursday, August 10, 2017**\n\n**​Impact**: Once a completed workflow is aged out of the system, it can no longer be accessed using the workflow status endpoint. \n\nIf you have any questions or concerns, please contact gbdx-support@digitalglobe.com​ as soon as possible. \n\n##June 12, 2017\nCatalog V1 is being retired today. Users will no longer be able to access Catalog V1 APIs. \n\nIf you haven't upgraded to a version of gbdxtools that uses the Catalog V2 API yet, do this: ```pip install gbdxtools==0.11.2```\n\n\n##May 3, 2017\nIDAHO users: HTTPS is now enabled for idaho.geobigdata.io. \n\nIf you are currently using http://idaho.geobigdata.io, please switch to https://idaho.geobigdata.io.\n\nhttp://idaho.geobigdata.io​ is now deprecated. We will support http for 60 days, but please update to https as soon as possible. The official End of Life (EOL) date is July 2, 2017.\n\nQuestions? Please contact gbdx-support@digitalglobe.com\n\n##April 14, 2017\nENVI Task Runner patch release. All ENVI tasks have been updated to version 1.0.3.\n\nRelease notes: Refactored metadata handling by way of using ENVI to generate header files, In order to improve ENVI algorithm execution on the GBDX platform.\n\nDocumentation: All published ENVI documentation on GBDX University has been updated to account for all recent ENVI Task Runner updates. \n\n\n##April 12, 2017 - Introducing the new Catalog V2 API\n\nToday we released version 2 of the GBDX Catalog API. The Catalog V2 API is a simplified API that offers faster querying capabilities and better data consistency.  For documentation and potential breaking changes, see [Catalog V2 API Course](doc:catalog-v2-course) .\n\n**Catalog v1 has entered a 60-day deprecation period, with an end-of-life (EOL) retirement of June 12, 2017. All users will need to migrate to the Catalog V2 API before that time.** \n\nThe Python-based tools suite, gbdxtools, has been updated to use the Catalog v2 API. See [instructions for upgrading gbdxtools](http://gbdxdocs.digitalglobe.com/docs/catalog-v2-course#section-gbdxtools-requires-an-update).\n\nThe GBDX Postman Collection has been updated with query examples that use the Catalog V2 API. To upload the latest Postman collection, see [Postman Instructions & Collections](doc:postman-instructions-collections) Postman Instructions.\n\nSubscribe to the [GBDX Status page scheduled maintenance](http://status.geobigdata.io/incidents/zzgw75bnb3yn). \n\n## March 23, 2017\nENVI Task Runner Patch Release: version 1.0.1\n\nThe ENVI task runner will now build appropriate header files for images that have gone through the AOP_Strip_Processor with Pansharpening on, resulting in the output image having only 4 bands instead of 8 bands.\n\n## February 22, 2017 \nENVI Task Runner Release Notes\n\nWe've released a major version update to all ENVI tasks registered on GBDX. All tasks now have a GBDX version number of \"1.0.0\".\n\nThe following new features are now available on all ENVI tasks on GBDX:\n\n* New Input Raster features, see [here](http://gbdxdocs.digitalglobe.com/docs/envi-task-runner-inputs) for full usage document: \n  * Added intelligent file discovery for DG products. \n  * Added supplemental port *input_raster_format* for selecting which format the input raster is so ENVI can open it appropriately.\n  * Added supplemental port *input_raster_band_grouping* for selecting the group of bands to use for the task. \n  * Added supplemental port *input_raster_filename* for overriding file lookup.\n* New DEM Raster features, see [here](http://gbdxdocs.digitalglobe.com/docs/envi-task-runner-inputs#section-envi-dem-rasters) for full usage document:\n  * Added alternate port *dem_raster_filename*, to support using ENVI built in GMTED2010 DEM raster with 30 arc-sec resolution, and added a GMTED2010 DEM raster with 7.5 arc-sec resolution. \n* New Spectral Library features, see [here](http://gbdxdocs.digitalglobe.com/docs/envi-task-runner-inputs#section-envispectrallibrary) for full usage document: \n  * Added alternate port *input_spectral_library_filename* for using ENVI's built in spectral library files.\n* URI input filtering, see [here](http://gbdxdocs.digitalglobe.com/docs/envi-task-runner-inputs#section-enviuri) for full usage document: \n  * ​Added supplemental port *input_uri_filter* for selecting a file(s) for ENVI to run the task on. \n* Task Runner builds header files for AOP and ACOMP outputs, where applicable.\n* **Deprecation warning**: the *file_types* port is planned for deprecation by version 2.0.0.\n\n\n##January 12, 2017\nTask Versioning Change\nTask version numbers are being added to tasks. All tasks are being given a version number of 0.0.1. All new tasks will require a version number bump.\nhttp://status.geobigdata.io/incidents/klpvv8qsw9hw\n\n## November 10, 2016 \nPlatform maintenance is complete.If you're a gbdxtools user, please upgrade to version 0.7.2\n\n## November 10, 2016\nToday's platform maintenance includes the following:\n\n### Batch workflow breaking change:\nThis is a change to the batch workflow request format. See [batch workflow documentation](http://gbdxdocs.digitalglobe.com/docs/workflow-api-course#section-batch-workflows).\n\n*Important*: gbdxtools users will need to upgrade their gbdxtools package after the deployment. This page will be updated when the deployment is complete. \n\n### New way to save task outputs to S3\nYou can now save task outputs to the S3 customer location by setting the \"persist\" flag on the output port. You can also specify a location other than the default location using \"persistLocation. \" See the [How to Save Task Outputs](http://gbdxdocs.digitalglobe.com/docs/how-to-save-task-outputs) documentation. \n\n##Scheduled for Thursday 11/10/2016 BREAKING CHANGE: Update to Batch Workflows \n\nThis applies only if you are submitting batch workflows using the Batch Workflow API endpoint. The batch workflow template will be revised to allow for more flexibility in adding batch values. The current request template will no longer work once this change is applied. Documentation and an example will be added here prior to the change. \n\nCurrent Batch Workflow documentation: http://gbdxdocs.digitalglobe.com/docs/workflow-api-course#section-batch-workflows\n\n\n\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"The Material Sets API will be deprecated soon.\",\n  \"body\": \"With new functionality like batch workflows and auto-ordering, this API is no longer needed. Contact gbdx-support@digitalglobe.com if you have any concerns.\"\n}\n[/block]\n## October 13, 2016 \n\nTIME CHANGE: Today's platform upgrade will now take place between 1 PM and 5 PM MST. \n\nToday's platform maintenance includes a CATALOG outage and a brief WORKFLOW outage. Follow us on Twitter for updates. \n\n## October 12, 2016\nTomorrow's maintenance window will include a catalog outage and a delay in workflow processing time. Users can submit workflows, but they may not be processed right away. The maintenance window is between 10 AM and 2 PM MST. Watch our Twitter feed (see above) for updates. \n\n## October 6, 2016\nThere will be no weekly platform maintenance taking place today. \n\n## September 29, 2016\n\nThe following maintenance will be taking place.\n\nGBDX Platform Maintenance - Minor functionality updates will be applied today.\n\nScheduled Start: 29 September 2016 @ 10:00AM MT\n\nScheduled End: 29 September 2016 @ 2:00PM MT\n\nDuring this maintenance window, you may experience slowness or temporary service interruptions while using the GBDX Platform.\n\n\n## September 27, 2016\n\nThere will be unscheduled downtime for platform maintenance work starting at 6 PM MST. The main Catalog server will be restarted. \n\nThe following services are impacted:\n* Workflow Service - Task-Worker\n* Catalog Service\n\nWe appreciate your patience while we work to complete the maintenance. If you have any questions or issues please contact gbdx-support@digitalglobe.com\n\n## September 22, 2016\n\nGBDX Platform Maintenance - Critical catalog maintenance will be applied.  Catalog Service outage should be expected during this time. This impacts the catalog API and the web application.\n\nScheduled Start: 22 September 2016 @ 10:00AM MT\n\nScheduled End: 22 September 2016 @ 2:00PM MT\n\n-------\n\n## September 15, 2016\n\nThe following maintenance will be taking place.\n\nGBDX Platform Maintenance - Various stability and functionality updates will be applied\n\nScheduled Start: 15 September 2016 @ 10:00AM MT\n\nScheduled End: 15 September 2016 @ 4:00PM MT\n\nDuring this maintenance window, you may experience slowness or temporary service interruptions while using the GBDX Platform.\n\n\n\n------------\n\n## September 13, 2016\n\nThe GBDX workflow system has been running at normal speed since the weekend. The issue with task scheduling has been resolved. \n\n-------\n\n## September 9, 2016 1:50 PM MST - RESOLVED\n\nGBDX customers are experiencing longer than normal workflow processing times. \n\n**What’s going on?**\nCustomer engagement with the GBDX platform is at an all-time high.  We’ve seen a big increase in the number of workflows submitted over the past several weeks. The SQL query that schedules tasks is taking longer to run. The more workflows that are scheduled, the slower the query runs. We’re also investigating whether our Amazon Relational Database (RDS ) is contributing to the problem. \n\n**What’s the solution?**\nWe’re working on optimizing the task scheduling query and the database. \n\n**When will it be fixed?**\nResolving this issue is our top priority. We have dedicated team members working on query optimization and database tuning. We’ll test and deploy a fix as soon as we have it ready. Once we’re running at normal processing times again, it may take some extra time to work through the full backlog.\n\n**Do I need to resubmit my workflow?**\n•\tIf you’ve successfully submitted a workflow, you don’t need to do anything. It’s in the queue and will be processed. \n•\tIf you receive a 500 or 503 error when submitting a workflow, you will need to resubmit it. This error is due to submitting a workflow while server maintenance was occurring.\n•\tIf your task’s status is “failed”, you’ll need to resubmit the workflow. The task may have timed out due to the longer processing times.\n\nWe’ll post an update when this is resolved, and will continue to send status updates until we’ve worked through the backlog.\n\n\n\n\n\n## September 9, 2016\n\nThe following maintenance will be taking place.\n\nContinued GBDX Platform Maintenance - task scheduler maintenance to improve/fix task queueing times.  Workflows can still be submitted, but task queueing/scheduling continues to be delayed.\n\nScheduled Start: 9 September 2016 @ 9:00AM MT\n\nScheduled End: 9 September 2016 @ 5:00PM MT\n\nDuring this maintenance window, you may experience slowness or temporary service interruptions while using the GBDX Platform.\n\n\n\n\n----------\n\n## September 8, 2016\nThe following maintenance will be taking place.\nGBDX Platform Maintenance - Various stability and functionality updates will be applied\nScheduled Start: 8 September 2016 @ 10:00AM MT\nScheduled End: 8 September 2016 @ 2:00PM MT\n\nDuring this maintenance window, you may experience slowness or temporary service interruptions while using the GBDX Platform.\n\n\n---------\n\n## September 6, 2016 \n1:00 PM MST - We are currently investigating a long running query in the Workflow system causing a delay before tasks are queued for execution. \n\nThe following GBDX services are impacted:\n\nWorkflow System\n\nWe appreciate your patience. If you have any questions please contact gbdx-support@digitalglobe.com\n\n##September 2, 2016\n\nToday's platform release includes these new features:\n\n**Ordering with Callbacks**\nNow you can place an order and request a callback notification. Submit your order request to the new Ordering with Callbacks API, and we'll send you a notification when your order has been delivered. \n[Ordering with Callbacks documentation](http://gbdxdocs.digitalglobe.com/docs/ordering-course-v2#section-ordering-with-callback-notifications)\n\n**Run a Workflow with Callbacks**\nYou can request callback notifications when you submit a workflow to the Workflow API.\n*Documentation coming soon.*\n\n**Waiting Task Status**\nA task can be set to the \"waiting\" state. Any continue request from the user will resume the task. \n*Documentation coming soon.*\n\nNote: Auto-ordering will release next week.\n\n\n-------\n\n## SEPT 1, 2016 - weekly platform release scheduled for today. \nThe maintenance window is 10 AM to 2 PM. You may experience some platform slowness during this time. This release includes the new ordering callbacks API, workflow callbacks, and a \"waiting\" task status.\n\n--------\n\n## AUGUST 18, 2016 - PLATFORM MAINTENANCE NOTIFICATION\n\nThe following maintenance will be taking place.\n\nGBDX Platform Maintenance - Various stability and functionality updates will be applied:\n\n - ProductCataloger fixes: Enhanced speed & reliability of product cataloging. Smarter retry system upon catalog API errors.\n - Catalog configuration:   update/maintenance\n\n\nScheduled Start: 18 August 2016 @ 10:00AM MT\n\nScheduled End: 18 August 2016 @ 2:00PM MT\n\nDuring this maintenance window, you may experience slowness or temporary service interruptions while using the GBDX Platform.\n\n------\n\n## July 12, 2016\n\n**30 cm imagery is now available!**\nNow when you order imagery from Worldview-3, we'll deliver 30 cm resolution imagery. Learn more about [DigitalGlobe's 30 cm imagery](http://microsites.digitalglobe.com/30cm/).\n\n--------\n\n## June 9, 2016\n\n**Batch Workflows**\nWith batch workflows, you can now submit multiple workflows with one API request. A batch workflow request spawns multiple workflows that run the same tasks on multiple inputs concurrently.\n[Batch workflow documentation](http://gbdxdocs.digitalglobe.com/docs/workflow-api-course#section-batch-workflows-new-)\n\n-------\n\n## May 5, 2016\n\n**Task User Impersonation**\nUser can allow a task in a workflow access to run on their behalf. \n* Added \"auth_required equired flag to task definition schema (true/false)\n* Added \"impersonation_allowed\" to the workflow definition. \n* The user token is added to runtime information when impersonation is allowed.\n[Task User Impersonation Documentation](http://gbdxdocs.digitalglobe.com/docs/workflow-api-course#task-user-impersonation)\n\n**Task Runtime Design**\n* In work directory, in addition to input ports.json, add an additional file called gbdx_runtime.json that contains task_id, workflow_id, and domain.\n* Location:  /mnt/work/gbdx_runtime.json\n* Information is available to the worker, so this can be mounted inside the docker.\n#### Full documentation for changes to the Task Runtime design will be live Friday, May 6. Check back here for updates or follow us on Twitter.\n\n-------\n\n## April 28, 2016\n\n**Orders V2 updates:**\n-Added a limitation of 100 images per order, and better error messaging when the limit is exceeded.\n\n-When duplicate catalog IDs are included in an order, the order is allowed and the duplicates are collapsed into a single catalog ID. \n\n**Web Application**\nUpdates to the credit card section of self-registration to explain credit card requirement and allow for A/B testing. \n\n-------\n\n## April 26, 2016\nThe Postman collection has been updated to include a Getting Started section and two new workflow requests (stdout and stderr outputs). Download and import the latest [GBDX Postman collection file](http://gbdxdocs.digitalglobe.com/docs/postman-instructions-collections).\n\nTwo new endpoints have been added to the Workflow API.\n[STDOUT output from a task in a workflow](http://gbdxdocs.digitalglobe.com/docs/stdout-output-from-a-workflow-task)\n[STDERR output from a task in a workflow](http://gbdxdocs.digitalglobe.com/docs/stderr-output-from-a-workflow-task)\n\n--------\n\n## March 31, 2016\n\nThere is no platform release this week.\n\n---------\n\n## March 24, 2016\n\nBug fixes\n    \n## March 17, 2016\n\nCatalog improvements:\n\t-Upgraded to OrientDB 2.1.11\n\t-Bug fixes\n\nWorkflows\n\t-added multiplex inputs for workflows (more information coming soon)\n\nWeb application\n\t-The web application now uses the Ordering V2 api. This change is invisible to web app users.\n\n\n## March 10, 2016\n\nBug fixes:\n               -Email address is no longer case-sensitive anywhere in the web application\n               -Mailing address is now included in account creation email to GBDX Support\n\nNew:\n               -Added “vector” as an account type to support Vector customers\n\nOperations:\n               Reliability and performance improvements\n\n\n## March 1, 2016\nBug fix: Some Chrome users in the Orbit desktop could not see the login screen. This has been fixed in the production environment. \n\n## February 29, 2016\nThe Postman collection has been updated with the  new Ordering V2 API requests. You'll need to import the latest GBDX collection. \n\n<a href=\"http://gbdxdocs.digitalglobe.com/docs/lesson-postman-api-requests\" target=\"_blank\">Postman Setup Instructions</a>\n<a href=\"http://gbdxdocs.digitalglobe.com/v1/docs/postman-collection-1\" target=\"_blank\">Postman Collection</a>\n\n\n\n## February 25, 2016\n\nOrdering V2 is here!\n\nOrdering V2 provides big gains in performance, reliability, and ease of use. These improvements include:\n\n* The ability to place as many orders as you want, as quickly as you want. \n* New factory throttling guarantees we won't overload the DigitalGlobe (DG) factory. This means fewer ordering issues or failures for our customers.\n* No more duplicate orders. If a catalog ID has been ordered once, we won't order it again. \n* Simplified REST API. You'll use a single endpoint to place an order and check order status. API Responses have been simplified so you can quickly find the information you need.\n\nNote: In version 2, the term order_id replaces sales_order_number.\n\nImagery ordered using Ordering V1 has been migrated. If you order imagery that has been ordered previously, your order will be satisfied immediately.\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Ordering V1 will be supported for the next two weeks\",\n  \"body\": \"Please migrate to Ordering V2 during this time.\"\n}\n[/block]\nFor more information: \n\nWatch this [short video](http://gbdxdocs.digitalglobe.com/v1/docs/video-ordering-v2) to learn how to use the new Ordering APIs\n\n[Ordering Course V2](http://gbdxdocs.digitalglobe.com/docs/ordering-course-v2)\n[Check Orders Heartbeat](http://gbdxdocs.digitalglobe.com/docs/orders-heartbeat-v2)\n[Place an Order](http://gbdxdocs.digitalglobe.com/docs/place-an-order-v2)\n[Get Order Status](http://gbdxdocs.digitalglobe.com/docs/get-order-status-v2)\n\n\n## February 18, 2016\nBug fix - Evaluation Tier Users can’t add materials from approved geographic areas to material sets\n\n## February 11, 2016 \nBug fix - New Users activating accounts get error message, but account is activated","slug":"release-notes","title":"Release Notes"}

Release Notes


#Get the latest platform updates Check back here regularly for updates and release notes. Follow [@GBDXReleaseLog](http://twitter.com/GBDXReleaseLog) on Twitter. ##July 26, 2017 **New process**: Completed workflows that are more than 4 months old will be removed from the system. **When**: This process will be implemented on or shortly after **Thursday, August 10, 2017** **​Impact**: Once a completed workflow is aged out of the system, it can no longer be accessed using the workflow status endpoint. If you have any questions or concerns, please contact gbdx-support@digitalglobe.com​ as soon as possible. ##June 12, 2017 Catalog V1 is being retired today. Users will no longer be able to access Catalog V1 APIs. If you haven't upgraded to a version of gbdxtools that uses the Catalog V2 API yet, do this: ```pip install gbdxtools==0.11.2``` ##May 3, 2017 IDAHO users: HTTPS is now enabled for idaho.geobigdata.io. If you are currently using http://idaho.geobigdata.io, please switch to https://idaho.geobigdata.io. http://idaho.geobigdata.io​ is now deprecated. We will support http for 60 days, but please update to https as soon as possible. The official End of Life (EOL) date is July 2, 2017. Questions? Please contact gbdx-support@digitalglobe.com ##April 14, 2017 ENVI Task Runner patch release. All ENVI tasks have been updated to version 1.0.3. Release notes: Refactored metadata handling by way of using ENVI to generate header files, In order to improve ENVI algorithm execution on the GBDX platform. Documentation: All published ENVI documentation on GBDX University has been updated to account for all recent ENVI Task Runner updates. ##April 12, 2017 - Introducing the new Catalog V2 API Today we released version 2 of the GBDX Catalog API. The Catalog V2 API is a simplified API that offers faster querying capabilities and better data consistency. For documentation and potential breaking changes, see [Catalog V2 API Course](doc:catalog-v2-course) . **Catalog v1 has entered a 60-day deprecation period, with an end-of-life (EOL) retirement of June 12, 2017. All users will need to migrate to the Catalog V2 API before that time.** The Python-based tools suite, gbdxtools, has been updated to use the Catalog v2 API. See [instructions for upgrading gbdxtools](http://gbdxdocs.digitalglobe.com/docs/catalog-v2-course#section-gbdxtools-requires-an-update). The GBDX Postman Collection has been updated with query examples that use the Catalog V2 API. To upload the latest Postman collection, see [Postman Instructions & Collections](doc:postman-instructions-collections) Postman Instructions. Subscribe to the [GBDX Status page scheduled maintenance](http://status.geobigdata.io/incidents/zzgw75bnb3yn). ## March 23, 2017 ENVI Task Runner Patch Release: version 1.0.1 The ENVI task runner will now build appropriate header files for images that have gone through the AOP_Strip_Processor with Pansharpening on, resulting in the output image having only 4 bands instead of 8 bands. ## February 22, 2017 ENVI Task Runner Release Notes We've released a major version update to all ENVI tasks registered on GBDX. All tasks now have a GBDX version number of "1.0.0". The following new features are now available on all ENVI tasks on GBDX: * New Input Raster features, see [here](http://gbdxdocs.digitalglobe.com/docs/envi-task-runner-inputs) for full usage document: * Added intelligent file discovery for DG products. * Added supplemental port *input_raster_format* for selecting which format the input raster is so ENVI can open it appropriately. * Added supplemental port *input_raster_band_grouping* for selecting the group of bands to use for the task. * Added supplemental port *input_raster_filename* for overriding file lookup. * New DEM Raster features, see [here](http://gbdxdocs.digitalglobe.com/docs/envi-task-runner-inputs#section-envi-dem-rasters) for full usage document: * Added alternate port *dem_raster_filename*, to support using ENVI built in GMTED2010 DEM raster with 30 arc-sec resolution, and added a GMTED2010 DEM raster with 7.5 arc-sec resolution. * New Spectral Library features, see [here](http://gbdxdocs.digitalglobe.com/docs/envi-task-runner-inputs#section-envispectrallibrary) for full usage document: * Added alternate port *input_spectral_library_filename* for using ENVI's built in spectral library files. * URI input filtering, see [here](http://gbdxdocs.digitalglobe.com/docs/envi-task-runner-inputs#section-enviuri) for full usage document: * ​Added supplemental port *input_uri_filter* for selecting a file(s) for ENVI to run the task on. * Task Runner builds header files for AOP and ACOMP outputs, where applicable. * **Deprecation warning**: the *file_types* port is planned for deprecation by version 2.0.0. ##January 12, 2017 Task Versioning Change Task version numbers are being added to tasks. All tasks are being given a version number of 0.0.1. All new tasks will require a version number bump. http://status.geobigdata.io/incidents/klpvv8qsw9hw ## November 10, 2016 Platform maintenance is complete.If you're a gbdxtools user, please upgrade to version 0.7.2 ## November 10, 2016 Today's platform maintenance includes the following: ### Batch workflow breaking change: This is a change to the batch workflow request format. See [batch workflow documentation](http://gbdxdocs.digitalglobe.com/docs/workflow-api-course#section-batch-workflows). *Important*: gbdxtools users will need to upgrade their gbdxtools package after the deployment. This page will be updated when the deployment is complete. ### New way to save task outputs to S3 You can now save task outputs to the S3 customer location by setting the "persist" flag on the output port. You can also specify a location other than the default location using "persistLocation. " See the [How to Save Task Outputs](http://gbdxdocs.digitalglobe.com/docs/how-to-save-task-outputs) documentation. ##Scheduled for Thursday 11/10/2016 BREAKING CHANGE: Update to Batch Workflows This applies only if you are submitting batch workflows using the Batch Workflow API endpoint. The batch workflow template will be revised to allow for more flexibility in adding batch values. The current request template will no longer work once this change is applied. Documentation and an example will be added here prior to the change. Current Batch Workflow documentation: http://gbdxdocs.digitalglobe.com/docs/workflow-api-course#section-batch-workflows [block:callout] { "type": "warning", "title": "The Material Sets API will be deprecated soon.", "body": "With new functionality like batch workflows and auto-ordering, this API is no longer needed. Contact gbdx-support@digitalglobe.com if you have any concerns." } [/block] ## October 13, 2016 TIME CHANGE: Today's platform upgrade will now take place between 1 PM and 5 PM MST. Today's platform maintenance includes a CATALOG outage and a brief WORKFLOW outage. Follow us on Twitter for updates. ## October 12, 2016 Tomorrow's maintenance window will include a catalog outage and a delay in workflow processing time. Users can submit workflows, but they may not be processed right away. The maintenance window is between 10 AM and 2 PM MST. Watch our Twitter feed (see above) for updates. ## October 6, 2016 There will be no weekly platform maintenance taking place today. ## September 29, 2016 The following maintenance will be taking place. GBDX Platform Maintenance - Minor functionality updates will be applied today. Scheduled Start: 29 September 2016 @ 10:00AM MT Scheduled End: 29 September 2016 @ 2:00PM MT During this maintenance window, you may experience slowness or temporary service interruptions while using the GBDX Platform. ## September 27, 2016 There will be unscheduled downtime for platform maintenance work starting at 6 PM MST. The main Catalog server will be restarted. The following services are impacted: * Workflow Service - Task-Worker * Catalog Service We appreciate your patience while we work to complete the maintenance. If you have any questions or issues please contact gbdx-support@digitalglobe.com ## September 22, 2016 GBDX Platform Maintenance - Critical catalog maintenance will be applied. Catalog Service outage should be expected during this time. This impacts the catalog API and the web application. Scheduled Start: 22 September 2016 @ 10:00AM MT Scheduled End: 22 September 2016 @ 2:00PM MT ------- ## September 15, 2016 The following maintenance will be taking place. GBDX Platform Maintenance - Various stability and functionality updates will be applied Scheduled Start: 15 September 2016 @ 10:00AM MT Scheduled End: 15 September 2016 @ 4:00PM MT During this maintenance window, you may experience slowness or temporary service interruptions while using the GBDX Platform. ------------ ## September 13, 2016 The GBDX workflow system has been running at normal speed since the weekend. The issue with task scheduling has been resolved. ------- ## September 9, 2016 1:50 PM MST - RESOLVED GBDX customers are experiencing longer than normal workflow processing times. **What’s going on?** Customer engagement with the GBDX platform is at an all-time high. We’ve seen a big increase in the number of workflows submitted over the past several weeks. The SQL query that schedules tasks is taking longer to run. The more workflows that are scheduled, the slower the query runs. We’re also investigating whether our Amazon Relational Database (RDS ) is contributing to the problem. **What’s the solution?** We’re working on optimizing the task scheduling query and the database. **When will it be fixed?** Resolving this issue is our top priority. We have dedicated team members working on query optimization and database tuning. We’ll test and deploy a fix as soon as we have it ready. Once we’re running at normal processing times again, it may take some extra time to work through the full backlog. **Do I need to resubmit my workflow?** • If you’ve successfully submitted a workflow, you don’t need to do anything. It’s in the queue and will be processed. • If you receive a 500 or 503 error when submitting a workflow, you will need to resubmit it. This error is due to submitting a workflow while server maintenance was occurring. • If your task’s status is “failed”, you’ll need to resubmit the workflow. The task may have timed out due to the longer processing times. We’ll post an update when this is resolved, and will continue to send status updates until we’ve worked through the backlog. ## September 9, 2016 The following maintenance will be taking place. Continued GBDX Platform Maintenance - task scheduler maintenance to improve/fix task queueing times. Workflows can still be submitted, but task queueing/scheduling continues to be delayed. Scheduled Start: 9 September 2016 @ 9:00AM MT Scheduled End: 9 September 2016 @ 5:00PM MT During this maintenance window, you may experience slowness or temporary service interruptions while using the GBDX Platform. ---------- ## September 8, 2016 The following maintenance will be taking place. GBDX Platform Maintenance - Various stability and functionality updates will be applied Scheduled Start: 8 September 2016 @ 10:00AM MT Scheduled End: 8 September 2016 @ 2:00PM MT During this maintenance window, you may experience slowness or temporary service interruptions while using the GBDX Platform. --------- ## September 6, 2016 1:00 PM MST - We are currently investigating a long running query in the Workflow system causing a delay before tasks are queued for execution. The following GBDX services are impacted: Workflow System We appreciate your patience. If you have any questions please contact gbdx-support@digitalglobe.com ##September 2, 2016 Today's platform release includes these new features: **Ordering with Callbacks** Now you can place an order and request a callback notification. Submit your order request to the new Ordering with Callbacks API, and we'll send you a notification when your order has been delivered. [Ordering with Callbacks documentation](http://gbdxdocs.digitalglobe.com/docs/ordering-course-v2#section-ordering-with-callback-notifications) **Run a Workflow with Callbacks** You can request callback notifications when you submit a workflow to the Workflow API. *Documentation coming soon.* **Waiting Task Status** A task can be set to the "waiting" state. Any continue request from the user will resume the task. *Documentation coming soon.* Note: Auto-ordering will release next week. ------- ## SEPT 1, 2016 - weekly platform release scheduled for today. The maintenance window is 10 AM to 2 PM. You may experience some platform slowness during this time. This release includes the new ordering callbacks API, workflow callbacks, and a "waiting" task status. -------- ## AUGUST 18, 2016 - PLATFORM MAINTENANCE NOTIFICATION The following maintenance will be taking place. GBDX Platform Maintenance - Various stability and functionality updates will be applied: - ProductCataloger fixes: Enhanced speed & reliability of product cataloging. Smarter retry system upon catalog API errors. - Catalog configuration: update/maintenance Scheduled Start: 18 August 2016 @ 10:00AM MT Scheduled End: 18 August 2016 @ 2:00PM MT During this maintenance window, you may experience slowness or temporary service interruptions while using the GBDX Platform. ------ ## July 12, 2016 **30 cm imagery is now available!** Now when you order imagery from Worldview-3, we'll deliver 30 cm resolution imagery. Learn more about [DigitalGlobe's 30 cm imagery](http://microsites.digitalglobe.com/30cm/). -------- ## June 9, 2016 **Batch Workflows** With batch workflows, you can now submit multiple workflows with one API request. A batch workflow request spawns multiple workflows that run the same tasks on multiple inputs concurrently. [Batch workflow documentation](http://gbdxdocs.digitalglobe.com/docs/workflow-api-course#section-batch-workflows-new-) ------- ## May 5, 2016 **Task User Impersonation** User can allow a task in a workflow access to run on their behalf. * Added "auth_required equired flag to task definition schema (true/false) * Added "impersonation_allowed" to the workflow definition. * The user token is added to runtime information when impersonation is allowed. [Task User Impersonation Documentation](http://gbdxdocs.digitalglobe.com/docs/workflow-api-course#task-user-impersonation) **Task Runtime Design** * In work directory, in addition to input ports.json, add an additional file called gbdx_runtime.json that contains task_id, workflow_id, and domain. * Location: /mnt/work/gbdx_runtime.json * Information is available to the worker, so this can be mounted inside the docker. #### Full documentation for changes to the Task Runtime design will be live Friday, May 6. Check back here for updates or follow us on Twitter. ------- ## April 28, 2016 **Orders V2 updates:** -Added a limitation of 100 images per order, and better error messaging when the limit is exceeded. -When duplicate catalog IDs are included in an order, the order is allowed and the duplicates are collapsed into a single catalog ID. **Web Application** Updates to the credit card section of self-registration to explain credit card requirement and allow for A/B testing. ------- ## April 26, 2016 The Postman collection has been updated to include a Getting Started section and two new workflow requests (stdout and stderr outputs). Download and import the latest [GBDX Postman collection file](http://gbdxdocs.digitalglobe.com/docs/postman-instructions-collections). Two new endpoints have been added to the Workflow API. [STDOUT output from a task in a workflow](http://gbdxdocs.digitalglobe.com/docs/stdout-output-from-a-workflow-task) [STDERR output from a task in a workflow](http://gbdxdocs.digitalglobe.com/docs/stderr-output-from-a-workflow-task) -------- ## March 31, 2016 There is no platform release this week. --------- ## March 24, 2016 Bug fixes ## March 17, 2016 Catalog improvements: -Upgraded to OrientDB 2.1.11 -Bug fixes Workflows -added multiplex inputs for workflows (more information coming soon) Web application -The web application now uses the Ordering V2 api. This change is invisible to web app users. ## March 10, 2016 Bug fixes: -Email address is no longer case-sensitive anywhere in the web application -Mailing address is now included in account creation email to GBDX Support New: -Added “vector” as an account type to support Vector customers Operations: Reliability and performance improvements ## March 1, 2016 Bug fix: Some Chrome users in the Orbit desktop could not see the login screen. This has been fixed in the production environment. ## February 29, 2016 The Postman collection has been updated with the new Ordering V2 API requests. You'll need to import the latest GBDX collection. <a href="http://gbdxdocs.digitalglobe.com/docs/lesson-postman-api-requests" target="_blank">Postman Setup Instructions</a> <a href="http://gbdxdocs.digitalglobe.com/v1/docs/postman-collection-1" target="_blank">Postman Collection</a> ## February 25, 2016 Ordering V2 is here! Ordering V2 provides big gains in performance, reliability, and ease of use. These improvements include: * The ability to place as many orders as you want, as quickly as you want. * New factory throttling guarantees we won't overload the DigitalGlobe (DG) factory. This means fewer ordering issues or failures for our customers. * No more duplicate orders. If a catalog ID has been ordered once, we won't order it again. * Simplified REST API. You'll use a single endpoint to place an order and check order status. API Responses have been simplified so you can quickly find the information you need. Note: In version 2, the term order_id replaces sales_order_number. Imagery ordered using Ordering V1 has been migrated. If you order imagery that has been ordered previously, your order will be satisfied immediately. [block:callout] { "type": "warning", "title": "Ordering V1 will be supported for the next two weeks", "body": "Please migrate to Ordering V2 during this time." } [/block] For more information: Watch this [short video](http://gbdxdocs.digitalglobe.com/v1/docs/video-ordering-v2) to learn how to use the new Ordering APIs [Ordering Course V2](http://gbdxdocs.digitalglobe.com/docs/ordering-course-v2) [Check Orders Heartbeat](http://gbdxdocs.digitalglobe.com/docs/orders-heartbeat-v2) [Place an Order](http://gbdxdocs.digitalglobe.com/docs/place-an-order-v2) [Get Order Status](http://gbdxdocs.digitalglobe.com/docs/get-order-status-v2) ## February 18, 2016 Bug fix - Evaluation Tier Users can’t add materials from approved geographic areas to material sets ## February 11, 2016 Bug fix - New Users activating accounts get error message, but account is activated