Closed justb4 closed 5 years ago
Another option could be to not display a table, and when a user clicks on a point, then show a table of just that feature's properties, displayed similarly to a single feature HTML page.
Not displaying a table would affect non-Point geometries (see e.g. Great Lakes
Dataset) as these can (currently) not be clicked in Map.
A table is usefull here imho.
As a start, we could limit the list to the first 8 columns?
If at some point we add more semantics to pygeoapi, for example indicate which field is id/name/description, we can select certain fields to display in list mode, or allow user to indicate which fields to show in list mode.
+1
Think we're done here. Thanks @pvgenuchten and @tomkralidis . Closing, pls re-open if still work needed.
In some cases where a Feature has many attributes (columns), the HTML Table display within the items.html template gets "too compact". See image below (feature 'RD Point' has around 20 attributes/columns):
How to solve? Ideas: