Attribute Table
Sort, search, filter, and clean a dataset's attribute table — rename/delete fields, trim whitespace, find-and-replace, convert types, and remove duplicates.
How to use
- Paste/upload a CSV or GeoJSON file, or pick an existing dataset from the selector once you have one in your workspace.
- Search, add filter conditions (AND/OR), and click a column header to sort — none of this changes the underlying data, only what you see.
- Open "Field tools" to rename/delete a field, trim whitespace, find-and-replace, convert a field's type, or remove duplicate rows by a key field — these DO change the dataset, and are recorded in its operation history (visible on the Workspace page).
- Converting a field to "number" never turns an empty string into 0 — a value that can't convert cleanly is left as-is and counted in a warning instead.
- Selecting rows highlights them on the map, but clicking the map doesn't select a row back (table → map sync only, for now).
No dataset is active. Paste or upload a CSV or GeoJSON file to start, or pick one from the dataset selector above once you have one.
CSV rows load as attribute-only data (no geometry) — to attach coordinates first, use Coordinate Converter's batch mode or the File Converter.
Attribute Table Coverage
Sort, search, and filter a dataset's attribute table, then clean it up with rename/delete field, trim whitespace, find-and-replace, type conversion, and duplicate removal. Search/filter/sort only change what's displayed; only the field-tools actions change the underlying data, and those are recorded in its operation history.
Null, empty string, and the number 0 are always kept distinguishable — converting a field to a number, for instance, never silently turns an empty string into 0; a value that can't convert cleanly is left untouched and counted in a warning instead.
Frequently asked questions
Does filtering or sorting change my underlying data?
No — search, filters, sort, and hiding a column only change what's displayed. Only rename/delete field, trim, find-and-replace, type conversion, and deduplication change the actual data, and those changes are recorded in the dataset's operation history on the Workspace page.
What happens to a value that can't convert to a number?
It's left exactly as it was — an empty string or a non-numeric string is never turned into 0 or any other value, and the tool reports how many values couldn't convert.