You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thomas will explore the different options that we have to query this type of data in order to evaluate if it is enough for our use cases or if it is better to define the actual data type of the columns in geodb.
Please, work on the geodb branch and create a copy of the previous notebook (can call it geodb_json.ipynb for example).
The text was updated successfully, but these errors were encountered:
I have experimented with JSON-based queries, and I recommend not to use those as queries tend to get very complicated. Rather, I have changed the notebook so that the actual types are used, and JSON columns are stored as strings. As such, they are 1) easily queriable and 2) can still be converted to JSON after fetching them from the geoDB.
At this moment all the columns in the stac catalogs stores in geodb use the type"json".
This makes easy to store any kind of data but limits query functionality on geodb.
You can see an example in https://github.com/earthpulse/eotdl/blob/geodb/tutorials/notebooks/geodb.ipynb
Thomas will explore the different options that we have to query this type of data in order to evaluate if it is enough for our use cases or if it is better to define the actual data type of the columns in geodb.
Please, work on the geodb branch and create a copy of the previous notebook (can call it geodb_json.ipynb for example).
The text was updated successfully, but these errors were encountered: