It would be interesting to be able to use the LI3DS API server without having the full LI3DS model to fill in.
We have the following use case :
a user computes oriented images and point cloud with micmac
he therefore has a simple model with images orientation and basic transformation
he wants to put this data into the database and serve a LIDS-API service
Proposal :
Create a specific schema in LI3DS model with all informations needed for basically serving oriented images ( x,y,z, roll, pitch,yaw, url.. ?)
This schema could be either (materialized) views on the LI3DS model ( in case we have all the metadata with transformations & more) or static tables ( in case we have only directly relevant informations)
The Flask application based on this specific schema would allow for both ways without modification
The exact list of parameters we need in the API, and the API itself, still has to be refined.
It would be interesting to be able to use the LI3DS API server without having the full LI3DS model to fill in.
We have the following use case :
Proposal :
The exact list of parameters we need in the API, and the API itself, still has to be refined.
@ldgeo any reaction ?