Repository navigation
|
I want to build a dashboard to visualise real-time datasets (and historical/batch datasets) and want to know whether GeoNode is an appropriate tool for this. I have several use cases. I'd appreciate someone with more GeoNode experience double checking my thinking:
Is this all correct? Is there a better way to add NEW datasets to a dashboard? Currently we're publishing all metadata (organisations/people/sensors involved with datasets,and links to various datasets and "distributions" (files/APIs/data services where the dataset is represented) to an internal catalogue built around DCAT. We're not using CSW since there is lots of non-spatial data items and services that need to access the data. I see DCAT support in Geonode was dropped a couple of years ago. Are there any examples somewhere of something similar being done in GeoNode? Is GeoNode an appropriate tool for this? |
Replies: 2 comments 3 replies
|
@matthesrieke 52°N has used GeoNode in projects where sensor data was provisioned, right? |
|
@RoryMMMM, you're covering several use cases! As @gannebamm wrote, the GeoNode APIs already cover many cases, where you can automate operations, ingestions, uploads, publishing, etc. For streams of sensor data, the usual approach is to stream to a database from which your dataset is reading. How GeoNode will read it (and automatically get the updated data) depends on where your dataset is published. The internal GeoNode data DB? An external DB served by an external Geoserver? An external DB served by the GeoNode's internal Geoserver? And so forth... Suggesting the best approach on the side of GeoNode really depends on your data architecture. There are many ways to solve the same use case. The right solution depends on the details. Regarding the ability to automatically add a new dataset to a dashboard, this is not supported. Doing it on an existing dashboard would be tricky because the layout is not fixed. How do you tell how and where the new dataset map should be placed and configured? |
Yeah it is possible :)
And in many ways.
Regarding SensorThings we have worked with it for a customer. A simple approach is the one that you mentioned, with a Geoserver SQL View over the frost DB tables. Then you can publish the Geoserver view in GeoNode as a dataset. Take a look at the
updatelayersmanagement command, which allows publishing Geoserver layers in GeoNode.