Attributes, fields, filters and tables

Use the Attributes table for record-level work

Open the Data/GIS window for an editable layer and choose Attributes. The table shows one record per feature and renders controls according to the layer schema rather than treating every value as untyped text.

Supported field types include text, integer, decimal, boolean, date and datetime. Read-only fields remain visible but cannot be edited. Changes made through the table use the same project data model as map edits.

Sort and inspect records

Click a column heading to sort. Shift-click another heading to add a secondary sort; the table displays the sort priority so multi-column order is explicit.

Use table search and the Filter tab for different purposes: table search is a quick view aid, while a layer filter is a reusable dataset condition that can also become the Filtered input scope in Processing.

Edit typed values safely

Edit a cell using the control appropriate to its field type. Numeric values remain numeric, booleans use explicit true/false controls, and date/datetime fields are validated before being written back to the layer.

If a value cannot be converted to the target field type, EditPolygon reports the problem instead of silently storing a misleading value.

Manage fields and schemas

Open Fields & stats to add, change or remove fields and to inspect the schema as a dataset rather than one record at a time.

1. Add a field.

   Choose a field name, optional alias, type, nullability and default value as appropriate.

2. Preview type conversion before changing an existing field.

   EditPolygon reports values that cannot be converted so you can decide whether to cancel, clean the data or explicitly replace invalid values.

3. Review read-only/system fields.

   Fields that are not intended for direct editing remain protected.

Calculate a field

The Field calculator evaluates an expression against records and previews the prospective output before applying it. Choose the output field and type deliberately so a numeric calculation does not become text data.

Use calculator preview to catch invalid expressions or incompatible results before the complete layer is mutated.

Inspect field statistics

Fields & stats can summarise populated/missing values, unique values and numeric statistics such as minimum, maximum, sum, mean, median and distribution information where applicable. These summaries are useful before choosing classification breaks, a join key or a calculation rule.

Build compound filters

The Filter tab supports multiple conditions and AND/OR logic. Operators depend on the field and include normal comparisons such as equality, contains, greater/less than and range tests.

Save a useful filter when it represents a repeatable subset. Applying or clearing a filter updates the layer's filtered state without deleting records.

Export a normal spreadsheet CSV

The Attributes table has its own record export. Choose the record scope you need, then select the format:

Complex polygons can create extremely long WKT values. Do not choose CSV + WKT merely because you want a spreadsheet—use CSV — attributes only when geometry is irrelevant.

Use joins when data belongs in another table or layer

Open Join & summarize for table-oriented joins and summaries, or use Processing → Join attributes by location when the relationship is spatial. The correct choice depends on whether records match by a key field or by geometry.

See Spatial joins and location queries for spatial relationships, multiple matches and one-output-per-match behaviour.

Undo, project state and downstream dependencies

Attribute and schema changes participate in the current project state and history where supported. Undo/Redo can restore earlier values or schemas, and the Data/GIS interface refreshes after a history restore rather than leaving stale phantom fields on screen.

Save an .epz project before a large schema migration or calculated-field operation that will be difficult to reconstruct from the source file alone.