Evaluate how components handle tabular data

[ridoo]

• Geoserver:
  • Remove links which do not make sense, e.g. WMS, png, ..
  • Ensure smooth import/publish process
• pyCSW
  • Check metadata output
• GeoNode API v2
  • ensure attributes_set is properly set (see Support for attribute_set for detailed description of the dataset contrib_datapackage#10)
  • ensure tabular data is filterable (see Differentiate tabular datasets from regular datasets #7)

[ridoo]

• Remove unnecessary links
  • Remove unnecessary image links #19
• Avoid thumbnail creation via WMS
  • Task: thumbnail for tabular data #18
• Exceptions/Errors on deleting tabular data
  • Cascading delete lets GeoServer throw exceptions #20
• GeoWebCache
  • GeoNode tries to access tabular data via GWC #14
• default style is required
  • updatelayer raises exception on tabular data #13
• After changing metadata of nonSpatial Dataset its converted to geo Dataset contrib_datapackage#4
• OWSListView: get() irrelevant as it provides just a list of available endpoints (seems to be legacy as of /api/ows_endpoints)

[ridoo]

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]

Evaluation done. Relevant cases are handled via dedicated issues.