HTML Table layout problem with many-column features about pygeoapi

[tomkralidis]

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.

[justb4]

Not displaying a table would affect non-Point geometries (see e.g. Great Lakes Dataset) as these can (currently) not be clicked in Map.

[pvgenuchten]

A table is usefull here imho.

• It helps people people to identify there is a list of items on the page, giving insight in the attributes without clicking in the map
• It helps machines (search engines) to identify there is a list of items on the page

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.

[tomkralidis]

+1

[justb4]

Think we're done here. Thanks @pvgenuchten and @tomkralidis . Closing, pls re-open if still work needed.