Open soxofaan opened 1 year ago
This would also be good for the openeo-processes-dask. Currently we're using a custom "load_vector_cube" process for loading the remote geometries and it would be better to replace it with the load_geojson process in the implementations ( for the obvious benefit of alignment ).
In order to realise this change we would currently need to support the additional process of load_url in the dask processes, but, as already mentioned the code to support loading from URLs direclty in the geojson implementation is minimal, and would be less work than implementing load_url and ensuring correct behaviour on our side.
Whenever the discussion is held, also a thumbs up from eodc for this!
This is follow-up of multiple earlier discussions (e.g. #322 #415 #427 #346).
Current openeo-processes draft has:
load_geojson
to load inline GeoJSON object, supports aproperties
parameter to let user select feature properties to load as cube dataload_url
to (among others) load GeoJSON from a URL, supports a genericoptions
parameterThe
properties
parameter ofload_geojson
is not that trivial (e.g. see #448), but it is quite an important feature.How to get this feature in
load_url
+GeoJSON? I guess currently the only way is that the "GeoJSON" input format (GET /file_formats
) defines aproperties
parameter that aligns with theproperties
parameter ofload_geojson
.This has a couple of disadvantages for users, backends and documentation:
load_url
+GeoJSON it's a lot harder for regular users to discover theproperties
feature and it's documentation.properties
option for theload_url
process, while this is trivial forload_geojson
Possible alternative: add support in
load_geojson
for loading from URL in addition to inline GeoJSON. I would guess that the additional implementation work for a back-end implementer is very minimal to add this.This has been discussed before, but I can not completely reconstruct if this idea was intentionally dropped or forgotten.