In general this release will cover the changes between API versions 0.4.2 and 1.0.0 without backward compatibility. Changes in the data models due to the new API are not listed here.
Note: similarly named functions that work on different objects are abrreviated by a *
, e.g. describe_*()
for describe_job()
, describe_service()
, ...
Parameter
into a descriptive formGraph
(e.g. as(x,"Graph")
, where x is a R function returning a ProcessNode
)privacy_policy()
and terms_of_service()
to view the privacy policy and the terms of serviceconformance()
operated on the new corresponding api endpointProcessCollection
in order to divide the Graph object and the graph building. It is created upon connection and obtainable via processes()
.logs()
, log_job()
and log_service()
to request the back-end logs of a job or a service. The logging blocks the console and requests every second an update of the log at the back-end. Also when queing a job via start_job()
an immediate logging can be triggered.FileFormatList
(as.data.frame.FileFormaList
)FileFormat
(print.FileFormat
)ServiceType
(print.ServiceType
)ServiceList
(as.data.frame.ServiceList
, print.ServiceList
)Service
(print.Service
)CollectionList
Collection
(print.Collection
)Log
(print.Log
)Job
(print.Job
)JobList
(print.JobList
)ResultList
(print.ResultList
)AssetList
(as.data.frame.AssetList
)ProcessInfo
(as.Graph.ProcessInfo
)UdfRuntime
(as.character.UdfRuntime
)UdfRuntimeList
CubeDimension
(as.character.CubeDimension
)CubeDimensions
(print.CubeDimensions
)ProcessInfo
(as.Process.ProcessInfo
)UdfRuntimeArgument
, UdfRuntimeVersionArgument
, UdfCodeArgument
ArgumentList
to Process
in order to allow an easier value assignment, e.g. node1$parameter$x = ...
, which comes in handy, when the node is assigned to a variable and a parameter has to changed laterUserProcessCollection
and user_processes()
) like ProcessCollection
for predefined processes, which offers a users stored process graph as a usable function that creates a ProcessNode
Parameter
parent class in order to manipulate parameter representations later, when defining Parameters in user defined processesProcessGraph
as a parameter requires a function wrapping - meaning you should not pass an openeo process like p$min
directly, because with the elaborated ProcessGraphParameter
we cannot do a reliable automatic variable matching, e.g. often the ProcessGraphParameter "context" is misinterpreted*_viewer()
functions to visualize collection and processes following the new api definitionanyOf
is still be used in the client.Callback
was renamed into ProcessGraphArgument
(Graph is still a different Concept), which is used in reducer or aggregation functionscallback-value
was renamed into ProcessGraphParameter
ProcessGraphParameter
are derived automatically from R functions that are passed as ProcessGraphArgument
(former Callback
) and they become parameters that shall be set by a user upon use of this user defined graphprint
functionsupdate_*
and create_*
functions return their respective object (e.g. update_job
--> Job
) instead of their ID (previous behaviour)list_*
functions return a named list of those particular exchange objects (e.g. list_jobs
--> named list of Job
)Graph
object does not hold a reference about the available data sets any longerupdate_process_graph
and merged with the new information given by the function parameterlist_file_formats()
to list_file_formats()
list_process_graphs()
to list_user_processes()
describe_process_graph()
to describe_user_process()
delete_process_graph()
to delete_user_process()
create_process_graph()
to create_user_process()
update_process_graph()
to update_user_process()
validate_process_graph()
to validate_process()
FileFormat
object can passed to OutputFormat
parameterlist_*
and describe_*
can be passed as parameter*Info
class names are reduced to the respective shorter class name without "Info", except for ProcessInfo
list_*
and describe_*
are labeled with the same class and printed with the information available (either overview or detailed view)GeoJson
argumentlog
at start_job()
follow_job()
(replaced by log_job()
)connection
which linked to the used openEO client from the process graph objectprocess_graph_builder()
callback()
, because those Process Graphs are either created from an R function or an resulting ProcessNode
user_id
as a parameter from the files request, because the user information is send with the bearer tokensend_udf
can now handle user_contextsend_udf
has now a parameter for legacy support (which calls the legacy endpoint of a UDF service with API version 0.1.0)run_udf
openEO process) [#48]commonmark
process_viewer
spawns now a viewer in RStudio and renders a beautiful website containing the process informationprocesses
that will create an object that has the processes that are available on the connected openEO service. It is quite similar to the return value of process_graph_builder
which will create a Graph
object with basically the same functionality plus the graph related functionssend_udf
and added documentation to the functionGraph
object explicitly, passing the end node of the defined workflow is now possible.active_connection
now gets and sets the latest connected service into a package variablepi
and e
(in R pi
and exp(1)
) are parsed from the data and translated into the corresponding openEO processes in order to avoid errors due to rounded valuesProcessNode
and callback-value
classesmarkdownViewer
function in favour of process_viewer
and collection_viewer
band_arithmetics
, because callbacks can now be functionsconnect
with new parameters exchange_token
and external
. With the latter we can specify 'google' as an external identity provider and with exchange_token
we can specify if we send the default access_token
or the id_token
as Bearer token in the authentication headerOpenEOClient$isLoggedIn()
) and made it optional at the following endpoints to sent a Bearer token as Authorization-header depending on whether the user is logged in: GET /output_formats
GET /udf_runtimes
GET /service_types
GET /collections
GET /collections/{collection_id}
GET /processes
POST /validation
client_version
was renamed into api_version
and returns the openEO API version which the client usescreate_job
now refers to the HTTP response header "OpenEO-Identifier" rather than parsing the "Location" headerband_arithmetics
where the parameter in array_element were falsely assigneddownload_results
list_file_types
compute_result
)Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.