Raster Instance

API endpoint for rasterlayer objects.

Rasterlayers visualise raster data. The actual data is contained in rastersources. To connect a rasterlayer to a rastersource, configure the rasterlayer's source field as follows:

{
    "graph": {
        "rastersource": [
            "lizard_nxt.blocks.LizardRasterSource",
            "<uuid of a rastersource object>"
        ]
    },
    "name": "rastersource"
}

Note that the organisations of the rastersource and rasterlayer should be equal. The raster_sources field cannot be used to configure the source: it is merely a (read-only) hyperlink to the /rastersources endpoint.

GeoBlocks

Instead of directly visualising a raster source, raster layers can also perform on-the-fly operations on multiple raster sources. This can be done by extending the above example for the source field. See https://docs.lizard.net. Note that the rasterlayers's organisation must have geoblocks-permissions to be able to use this feature.

Deletion

If a rasterlayer is deleted, its raster sources (see /rastersources endpoint) will remain available. These need to be cleaned up seperately, or else they will keep using space.

If a rastersource was deleted while there was a rasterlayer referencing it, the rasterlayer will become broken. In this case, the deleted rastersources will be listed in the source.deleted_sources field.

Query parameters:

name Text filter on the name field. All text field filter methods, like startswith, endswith, icontains are supported.

uuid Filter on uuid field. UUIDs must be separated by commas and must be specified in their canonical textual representation (in their 8-4-4-4-12 form, that is). Filtering is case insensitive and may be done across relationships.

organisation Filter on Organisations.

observation_type Filter on ObservationType.

layer_collections Filter on LayerCollection.

first_value_timestamp Temporal filter on first_value_timestamp.

last_value_timestamp Temporal filter on last_value_timestamp.

raster_sources__uuid Show rasters that make use of a raster_source with given uuid.

access_modifier Filter on access_modifier, options are 'Public', 'Private', 'Common', or 'Hidden'.

ordering Show the results in a specific order. You can order them by name, last_modified, supplier, temporal, access_modifier, first_value_timestamp, last_value_timestamp, observation_type, observation_type__code, observation_type__parameter, observation_type__unit, and organisation__name. Add a - in front to reverse the order.

created: Temporal filter on created. Supports various lookup types (exact, lt, lte, gt, gte; created__exact by default). Filter values should be specified in ISO 8601 YYYY-MM-DDThh:mm:ssZ format.

last_modified: Temporal filter on last_modified. Supports various lookup types (exact, lt, lte, gt, gte; last_modified__exact by default). Filter values should be specified in ISO 8601 YYYY-MM-DDThh:mm:ssZ format.

Examples

?name__icontains=Elevation

?organisation__name=DDSC

?organisation__uuid=61f5a464c35044c19bc7d4b42d7f58cb

?organisation__name__startswith=Nelen

?organisation__name__icontains=Schuur

?observation_type__code=HOOGTEmNAP

?observation_type__parameter=Hoogte

?uuid=10415ccb-ec31-4d43-bdb3-db597061527b,
4a544b7a-772b-45fb-9aa4-a69447f34f52

?first_value_timestamp=2016-06-21T06:05:00Z

?first_value_timestamp__lt=2016-06-21T06:05:00Z

?layer_collections__slug=10855cc

?raster_sources__uuid=10415ccb-ec31-4d43-bdb3-db597061527b

?access_modifier=Private

?access_modifier=100

?ordering=name

?ordering=-last_modified

?created__gte=2017-01-01T00:00:00Z

?last_modified__lt=2018-01-01T00:00:00Z