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
GET /api/v4/rasters/d58b2c74-313a-4f92-b5d7-edd29d755b33/?format=api
https://demo.lizard.net/api/v4/rasters/d58b2c74-313a-4f92-b5d7-edd29d755b33/?format=api", "uuid": "d58b2c74-313a-4f92-b5d7-edd29d755b33", "last_modified": "2021-01-18T07:52:43.288318Z", "created": "2021-01-12T09:50:13.021323Z", "organisation": { "url": "https://demo.lizard.net/api/v4/organisations/064ae6fb-4691-4fe7-ad42-6125da4771be/?format=api", "uuid": "064ae6fb-4691-4fe7-ad42-6125da4771be", "name": "Zundert" }, "access_modifier": "Public", "supplier": "chris.kerklaan", "shared_with": [], "writable": false, "is_geoblock": true, "source": { "name": "endpoint", "graph": { "area": [ "dask_geomodeling.raster.misc.Reclassify", "gemeente", [ [ 160, 1 ], [ 50000, 0 ] ], true ], "store_1": [ "dask_geomodeling.raster.temporal.Snap", "store_2", "area" ], "store_2": [ "dask_geomodeling.raster.combine.Group", "RasterStoreSource_4", "RasterStoreSource_2", "RasterStoreSource_3", "RasterStoreSource_1" ], "endpoint": [ "dask_geomodeling.raster.misc.Clip", "store_1", "area" ], "gemeente": [ "lizard_nxt.blocks.LizardRasterSource", "501e1d53-0bdc-4aa3-9298-a6d5ab5ddb39" ], "RasterStoreSource_1": [ "lizard_nxt.blocks.LizardRasterSource", "2bcffbed-0dd6-4e97-94c1-da2a2dd6b716" ], "RasterStoreSource_2": [ "lizard_nxt.blocks.LizardRasterSource", "85c79bb9-5a16-4c8e-9b33-7a052a687161" ], "RasterStoreSource_3": [ "lizard_nxt.blocks.LizardRasterSource", "ec469dde-deed-438e-b62e-4dfdd0abd5cc" ], "RasterStoreSource_4": [ "lizard_nxt.blocks.LizardRasterSource", "2441d662-472a-418e-b1ec-6f4eb6d29c8b" ] } }, "weight": 9, "raster_sources": [ "https://demo.lizard.net/api/v4/rastersources/ec469dde-deed-438e-b62e-4dfdd0abd5cc/?format=api", "https://demo.lizard.net/api/v4/rastersources/2441d662-472a-418e-b1ec-6f4eb6d29c8b/?format=api", "https://demo.lizard.net/api/v4/rastersources/2bcffbed-0dd6-4e97-94c1-da2a2dd6b716/?format=api", "https://demo.lizard.net/api/v4/rastersources/85c79bb9-5a16-4c8e-9b33-7a052a687161/?format=api", "https://demo.lizard.net/api/v4/rastersources/501e1d53-0bdc-4aa3-9298-a6d5ab5ddb39/?format=api" ], "name": "Hoogte maaiveld", "description": "De kaart van de maaiveldhoogte laat in een oogopslag zien waar de hoogten en laagten zich bevinden en in welke richting het water grofweg gaat stromen als het regent. In het kader van klimaatbestendigheid zijn vooral de laag gelegen delen interessant: waar bevinden zich lokale depressies met het grootste risico op wateroverlast bij neerslag?\r\n\r\nDe gegevens zijn afkomstig van de AHN2 (Actueel Hoogtebestand Nederland 2). Met laserapparatuur is het aardoppervlak afgetast om de hoogte te bepalen. Gemiddeld zijn acht hoogtemetingen per vierkante meter uitgevoerd. Deze zijn vertaald naar een maaiveldhoogte per 0,25 vierkante meter. Uit deze ruwe gegevens zijn bomen, auto’s en huizen gefilterd en geïnterpoleerd om een goed overzicht van het maaiveld te krijgen. Meer informatie kunt u vinden op [www.ahn.nl](http://www.ahn.nl/common-nlm/over-ahn.html \"\").", "observation_type": { "url": "https://demo.lizard.net/api/v4/observationtypes/308/?format=api", "id": 308, "code": "HOOGTE (mNAP)", "parameter": "Hoogte", "unit": "m", "scale": "interval", "description": "", "domain_values": null, "reference_frame": "NAP", "compartment": "", "created": "2015-09-11T07:13:11.538482Z", "last_modified": "2019-06-25T07:26:10.441021Z" }, "temporal": false, "layer_collections": [ { "url": "https://demo.lizard.net/api/v4/layercollections/zundert_klimaatatlas/?format=api", "slug": "zundert_klimaatatlas", "organisation": { "url": "https://demo.lizard.net/api/v4/organisations/064ae6fb-4691-4fe7-ad42-6125da4771be/?format=api", "uuid": "064ae6fb-4691-4fe7-ad42-6125da4771be", "name": "Zundert" }, "access_modifier": "Public", "supplier": "chris.kerklaan", "created": "2021-01-12T09:38:18.945492Z", "last_modified": "2021-01-18T07:51:40.056365Z" } ], "first_value_timestamp": "1970-01-01T00:00:00Z", "last_value_timestamp": "1970-01-01T00:00:00Z", "spatial_bounds": { "west": 3.253713155100211, "east": 7.243161224559517, "north": 53.54488089129097, "south": 50.73417297437435 }, "projection": "EPSG:28992", "origin_x": 13564.4, "origin_y": 306844.0, "upper_bound_x": 278026.4, "upper_bound_y": 619234.0, "pixelsize_x": 0.5, "pixelsize_y": -0.5, "interval": null, "wms_info": { "endpoint": "https://demo.lizard.net/wms/", "layer": "zundert:hoogte-maaiveld-zd5rvvje" }, "options": { "styles": "dem-nl" }, "colormap": {}, "rescalable": false, "aggregation_type": "curve", "dtype": null, "fill_value": null }{ "url": "