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/53867647-1eef-482b-b179-405b1a8ea643/?format=api
https://demo.lizard.net/api/v4/rasters/53867647-1eef-482b-b179-405b1a8ea643/?format=api", "uuid": "53867647-1eef-482b-b179-405b1a8ea643", "last_modified": "2024-05-03T11:49:25.433478Z", "created": "2024-05-03T10:16:31.961968Z", "organisation": { "url": "https://demo.lizard.net/api/v4/organisations/bb454ac7-4523-4aa5-a94f-4b06144dafe5/?format=api", "uuid": "bb454ac7-4523-4aa5-a94f-4b06144dafe5", "name": "HLTsamen" }, "access_modifier": "Public", "supplier": "jelmer.roosjen", "shared_with": [], "writable": false, "is_geoblock": false, "source": { "name": "raster", "graph": { "raster": [ "lizard_nxt.blocks.LizardRasterSource", "7b00c6b1-fee7-4633-b234-ad18ab0de9c4" ] } }, "weight": 0, "raster_sources": [ "https://demo.lizard.net/api/v4/rastersources/7b00c6b1-fee7-4633-b234-ad18ab0de9c4/?format=api" ], "name": "Gevoelstemperatuur (PET) [2024]", "description": "De kaartlaag ‘Gevoelstemperatuur (PET)’ geeft aan waar hittestress kan optreden tijdens zomerse dagen. De kaart toon de Physical Equivalent Temperature (PET/Gevoelstemperatuur) op een warme dag die 1 keer per 1000 zomerdagen voorkomt in het huidige klimaat (onder een zomerdag valt de periode van 1 april t/m 30 september). De rode gebieden zijn zeer gevoelig voor hittestress, de groene gebieden nauwelijks.\r\n\r\n**Opbouw**\r\n\r\nBij de totstandkoming van deze kaart spelen de volgende fysische factoren een rol:\r\n\r\n- Schaduw;\r\n- Windsnelheid;\r\n- Luchtvochtigheid;\r\n- Luchttemperatuur;\r\n- Straatbreedte;\r\n- Gebouwhoogte;\r\n- Bomen en andere vegetatie.\r\n\r\nDe bovenstaande factoren zijn afgeleid uit de volgende bronnen:\r\n\r\n- Weerstations (KNMI);\r\n- Sky view factor Nederland (KNMI);\r\n- Algemeen Hoogte Bestand Nederland (AHN4);\r\n- Landelijk beeldvoorzieningbeeld Nederland (LVB).\r\n\r\n**Verantwoording**\r\n\r\nDeze hittestresskaart is de standaard voor Nederland. De methodiek, ontwikkeld door de Universiteit Wageningen is te vinden in het volgende rapport: \r\n[https://www.rivm.nl/bibliotheek/rapporten/2019-0008.pdf](https://www.rivm.nl/bibliotheek/rapporten/2019-0008.pdf \"https://www.rivm.nl/bibliotheek/rapporten/2019-0008.pdf\").\r\nDeze kaart is opgesteld in 2024.", "observation_type": { "url": "https://demo.lizard.net/api/v4/observationtypes/549/?format=api", "id": 549, "code": "TAVG", "parameter": "Temperature", "unit": "°C", "scale": "interval", "description": "", "domain_values": null, "reference_frame": null, "compartment": null, "created": "2016-11-24T12:15:28.253800Z", "last_modified": "2019-06-25T07:26:10.441021Z" }, "temporal": false, "layer_collections": [ { "url": "https://demo.lizard.net/api/v4/layercollections/hltsamen_klimaatatlas/?format=api", "slug": "hltsamen_klimaatatlas", "organisation": { "url": "https://demo.lizard.net/api/v4/organisations/bb454ac7-4523-4aa5-a94f-4b06144dafe5/?format=api", "uuid": "bb454ac7-4523-4aa5-a94f-4b06144dafe5", "name": "HLTsamen" }, "access_modifier": "Public", "supplier": "jelmer.roosjen", "created": "2019-10-24T13:39:13.269476Z", "last_modified": "2024-05-03T11:48:35.110680Z" } ], "first_value_timestamp": "1970-01-01T00:00:00Z", "last_value_timestamp": "1970-01-01T00:00:00Z", "spatial_bounds": { "west": 4.453332579367915, "east": 4.614016538386595, "north": 52.318585329204396, "south": 52.179107598257346 }, "projection": "EPSG:28992", "origin_x": 91325.0, "origin_y": 466071.5, "upper_bound_x": 102118.0, "upper_bound_y": 481464.5, "pixelsize_x": 0.5, "pixelsize_y": -0.5, "interval": null, "wms_info": { "endpoint": "https://demo.lizard.net/wms/", "layer": "nelen-schuurmans-consultancy:gevoelstemperatuur-pet-2024" }, "options": { "styles": "pet_heatstress:38:52" }, "colormap": {}, "rescalable": true, "aggregation_type": "curve", "dtype": "f4", "fill_value": "3.4028234663852886e+38" }{ "url": "