GBDX

GBDX Release Notes

See the GBDX Platform Status Page for real-time platform operations status and maintenance announcements.

Follow @GBDXReleaseLog on Twitter.

See the GBDX Deprecation Schedule for a list of deprecated components and their retirement dates.

August 10, 2018

GBDX University has been updated with some design and navigation improvements. Updates include:

A cleaner landing page design An additional layer of navigation in the left navigation pane
User documentation and API reference material each have their own section The API reference section uses a new 3-column format

The Validate Token request was updated to include client ID for tracking purposes.

The Postman collection has been updated to reflect recent API retirements.

The GBDX Thumbnail Service API was removed All references to previously deprecated APIs were removed
The "submit a workflow" example was updated The Postman Environment file was updated to remove API key since it's no longer used for GBDX Authentication.

July 23, 2018

A number of components and tasks have been retired from the GBDX platform during July. Please see the GBDX Deprecation Schedule for a complete list.

June 30, 2018

The ENVI® Task Engine software on the GBDX platform has been updated with a licensing maintenance deployment of new v1.3.2 version for all ENVI tasks on GBDX. The new v1.3.2 version of ENVI tasks will be the active supported version of the ENVI® Task Engine software on GBDX effective immediately. All workflows that run ENVI tasks without explicit task version execution will continue to operate since the latest v1.3.2 version will automatically be executed. Any existing workflows with explicit ENVI task version execution of v1.3.1 or older will need to be updated by either removing the explicit task version execution (recommended) or updating the explicit version being executed to "1.3.2". For more information on GBDX task versioning behavior in workflows please consult the documentation on this topic:
https://gbdxdocs.digitalglobe.com/docs/how-to-version-a-task#section-using-a-versioned-task-in-a-workflow

June 21, 2018

The following functionality and tasks on the GBDX platform have been deprecated and will be retired on 7/23/2018:

Functionality:
-Workflow Library Tasks

Tasks:
Change Detection Image Pair Alignment Task (cd_prep)
Urban Change Detection Task (urban_change)
Cloud Mask Task (protogenV2RAC)
Soil Mask Task (protogenV2RAS)
Vegetation Mask Task (protogenV2RAV)
Water Mask Task (protogenV2RAW)

See the GBDX Deprecation Schedule for links to deprecation notices and migration instructions. Follow along on http://status.geobigdata.io/incidents/xmg3sdpxck2r .

May 25, 2018

The ENVI® Task Engine software available on the GBDX platform has been updated to the latest ENVI version 5.5 available from Harris Geospatial Solutions.

The following new ENVI tasks have been added to GBDX platform:
ENVI® Build Grid Definition From Raster
ENVI® Build Layer Stack
ENVI® Create Subrects From ROI
ENVI® Export Raster To NITF20
ENVI® Export Raster To NITF21
ENVI® Export Raster To NSIF10
ENVI® Export Raster To TIFF
ENVI® Label Regions
ENVI® Linear Spectral Unmixing
ENVI® Matched Filter
ENVI® Mixture Tuned Matched Filter
ENVI® Pixel Purity Index
ENVI® SAM Image Difference
ENVI® Topographic Features
ENVI® Topographic Modeling

The ENVI raster/time series tasks cannot be supported on GBDX. The following tasks have been removed from the platform since they were not functional:

ENVI® Build Raster Series
ENVI® Build Time Series
ENVI® Regrid Raster Series
ENVI® Regrid Raster Series By Index
ENVI® Regrid Raster Series By Intersection
ENVI® Regrid Raster Series By Union

May 22, 2018

The GBDX Thumbnail Service has been deprecated and will be retired on July 22, 2018. See GBDX Thumbnail Service Deprecation Notice for migration instructions.

May 8, 2018

The GBDX Web Application has been deprecated and will be retired on July 9, 2018.See the GBDX Web App Deprecation Notice for more information.

May 7, 2018

IMPORTANT: GBDX Accounts that have been inactive for 60 days will be deactivated on May 22, 2018.
To keep your account active, simply sign in with your credentials to https://dashboard.geobigdata.io before May 22nd. Read the full announcement on the GBDX Status Page.

April 19, 2018

Today we are announcing the deprecation of the "StageDataToS3" task. It will be retired on June 18, 2018.
Read the StageDatatoS3 Task Deprecation Announcement
Learn How to Save Task Outputs using the `'persist' flag or the new "SaveToS3" task

April 12, 2018

GBDX Raster Data Access (RDA) is now available. See Raster Data Access Course for an overview and more information.

With this release, the following IDAHO get chip services are now deprecated, and will be retired on July 11, 2018.

These services will no longer be available on GBDX at the end-of-life date of July 11, 2018. We recommend that GBDX users who need to access imagery chips utilize our new Raster Data Access (RDA) framework as described in the Getting an RDA Chip using gbdxtools.

March 22, 2018

Reminder: GBDX will be offline for maintenance starting tomorrow at 8 AM MST while we deploy the authentication update. See https://gbdxdocs.digitalglobe.com/docs/authentication-changes for more information.

February 22, 2018

2nd Breaking Change Notice: Summary: The GBDX team will release a new Authentication system on Thursday, March 22, 2018. The new system is designed with a goal of significant improvements in reliability. See the notification on the GBDX Status Page for details.

February 8, 2018

Breaking Change Notification: The GBDX nvidiagpu domain will be retired Thursday, April 5, 2018

Action required: If you are using the "nvidiagpu" domain, you will need to move to the nvidiag2 or nvidiap2 domain by this date. More information about these domains can be found in the Amazon EC2 instances in the GBDX Configuration documentation.

If you need help with this, please contact GBDX Support.

February 6, 2018

ENVI® Task Engine Update and Newly Registered Tasks
The underlying ENVI® Task Engine software supplied by Harris Geospatial Solutions has been updated to version ENVI v5.4.1.
The ENVI task runner now supports input of DigitalGlobe imagery that has been preprocessed using the Advanced Image Preprocessor with AComp task (AOP_Strip_Processor) with the dynamic range adjustment (DRA) option enabled which results in a 3-band RGB unsigned byte dataset.
The ENVI task runner now supports input of raw WorldView-3 SWIR imagery products, for more information on this workflow please consult the ENVI task runner documentation

The following new ENVI tasks are now available on GBDX with associated task documentation on GBDX University (which now makes the total # of ENVI tasks on GBDX = 153):
ENVI® Binary Morphological Filter
ENVI® Cast Raster
ENVI® Create Subrects From Distance
ENVI® Create Subrects From Pixels
ENVI® Create Subrects From Tile Count
ENVI® Create Subrects From Vector
ENVI® Dice Raster By Subrects
ENVI® Dice Raster By Distance
ENVI® Dice Raster By Pixels
ENVI® Dice Raster By Tile Count
ENVI® Dice Raster By Vector
ENVI® Export Rasters To Directory
ENVI® Export Raster To ENVI
ENVI® First Order Entropy Texture
ENVI® Grayscale Morphological Filter
ENVI® Label Entropy Texture
ENVI® Mirror Raster
ENVI® Pixelwise Band Math Raster
ENVI® Rank Strength Texture
ENVI® ROI Statistics
ENVI® Transpose Raster

January 29, 2018

BREAKING CHANGE NOTIFICATION

Summary: The GBDX team will release a new Authentication system on Thursday, March 22, 2018. The new system is designed with a goal of significant improvements in reliability.

Release Date: Thursday, March 22, 2018.

Impact: The known impacts of this change are:
-GBDX downtime is required for migration and deployment. This deployment will take 4-8 hours.
-Passwords may need to be reset following the deployment.
-A new token will be required. Old tokens will not work once the new system is deployed.
-The "validate token" response will change.

More information:
The Authentication Changes document describes the list of upcoming changes. Since this project is still in development, any additional changes that occur during development will be documented here.

Subscribe to the

January 11, 2018

taskOwnerEmail is now a required field in the task definition.

Impact: Any new task or new version of a task must include a value for this field. Existing tasks were not update. However, we recommend adding the field and value to your existing task. This can be done by a "put" request, and does not require the task to be re-registered.

Example Task Definition

December 18, 2017

Catalog V2 API and Dataset Documentation Updates:

The following updates have been made to the GBDX University Catalog V2 API and Dataset docs.

  • Datasets Docs: The section on GBDX University called "Datasets on GBDX" now includes an end-to-end doc for using each dataset we have cataloged. If you're looking for search examples, properties, and more, these docs are the source of truth.

  • Cat V2 API Course: removed examples for specific datasets, re-organized and updated content, added a table of contents, added links to each dataset doc.

  • Catalog V2 Metadata: the information from this doc has been moved to the Catalog V2 API course, and the doc has been "unpublished". Full path links to this page will still work.

*API try it out pages: simplified this section to 3 pages. Instead of having multiple pages for different types of searches, the "search the catalog" page uses an example that includes all possible search criteria. Other search example pages have been unpublished, but full path links to them will still work.

November 9, 2017

"taskOwnerEmail" has been added as an optional element of the task definition.
Example Task Definition

On January 11, 2018, this will become a required field for new tasks and new versions of a task. See the "breaking change notification" below.

November 3, 2017 - BREAKING CHANGE NOTIFICATION

  • Thursday, Nov 9, 2017: taskOwnerEmail will be added to the task definition as an optional field.
  • Breaking Change: Thursday, Jan 11, 2018: taskOwnerEmail will be updated to be a required field.

Impact: Once this field is required, any new task or new version of a task must include a value for this field. Existing tasks will not be impacted. However, we recommend adding the field and value to your existing task. This can be done by a "put" request, and does not require the task to be re-registered.

taskOwnerEmail must be in a valid email format. Example: test@test.com

Example task definition:

{
	"inputPortDescriptors": [{
			"required": true,
			"description": "A string input.",
			"name": "inputstring",
			"type": "string"
		},
		{
			"name": "dependency_input",
			"type": "string"
		}
	],
	"outputPortDescriptors": [{
		"name": "dependency_output",
		"type": "string"
	}],
	"containerDescriptors": [{
		"type": "DOCKER",
		"command": "",
		"properties": {
			"image": "tdgp/test-success",
			"mounts": [{
				"local": "$task_data_dir",
				"container": "/mnt/work",
				"read_only": false
			}]
		}
	}],
	"description": "Runs a no-op task that writes successful output status.",
	"name": "test-success",
	"taskOwnerEmail": "TEST@TEST.com",
	"version": "0.0.1",
	"properties": null
}

October 26, 2017

Task Execution Removed from the Web Application
We're making some changes to the GBDX web application to optimize for evaluating our imagery search and discovery options. We've taken the first step toward this goal by removing task execution from the web application. We offer more flexibility to run tasks in a way that meets your business needs through direct API access, AnswerFactory, and our python-based tools suite "gbdxtools". You can explore these options in our developer documentation on GBDX University. You can still browse the task library to see a sample list of certified algorithms available on GBDX.

September 25, 2017

ENVI v5.4.1 Upgrade on GBDX

The Platform team is excited to announce that the version of the ENVI Services Engine software available on the GBDX platform has been upgraded to the most recent 5.4 Service Pack 1 (v5.4.1) recently released by Harris Geospatial Solutions. This upgrade involved updates to the GBDX platform ENVI task runner and deployment of all new ENVI_ tasks with GBDX task versioning of v1.1.0. Furthermore, this new ENVI v5.4.1 also includes full support for Sentinel-2 on AWS datasets. Consequently, the Sentinel-2 data that was recently cataloged for availability on the GBDX platform can now be passed into the ENVI analytic tasks that perform raster processing suitable for Sentinel-2 imagery. For more informatinon on the Sentinel-2 dataset, see https://gbdxdocs.digitalglobe.com/docs/sentinel-2

The new ENVI tasks on GBDX include the ability to specify the desired raster band grouping from the Sentinel-2 dataset ("M1-10m" | "M2-20m" | "M3-60m") via input port designation when the ENVI task is executed. Here is a simple gbdxtools Python script example illustrating effective execution of the ENVI_SpectralIndices task on the "M1-10m" bands of a Sentinel-2 dataset:

from gbdxtools import Interface
gbdx = Interface()

raster_location = 's3://sentinel-s2-l1c/tiles/15/R/XP/2016/9/3/0'

task = gbdx.Task('ENVI_SpectralIndices:1.1.0')
task.inputs.input_raster = raster_location
task.inputs.input_raster_format = 'sentinel-2'
task.inputs.input_raster_band_grouping = 'M1-10m'
task.inputs.index = '["Normalized Difference Vegetation Index"]'

wf = gbdx.Workflow([task])
wf.savedata(task.outputs.output_raster_uri, location='ENVI_Indices')

wf.execute()

For those users who wish to continue using the previous ENVI 5.3 Service Pack 2 (v5.3.2) version of the ENVI tasks these are still available for execution on the GBDX platform by explicitly calling v1.0.6 of the desired ENVI task (e.g. ENVI_SpectralIndices:1.0.6). Please keep in mind per GBDX task versioning and workflow system behavior if an ENVI task is simply executed by name the workflow system will always run the most recently registered version. Consequently, if you are developing operational applications where ENVI task execution is best tested and deployed based on guaranteed behavior of a specific task version please make sure to explicitly call the desired task version in your workflow definition. For more information on GBDX task versioning behavior please consult the documentation on this topic:
https://gbdxdocs.digitalglobe.com/docs/how-to-version-a-task

September 11, 2017

We're updating our web application, https://gbdx.geobigdata.io, to create a simpler and more flexible GBDX user experience.

In October, we'll introduce a new, streamlined web application experience, focusing on actions best achieved through a graphical user interface. The GBDX web application will be optimized for discovering and ordering imagery. Task execution will be removed from the web application, but will still be available through all other means: direct API access, AnswerFactory, and our python-based tools suite "gbdxtools". These tools offer more flexibility for running tasks in ways that meet all business needs.

We'll remind you this change is coming when we get closer to the date. In the meantime, if you have any questions, please contact us at gbdx-support@digitalglobe.com

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 .

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.

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 Postman Instructions.

Subscribe to the GBDX Status page scheduled maintenance.

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 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 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 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 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.

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 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

The Material Sets API will be deprecated soon.

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.

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

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.


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


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

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.

Two new endpoints have been added to the Workflow API.
STDOUT output from a task in a workflow
STDERR output from a task in a workflow


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.

Postman Setup Instructions
Postman Collection

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.

Ordering V1 will be supported for the next two weeks

Please migrate to Ordering V2 during this time.

For more information:

Watch this short video to learn how to use the new Ordering APIs

Ordering Course V2
Check Orders Heartbeat
Place an Order
Get Order Status

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