Releases and Changes

SpaceKnow Backend Release 146

Released on 2018-10-11. List of changes since release 145 follows.

Highlights

  • noaa VIIRS/Daily data have been made available in the platform.
  • kraken-download.py CLI tool now supports serving all raster results in SKI format. Use +ski in --types argument to download SKI files.

Changes in Deployed Algorithms

  • weather detection algorithm which detects clouds and snow has been added.
  • Prediction quality of destruction and ships algorithms have been improved.
  • S-score metadatum has been added to SKI results of all algorithms for pl PSOrthoTile imagery. See Kraken API documentation for more information.

CLI Tool Changes

  • +mask flag in --types argument of kraken-download.py is deprecated and will be removed on 2019-01-01. Use +png instead.
  • kraken-download.py now saves bands.json for all map types that support it, e.g. night lights, NDVI, NDBI, NDMI, change detection heatmaps.

SpaceKnow Backend Release 145

Released on 2018-10-02. List of changes since release 144 follows.

REST API Changes

  • Kraken API grid endpoint now supports serving all raster results in SKI format.

SpaceKnow Backend Release 144

Released on 2018-09-27. List of changes since release 141.2 follows.

Highlights

  • NOAA VIIRS night-time monthly composites have been connected.
  • New algorithms NDMI, NDBI and sar-blobs are now available.

REST API Changes

  • Kraken grid endpoint serves mean pixel intensities per band in bands.json file.
  • Error codes RESOLUTION-TOO-COARSE and UNSUPPORTED-SATALLITE have been replaced by UNSUPPORTED-IMAGERY.
  • Kraken API grid endpoint no longer serves data for invalid pixels in heatmap raster output.
  • Tasking API endpoint /tasking/get-status and ../initiate now contain nextTry key. See documentation of Tasking API for more information.
  • Object detection algorithms now also provide area.json grid file (known from semantic segmentation algorithms) in Kraken API for newly generated map IDs.

Changes in Deployed Algorithms

  • Prediction quality of NDVI, ships, cars-30-idaho-pansharpened and cars-50-idaho-pansharpened improved.
  • New algorithms NDMI, NDBI and sar-blobs are now available.

CLI Tool Changes

  • bands filter has been added to ragnar-filter.py.
  • kraken-download.py now outputs area.json for all semantic segmentation and object detection algorithms. (solar-panels, ships...)

SpaceKnow Backend Release 141.2

Released on 2018-09-07. List of changes since release 141.1 follows.

Important Fixes

  • HTTP 503 Server Error: Service Unavailable: Back-end server is at capacity errors when downloading GBDX IDAHO imagery should now be mitigated by request throttling.
  • Broken authentication in ragnar-order.py, ragnar-download.py has been fixed.

SpaceKnow Backend Release 141.1

Released on 2018-09-05. List of changes since release 137 follows.

Highlights

  • Kraken API now supports destruction algorithm.
  • Mode and orbit pass metadata have been added to ee COPERNICUS/S1_GRD scenes.

Deprecation Notices

  • /user/get, /user/promote and /user/search endpoints of User API have been deprecated. Use Auth0 Management API directly together with User API /user/manage endpoint instead.

REST API Changes

  • User API has got new endpoint /user/manage. This endpoint returns a “Bearer” which can be used to access Auth0 management API directly. See User API docs for more info.

Changes in Deployed Algorithms

  • Kraken API now supports destruction algorithm.

Important Fixes

  • Empty or dashed lines are no longer present at borders of Kraken tiles.

CLI Tool Changes

  • canonicalize-geojson.py has been introduced. It validates and canonicalizes a GeoJSON file.
  • orbit-pass and mode filters have been added to ragnar-filter.py.

SpaceKnow Backend Release 137

Released on 2018-08-09. List of changes since release 135 follows.

Highlights

  • Kraken API now support change detection on Sentinel 2 imagery.
  • anomalousRatio metadatum has been added for Planet scenes.
  • Planet data now contain corrupt pixel masks which can be used for distinction between blackfill and corrupt pixels. See Ragnar API documentation for more information.

REST API Changes

  • Multiple band names in gbdx provider have been reduced to single, canonical (lowercase) name.
  • Panchromatic band of GBDX WV-01 is now called panchromatic for consistency. Previously it was known as Panchromatic, pan, grayscale, greyscale.
  • Ordinary users have been given permission to access User API /user/authorize endpoint. See Check Token for more information.
  • Paths of the following API endpoints have been changed. The old paths are deprecated and will be removed in version 140.
    • /size-info endpoint of Ragnar API has been moved to path /imagery/size-info.
    • All Ninja API endpoint paths have been prefixed with /ninja.
  • anomalousRatio metadatum has been added for Planet scenes.

Changes in Deployed Algorithms

  • The NDVI algorithm now supports ee COPERNICUS/S2 imagery.

CLI Tool Changes

  • ragnar-filter.py daily and other periodic filters take anomalous ratio into account.
  • rangar-filter.py anomalous-ratio filter has been added.

Known Issues

  • Occasionally, 1px wide empty or dashed lines are present at borders of Kraken tiles.

SpaceKnow Backend Release 135

Released on 2018-07-26. List of changes since release 133 follows.

Highlights

  • Kraken API now supports SAR change algorithm.

REST API Changes

  • Min-intersection filter of Ragnar API search endpoint now behaves better: if omitted or set to zero, only scenes which have intersection with area greater than zero are returned as opposed to all scenes with arbitrary intersection (e.g. point, line, and other non-area-based intersections).
  • Input GeoJSON (i.e. extent) to various APIs, including Ragnar, Kraken and Credits API, must have non-zero area as opposed to former and weaker condition to have non-empty minimum bounding rectangle.

Changes in Deployed Algorithms

  • Detections of large houses are no longer missing in the resulting GeoJSON. The raster masks of these large houses were not affected.

CLI Tool Changes

  • KrakenDownloader no longer downloads tiles outside of the requested area and the footprint of the scene. The result is a significant speed-up in downloading tiles for certain extents. It also reduces the frequency of TILE-DOES-NOT-EXIST errors during downloading.

Known Issues

  • Occasionally, 1px of empty lines or dashed lines occur at borders of Kraken tiles.

SpaceKnow Backend Release 133

Released on 2018-07-13. List of changes since release 130.1 follows.

REST API Changes

  • Allowed HTTP methods were unified across all APIs. Kraken Grid endpoint allows GET requests only, all other handlers allow POST only.

Changes in Deployed Algorithms

  • Prediction quality of the following algorithms has been improved on gbdx idaho-pansharpened imagery: EME, trees, WRUNC.
  • The change detection algorithm has been fixed to produce correct attention regions.

CLI Tool Changes

  • New tool generate-credentials.py for generating encrypted credentials has been introduced. It can be used to conviently generate credentials.
  • ragnar-filter.py earliest [--count=N] was introduced.
  • kraken-allocate.py no longer has the -n, --dry-run` functionality. Use ``ragnar-availability-report.py instead.
  • ragnar-availability-report.py now includes new cumulative billable area [sq km] column in its CSV output. It is the new recommended way to estimate cost of planned delivery.
  • ragnar-filter.py yearly|montly|weekly|daily now take cloud cover into account, preferring cloud-free imagery.
  • ragnar-availability-report.py has got new cumulative area [sq km] column in its CSV output. It shows total amount of mosaicked imagery to be analyzed.

SpaceKnow Backend Release 130

Released on 2018-06-19. List of changes since release 128 follows.

Highlights

  • Maximum extent area in Kraken API has been raised from 900 MPix to 4.9 GPix. This is 21 x 21 km at 0.3 m/pix resolution, which de-facto means “unlimited” as GBDX scenes are under 20 x 20 km and all other providers have lower resolution.
  • Datasets MODIS/006/MOD08_M3 and MODIS/006/MYD08_M3 for provider ee are now available through Ragnar API. See Available Satellite Imagery Providers for more info and 2. (Optionally) Filter Scene-tile Records for usefult tips.
  • Kraken API now guarantees that whole requested area is covered by at most four tiles. In other words, the returned tiles are at sufficiently low zoom level so at most four of them covers the whole AOI.

REST API Changes

  • Kraken API now guarantees that whole requested area is covered by at most four tiles. In other words, the returned tiles are at sufficiently low zoom level so at most four of them covers the whole AOI.
  • Tile endpoints of Credits API have been dropped.
  • Kraken API does not longer support tiles as input to its release endpoints.

Other Changes

CLI Tool Changes

  • ragnar-filter.py periodic filters used with --aggregate-until got support for the --clip option.

SpaceKnow Backend Release 128

Released on 2018-06-06. List of changes since release 126 follows.

REST API Changes

  • Map IDs returned by Kraken API now expire in 365 days.
  • The precision of allocated area in Credits API has been improved.
  • The precision of results in area.json has been improved.

Changes in Deployed Algorithms

  • Prediction quality of all algorithms has been improved.

SpaceKnow Backend Release 126

Released on 2018-05-24. List of changes since release 123.1 follows.

Highlights

  • idaho-swir and idaho-panchromatic datasets were introduced. Previously, scenes from SWIR satellites were mixed in idaho-pansharpened and idaho datasets.
  • preview dataset was similarly broken up. Use preview-multispectral to order idaho-pansharpened scenes, preview-panchromatic to order idaho-panchromatic scenes and preview-swir to order idaho-swir scenes. The ordering API has remained the same.
  • idaho dataset was removed.
  • Kraken API now supports NDVI computation, trees algorithm, and EME algorithm.
  • Sentinel 1 GRD backscatter data are now fully available.

Changes in Deployed Algorithms

  • Prediction quality of following algorithms has been improved:
    • houses on gbdx idaho-pansharpened,
    • coal and lithium on ee COPERNICUS/S2.

Important Fixes

  • Planet visualization has been improved. It no longer gives too bright or too dark results.

Other Changes

  • Reflectance parameters for Planet scenes are available only from metadata stored inside returned SKIs and not in Ragnar API search response.

CLI Tool Changes

  • ragnar-search.py may tile areas into a slightly different grid due to changes in calculation of AOI bounding box width and height.

SpaceKnow Backend Release 123.1

Released on 2018-05-04. List of changes since release 123 follows.

Highlights

  • New WRUNC Change service introduced. It can be used to find differences in individual WRUNC classes (e.g. roads) between two images.

REST API Changes

  • Kraken API endpoint /retrieve now returns detectionsGeojsonUrl in the response for map types which have available vector output detections.geojson. GeoJSON with detections for the whole AOI is available at this url.
  • Kraken API /grid endpoint has been sped up.

Changes in Deployed Algorithms

  • Following properties have been introduced for the output GeoJSON of aircraft and ships algorithms (both on pl PSOrthoTile dataset): aspectRatio, reflectance, confidence.

CLI Tool Changes

  • kraken-download.py now supports --max-zoom <level> option to constrain zoom level of fetched PNGs. This is useful to reduce resolution of fetched files, saving bandwidth and time.
  • ragnar-filter.py periodic filters (weekly, daily, ...) got new option --aggregate-until <sqkm>. It is useful to generate an imagery coverage of AOIs.
  • kraken-download.py PNG tile fetching has been sped up tenfold by downloading them concurrently.
  • ragnar-availability-report.py has got new --coverage-geojson <file> option to write GeoJSON that contains AOI coverage for each requested time period. This is useful for communicating what part of their AOIs is covered by imagery.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened and pl PSOrthoTile gives only approximate truecolor. It performs well for some scenes, other scenes may have shifted histograms.

SpaceKnow Backend Release 123

Released on 2018-04-30. List of changes since release 120.1 follows.

Highlights

  • New CLI ragnar-grid.py to generate grid of tiles covering input GeoJSON has been introduced, see documentation and its --help text.
  • New CLI kraken-geotiff.py to convert output of kraken-download.py to georeferenced GeoTIFF files has been introduced, see documentation and its --help text.
  • Support for search for scenes from provider ee dataset COPERNICUS/S1_GRD (ESA Sentinel 1 satellites) was added.

REST API Changes

  • Allocation checking through Credits API now only applies to high-resolution imagery. Other imagery is not publicly available and requires special permission.

Changes in Deployed Algorithms

  • Prediction quality of following algorithms has been improved: houses, cows (both on gbdx idaho-pansharpened), lithium (on ee COPERNICUS/S2), ships and aircraft (both on pl psorthotile).

Important Fixes

  • Proper projection of tiles in Kraken maps has been implemented. This fixes frames around individual tiles which were visible on Planet imagery and analyses.

CLI Tool Changes

  • ragnar-search.py now supports alternative UTM tilling algorithm, see --help for more info. Generated tiles are aligned on grid with respect to the origin of specified UTM zone.
  • New CLI ragnar-grid.py to generate grid of tiles covering input GeoJSON has been introduced, see documentation and its --help text.
  • ragnar-order.py now defaults to -j 50 instead of -j 1 because the former default could cause it to run for days to process just a couple of scenes.
  • ragnar-search.py and ragnar-filter.py no longer write output files directly. Instead, they write to {final}.temp file and rename it to final output file atomically at the end. This ensures that incomplete files aren’t accidentally used.
  • ragnar-download.py and kraken-download.py no longer append to failed-records.jsons files, they overwrite them instead. This is less surprising behavior.
  • New CLI kraken-geotiff.py to convert output of kraken-download.py to georeferenced GeoTIFF files has been introduced, see documentation and its --help text.
  • Example of jq expression to export available-tiles.jsons as a CSV file has been added to CLI docs.
  • ragnar-get-scene.py script was introduced to fetch and dump scene metadata.
  • ragnar-availability-report.py CLI tool has been introduced to create a CSV availability table out of available tiles.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened and pl PSOrthoTile gives only approximate truecolor. It performs well for some scenes, other scenes may have shifted histograms.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.

SpaceKnow Backend Release 120

Released on 2018-04-12. List of changes since release 118 follows.

Highlights

  • ee provider datasets LANDSAT/LC8_L1T and LANDSAT/LE7_L1T will be removed during April. New datasets LANDSAT/LC08/C01/T1, LANDSAT/LE07/C01/T1 providing fresh data have been introduced.

REST API Changes

  • Ragnar API and Kraken API GeoJSON endpoints now check Credits allocation only in part of the requested extent which is covered by requested scene’s footprint.
  • Minimum 5 km2 limit is no longer enforced in Ragnar API /imagery/order endpoint. To order a scene, it is sufficient to allocate minimum billable area intersecting with the scene.

Changes in Deployed Algorithms

  • Prediction quality of following algorithms has been improved: cranes, solar-panels (both on gbdx idaho-pansharpened) and coal (on ee COPERNICUS/S2).

Known Issues

  • Autovisualization of gbdx idaho-pansharpened and pl PSOrthoTile gives only approximate truecolor. It performs well for some scenes, other scenes may have shifted histograms.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • There are visible “frames” around Planet imagery tiles and analysis result masks. This is a display-only problem not affecting vector analysis results. This will be fixed in future by using proper image transformation.

SpaceKnow Backend Release 118

Released on 2018-03-28. List of changes since release 116.2 follows.

Highlights

  • Kraken API now supports cows, lithium, and cranes algorithms.
  • Planet and Airbus imagery provider integration is now based on the new Phoenix system. This improves caching, speed, etc. Hooray!

Changes in Deployed Algorithms

  • Prediction quality of following algorithms has been improved: cars, houses (all of them on gbdx idaho-pansharpened) and coal (on ee COPERNICUS/S2).
  • The construction class of houses algorithm has been split to constructions-medium and constructions-early classes (indicating the phase of a house construction).

Known Issues

  • Autovisualization of gbdx idaho-pansharpened and pl PSOrthoTile gives only approximate truecolor. It performs well for some scenes, other scenes may have shifted histograms.
  • Urthecast imagery is currently unavailable.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • There are visible “frames” around Planet imagery tiles and analysis result masks. This is a display-only problem not affecting vector analysis results. This will be fixed in future by using proper image transformation.

SpaceKnow Backend Release 116.2

Released on 2018-03-15. List of changes since release 115.1 follows.

Highlights

  • Kraken API now supports houses algorithm.

REST API Changes

  • Ragnar API order endpoint now requires extent parameter, see Order Scene. Passed extent must be allocated.
  • Ragnar API order pipelines finish only after the order gets into DELIVERED or FAILED state. It used to finish just after the order was placed.
  • Ragnar API order retrieve endpoints now return only status, it no longer returns providerOrderId nor previewSceneId.
  • Rangar returns raw Earth Engine metadata in the form of an auxiliary file in SKIs.

Changes in Deployed Algorithms

  • Performance of WRUNC algorithm has been improved on gbdx idaho-pansharpened imagery.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened and pl PSOrthoTile gives only approximate truecolor. It performs well for some scenes, other scenes may have shifted histograms.
  • Urthecast imagery is currently unavailable.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • There are visible “frames” around Planet imagery tiles and analysis result masks. This is a display-only problem not affecting vector analysis results. This will be fixed in future by using proper image transformation.
  • Search and download of Planet imagery is unnecessarily slow. Search can take up to tens of minutes on large areas and long time spans. Fetching imagery can currently take over 15 minutes. This is being fixed, but needs architectural changes. This is expected to be fixed by Q1 2018.

SpaceKnow Backend Release 115

Released on 2018-03-05. List of changes since release 113 follows.

Highlights

  • New Kraken API GeoJSON endpoints have been introduced. It is now possible to release Kraken specifying area of interest as GeoJSON instead of specifying tiles. See documentation. for more information.
  • Kraken API now supports coal algorithm.

REST API Changes

  • Satellite azimuth has been added to Copernicus/S2 dataset and all GBDX datasets.
  • geojson/geometry/save response has been changed. It now contains canonicalized geometry, see documentation.

Changes in Deployed Algorithms

  • Prediction quality of following algorithms has been improved on gbdx idaho-pansharpened: containers, pools, ships, solar-panels.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened and pl PSOrthoTile gives only approximate truecolor. It performs well for some scenes, other scenes may have shifted histograms.
  • Urthecast imagery is currently unavailable.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • There are visible “frames” around Planet imagery tiles and analysis result masks. This is a display-only problem not affecting vector analysis results. This will be fixed in future by using proper image transformation.
  • Search and download of Planet imagery is unnecessarily slow. Search can take up to tens of minutes on large areas and long time spans. Fetching imagery can currently take over 15 minutes. This is being fixed, but needs architectural changes. This is expected to be fixed by Q1 2018.

SpaceKnow Backend Release 113

Released on 2018-02-20. List of changes since release 111 follows.

Changes in Deployed Algorithms

  • Prediction quality of the solar panels algorithm has been improved on gbdx idaho-pansharpened dataset.

Important Fixes

  • Incorrect rendering of change detection heatmaps has been fixed.

Other Changes

  • Swimming pool algorithm has been made available to all users.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened and pl PSOrthoTile gives only approximate truecolor. It performs well for some scenes, other scenes may have shifted histograms.
  • Urthecast imagery is currently unavailable.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • There are visible “frames” around Planet imagery tiles and analysis result masks. This is a display-only problem not affecting vector analysis results. This will be fixed in future by using proper image transformation.
  • Search and download of Planet imagery is unnecessarily slow. Search can take up to tens of minutes on large areas and long time spans. Fetching imagery can currently take over 15 minutes. This is being fixed, but needs architectural changes. This is expected to be fixed by Q1 2018.

CLI Tool Changes

  • ragnar-allocate.py has been improved to properly allocate large areas.

SpaceKnow Backend Release 111

Released on 2018-02-09. List of changes since release 109 follows.

Highlights

  • Kraken API now supports pools algorithm.

REST API Changes

  • GeoJSON schemas for object detection algorithms have been augmented with count property indicating number of detected objects in the GeoJSON Feature. orientation property is not present when count is greater than 1.
  • Files API has been removed, storage URLs are returned by the APIs instead.

Changes in Deployed Algorithms

  • Cars count estimation of detections where multiple cars are joint together has been improved by introducing the count property (see above).
  • Prediction quality of the boats, cars, change, containers, pools and solar-panels detection algorithms has been improved on the gbdx idaho-pansharpened dataset.
  • Prediction quality of the ships and WRUNC algorithms has been improved on the pl PSOrthoTile dataset.

CLI Tool Changes

  • kraken-allocate.py now accepts --dry-run switch to determine how many km2-months would need to be allocated to the user for the given area.

SpaceKnow Backend Release 109

Released on 2018-01-23. List of changes since release 108 follows.

REST API Changes

  • ee COPERNICUS/S2 image metadata now contain cloudCover, sunEleveation, sunAzimuth, satellite, offNadir, reflectanceMult and reflectanceAdd.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened and pl PSOrthoTile gives only approximate truecolor. It performs well for some scenes, other scenes may have shifted histograms.
  • Urthecast imagery is currently unavailable.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • There are visible “frames” around Planet imagery tiles and analysis result masks. This is a display-only problem not affecting vector analysis results. This will be fixed in future by using proper image transformation.
  • Search and download of Planet imagery is unnecessarily slow. Search can take up to tens of minutes on large areas and long time spans. Fetching imagery can currently take over 15 minutes. This is being fixed, but needs

SpaceKnow Backend Release 108

Released on 2018-01-17. List of changes since release 107 follows.

Highlights

  • Kraken API now supports solar-panels algorithm.

REST API Changes

  • Ragnar API get-image response now contains property url. Property fileId will be removed in the near future.
  • Erlendur, Vidar, and Visualization APIs have been dropped. Use Kraken API instead.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened and pl PSOrthoTile gives only approximate truecolor. It performs well for some scenes, other scenes may have shifted histograms.
  • Urthecast imagery is currently unavailable.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • There are visible “frames” around Planet imagery tiles and analysis result masks. This is a display-only problem not affecting vector analysis results. This will be fixed in future by using proper image transformation.
  • Search and download of Planet imagery is unnecessarily slow. Search can take up to tens of minutes on large areas and long time spans. Fetching imagery can currently take over 15 minutes. This is being fixed, but needs architectural changes. This is expected to be fixed by Q1 2018.

SpaceKnow Backend Release 107

Released on 2018-01-10. List of changes since release 106.1 follows.

REST API Changes

  • API response headers now contain SpaceKnow-Request-Id.

Changes in Deployed Algorithms

  • Prediction quality of car & truck, ship detection and WRUNC semantic segmentation algorithms has been improved on gbdx idaho-pansharpened dataset.
  • Prediction quality of the aircraft detection algorithm had been improved on pl PSOrthoTile dataset.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened and pl PSOrthoTile gives only approximate truecolor. It performs well for some scenes, other scenes may have shifted histograms.
  • Urthecast imagery is currently unavailable.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • There are visible “frames” around Planet imagery tiles and analysis result masks. This is a display-only problem not affecting vector analysis results. This will be fixed in future by using proper image transformation.
  • Search and download of Planet imagery is unnecessarily slow. Search can take up to tens of minutes on large areas and long time spans. Fetching imagery can currently take over 15 minutes. This is being fixed, but needs architectural changes. This is expected to be fixed by Q1 2018.

SpaceKnow Backend Release 106.1

Released on 2018-01-02. List of changes since release 104.1 follows.

Deprecation Notices

  • Visualization API is deprecated and will be removed in version 109 (2018-01-22). Use Kraken API instead.

Highlights

  • All object detection algorithms (aircraft, boats, cars, ships) now provide oriented bounding boxes around detected objects on all eligible datasets. Previously, bounding boxes were aligned with parallels and meridians.

REST API Changes

  • Input GeoJSON (in API request payloads) are rounded to 7 decimal places. This may slightly affect behavior of some APIs, specifically images returned by Ragnar API may have different dimensions about up to 2 pixels, however this should be rare.
  • Polygon API has been replaced by GeoJSON API. See docs for more information.
  • Kraken API grid endpoint does no longer accept polygon ID from discontinued Polygon API, it now accepts geometry ID from GeoJSON API instead.

Changes in Deployed Algorithms

  • GeoJSON output of algorithms is now canonicalized.
  • Coordinates in object and change detection algorithm GeoJSON outputs are now rounded to 7 decimal places.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened and pl PSOrthoTile gives only approximate truecolor. It performs well for some scenes, other scenes may have shifted histograms.
  • Urthecast imagery is currently unavailable.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • There are visible “frames” around Planet imagery tiles and analysis result masks. This is a display-only problem not affecting vector analysis results. This will be fixed in future by using proper image transformation.
  • Search and download of Planet imagery is unnecessarily slow. Search can take up to tens of minutes on large areas and long time spans. Fetching imagery can currently take over 15 minutes. This is being fixed, but needs architectural changes. This is expected to be fixed by Q1 2018.

SpaceKnow Backend Release 104.1

Released on 2017-12-12. List of changes since release 102.2 follows.

Highlights

  • Cloud cover metadatum is available for dg wfs-wms.
  • Cloud cover metadatum is available for pl PSOrthoTile and REOrthoTile.

REST API Changes

  • Files API endpoint for file downloading has been changed. See Files API documentation for more information.
  • File IDs generated before release of this version are no longer available.
  • Most File IDs now expire in 24 hours after their creation.

Changes in Deployed Algorithms

  • Prediction quality of the boats detection algorithm has been improved on gbdx idaho-pansharpened dataset using specific model trained on this dataset.

CLI Tool Changes

  • ragnar-filter.py can filter scenes by cloud cover.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened and pl PSOrthoTile gives only approximate truecolor. It performs well for some scenes, other scenes may have shifted histograms.
  • Urthecast imagery is currently unavailable.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • There are visible “frames” around Planet imagery tiles and analysis result masks. This is a display-only problem not affecting vector analysis results. This will be fixed in future by using proper image transformation.
  • Search and download of Planet imagery is unnecessarily slow. Search can take up to tens of minutes on large areas and long time spans. Fetching imagery can currently take over 15 minutes. This is being fixed, but needs architectural changes. This is expected to be fixed by Q1 2018.

SpaceKnow Backend Release 102.1

Released on 2017-12-05. List of changes since release 101.1 follows.

REST API Changes

  • Ragnar API now returns cloudCover metadatum for all datasets of gbdx, see API docs for more information.

Changes in Deployed Algorithms

  • Prediction quality of the aircraft detection on``gbdx`` idaho-pansharpened data has been improved.

CLI Tool Changes

  • ragnar-filter.py in <other-records-file> has been introduced to limit available-tiles.jsons file to be a subset of other record list.
  • ragnar-search.py has got --min-intersection argument.
  • New CLI tool kraken-download.py to download any Kraken API map has been introduced, see documentation and its --help text.
  • All users in the developer group have now permission to do get-pipeline.py ....

Known Issues

  • Autovisualization of gbdx idaho-pansharpened and pl PSOrthoTile gives only approximate truecolor. It performs well for some scenes, other scenes may have shifted histograms.
  • Urthecast imagery is currently unavailable.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • There are visible “frames” around Planet imagery tiles and analysis result masks. This is a display-only problem not affecting vector analysis results. This will be fixed in future by using proper image transformation.
  • Search and download of Planet imagery is unnecessarily slow. Search can take up to tens of minutes on large areas and long time spans. Fetching imagery can currently take over 15 minutes. This is being fixed, but needs architectural changes. This is expected to be fixed by Q1 2018.

SpaceKnow Backend Release 101

Released on 2017-11-28. List of changes since release 99 follows.

Highlights

  • Separate and more precise algorithms for provider gbdx were introduced. Namely this affects detection of Aircraft, Containers, Ships and WRUNC segmentation.
  • Big polygon imagery and analysis serving (Kraken API) has been made faster and more efficient.

Deprecation Notices

  • Vidar API and Erlendur API have been deprecated. They will be removed in version 104 (2017-12-18).

Changes in Deployed Algorithms

  • Prediction quality of aircraft, ships, WRUNC and containers detection algorithms has been improved on gbdx/idaho-pansharpened by using separate re-trained models on this dataset.

Important Fixes

  • Geographic clipping of images has been fixed. It used to produce images which had one more column and row than they should have. This also fixes 1 px spaces in Kraken API analysis masks.
  • A number of operational failures has been decreased resulting in significantly smaller failed pipeline ratio.

Known Issues

  • Autovisualization of gbdx/idaho-pansharpened and pl/PSOrthoTile gives only approximate truecolor. It performes well for some scenes, other scenes may have shifted histograms.
  • Urthecast imagery is currently unavailable.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • There are visible “frames” around Planet imagery tiles and analysis result masks. This is a display-only problem not affecting vector analysis results. This will be fixed in future by using proper image transformation.
  • Search and download of Planet imagery is unnecessarily slow. Search can take up to tens of minutes on large areas and long time spans. Fetching imagery can currently take over 15 minutes. This is expected to be fixed by Q1 2018.

Spaceknow Backend Release 99

Released on 2017-11-13. List of changes since release 97 follows.

Highlights

  • Ships detection is enabled for pl PSOrthoTile.
  • Change detection is enabled for pl PSOrthoTile.
  • Kraken and Erlendur API now supports cross-provider change detection.

REST API Changes

  • Ragnar API, Erlendur API and Vidar API now supports any GeoJSON with non-empty MBR as extent.
  • Kraken and Erlendur API now supports pl PSOrthoTile on scenes with GSD up-to 4.5m.
  • Deprecated Kraken API and Vidar API WUNC endpoints /kraken/release/wunc/tiles/{initiate|release}, /vidar/segmentation/wunc/{initiate|retrieve} has been removed.

Changes in Deployed Algorithms

  • Prediction quality of WRUNC on all on data was improved.
  • Fixed detection of ships larger than 10000:math:m^2.

Other Changes

  • Requested area mask in images returned from Ragnar API was made more accurate.

Spaceknow Backend Release 97

Released on 2017-11-01. List of changes since release 95 follows.

Highlights

  • WRUNC detection is enabled for planet PSOrthoTile on APIs.
  • Aircraft detection is enabled for planet PSOrthoTile on APIs.

REST API Changes

  • Maps API was removed.

Changes in Deployed Algorithms

  • New WRUNC detection service was created for planet PSOrthoTile.
  • New Aircraft detection service was created for planet PSOrthoTile.

Important Fixes

  • Some algorithm pipelines were failing during automatic scaling down of computational resources. This has been fixed.
  • Ragnar, Vidar and Erlendur APIs now return proper error NO-VALID-PIXELS when a client requests extent which has no intersection with valid data.

CLI Tool Changes

  • ragnar-filter.py now supports commands weekly and daily.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened gives only approximate truecolor. For some scenes it performes well, other scenes may have shifted histograms.
  • Urthecast imagery is temporarily unavailable due to API changes on provider side.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.

Spaceknow Backend Release 95

Released on 2017-10-18. List of changes since release 92.2 follows.

Highlights

Deprecation Notices

  • Current Credits API is available under a new URL. Instead https://spaceknow-billing.appspot.com/ use https://spaceknow-credits.appspot.com/. API version running under the old URL won’t be updated anymore and the URL will be invalidated by October 19th, 2017.

REST API Changes

  • Ragnar API search now accepts arbitrary GeoJSON in extent parameter.

Other Changes

  • Regular users are not allowed to use WRUNC anymore.

CLI Tool Changes

  • ragnar-search.py now allows passing --tile-size 0 to disable tiling. This is useful especially for kraken-download.py.
  • ragnar-search.py now accepts any GeoJSON and extracts all area-based geometries from it.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened gives only approximate truecolor. For some scenes it performes well, other scenes may have shifted histograms.
  • Urthecast imagery is temporarily unavailable due to API changes on provider side.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.

Spaceknow Backend Release 92.2

Released on 2017-09-27. List of changes since release 92.1 follows.

Important Fixes

  • Occasional failures of the change detection analyses were fixed.

Spaceknow Backend Release 92.1

Released on 2017-09-26. List of changes since release 89 follows.

Highlights

  • New Kraken API endpoints for change detection have been introduced. From now all algorithms are supported by Kraken API.
  • Kraken API is now production ready.

REST API Changes

  • Kraken API is now production ready.
  • New Kraken API endpoints for change detection have been introduced. From now all algorithms are supported by Kraken API.
  • Ragnar API response metadata approximateResolutionX and approximateResolutionY are now available even in search for some scenes.

Important Fixes

  • gbdx idaho-pansharpened has been allowed for change detection in Vidar and Kraken APIs.
  • Kraken API used to double detect objects at the edges of some tiles. This has been fixed.

Other Changes

  • Visualization of GBDX Preview has been fixed.
  • Road color in WRUNC visualization was changed from brown to violet.
  • Image scaling in Ragnar API now matches requested resolution more precisely. As a result, width and height of scaled images may change slightly.
  • Approximate resolution of imagery downloaded from Ragnar API is now calculated with a different and more accurate algorithm.

CLI Tool Changes

  • ragnar-filter.py and ragnar-search.py date filter has been updated to be inclusive in both sides.
  • ragnar-download.py now prints summary information when it finishes.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened gives only approximate truecolor. For some scenes it performes well, other scenes may have shifted histograms.
  • Urthecast imagery is temporarily unavailable due to API changes on provider side.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.

Spaceknow Backend Release 89

Released on 2017-09-04. List of changes since release 87.3 follows.

Highlights

  • New Vidar API and Kraken API endpoints for segmentation of boats have been introduced.
  • WUNC algorithm was replaced by WRUNC (water, roads, urban, non-urban, clouds) algorithm.

Deprecation Notices

  • Kraken API and Vidar API WUNC endpoints /kraken/release/wunc/tiles/{initiate|release}, /vidar/segmentation/wunc/{initiate|retrieve} were deprecated. They will be removed with version 93 (2017-10-03).

REST API Changes

  • New Vidar API and Kraken API endpoints for boats segmentation have been introduced.

Changes in Deployed Algorithms

  • Prediction quality of the ships algorithm has been improved. Images with few invalid pixels can be processed.
  • WUNC algorithm has been updated to WRUNC (added detection of roads and railways). The algorithm is newly allowed on dg idaho-pansharpened imagery.
  • Change detection is newly allowed on dg idaho-pansharpened imagery.

Other Changes

  • Planet scenes with multi-polygon footprint are no longer filtered-out.
  • Planet imagery has got offNadir.

CLI Tool Changes

  • ragnar-download.py imagery pipeline timeout has been increased from 30 do 60 minutes to accommodate for delays caused by “activating” assets in Planet API.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened gives only approximate truecolor. For some scenes it performes well, other scenes may have shifted histograms.
  • Urthecast imagery is temporarily unavailable due to API changes on provider side.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • gbdx preview images cannot be downloaded.

Spaceknow Backend Release 87.1

Released on 2017-08-23. List of changes since release 84.1 follows.

Highlights

  • Planet imagery is now 16bit instead 8bit and near-infrared band has been added.
  • New Vidar API endpoints for container segmentation have been introduced.
  • Kraken API now fully supports Cars & Trucks, WUNC, Ships, Aircraft and Containers algorithms. This means large areas can now be analysed.
  • Kraken API maximum area limit has been increased from 64 MPix to 900 MPix. E.g., for high resolution imagery this corresponds to increase from \(5 km^2\) to \(81 km^2\).

Deprecation Notices

  • Kraken /grid endpoint path changed to /kraken/grid/<map_id>/<polygon_id>/<z>/<x>/<y>/<file_name>. Previous path /kraken/grid/<map_id>/<polygon_id>/<z>/<x>/<y>.<suffix> is supported for now but will be removed by 30.9.2017.
  • Instead of /kraken/release/scene/{initiate|retrieve} use /kraken/release/imagery/tiles/{initiate|retrieve}. The old endpoint will be removed by 30.9.2017.

REST API Changes

  • New Vidar API endpoints for container segmentation have been introduced.
  • Kraken API maximum area limit has been increased from 64 MPix to 900 MPix. E.g., for high resolution imagery this corresponds to increase from \(5 km^2\) to \(81 km^2\).

Changes in Deployed Algorithms

  • Cars & Trucks, Ships and Aircraft algorithms produce less false positive small area segments in detection GeoJSON.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened gives only approximate truecolor. For some scenes it performes well, other scenes may have shifted histograms.
  • Urthecast imagery is temporarily unavailable due to API changes on provider side.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.

CLI Tool Changes

  • ski-show.py and ski-save.py now support --bands argument to visualize and store arbitrary bands to red, green, blue channels. Examples to visualize various algorithm results: ski-show.py --bands heatmap change.ski ski-show.py --bands water,urban,nonurban --top 0.005 wunc.ski

Spaceknow Backend Release 84

Released on 2017-08-03. List of changes since release 80.1 follows.

Highlights

  • Usage of APIs is now billed based on \(km^2 \cdot month\) usage. This affects Ragnar API, Vidar API, Erlendur API and Kraken API. See documentation of Credits API for more information.

REST API Changes

  • Usage of APIs is now billed based on \(km^2 \cdot month\) usage. This affects Ragnar API, Vidar API, Erlendur API and Kraken API. See documentation of Credits API for more information.
  • Payment API was dropped.

CLI Tool Changes

  • ragnar-allocate.py script was added. It serves for area allocation in Credits API. See documentation for more information.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened gives only approximate truecolor. For some scenes it performes well, other scenes may have shifted histograms.
  • Urthecast imagery is temporarily unavailable due to API changes on provider side.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.

Spaceknow Backend Release 80

Released on 2017-07-08. List of changes since release 77.1 follows.

Highlights

  • Cars & trucks, Ships and Aircraft API endpoints now provide vector GeoJSON output with detected objects.

REST API Changes

  • Responses of the following Vidar API endpoints have got new property detectionsGeoJsonFileId which is File ID of a detections GeoJSON:
    • /vidar/segmentation/cars/retrieve
    • /vidar/segmentation/ships/retrieve
    • /vidar/segmentation/aircraft/retrieve

Changes in Deployed Algorithms

  • Ships algorithm model has been reverted to previous version that yields fewer false positives.

Important Fixes

  • Ragnar API search for scenes from provider dg and dataset wfs-wms took very long time when many hundreds of scenes were found. This has been fixed.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened gives only approximate truecolor. For some scenes it performes well, other scenes may have shifted histograms.
  • Urthecast imagery is temporarily unavailable due to API changes on provider side.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.

Spaceknow Backend Release 77.1

Released on 2017-06-15. List of changes since release 74.2 follows.

Highlights

  • Visualization API has new true-color endpoint /visualization/true-color that automatically visualizes true-color image.
  • gbdx idaho-pansharpened dataset is now available through Kraken API with autovisualization.
  • We have switched to GBDX Catalog API v2 from v1.
  • We have observed that number of available GBDX scenes more than doubled after migrating to Catalog API v2.

Deprecation Notices

  • The Visualization API endpoint /visualization/ski should not be used anymore. It will be removed by 2017-07-31. Instead, there is a new endpoint /visualization/true-color.

REST API Changes

  • For gbdx preview, Ragnar API now returns datetime including seconds in scene metadata.
  • For provider gbdx, WV03 satelite name has been replaced by either WV03_VNIR or WV03_SWIR in Ragnar API.
  • Imagery from gdbx provider idaho-pansharpened dataset has been enabled in Vidar API for aircraft, building, car and ship segmentation algorithms.
  • Vidar and Erlendur APIs now disallow ab spot imagery in their /initiate endpoints. Previously this was allowed but the pipelines always failed.

Changes in Deployed Algorithms

  • Prediction quality of ships has been improved.

Important Fixes

  • User search has been fixed.

Known Issues

  • Autovisualization of gbdx idaho-pansharpened gives only approximate truecolor. For some scenes it performes well, other scenes may have shifted histograms.
  • Urthecast imagery is temporarily unavailable due to API changes on provider side.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • Searching dg wfs-wms dataset takes too long in locations with multiple hundreds of scenes.

CLI Tool Changes

  • Support for stored credentials was added to CLI scripts. See documentation for more information.

Spaceknow Backend Release 74.2

Released on 2017-06-06. List of changes since release 74.1 follows.

Important Fixes

  • Files API /download endpoint now returns meaningful replies like HTTP 400 or 403 instead of bogus HTTP 500 errors.
  • A bug in Vidar API causing HTTP 500 errors has been fixed.

Known Issues

  • Urthecast imagery is temporarily unavailable due to API changes on provider side.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • gbdx idaho-pansharpened dataset misses proper visualization. Only raw 16bit images are available so far.
  • Searching dg wfs-wms dataset takes too long in locations with multiple hundreds of scenes.

Spaceknow Backend Release 74.1

Released on 2017-05-29. List of changes since release 73 follows.

Highlights

  • Search and imagery for dataset idaho-pansharpened of gbdx is now available through Ragnar API.

Changes in Deployed Algorithms

  • Prediction quality of Cars & Trucks segmentation / detection has been improved, especially for images around 30cm GSD.

Important Fixes

  • A bug that could cause some dg wfs-wms scenes being concealed in search has been fixed. As a result, more scenes can now appear in some locations.

Other Changes

  • Satellite names in all gbdx datasets have been renamed to match names already used in dg wfs-wms. Specifically:
    • GEOEYE01 -> GE01
    • QUICKBIRD02 -> QB02
    • WORLDVIEW01 -> WV01
    • WORLDVIEW02 -> WV02
    • WORLDVIEW03 -> WV03

Known Issues

  • Urthecast imagery is temporarily unavailable due to API changes on provider side.
  • Landsat scenes acquired after 1st May 2017 are temporarily unavailable.
  • Download of Sentinel imagery is currently unreliable due to rate limiting on provider side.
  • gbdx idaho-pansharpened dataset misses proper visualization. Only raw 16bit images are available so far.
  • Searching dg wfs-wms dataset takes too long in locations with multiple hundreds of scenes.

Spaceknow Backend Release 73

Released on 2017-05-15. List of changes since release 72 follows.

Important Fixes

  • Wrong radiance values in Landsat metadata has been fixed.
  • Ragnar API search didn’t work on locations with too many imagery found. This has been fixed.

Known Issues

  • Urthecast imagery is temporarily unavailable due to API changes on provider side.

Spaceknow Backend Release 72

Released on 2017-05-11. List of changes since release 70.1 follows.

Highlights

  • New Vidar API endpoints for building segmentation have been introduced.

REST API Changes

  • New Vidar API endpoints for building segmentation have been introduced.
  • Obsolete Vidar API endpoints /vidar/cars/* have been removed.

Changes in Deployed Algorithms

  • Prediction quality of aircraft and cars have been improved.

Other Changes

  • Requested area mask in SKIs returned from Ragnar API is generated by a different algorithm. This may result in a slightly different mask for equal requests.

Known Issues

  • Landsat 7 metadata may contain wrong radiance values.
  • Urthecast imagery is temporarily unavailable due to API changes on provider side.

Spaceknow Backend Release 70.1

Released on 2017-04-26. This release doesn’t introduce any important user-facing changes.

Spaceknow Backend Release 70

Released on 2017-04-25. List of changes since release 69 follows.

Known Issues

  • Landsat 7 metadata may contain wrong radiance values.
  • Urthecast imagery is temporarily unavailable due to API changes on provider side.

Spaceknow Backend Release 69

Released on 2017-04-24. List of changes since release 68 follows.

Highlights

  • API endpoints for WUNC, General Change Detection, Ships and Aircraft detection now accept Airbus imagery.
  • Airbus imagery is now available worldwide.

REST API Changes

  • Ragnar API response to /get-image now returns approximate resolution for each band in bands metadata.

Changes in Deployed Algorithms

  • Change detection output GeoJSON orientation has been fixed.
  • Performance of WUNC have been improved.
  • WUNC, ships, change detection, aircraft algorithms now work on Airbus Pleiades imagery.

Important Fixes

  • A bug in Ragnar API which made it impossible to download Landsat and Planet close to scene margins has been fixed.
  • ragnar-search.py failed on certain input GeoJSONs because of a bug in polygon decomposition algorithm. This has been fixed.
  • Visualization of two ee datasets LANDSAT/LE7_L1T and COPERNICUS/S2 in Kraken API has been fixed.

Other Changes

  • All users now can use aircraft segmentation.

Known Issues

  • Landsat 7 metadata may contain wrong radiance values.
  • Urthecast imagery is temporarily unavailable due to API changes on provider side.

CLI Tool Changes

  • ragnar-search.py pipeline timeout has been increased from 15 to 20 minutes so that it can cope with one expired task in the pipeline.

Spaceknow Backend Release 68

Released on 2017-04-11. List of changes since release 67 follows.

Highlights

  • New Vidar API endpoints for aircraft segmentation have been introduced.

REST API Changes

  • Ragnar API response to get-image now returns CRS origin for each band in its metadata, see Ragnar API documentation.
  • New Vidar API endpoints for aircraft segmentation have been introduced, see Vidar API documentation.

Changes in Deployed Algorithms

  • Performance of aircraft detection has been improved (fewer false positives).
  • Performance of change detection and car detection has been improved.

Important Fixes

  • Support for arbitrarily small extents was added to algorithm pipelines.
  • Change detection algorithm pipeline failures due to invalid attention regions GeoJSON output have been fixed.

Other Changes

  • Regular users can now run ships segmentation, thus having access to the same set of analyses as power users.

Spaceknow Backend Release 67

Released on 2017-03-31. List of changes since release 63 follows.

Highlights

  • Ship segmentation is now available through API. See below.
  • New change detection algorithm with cloud filtering is now available through API endpoints. See below.

Deprecation Notices

  • Erlendur API endpoints /change-detection-pair/initiate and /change-detection-pair/retrieve were deprecated. They will be removed in version 70 (week starting on 2017-04-24).

REST API Changes

  • Ragnar API endpoint /kraken/release/scene/retrieve returns also maxZoom.
  • Ship detection (segmentation) was introduced through new Vidar API endpoint /vidar/segmentations/ships.
  • Erlendur API has got new endpoints for an improved version of change detection. See its documentation for more information. One notable difference is that the new algorithm currently works only on DG imagery.

Changes in Deployed Algorithms

  • The performance of the ships algorithm improved thanks to the BEP threshold fix.
  • Deployed algorithms should run faster thanks to internal improvements (caching of the loaded model).

Important Fixes

  • The issue with Ragnar imagery pipelines failing for region-based providers (like DG) has been fixed. This issue has affected areas in South Pacific Ocean, those with longitude -180° to -100° and latitude -10° to -90°. Note that a similar issue, but for tiling providers, needs to be fixed independently.

Other Changes

  • Regular users now can use WUNC segmentation and cars / trucks segmentation, in addition to already available change detection. Ship segmentation is currently available to power users.
  • Timeout was added to many HTTP requests, including requests to Airbus, Planet and Urthecast APIs. This shall improve robustness in case of unreliable provider systems.

Known Issues

  • Segmentation algorithms and change detection cannot currently run on too tiny polygons.
  • Urthecast imagery is temporarily unavailable due to API changes on provider side.

Spaceknow Backend Release 63

Released on 2017-03-06. List of changes since release 62.2 follows.

Highlights

  • Planet search and imagery is available through Ragnar API. Currently, only images from California can be downloaded. It should serve as a demo so far.

REST API Changes

  • Vidar API endpoint /vidar/segmentation/wunc count.totalPixels response attribute has been renamed to count.requestedValidPixels.
  • Vidar API endpoint /vidar/segmentation/wunc now additionally returns count.*SquareMeters attribute for each count.*Pixels attribute.

Changes in Deployed Algorithms

  • WUNC, cars, ships, change detection algorithms now perform analysis only on requested mask.
  • WUNC and ships algorithms now also return square meters in addition to pixels.

Known Issues

  • Airbus imagery is temporarily not available through Ragnar API.

Spaceknow Backend Release 62.2

Released on 2017-03-01. List of changes since release 62.1 follows.

CLI Tool Changes

  • API clients did not wait between request retries (on 5xx API failures). This has been fixed by adding exponential back-off set to 2, 4 and 8 seconds. Number of retries was kept intact. This should help ragnar-*.py, watchdog and all other SpaceKnow clients.

Spaceknow Backend Release 62.1

Released on 2017-02-28. List of changes since release 62 follows.

REST API Changes

  • Access token to access Kraken API grid tiles is no longer required, it was superseded by signed map ID. Endpoint /kraken/get-access-token was removed because it is no longer needed.

Spaceknow Backend Release 62

Released on 2017-02-27. List of changes since release 59.1 follows.

Highlights

  • Water, Urban, Non-Urban and Clouds segmentation and Cars & Trucks segmentation algorithms and APIs were introduced (see below).

Deprecation Notices

  • Old car detection endpoints of Vidar API became deprecated. They will be removed in version 64 (week 2017-03-13).

REST API Changes

  • Water, Urban, Non-Urban and Cloud segmentation was added to Vidar API.
  • Cars & Tracks segmentation algorithm API was introduced. See Vidar API documentation for more information.

Important Fixes

  • Ragnar Get image pipelines should no longer fail on freshly searched scenes due to the fact that the relevant scene has been removed from provider’s system. This is because SpaceKnow backend platform now removes (thus no longer returns in search) scenes not available from providers anymore. This has affected the dg provider.

Known Issues

  • Cars & Trucks segmentation, WUNC segmentation is currently performed on the whole passed image, ignoring requested mask.
  • All newly deployed algorithms currently enforce some minimum size of passed image and fail for smaller ones. This will be fixed in the future by enlarge-process-cut approach.

Spaceknow Backend Release 59-1

Released on 2017-02-11. List of changes since release 59 follows.

REST API Changes

  • Airbus scene metadata now include off-nadir angle in Ragnar API responses.

Important Fixes

  • Failing Ragnar Airbus search pipelines have been fixed by filtering-out scenes with empty ortho-rectified footprint. We’ll look further into this.

Known Issues

  • Search for dg wfs-wms scenes can currently offer scenes that were in fact already removed from wfs-wms catalogue. Trying to download their imagery then fails.

Spaceknow Backend Release 59

Released on 2017-02-09. List of changes since release 56 follows.

Highlights

  • Reflectance and radiance parameters were added to Landsat 7 and Landsat 8 imagery from provider ee.
  • Images from Google Earth Engine (provider ee) COPERNICUS/S2 dataset (Sentinel-2A satellite) are available through Ragnar API.

REST API Changes

  • Visualization API got new async endpoints /visualization/segmentation-masks/.... It visualizes segmentation masks. See Visualization API documentation for more information.
  • Ragnar API has got support for radiance & reflectance parameters in band metadata. See Ragnar API documentation for more information.
  • Band bit depths of ee scenes shall be known after search. Before this change it was sometimes known only after imagery was downloaded.
  • Min intersection ratio in Ragnar API is now calculated on area-based geometries from requested extent instead of its bounding box. Also support for 0 (arbitrarily small) intersection ratio was added.
  • Kraken release API endpoint now returns:
    • NON-EXISTING-SCENE if requested scene does not exist (this is checked even if tiles already exist)
    • TILE-OUTSIDE-SCENE is requested tile has no intersection with given scene.
  • Regular users can now use Kraken’s release endpoint.

Important Fixes

  • Kraken API now correctly handles tiles on borders of scenes.
  • Kraken API now correctly draws valid data mask into alpha channel of served PNG tiles. Before this fix, valid data mask was ignored.
  • Endpoint /kraken/release/scene/initiate from Kraken API wrongly calculated maximum area for release. This has been fixed. The effect of the fix is that the limits are currently different that they used to be.
  • Scenes from IKONOS satellite (gbdx idaho) were removed from Ragnar Search. This is because the imagery couldn’t be downloaded.

Known Issues

  • Airbus imagery does not currently contain off nadir angle in its metadata.
  • Search for dg wfs-wms scenes can currently offer scenes that were in fact already removed from wfs-wms catalogue. Trying to download their imagery then fails.

Spaceknow Backend Release 56

Released on 2017-01-17. List of changes since release 54.1 follows.

Highlights

  • New CLI tool ragnar-order.py was added. The script reads available-tiles.jsons (which must contain only records of provider gbdx and dataset preview) and orders all encountered scenes into GBDX IDAHO catalogue.
  • Dataset hybrid of provider gbdx was removed from Ragnar API. The functionality was superseded by the recently introduced Ragnar API order endpoint.

REST API Changes

  • Map ID returned from Kraken API /kraken/release/scene/retrieve endpoint was changed to a JWT with encoded plain map ID, x, y and zoom. The token and requested coordinates are validated in /kraken/grid/* endpoint.

Important Fixes

  • dg wfs-wms and gbdx idaho imagery as returned from Ragnar API should become pixel precise and have even and deterministic degrees-per-pixel size throughout a given scene; neither was the case previously. Some images may shift and change dimensions by a couple of pixels compared to previous responses.
  • Degrees-per-pixel size computation has been changed for gbdx idaho scenes. Scene reference pixel size is computed in a way that pixels are approximately square-in-meters in some point of a scene; previously idaho had approximately square-in-degrees pixels. A positive side-effect is that 500x500 meter polygons are now downloadable even in northern and southern areas.
  • Expected resolution ranges have been revised for all providers and datasets. It influences Ragnar API extent size checker and zoom levels in Kraken API.

Other Changes

  • Ragnar response image metadata object has been documented along with individual attribute availability.
  • Watchdog now automatically orders imagery for provider gbdx dataset preview. The high resolution imagery is then available via gbdx idaho, so both these datasets should be enabled for watchdogs working on top of GBDX.

Known Issues

  • Ragnar search for gbdx preview can return some scenes from IKONOS satellite. These scenes however can be neither ordered to idaho nor downloaded as images, which renders them useless currently. In future these results will be either filtered-out or ordering/download made possible.

Spaceknow Backend Release 54-1

Released on 2017-01-06. List of changes since release 54 follows.

Important Fixes

  • Fixed coarsest expected resolution for DG WFS-WMS from 0.3 to 0.6.

Spaceknow Backend Release 54

Released on 2017-01-05. List of changes since release 52 follows.

Highlights

  • All imagery providers were added to Kraken API.
  • Polygon clipping was added to Kraken API.

REST API Changes

  • There is a new ragnar API endpoint that supports scene ordering for GBDX preview sceneId.

Important Fixes

  • Fixed search in GBDX Preview SWIR imagery.
  • Dimension checking in Ragnar has been consolidated. The API now checks whether resulting image would pass by consulting a table of expected resolution ranges for each provider dataset. This should fix Ragnar API refusing to serve imagery that would turn out valid.
  • Dimension checking in UrtheCast imagery has been consolidated, which should avoid Region dimensions are too large pipeline errors.
  • Ragnar API endpoint get-image now preserves 16 bit image depth even with scaling. There was a bug that for non-zero resolution parameter 8bit image was returned instead. This change influences only 16bit image providers like gbdx with dataset idaho.

Known Issues

  • Kraken /kraken/release/scene/retrieve endpoint currently fails every time. The pipeline finishes correctly (tiles are prepared), the problem only happens when creating result in the API.

Spaceknow Backend Release 52

Released on 2016-12-21. List of changes since release 51 follows.

REST API Changes

  • Ragnar API search page size was changed from constant to dynamic. This fixes bug where some searches failed and makes paging faster because pages are larger on average.
  • Non-determinism of data returned from Ragnar API for provider dg dataset wfs-wms was removed.

Important Fixes

  • Some gbdx idaho images were shifted, this was fixed.
  • Ragnar API search page size was changed from constant to dynamic. This fixes bug where some searches failed and makes paging faster because pages are larger in average.

Spaceknow Backend Release 51

Released on 2016-12-15. List of changes since release 50 follows.

Highlights

  • Airbus spot and pleiades imagery were made available through Ragnar API.
  • Ragnar API scenes search performance was improved.

Important Fixes

  • The red and blue bands were swapped in 4-bands GBDX IDAHO scenes, this was fixed.
  • Times for scenes from provider gbdx dataset idaho were always 00:00:00. This was fixed.

Spaceknow Backend Release 50

Released on 2016-12-07. List of changes since release 49 follows.

Highlights

  • The way Ragnar computes returned image offset and size has changed, unscaled images may be 1 px shifted and 1 px smaller/larger on each side now. Dimensions of scaled images will not change. The new algorithm is correct in a way that tiling should be pixel-perfect now.

REST API Changes

  • Credit subtraction was removed from Vidar API endpoint /vidar/cars/file-id/initiate. This change does not affect /vidar/cars/scene-id/initiate.
  • List of detections was removed from response of Vidar API endpoints /vidar/cars/file-id/retrieve and /vidar/cars/scene-id/retrieve. The response now contains number of detections and file ID of a GeoJSON with precise location of each detection.
  • Deprecated Vidar API endpoints /vidar/cars/initiate and /vidar/cars/retrieve were removed.

Important Fixes

  • Fixed search for GBDX scenes containing IKONOS images. Datasets preview and hybrid are affected.
  • The way Ragnar computes returned image offset and size has changed, unscaled images may be 1 px shifted and 1 px smaller/larger on each side now. Dimensions of scaled images will not change. The new algorithm is correct in a way that tiling should be pixel-perfect now.
  • Rounding mismatch in Ragnar that prevented some scene extents from being served by /get-image has been fixed.

Spaceknow Backend Release 49

Released on 2016-11-28. List of changes since release 48 follows.

Highlights

  • Airbus’s spot and pleiades are searchable through Ragnar API. Imagery cannot be downloaded yet.

Spaceknow Backend Release 48

Released on 2016-11-21. List of changes since release 47 follows.

Highlights

  • Kraken API release endpoints were introduced. This introduces possibility to display large areas on web map.

REST API Changes

  • Erlendur change detection API no longer clips 1 pixel of each side of the heatmap relative to the old image. The heatmap is the same size as the old image now.

Spaceknow Backend Release 47

Released on 2016-11-14. List of changes since release 45 follows.

Highlights

  • SKI images as returned from Ragnar API have got extent property.
  • Urthecast’s deimos-2 is available through Ragnar API.

Deprecation Notices

  • Endpoints /vidar/cars/initiate and /vidar/cars/retrieve of Vidar API were deprecated.

    Replacement endpoints /vidar/cars/scene-id/initiate and /vidar/cars/scene-id/retrieve were introduced.

REST API Changes

  • Endpoints /vidar/cars/file-id/initiate and /vidar/cars/file-id/retrieve were added to Vidar API. This endpoints detect cars in an SKI accessible on Files API.
  • Vidar API endpoints /vidar/cars/scene-id/initiate and /vidar/cars/scene-id/retrieve were introduced.
  • extent was added to response of Ragnar API endpoint /imagery/get-image/retrieve.

Important Fixes

  • Ragnar API used to return wrong pixel size for scaled images. Images requested in original resolution were unaffected. This bug was fixed.

Spaceknow Backend Release 45

Released on 2016-11-02. List of changes since release 43 follows.

Highlights

  • Deimos-2 was connected to Spaceknow platform.
  • Dataset hybrid for provider gbdx was added.

REST API Changes

  • Maps API /osm/mask/json used to respond with invalid GeoJSON for Polygon geometries. This has been fixed.

Spaceknow Backend Release 43

Released on 2016-10-18. List of changes since release 42 follows.

Highlights

  • Scenes footprint is now approximated to ~1m accuracy, which fixes DG WFS-WMS ragnar search for some scenes. Previously it was returned as retrieved from provider and the representation could have been too large.

REST API Changes

  • Handler /imagery/search/initiate in Ragnar API has got better validation of request provider and dataset. Misspells get caught and an alternative is suggested. #restapi
  • dataset argument to Ragnar API /size-info endpoint was made mandatory. #restapi
  • Names of properties in response of Ragnar API /size-info has been changed to camel case. #restapi
    • max_dim -> maxDim
    • max_area -> maxArea
    • max_ratio -> maxRatio

Spaceknow Backend Release 42

Released on 2016-10-07. List of changes since release 39 follows.

Highlights

  • An intial versions of Kraken API endpoints /kraken/get-access-token and /kraken/grid were implemented.

REST API Changes

  • lineWidth argument is now mandatory for Maps API /osm/mask/image endpoint.

  • New permission payment.get-plan was introduced and added to group user.

  • Payment API /plans/list response has got new property results[i].billingItems which is a list of IDs of related Billing API plans.

  • Billing API: /plans/list-plan-item was removed. Successor with similar functionality /plans/get-plan was introduced:

    {
        "planId": "enterprise",
        "life": 2592000,
        "name": "Enterprise",
        "planItems": [{
            "id": 0,
            "bucket": "high-resolution",
            "credit": 825
        }]
    }
    

Spaceknow Backend Release 39

Released on 2016-09-21. List of changes since release 33 follows.

Highlights

  • Scene metadata now contains ‘footprint’ which is a GeoJSON MultiPolygon. Ragnar API, batchloader and other systems are affected.
  • Fundamental change in scene definition
    • scene ID (now it is encrypted provider + dataset info)
    • UrtheCast not ported yet (i.e. not working at this moment)
    • contains GBDX Preview + Idaho + preliminary scenes ordering

REST API Changes

  • Visualization API /visualization/ski/initiate has got transparent argument which tells the API whether to draw valid data and requested date masks to alpha channel.
  • Dropped support for band indexing in Visualization API (only band names are now supported).
  • Ragnar API now returns pixel size for EE imagery.
  • Ragnar API may return scene bands metadata info without GSD if provider response does not contain necessary data.
  • crsEpsg property was introduced to scene metatada object which is returned by Ragnar API.