πPublish your outputs as Ellipsis Drive layers
Ellipsis Drive is a solution optimized to allow you to efficiently and flexibly deliver your spatial data. If you create lots of it, automation might be what you are looking for!
Publishing your spatial data to Ellipsis Drive can of course be done via the app, but when you need to publish many layers, or need to update them very frequently, you might want to automate the publication procedure.
Automatic delivery can be easily achieved using either the API, Python package or R library. Delivery always consists of the following steps. (The api calls refer to the raster section of the api, but by replacing /raster in the url for /vector or /pointCloud the same procedure can be used for other types of data)
Step 1: Create a token to authenticate with. We recommend using the access token variant.
Step 2: obtain the folder id where you wish to place your new layer. If no folder id is given you will be publishing in the root.
Step 3: Create a layer in the given folder using this api call.
Step 4: Create a timestamp in the given layer using this api call.
Step 5: Upload one or more files to the created timestamp using this api call.
Step 6: After all uploads are completed activate the timestamp using this api call.
Step 7: Ellipsis Drive will now transform your files into a high performance and completely interoperable web service.
The same can be achieved via Python and R. We generally recommend to use Python to create automated delivery pipelines. A working example for the Python case can be found here.
Vector data updates
Vector layers can be populated using vector files, such as geopackages or shapes. But they can also be populated in a transactional fashion. Individual vectors can be added, deleted or edited. The same can of course be achieved using Python and R. In the case of Python you can use shapely geometries and geopanda dataFrames instead of geoJsons. Documentation can be found here.
Last updated