Skip to content

Latest commit

 

History

History

stac-example

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 

SATC OGC Services example project

This project allows to use STAC API server as an input catalog for available rasters. GeoTrellis server translates input OGC queries into STAC queries and reads requested items assets respectively.

GeoTrellis server can also take advantage of the the STAC Layer extension, but does not require it.

Project description

List of commands available to run from this folder:

  • make run - starts the postgres database for Franklin, applies all Franklin migrations, inserts the ./catalog, starts the Franklin server and start the geotrellis-server that is configured to work with this layer.
  • make run-geotrellis-server - runs the GeoTrellis OGC server

For more details about available commands you can look into the Makefile.

Compatible STAC Catalogs

In the ./catalog folder you can find a GeoTrellis server compatible static STAC catalog with the STAC Layer extension, that can be imported into Franklin.

The new STAC configuration description

stac-lc8-red-us = {
  type = "stacsourceconf"
  name = "stac-lc8-red-us" // OGC Layer name
  with-gdal = true // to use gdal to access stac assets
  with-vsiaz = false // force https => wasbs URIs covnersions (works with GDAL = true only) 
  title = "Landsat LayerUS Red"
  // GT Server can use the STAC Collection as a source or the STAC Layer
  layer = "layer-us" // STAC Layer
  collection = "landsat-8-l1" // STAC Collection
  asset = "^B4$" // STAC Asset to read, it is a regex selector, selects the first matching STAC Asset
  asset-limit = 1000 // Max assets returned by STAC search endpoint requests
  page-limit = 30 // is not set by default, the size of a page returned by the each search request
  source = "http://localhost:9090/" // Path to the STAC API endpoint
  default-style = "red-to-blue"
  // force time positions fetch from items even if the range is given through the collection / layer summary
  fetch-time-positions = true
  // optional field (can be added to all layers definitions)
  // the default value is "default", meaning that it would use the OGC Time in a format recieved from the source
  time-format = "{interval | positions | default}"
  ignore-time = false // work with temporal layers as with spatial layers, false by default
  // specify the default temporal rollback, oldest by default
  time-default = "{newest | oldest | ISO compatible date time}"
  // an experimental feature to use parallel mosaic
  // parallelism is controled via the geotrellis.blocking-thread-pool.threads option
  // which is set to the amount of available CPUs by default
  parallel-mosaic = {false | true}
  styles = [
    {
      name = "red-to-blue"
      title = "Red To Blue"
      type = "colorrampconf"
      colors = ${color-ramps.red-to-blue}
      stops = 64
      }
  ]
}

Such layer can be used within the MAML expression.