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/9525ca7a-34df-42d9-b855-d4485be06277/?format=api
https://demo.lizard.net/api/v4/rasters/9525ca7a-34df-42d9-b855-d4485be06277/?format=api", "uuid": "9525ca7a-34df-42d9-b855-d4485be06277", "last_modified": "2019-12-05T14:23:42.380369Z", "created": "2019-10-24T13:30:34.490743Z", "organisation": { "url": "https://demo.lizard.net/api/v4/organisations/474afd21-2f2e-4b4f-8261-5142f1d67acb/?format=api", "uuid": "474afd21-2f2e-4b4f-8261-5142f1d67acb", "name": "Hoogheemraadschap Hollands Noorderkwartier" }, "access_modifier": "Public", "supplier": "chris.kerklaan", "shared_with": [], "writable": false, "is_geoblock": true, "source": { "name": "Clip", "graph": { "Clip": [ "dask_geomodeling.raster.misc.Clip", "LizardRasterSource", "Reclassify" ], "Group": [ "dask_geomodeling.raster.combine.Group", "RasterStoreSource_3", "RasterStoreSource_5" ], "Subtract_1": [ "dask_geomodeling.raster.elemwise.Subtract", "Group", "Interpolate" ], "Subtract_2": [ "dask_geomodeling.raster.elemwise.Subtract", "RasterStoreSource_1", "RasterStoreSource_2" ], "Reclassify": [ "dask_geomodeling.raster.misc.Reclassify", "RasterStoreSource_4", [ [ 15, 1 ], [ 50000, 0 ] ], true ], "Interpolate": [ "raster_store.blocks.Interpolate", "Subtract_2", "EPSG:28992", [ 0.0, 250.0, 0.0, 625000.0, 0.0, -250.0 ] ], "RasterStoreSource_1": [ "lizard_nxt.blocks.LizardRasterSource", "98bf908a-4bed-4635-b2a2-4dbd9efd9b07" ], "RasterStoreSource_2": [ "lizard_nxt.blocks.LizardRasterSource", "eaf35522-c4ad-4faa-bfc7-e530022e53d2" ], "RasterStoreSource_3": [ "lizard_nxt.blocks.LizardRasterSource", "a61657ac-328e-4cdd-97bc-16815206e610" ], "RasterStoreSource_4": [ "lizard_nxt.blocks.LizardRasterSource", "717d343a-acba-49a3-a5bf-c57d98ac08eb" ], "RasterStoreSource_5": [ "lizard_nxt.blocks.LizardRasterSource", "7283ef46-b41f-448a-9e9e-dc884202c069" ], "LizardRasterSource": [ "dask_geomodeling.raster.misc.MaskBelow", "Subtract_1", -10 ] } }, "weight": 12, "raster_sources": [ "https://demo.lizard.net/api/v4/rastersources/98bf908a-4bed-4635-b2a2-4dbd9efd9b07/?format=api", "https://demo.lizard.net/api/v4/rastersources/a61657ac-328e-4cdd-97bc-16815206e610/?format=api", "https://demo.lizard.net/api/v4/rastersources/7283ef46-b41f-448a-9e9e-dc884202c069/?format=api", "https://demo.lizard.net/api/v4/rastersources/eaf35522-c4ad-4faa-bfc7-e530022e53d2/?format=api", "https://demo.lizard.net/api/v4/rastersources/717d343a-acba-49a3-a5bf-c57d98ac08eb/?format=api" ], "name": "Gemiddeld hoogste grondwaterstand - Huidig klimaat", "description": "De intensiteit van de neerslag neemt naar verwachting tot 2050 verder toe. Dit geldt zowel voor de zomers als de winters. In gebieden met hoge peilen en grondwaterstanden én een lage infiltratiecapaciteit is de bodem bij een regenbui snel vol; de bodemberging is beperkt. In deze gebieden treedt als eerste wateroverlast op. In gebieden met lagere peilen en grondwaterstanden is meer bodemberging beschikbaar. Wellicht kan deze berging nog beter benut worden, zodat wateroverlast elders voorkomen wordt. Deze kaart geeft inzicht in de ruimtelijke verdeling van de beschikbare bodemberging, uitgaande van de berekende hoogste grondwaterstand met het Nationaal Watermodel (NWM) bij huidig klimaat.\r\n\r\nDe laag toont per rastercel van 0,5 bij 0,5 meter wat de beschikbare bodemberging is in millimeter. Hieruit volgt welk deel van een bui in de bodem geborgen kan worden. Per bodemtype is aangegeven wat de maximale infiltratiecapaciteit is (dus de snelheid waarmee het water de bodem in kan) én hoeveel millimeter daadwerkelijk in de bodem geborgen kan worden tot aan de berekende hoogste grondwaterstand bij huidig klimaat. Het gaat dus om de “worst-case” beschikbare bodemberging, waarbij de grondwaterstanden hoog zijn. Vervolgens is per peilgebied de mediaan van de bodemberging afgeleid.\r\n\r\nIn deze kaart wordt extra informatie gegenereerd op basis van verfijnd gevisualiseerde resultaten van het Nationaal Watermodel, bodemtypen en infiltratiecapaciteiten. Dit levert een verfijnd beeld met een resolutie van 0.5 bij 0.5 meter. Het rekenresultaat is echter nog steeds gebaseerd op het NWM met resolutie van 250 bij 250 meter. De bewerking levert een bruikbare kaart voor klimaatsessies, omdat deze gemakkelijk te interpreteren is tot op perceelsniveau. Het hoogheemraadschap accepteert geen aansprakelijkheid over onjuiste interpretatie van de kaart. Brondata en aanvullende informatie over het Nationaal Watermodel zijn te vinden via www.klimaateffectatlas.nl", "observation_type": { "url": "https://demo.lizard.net/api/v4/observationtypes/862/?format=api", "id": 862, "code": "GHG_mv", "parameter": "GHG", "unit": "m", "scale": "interval", "description": "", "domain_values": null, "reference_frame": "-MV", "compartment": "GW", "created": "2017-09-12T09:59:13.062841Z", "last_modified": "2019-06-25T07:26:10.441021Z" }, "temporal": false, "layer_collections": [ { "url": "https://demo.lizard.net/api/v4/layercollections/hhnk_klimaatatlas/?format=api", "slug": "hhnk_klimaatatlas", "organisation": { "url": "https://demo.lizard.net/api/v4/organisations/474afd21-2f2e-4b4f-8261-5142f1d67acb/?format=api", "uuid": "474afd21-2f2e-4b4f-8261-5142f1d67acb", "name": "Hoogheemraadschap Hollands Noorderkwartier" }, "access_modifier": "Public", "supplier": null, "created": "2019-09-18T07:08:16.480600Z", "last_modified": "2022-05-23T14:24:30.923651Z" } ], "first_value_timestamp": "1970-01-01T00:00:00Z", "last_value_timestamp": "1970-01-01T00:00:00Z", "spatial_bounds": { "west": 4.489037378593016, "east": 5.38720758743561, "north": 53.21786850266001, "south": 52.31592713962642 }, "projection": "EPSG:28992", "origin_x": null, "origin_y": null, "upper_bound_x": null, "upper_bound_y": null, "pixelsize_x": null, "pixelsize_y": null, "interval": null, "wms_info": { "endpoint": "https://demo.lizard.net/wms/", "layer": "hoogheemraadschap-hollands-noorderkwartier:ghg_huidig" }, "options": { "styles": "YlGnBu_r:0:2" }, "colormap": {}, "rescalable": false, "aggregation_type": "curve", "dtype": null, "fill_value": null }{ "url": "