Evaluate how components handle tabular data

GeoNodeUserGroup-DE / geonode-dev-datapackage

Datapackage development setup based on Docker Blueprint for GeoNode

0 stars 0 forks source link

Evaluate how components handle tabular data #6

Closed ridoo closed 3 months ago

ridoo commented 3 months ago

Geoserver:
- [x] Remove links which do not make sense, e.g. WMS, png, ..
- [x] Ensure smooth import/publish process
pyCSW
- [x] Check metadata output
GeoNode API v2
- [x] ensure attributes_set is properly set (see GeoNodeUserGroup-DE/importer-datapackage#10)
- [x] ensure tabular data is filterable (see GeoNodeUserGroup-DE/geonode-dev-datapackage#7)

ridoo commented 3 months ago

Remove unnecessary links
- https://github.com/GeoNodeUserGroup-DE/geonode-dev-datapackage/issues/19
Avoid thumbnail creation via WMS
- https://github.com/GeoNodeUserGroup-DE/geonode-dev-datapackage/issues/18
Exceptions/Errors on deleting tabular data
- https://github.com/GeoNodeUserGroup-DE/geonode-dev-datapackage/issues/20
GeoWebCache
- https://github.com/GeoNodeUserGroup-DE/geonode-dev-datapackage/issues/14
default style is required
- https://github.com/GeoNodeUserGroup-DE/geonode-dev-datapackage/issues/13
https://github.com/GeoNodeUserGroup-DE/importer-datapackage/issues/4
~~OWSListView: get()~~ irrelevant as it provides just a list of available endpoints (seems to be legacy as of /api/ows_endpoints)

ridoo commented 3 months ago

The geoserver catalog implementation always tries to calculate a bbox from the geometry and adds [0, -1, 0, -1] as bbox. GeoServer kind of excepts this bbox but declares it as invalid in the GUI:

However, one would have to re-calculate the bbox

ridoo commented 3 months ago

Evaluation done. Relevant cases are handled via dedicated issues.