Table

Gives the end-users of your published web map a read-only attribute table of the layers you choose, as a foldable panel docked at the bottom of the map. Each layer you pick becomes a sheet; you decide which attributes are visible and which browsing tools (search, column filters, export) end-users get.

It is separate from the attribute table you use while building the map: that one is your editing tool, and it never appears in the published viewer. The Table widget is the surface you deliberately expose to your audience.

The table is read-only for end-users — they can browse, sort, and (if you allow it) search, filter and export. To let end-users edit features, use the Feature editor widget instead.

Parameters

Parameter	What it does
Layers shown	The GeoJSON layers that become sheets. A layer only appears once you check it here — nothing checked leaves the widget empty.
Visible attributes	Per layer, loaded live from the real data as checkboxes. Tick the columns to show; nothing ticked = every attribute of that layer is shown.
Rows per page	How many rows each page holds (paged navigation keeps large layers responsive).
End-users can search	Shows the attribute search box.
End-users can filter columns	Adds a per-column “contains” filter under each header.
End-users can export	Offers a CSV export of the current view.
Open by default	The table dock is expanded when end-users load the map.

What end-users see

A panel docked at the bottom of the map, foldable with a chevron button. When several layers are shown, a row of sheet tabs switches between them. Clicking a column header sorts by that column (ascending, then descending, then off). If you enabled them, a search box narrows rows across the visible columns, per-column filter boxes narrow a single column, and an Export button downloads the current view as CSV. Large layers page through their rows rather than loading everything at once.