mapshaper 0.7.1 → 0.7.2

package/mapshaper.js

@@ -52127,7 +52127,7 @@ ${svg}
     });
   }
 
-  var version = "0.7.1";
+  var version = "0.7.2";
 
   // Parse command line args into commands and run them
   // Function takes an optional Node-style callback. A Promise is returned if no callback is given.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mapshaper",
-  "version": "0.7.1",
+  "version": "0.7.2",
   "description": "A tool for editing vector datasets for mapping and GIS.",
   "keywords": [
     "shapefile",
@@ -26,6 +26,7 @@
     "test": "mocha test",
     "build": "rollup --config",
     "docs": "node build-docs.mjs",
+    "roadmap": "node build-roadmap.mjs",
     "lint": "eslint --ext mjs src/",
     "prepublishOnly": "npm test; ./pre-publish",
     "postpublish": "./release_web_ui; ./release_github_version",

package/www/docs/_assets/docs.css

@@ -40,10 +40,15 @@ code, pre, .mono {
 .page-header {
   background-color: #1385B7;
   color: white;
-  padding: 0 14px;
-  height: 36px;
+  /* Asymmetric vertical padding (4px top, 8px bottom) optically centers the
+     baseline-aligned row: ascenders are taller than descenders, so equal
+     padding makes the text look ~2px low. */
+  padding: 2px 14px 8px;
+  height: 32px;
   display: flex;
-  align-items: center;
+  /* baseline-align so the 18px logo and the 14px nav text share a baseline,
+     not just a vertical center */
+  align-items: baseline;
   gap: 14px;
 }
 
@@ -76,7 +81,10 @@ code, pre, .mono {
   color: white;
   text-decoration: none;
   font-size: 14px;
-  padding: 6px 10px;
+  /* line-height: 1 keeps each anchor's hover background tight enough to fit
+     inside the 36px header once the row is baseline-aligned. */
+  line-height: 1;
+  padding: 6px 6px;
   border-radius: 3px;
 }
 
@@ -165,7 +173,9 @@ code, pre, .mono {
 
 .docs-nav a {
   display: block;
-  padding: 4px 8px;
+  /* Asymmetric vertical padding (6px top, 2px bottom) optically centers
+     the text inside the active/hover background. */
+  padding: 5px 8px 2px;
   border-radius: 3px;
   color: #333;
   font-size: 14px;

package/www/docs/examples/basics.html

@@ -33,7 +33,7 @@
     <article class="docs-article">
       <div class="docs-breadcrumbs"><a href="/docs/">Docs</a> &rsaquo; Examples &rsaquo; Basics</div>
       <h1 id="basics">Basics</h1>
-<p>Short Mapshaper recipes for common GIS tasks. The filenames and field names are illustrative &mdash; substitute your own. Most recipes also work in the <a href="/docs/essentials/web-app.html">web app&#39;s</a> console: drop the leading <code>mapshaper</code> and the input filename, since the GUI already has the layer loaded.</p>
+<p>Short Mapshaper examples for common tasks. The filenames and field names are illustrative &mdash; substitute your own. Most recipes also work in the <a href="/docs/essentials/web-app.html">web app&#39;s</a> console: drop the leading <code>mapshaper</code> and the input filename; the GUI should already your data loaded.</p>
 <blockquote>
 <p>Looking for the syntax of a particular command or option? See the <a href="/docs/reference.html">command reference</a>. For the JS expression context used by <code>-each</code>, <code>-filter</code>, <code>calc=</code> and other commands, see <a href="/docs/guides/expressions.html">JavaScript expressions</a>.</p>
 </blockquote>
@@ -248,7 +248,6 @@ mapshaper
 <ul>
 <li><a href="/docs/reference.html">Command reference</a> &mdash; every command and option</li>
 <li><a href="/docs/guides/expressions.html">JavaScript expressions</a> &mdash; the syntax and context used by <code>-each</code>, <code>-filter</code>, <code>calc=</code>, etc.</li>
-<li><a href="/docs/guides/">Guides</a> &mdash; longer-form walk-throughs of simplification, topology cleaning, and more</li>
 </ul>
 
       <div class="edit-link">

package/www/docs/examples/basics.html.md

@@ -5,7 +5,7 @@ description: A scannable collection of short Mapshaper recipes for common GIS ta
 
 # Basics
 
-Short Mapshaper recipes for common GIS tasks. The filenames and field names are illustrative — substitute your own. Most recipes also work in the [web app's](/docs/essentials/web-app.html.md) console: drop the leading `mapshaper` and the input filename, since the GUI already has the layer loaded.
+Short Mapshaper examples for common tasks. The filenames and field names are illustrative — substitute your own. Most recipes also work in the [web app's](/docs/essentials/web-app.html.md) console: drop the leading `mapshaper` and the input filename; the GUI should already your data loaded.
 
 > Looking for the syntax of a particular command or option? See the [command reference](/docs/reference.html.md). For the JS expression context used by `-each`, `-filter`, `calc=` and other commands, see [JavaScript expressions](/docs/guides/expressions.html.md).
 
@@ -368,4 +368,3 @@ mapshaper-xl 16gb counties_5m.shp -simplify 10% -o counties_5m.topojson
 
 - [Command reference](/docs/reference.html.md) — every command and option
 - [JavaScript expressions](/docs/guides/expressions.html.md) — the syntax and context used by `-each`, `-filter`, `calc=`, etc.
-- [Guides](/docs/guides/index.html.md) — longer-form walk-throughs of simplification, topology cleaning, and more

package/www/docs/formats/flatgeobuf.html

@@ -46,7 +46,6 @@ mapshaper provinces.shp -o provinces.fgb
 <p>There are no FlatGeobuf-specific <code>-o</code> options. The format honors the general flags (<code>precision=</code>, <code>gzip</code>, <code>zip</code>, etc.) where they apply.</p>
 <h3 id="practical-notes">Practical notes</h3>
 <ul>
-<li>FlatGeobuf is single-layer per file. Use <a href="/docs/formats/geopackage.html">GeoPackage</a> or <a href="/docs/formats/topojson.html">TopoJSON</a> when you need to package multiple layers in one file.</li>
 <li>Mapshaper reads CRS metadata from the file header when it&#39;s encoded as an EPSG code. WKT2-only definitions can&#39;t be parsed and produce an &quot;Unable to import WKT2 CRS from FlatGeobuf&quot; warning &mdash; the layer comes in without a CRS.</li>
 <li>On output, Mapshaper embeds an EPSG code in the FlatGeobuf header whenever it can derive one from the source: a round-tripped FlatGeobuf or GeoPackage CRS, an <code>epsg:NNNN</code> string passed to <code>-proj</code>, an <code>AUTHORITY[&quot;EPSG&quot;, N]</code> clause in a Shapefile <code>.prj</code>, or any encoding of WGS-84 or Web Mercator (which covers most GeoJSON, CSV-with-lat/lon and <code>-proj wgs84</code>/<code>-proj webmercator</code> outputs).</li>
 <li>Mapshaper cannot yet convert an arbitrary proj4 definition (such as a custom Albers projection set with <code>-proj +proj=aea ...</code>) to an EPSG code. In that case the file is written with no CRS in the header and a warning is printed: <em>&quot;Wrote <code>foo.fgb</code> without a CRS in the FlatGeobuf header...&quot;</em>. Re-run the file through <code>ogr2ogr</code> if you need the CRS embedded for downstream tools.</li>

package/www/docs/formats/flatgeobuf.html.md

@@ -27,7 +27,6 @@ There are no FlatGeobuf-specific `-o` options. The format honors the general fla
 
 ### Practical notes
 
-- FlatGeobuf is single-layer per file. Use [GeoPackage](/docs/formats/geopackage.html.md) or [TopoJSON](/docs/formats/topojson.html.md) when you need to package multiple layers in one file.
 - Mapshaper reads CRS metadata from the file header when it's encoded as an EPSG code. WKT2-only definitions can't be parsed and produce an "Unable to import WKT2 CRS from FlatGeobuf" warning — the layer comes in without a CRS.
 - On output, Mapshaper embeds an EPSG code in the FlatGeobuf header whenever it can derive one from the source: a round-tripped FlatGeobuf or GeoPackage CRS, an `epsg:NNNN` string passed to `-proj`, an `AUTHORITY["EPSG", N]` clause in a Shapefile `.prj`, or any encoding of WGS-84 or Web Mercator (which covers most GeoJSON, CSV-with-lat/lon and `-proj wgs84`/`-proj webmercator` outputs).
 - Mapshaper cannot yet convert an arbitrary proj4 definition (such as a custom Albers projection set with `-proj +proj=aea ...`) to an EPSG code. In that case the file is written with no CRS in the header and a warning is printed: *"Wrote `foo.fgb` without a CRS in the FlatGeobuf header..."*. Re-run the file through `ogr2ogr` if you need the CRS embedded for downstream tools.

package/www/docs/formats/overview.html

@@ -163,7 +163,6 @@
 <ul>
 <li><strong>Auto-detection by extension.</strong> You usually don&#39;t need to tell Mapshaper what format a file is &mdash; it picks the right reader from the file extension. Use <code>format=</code> on <code>-i</code> or <code>-o</code> to override.</li>
 <li><strong>TopoJSON is the only interchange format that preserves topology</strong> in the file itself. Topology-aware operations like <a href="/docs/reference.html#-dissolve"><code>-dissolve</code></a>, <a href="/docs/reference.html#-clean"><code>-clean</code></a> and <a href="/docs/reference.html#-simplify"><code>-simplify</code></a> work correctly regardless of the input format, but only TopoJSON keeps shared boundaries between adjacent polygons from being duplicated on disk. (Mapshaper&#39;s own <a href="/docs/formats/snapshot.html"><code>.msx</code></a> snapshots also preserve topology, but they&#39;re not readable by other tools.)</li>
-<li><strong>Most formats are single-layer per file.</strong> Multi-layer GeoJSON, Shapefile and FlatGeobuf datasets are conventionally split across multiple files (in the same directory on the CLI; selected together or zipped in the <a href="/docs/essentials/web-app.html">web app</a>); TopoJSON, GeoPackage and KML can hold many layers in one file.</li>
 <li><strong>Encoding.</strong> The <code>encoding=</code> option on <code>-i</code> and <code>-o</code> applies to Shapefile, DBF and CSV/TSV i/o (UTF-8 is the default) &mdash; the other formats are UTF-8-only.</li>
 </ul>
 

package/www/docs/formats/overview.html.md

@@ -31,5 +31,4 @@ A few things worth knowing across all formats:
 
 - **Auto-detection by extension.** You usually don't need to tell Mapshaper what format a file is — it picks the right reader from the file extension. Use `format=` on `-i` or `-o` to override.
 - **TopoJSON is the only interchange format that preserves topology** in the file itself. Topology-aware operations like [`-dissolve`](/docs/reference.html.md#-dissolve), [`-clean`](/docs/reference.html.md#-clean) and [`-simplify`](/docs/reference.html.md#-simplify) work correctly regardless of the input format, but only TopoJSON keeps shared boundaries between adjacent polygons from being duplicated on disk. (Mapshaper's own [`.msx`](/docs/formats/snapshot.html.md) snapshots also preserve topology, but they're not readable by other tools.)
-- **Most formats are single-layer per file.** Multi-layer GeoJSON, Shapefile and FlatGeobuf datasets are conventionally split across multiple files (in the same directory on the CLI; selected together or zipped in the [web app](/docs/essentials/web-app.html.md)); TopoJSON, GeoPackage and KML can hold many layers in one file.
 - **Encoding.** The `encoding=` option on `-i` and `-o` applies to Shapefile, DBF and CSV/TSV i/o (UTF-8 is the default) — the other formats are UTF-8-only.

package/www/docs/guides/combining-layers.html

@@ -45,6 +45,10 @@
 <li>A county boundary file from the California Open Data Portal &mdash; or, in this case, a <a href="https://geodata.lib.berkeley.edu/catalog/ark28722-s7hs4j">version clipped to the shoreline</a> from UC Berkeley&#39;s Geo Data Commons. The shoreline-clipped version reads more naturally on a map than the legal-boundary version, which extends into the bay.</li>
 <li>A statewide <a href="https://geodata.lib.berkeley.edu/catalog/ark28722-s7bp4z">places boundary file</a> for city boundaries.</li>
 </ul>
+<p>The legal county boundaries from the Census TIGER files extend straight across the water &mdash; San Francisco even reaches out to include the Farallon Islands:</p>
+<p><img src="/docs/images/tiger-counties.png" alt="Bay Area counties from the Census TIGER file, with boundaries cutting across the bay and extending offshore"></p>
+<p>The Berkeley library&#39;s version is clipped to the shoreline, so the bay shows as empty space between the counties:</p>
+<p><img src="/docs/images/cal-counties.png" alt="The same Bay Area counties, with each polygon clipped to the coastline so the bay is visible between them"></p>
 <p>Download both as <code>.zip</code> files.</p>
 <h2 id="open-them-in-mapshaper">Open them in Mapshaper</h2>
 <p>Drag the two <code>.zip</code> files onto <a href="/">mapshaper.org</a>, or run the web app locally with <code>mapshaper-gui</code>. You&#39;ll end up with two layers loaded into the session.</p>

package/www/docs/guides/combining-layers.html.md

@@ -20,6 +20,14 @@ We'll use two source files:
 - A county boundary file from the California Open Data Portal — or, in this case, a [version clipped to the shoreline](https://geodata.lib.berkeley.edu/catalog/ark28722-s7hs4j) from UC Berkeley's Geo Data Commons. The shoreline-clipped version reads more naturally on a map than the legal-boundary version, which extends into the bay.
 - A statewide [places boundary file](https://geodata.lib.berkeley.edu/catalog/ark28722-s7bp4z) for city boundaries.
 
+The legal county boundaries from the Census TIGER files extend straight across the water — San Francisco even reaches out to include the Farallon Islands:
+
+![Bay Area counties from the Census TIGER file, with boundaries cutting across the bay and extending offshore](/docs/images/tiger-counties.png)
+
+The Berkeley library's version is clipped to the shoreline, so the bay shows as empty space between the counties:
+
+![The same Bay Area counties, with each polygon clipped to the coastline so the bay is visible between them](/docs/images/cal-counties.png)
+
 Download both as `.zip` files.
 
 ## Open them in Mapshaper

package/www/docs/guides/simplification.html

@@ -39,10 +39,10 @@
 <ul>
 <li><strong><code>dp</code></strong> &mdash; Douglas-Peucker (also known as Ramer–Douglas–Peucker). Guarantees that simplified lines stay within a fixed distance of the original. Good for stripping excess vertices to reduce file size, but tends to grow visible spikes at high simplification.</li>
 <li><strong><code>visvalingam</code></strong> &mdash; The Visvalingam algorithm. Iteratively removes the point that forms the smallest triangle with its two neighbors.</li>
-<li><strong><code>weighted_visvalingam</code></strong> (Mapshaper&#39;s default) &mdash; Visvalingam&#39;s effective-area algorithm with a custom weighting that underweights points at sharp angles, so they are removed earlier than in standard Visvalingam. The result is visibly smoother lines and fewer jagged spikes at high simplification. This method can be effective at generalizing very detailed source files, but be careful that it doesn&#39;t remove long, thin geographic features that you want to keep.</li>
+<li><strong><code>weighted_visvalingam</code></strong> (Mapshaper&#39;s default) &mdash; Visvalingam&#39;s effective-area algorithm with a custom weighting that underweights points at sharp angles, so they are removed earlier than in standard Visvalingam. The result is visibly smoother lines and fewer jagged spikes at high simplification.</li>
 </ul>
-<p>Weighted Visvalingam is the default because it has proven to be versatile and effective at reducing detail in highly detailed source data. If you are only interested in minimizing file size, Douglas-Peucker is generally the better choice.</p>
-<p>You can control the amount of weighting used by Weighted Visvalingam with the <code>weighting=</code> option (default is 0.7).</p>
+<p>Weighted Visvalingam is the default because it has proven to be versatile and effective at reducing detail in highly detailed source data. This method can be effective at generalizing very detailed source files, but be careful that it doesn&#39;t remove long, thin geographic features that you want to keep.You can control the amount of weighting used by Weighted Visvalingam with the <code>weighting=</code> option (default is 0.7).</p>
+<p>If you are only interested in minimizing file size, Douglas-Peucker is generally the better choice.</p>
 <p><strong>Figures</strong></p>
 <p>Natural Earth 10m coastlines, simplified with modified Visvalingam at 5% point retention.
 <img src="/docs/images/simplification-mod2.png" alt="image"></p>

package/www/docs/guides/simplification.html.md

@@ -13,11 +13,13 @@ Mapshaper offers three simplification methods, selectable as flags to `-simplify
 
 - **`dp`** — Douglas-Peucker (also known as Ramer–Douglas–Peucker). Guarantees that simplified lines stay within a fixed distance of the original. Good for stripping excess vertices to reduce file size, but tends to grow visible spikes at high simplification.
 - **`visvalingam`** — The Visvalingam algorithm. Iteratively removes the point that forms the smallest triangle with its two neighbors.
-- **`weighted_visvalingam`** (Mapshaper's default) — Visvalingam's effective-area algorithm with a custom weighting that underweights points at sharp angles, so they are removed earlier than in standard Visvalingam. The result is visibly smoother lines and fewer jagged spikes at high simplification. This method can be effective at generalizing very detailed source files, but be careful that it doesn't remove long, thin geographic features that you want to keep.
+- **`weighted_visvalingam`** (Mapshaper's default) — Visvalingam's effective-area algorithm with a custom weighting that underweights points at sharp angles, so they are removed earlier than in standard Visvalingam. The result is visibly smoother lines and fewer jagged spikes at high simplification.
+
+Weighted Visvalingam is the default because it has proven to be versatile and effective at reducing detail in highly detailed source data. This method can be effective at generalizing very detailed source files, but be careful that it doesn't remove long, thin geographic features that you want to keep.You can control the amount of weighting used by Weighted Visvalingam with the `weighting=` option (default is 0.7).
+
+If you are only interested in minimizing file size, Douglas-Peucker is generally the better choice.
 
-Weighted Visvalingam is the default because it has proven to be versatile and effective at reducing detail in highly detailed source data. If you are only interested in minimizing file size, Douglas-Peucker is generally the better choice.
 
-You can control the amount of weighting used by Weighted Visvalingam with the `weighting=` option (default is 0.7).
 
 **Figures**
 

package/www/docs/reference.html

@@ -455,13 +455,13 @@ mapshaper counties.shp \
 <p><code>holes</code>  Delete any holes from a polygon layer.</p>
 <p><code>target=</code>  Layer(s) to target.</p>
 </section>
-<section class="cmd-section" data-id="-each" data-name="-each" data-options="this expression where target calc weight radius bbox"><h3 id="-each">-each</h3>
+<section class="cmd-section" data-id="-each" data-name="-each" data-options="this expression where target"><h3 id="-each">-each</h3>
 <p>Apply a JavaScript expression to each feature in a layer. Data properties are available as local variables; the feature&#39;s geometry-derived properties are available on the <code>this</code> object (e.g. <code>this.area</code>, <code>this.centroidX</code>, <code>this.bbox</code>).</p>
 <p><strong>Tip:</strong> Enclose JS expressions in single quotes when using the bash shell (Mac and Linux) to avoid shell expansion of <code>!</code> and other special characters. Using the Windows command interpreter, enclose JS expressions in double quotes.</p>
 <p><code>&lt;expression&gt;</code> or <code>expression=</code>  JavaScript expression to apply to each feature.</p>
 <p><code>where=</code>  Secondary boolean JS expression for targetting a subset of features.</p>
 <p><code>target=</code>  Layer to target.</p>
-<p>The same expression syntax and execution context are used by <code>-each</code>, <code>-filter</code>, <code>-sort</code>, <code>-inspect</code>, <code>-split</code>, <code>-subdivide</code>, <code>-calc</code> (and <code>calc=</code> options on <code>-dissolve</code>, <code>-join</code>, etc.), <code>-style</code>, <code>-symbols</code>, and any <code>where=</code>, <code>weight=</code>, <code>radius=</code> or <code>bbox=</code> option. See <a href="/docs/guides/expressions.html">JavaScript expressions</a> for the full reference: the available <code>this.*</code> properties for each geometry type, helper functions like <code>round()</code>, <code>sprintf()</code> and <code>format_dms()</code>, the <code>-calc</code> aggregation functions, the <code>A</code>/<code>B</code> pair context used by <code>-lines</code>, and common pitfalls. The <a href="/docs/examples/basics.html">Basics</a> page has practical recipes that put expressions to work.</p>
+<p>The same expression syntax and execution context are used by all commands that support expressions. See <a href="/docs/guides/expressions.html">JavaScript expressions</a> for the full reference. The <a href="/docs/examples/basics.html">Basics</a> page has practical recipes that put expressions to work.</p>
 <p><strong>Examples</strong></p>
 <pre><code class="hljs language-bash"><span class="hljs-comment"># Create two fields</span>
 mapshaper counties.shp \

package/www/docs/reference.html.md

@@ -681,7 +681,7 @@ Apply a JavaScript expression to each feature in a layer. Data properties are av
 
 `target=`  Layer to target.
 
-The same expression syntax and execution context are used by `-each`, `-filter`, `-sort`, `-inspect`, `-split`, `-subdivide`, `-calc` (and `calc=` options on `-dissolve`, `-join`, etc.), `-style`, `-symbols`, and any `where=`, `weight=`, `radius=` or `bbox=` option. See [JavaScript expressions](/docs/guides/expressions.html.md) for the full reference: the available `this.*` properties for each geometry type, helper functions like `round()`, `sprintf()` and `format_dms()`, the `-calc` aggregation functions, the `A`/`B` pair context used by `-lines`, and common pitfalls. The [Basics](/docs/examples/basics.html.md) page has practical recipes that put expressions to work.
+The same expression syntax and execution context are used by all commands that support expressions. See [JavaScript expressions](/docs/guides/expressions.html.md) for the full reference. The [Basics](/docs/examples/basics.html.md) page has practical recipes that put expressions to work.
 
 **Examples**
 

package/www/docs/whats-new.html

@@ -35,7 +35,8 @@
       <h1 id="whats-new">What&#39;s new</h1>
 <p>This is a curated list of recently added features. For the full list of changes, including bug fixes and internal work, see the <a href="https://github.com/mbloch/mapshaper/blob/master/CHANGELOG.md">changelog</a> on GitHub.</p>
 <h2 id="april-2026">April 2026</h2>
-<div class="whats-new-entry"><p><strong>Command files.</strong> A sequence of Mapshaper commands can be written to a <code>.txt</code> file with <code>#</code> comments and no shell quoting, and run with <code>-run &lt;file&gt;</code> (or just <code>mapshaper commands.txt</code>). Command files can also be written in a shell-compatible way, if you want to be able to paste the commands into the terminal or add them to a shell script. In a future release, these files will also be runnable in the browser.</p>
+<div class="whats-new-entry"><p><strong>Undo/redo buttons.</strong> The web UI now has an undo/redo toolbar. Undo and redo were already supported in the geometry and attribute editing modes; the toolbar makes them more discoverable for users who didn&#39;t know the keyboard shortcuts (<strong>⌘Z</strong> / <strong>⌘⇧Z</strong>) existed.</p>
+</div><div class="whats-new-entry"><p><strong>Command files.</strong> A sequence of Mapshaper commands can be written to a <code>.txt</code> file with <code>#</code> comments and no shell quoting, and run with <code>-run &lt;file&gt;</code> (or just <code>mapshaper commands.txt</code>). Command files can also be written in a shell-compatible way, if you want to be able to paste the commands into the terminal or add them to a shell script. In a future release, these files will also be runnable in the browser.</p>
 <pre><code class="hljs language-bash">mapshaper build.txt
 </code></pre>
 <p>→ See <a href="/docs/reference.html#command-files">Command files</a> in the reference.</p>

package/www/docs/whats-new.html.md

@@ -11,6 +11,12 @@ This is a curated list of recently added features. For the full list of changes,
 
 <div class="whats-new-entry">
 
+**Undo/redo buttons.** The web UI now has an undo/redo toolbar. Undo and redo were already supported in the geometry and attribute editing modes; the toolbar makes them more discoverable for users who didn't know the keyboard shortcuts (**⌘Z** / **⌘⇧Z**) existed.
+
+</div>
+
+<div class="whats-new-entry">
+
 **Command files.** A sequence of Mapshaper commands can be written to a `.txt` file with `#` comments and no shell quoting, and run with `-run <file>` (or just `mapshaper commands.txt`). Command files can also be written in a shell-compatible way, if you want to be able to paste the commands into the terminal or add them to a shell script. In a future release, these files will also be runnable in the browser.
 
 ```bash

package/www/index.html

@@ -43,6 +43,14 @@
 	  <polygon points="8 14.5 13 19 13 4 3 4 3 19 8 14.5" fill="#30d4ef"/>
 	</svg>
 
+	<svg id="undo-icon" version="1.1" xmlns="http://www.w3.org/2000/svg" width="16" height="16" viewBox="0 0 16 16">
+		<path d="M1.5,8 L7,4.5 L7,7 C10,7 12,9 12,11 L12,13 L10,13 L10,11 C10,10 9,9 7,9 L7,11.5 Z"/>
+	</svg>
+
+	<svg id="redo-icon" version="1.1" xmlns="http://www.w3.org/2000/svg" width="16" height="16" viewBox="0 0 16 16">
+		<path d="M14.5,8 L9,4.5 L9,7 C6,7 4,9 4,11 L4,13 L6,13 L6,11 C6,10 7,9 9,9 L9,11.5 Z"/>
+	</svg>
+
 </div>
 
 <div class="page-header">
@@ -60,10 +68,17 @@
 	</div></div>
 	<div id="mode-buttons" class="page-header-buttons">
 		<!-- <span class="project-btn header-btn btn">Project</span><span class="separator"> -->
-		<span class="console-btn header-btn btn">Console</span><span class="display-btn header-btn btn">Display</span><span class="separator"></span><span class="separator"></span></span><span class="simplify-btn header-btn btn">Simplify</span><span class="separator"></span><span class="export-btn header-btn btn">Export</span>
+		<span class="console-btn header-btn btn">Console</span><span class="display-btn header-btn btn">Display</span><span class="separator"></span><span class="separator"></span></span><span class="simplify-btn header-btn btn">Simplify</span><span class="separator"></span><span class="export-btn header-btn btn">Export</span><span class="separator"></span><span id="header-menu-btn" class="header-btn btn" role="button" aria-label="More links" aria-haspopup="true" aria-expanded="false" tabindex="0"><svg viewBox="0 0 16 16" aria-hidden="true" width="16" height="14"><rect x="1" y="3" width="14" height="2"/><rect x="1" y="7" width="14" height="2"/><rect x="1" y="11" width="14" height="2"/></svg></span>
+		<div id="header-menu-dropdown" class="hidden" role="menu" aria-labelledby="header-menu-btn">
+			<a class="header-menu-item" href="/docs/" target="_blank" rel="noopener" role="menuitem">Docs</a>
+			<a class="header-menu-item" href="https://github.com/mbloch/mapshaper" target="_blank" rel="noopener" role="menuitem">GitHub</a>
+			<a class="header-menu-item survey-en-link" href="https://tally.so/r/44Njok" target="_blank" rel="noopener" role="menuitem">1-minute survey</a>
+			<a class="header-menu-item survey-zh-link" href="https://tally.so/r/vGx7KQ" target="_blank" rel="noopener" lang="zh-CN" style="display:none" role="menuitem">意见反馈</a>
+			<a class="header-menu-item header-menu-sponsor" href="sponsor.html" target="_blank" rel="noopener" role="menuitem"><svg viewBox="0 0 24 24" aria-hidden="true"><path d="M12 21.35l-1.45-1.32C5.4 15.36 2 12.28 2 8.5 2 5.42 4.42 3 7.5 3c1.74 0 3.41.81 4.5 2.09C13.09 3.81 14.76 3 16.5 3 19.58 3 22 5.42 22 8.5c0 3.78-3.4 6.86-8.55 11.54L12 21.35z"/></svg>Become a sponsor</a>
+		</div>
 	</div>
 	<div id="splash-buttons" class="page-header-buttons">
-		<a href="/docs/"><span id="wiki-btn" class="header-btn btn">Docs</span></a><span class="separator"></span><a href="https://github.com/mbloch/mapshaper"><span id="github-btn" class="header-btn btn">GitHub</span></a><span class="separator"></span><a id="survey-en-link" href="https://tally.so/r/44Njok" target="_blank" rel="noopener"><span id="survey-en-btn" class="header-btn btn">1-minute survey</span></a><a id="survey-zh-link" href="https://tally.so/r/vGx7KQ" target="_blank" rel="noopener" style="display:none"><span id="survey-zh-btn" class="header-btn btn" lang="zh-CN">意见反馈</span></a><span class="separator"></span><a href="sponsor.html"><span id="sponsor-btn" class="header-btn btn"><svg viewBox="0 0 24 24" aria-hidden="true"><path d="M12 21.35l-1.45-1.32C5.4 15.36 2 12.28 2 8.5 2 5.42 4.42 3 7.5 3c1.74 0 3.41.81 4.5 2.09C13.09 3.81 14.76 3 16.5 3 19.58 3 22 5.42 22 8.5c0 3.78-3.4 6.86-8.55 11.54L12 21.35z"/></svg> Become a sponsor</span></a>
+		<a href="/docs/"><span id="wiki-btn" class="header-btn btn">Docs</span></a><span class="separator"></span><a href="https://github.com/mbloch/mapshaper"><span id="github-btn" class="header-btn btn">GitHub</span></a><span class="separator"></span><a class="survey-en-link" href="https://tally.so/r/44Njok" target="_blank" rel="noopener"><span id="survey-en-btn" class="header-btn btn">1-minute survey</span></a><a class="survey-zh-link" href="https://tally.so/r/vGx7KQ" target="_blank" rel="noopener" style="display:none"><span id="survey-zh-btn" class="header-btn btn" lang="zh-CN">意见反馈</span></a><span class="separator"></span><a href="sponsor.html"><span id="sponsor-btn" class="header-btn btn"><svg viewBox="0 0 24 24" aria-hidden="true"><path d="M12 21.35l-1.45-1.32C5.4 15.36 2 12.28 2 8.5 2 5.42 4.42 3 7.5 3c1.74 0 3.41.81 4.5 2.09C13.09 3.81 14.76 3 16.5 3 19.58 3 22 5.42 22 8.5c0 3.78-3.4 6.86-8.55 11.54L12 21.35z"/></svg> Become a sponsor</span></a>
 	</div>
 </div>
 
@@ -351,10 +366,11 @@ encoding=big5</span>. Click to see all options.</div></div></div>
 		if (/^zh(-Hans)?-CN\b/i.test(langs[i])) isChina = true;
 	}
 	if (isChina) {
-		var zh = document.getElementById('survey-zh-link');
-		var en = document.getElementById('survey-en-link');
-		if (zh) zh.style.display = '';
-		if (en) en.style.display = 'none';
+		// Swap every copy of the survey link (splash bar + hamburger menu)
+		var zhLinks = document.querySelectorAll('.survey-zh-link');
+		var enLinks = document.querySelectorAll('.survey-en-link');
+		for (var j = 0; j < zhLinks.length; j++) zhLinks[j].style.display = '';
+		for (var k = 0; k < enLinks.length; k++) enLinks[k].style.display = 'none';
 	}
 })();
 </script>

package/www/llms-full.txt

@@ -63,6 +63,12 @@ This is a curated list of recently added features. For the full list of changes,
 
 <div class="whats-new-entry">
 
+**Undo/redo buttons.** The web UI now has an undo/redo toolbar. Undo and redo were already supported in the geometry and attribute editing modes; the toolbar makes them more discoverable for users who didn't know the keyboard shortcuts (**⌘Z** / **⌘⇧Z**) existed.
+
+</div>
+
+<div class="whats-new-entry">
+
 **Command files.** A sequence of Mapshaper commands can be written to a `.txt` file with `#` comments and no shell quoting, and run with `-run <file>` (or just `mapshaper commands.txt`). Command files can also be written in a shell-compatible way, if you want to be able to paste the commands into the terminal or add them to a shell script. In a future release, these files will also be runnable in the browser.
 
 ```bash
@@ -791,7 +797,7 @@ Apply a JavaScript expression to each feature in a layer. Data properties are av
 
 `target=`  Layer to target.
 
-The same expression syntax and execution context are used by `-each`, `-filter`, `-sort`, `-inspect`, `-split`, `-subdivide`, `-calc` (and `calc=` options on `-dissolve`, `-join`, etc.), `-style`, `-symbols`, and any `where=`, `weight=`, `radius=` or `bbox=` option. See [JavaScript expressions](/docs/guides/expressions.html.md) for the full reference: the available `this.*` properties for each geometry type, helper functions like `round()`, `sprintf()` and `format_dms()`, the `-calc` aggregation functions, the `A`/`B` pair context used by `-lines`, and common pitfalls. The [Basics](/docs/examples/basics.html.md) page has practical recipes that put expressions to work.
+The same expression syntax and execution context are used by all commands that support expressions. See [JavaScript expressions](/docs/guides/expressions.html.md) for the full reference. The [Basics](/docs/examples/basics.html.md) page has practical recipes that put expressions to work.
 
 **Examples**
 
@@ -2168,11 +2174,13 @@ Mapshaper offers three simplification methods, selectable as flags to `-simplify
 
 - **`dp`** &mdash; Douglas-Peucker (also known as Ramer–Douglas–Peucker). Guarantees that simplified lines stay within a fixed distance of the original. Good for stripping excess vertices to reduce file size, but tends to grow visible spikes at high simplification.
 - **`visvalingam`** &mdash; The Visvalingam algorithm. Iteratively removes the point that forms the smallest triangle with its two neighbors.
-- **`weighted_visvalingam`** (Mapshaper's default) &mdash; Visvalingam's effective-area algorithm with a custom weighting that underweights points at sharp angles, so they are removed earlier than in standard Visvalingam. The result is visibly smoother lines and fewer jagged spikes at high simplification. This method can be effective at generalizing very detailed source files, but be careful that it doesn't remove long, thin geographic features that you want to keep.
+- **`weighted_visvalingam`** (Mapshaper's default) &mdash; Visvalingam's effective-area algorithm with a custom weighting that underweights points at sharp angles, so they are removed earlier than in standard Visvalingam. The result is visibly smoother lines and fewer jagged spikes at high simplification.
+
+Weighted Visvalingam is the default because it has proven to be versatile and effective at reducing detail in highly detailed source data. This method can be effective at generalizing very detailed source files, but be careful that it doesn't remove long, thin geographic features that you want to keep.You can control the amount of weighting used by Weighted Visvalingam with the `weighting=` option (default is 0.7).
+
+If you are only interested in minimizing file size, Douglas-Peucker is generally the better choice.
 
-Weighted Visvalingam is the default because it has proven to be versatile and effective at reducing detail in highly detailed source data. If you are only interested in minimizing file size, Douglas-Peucker is generally the better choice.
 
-You can control the amount of weighting used by Weighted Visvalingam with the `weighting=` option (default is 0.7).
 
 **Figures**
 
@@ -2826,6 +2834,14 @@ We'll use two source files:
 - A county boundary file from the California Open Data Portal &mdash; or, in this case, a [version clipped to the shoreline](https://geodata.lib.berkeley.edu/catalog/ark28722-s7hs4j) from UC Berkeley's Geo Data Commons. The shoreline-clipped version reads more naturally on a map than the legal-boundary version, which extends into the bay.
 - A statewide [places boundary file](https://geodata.lib.berkeley.edu/catalog/ark28722-s7bp4z) for city boundaries.
 
+The legal county boundaries from the Census TIGER files extend straight across the water &mdash; San Francisco even reaches out to include the Farallon Islands:
+
+![Bay Area counties from the Census TIGER file, with boundaries cutting across the bay and extending offshore](/docs/images/tiger-counties.png)
+
+The Berkeley library's version is clipped to the shoreline, so the bay shows as empty space between the counties:
+
+![The same Bay Area counties, with each polygon clipped to the coastline so the bay is visible between them](/docs/images/cal-counties.png)
+
 Download both as `.zip` files.
 
 ## Open them in Mapshaper
@@ -3009,7 +3025,6 @@ A few things worth knowing across all formats:
 
 - **Auto-detection by extension.** You usually don't need to tell Mapshaper what format a file is &mdash; it picks the right reader from the file extension. Use `format=` on `-i` or `-o` to override.
 - **TopoJSON is the only interchange format that preserves topology** in the file itself. Topology-aware operations like [`-dissolve`](/docs/reference.html.md#-dissolve), [`-clean`](/docs/reference.html.md#-clean) and [`-simplify`](/docs/reference.html.md#-simplify) work correctly regardless of the input format, but only TopoJSON keeps shared boundaries between adjacent polygons from being duplicated on disk. (Mapshaper's own [`.msx`](/docs/formats/snapshot.html.md) snapshots also preserve topology, but they're not readable by other tools.)
-- **Most formats are single-layer per file.** Multi-layer GeoJSON, Shapefile and FlatGeobuf datasets are conventionally split across multiple files (in the same directory on the CLI; selected together or zipped in the [web app](/docs/essentials/web-app.html.md)); TopoJSON, GeoPackage and KML can hold many layers in one file.
 - **Encoding.** The `encoding=` option on `-i` and `-o` applies to Shapefile, DBF and CSV/TSV i/o (UTF-8 is the default) &mdash; the other formats are UTF-8-only.
 
 ---
@@ -3285,7 +3300,6 @@ There are no FlatGeobuf-specific `-o` options. The format honors the general fla
 
 ### Practical notes
 
-- FlatGeobuf is single-layer per file. Use [GeoPackage](/docs/formats/geopackage.html.md) or [TopoJSON](/docs/formats/topojson.html.md) when you need to package multiple layers in one file.
 - Mapshaper reads CRS metadata from the file header when it's encoded as an EPSG code. WKT2-only definitions can't be parsed and produce an "Unable to import WKT2 CRS from FlatGeobuf" warning &mdash; the layer comes in without a CRS.
 - On output, Mapshaper embeds an EPSG code in the FlatGeobuf header whenever it can derive one from the source: a round-tripped FlatGeobuf or GeoPackage CRS, an `epsg:NNNN` string passed to `-proj`, an `AUTHORITY["EPSG", N]` clause in a Shapefile `.prj`, or any encoding of WGS-84 or Web Mercator (which covers most GeoJSON, CSV-with-lat/lon and `-proj wgs84`/`-proj webmercator` outputs).
 - Mapshaper cannot yet convert an arbitrary proj4 definition (such as a custom Albers projection set with `-proj +proj=aea ...`) to an EPSG code. In that case the file is written with no CRS in the header and a warning is printed: *"Wrote `foo.fgb` without a CRS in the FlatGeobuf header..."*. Re-run the file through `ogr2ogr` if you need the CRS embedded for downstream tools.
@@ -3605,7 +3619,7 @@ The ribbon icon in the layer panel opens the **snapshot menu**. From there you c
 
 # Basics
 
-Short Mapshaper recipes for common GIS tasks. The filenames and field names are illustrative &mdash; substitute your own. Most recipes also work in the [web app's](/docs/essentials/web-app.html.md) console: drop the leading `mapshaper` and the input filename, since the GUI already has the layer loaded.
+Short Mapshaper examples for common tasks. The filenames and field names are illustrative &mdash; substitute your own. Most recipes also work in the [web app's](/docs/essentials/web-app.html.md) console: drop the leading `mapshaper` and the input filename; the GUI should already your data loaded.
 
 > Looking for the syntax of a particular command or option? See the [command reference](/docs/reference.html.md). For the JS expression context used by `-each`, `-filter`, `calc=` and other commands, see [JavaScript expressions](/docs/guides/expressions.html.md).
 
@@ -3968,7 +3982,6 @@ mapshaper-xl 16gb counties_5m.shp -simplify 10% -o counties_5m.topojson
 
 - [Command reference](/docs/reference.html.md) &mdash; every command and option
 - [JavaScript expressions](/docs/guides/expressions.html.md) &mdash; the syntax and context used by `-each`, `-filter`, `calc=`, etc.
-- [Guides](/docs/guides/index.html.md) &mdash; longer-form walk-throughs of simplification, topology cleaning, and more
 
 ---
 

package/www/mapshaper-gui.js

@@ -5655,6 +5655,56 @@
     }
   }
 
+  // Hamburger menu in the top-right of the header. After the user starts
+  // editing, the splash bar (Docs / GitHub / Survey / Sponsor) is hidden by
+  // gui.mjs; this menu is the post-edit replacement, exposing the same links
+  // from a single button so the editing controls don't have to share the row.
+
+
+  function HeaderMenu() {
+    var btn = El('#header-menu-btn');
+    var dropdown = El('#header-menu-dropdown');
+    if (!btn.node() || !dropdown.node()) return; // markup missing; nothing to do
+
+    var open = false;
+
+    function setOpen(state) {
+      if (state === open) return;
+      open = state;
+      dropdown.classed('hidden', !open);
+      btn.attr('aria-expanded', open ? 'true' : 'false');
+    }
+
+    btn.on('click', function(e) {
+      e.stopPropagation();
+      setOpen(!open);
+    });
+
+    // Keyboard activation matches button semantics for the role="button" span.
+    btn.on('keydown', function(e) {
+      if (e.key === 'Enter' || e.key === ' ') {
+        e.preventDefault();
+        setOpen(!open);
+      }
+    });
+
+    // Outside click closes the menu. Clicks on menu items also close it (they
+    // navigate or open in a new tab; either way the menu shouldn't linger).
+    document.addEventListener('click', function(e) {
+      if (!open) return;
+      var target = e.target;
+      if (btn.node().contains(target)) return;
+      setOpen(false);
+    });
+
+    document.addEventListener('keydown', function(e) {
+      if (open && e.key === 'Escape') {
+        setOpen(false);
+        btn.node().focus();
+      }
+    });
+  }
+
   function SessionHistory(gui) {
     var commands = [];
     // index of first command after the last "save" boundary; commands at indices
@@ -5993,6 +6043,15 @@
 
     this.clear = function() {
       reset();
+      fireHistoryChange();
+    };
+
+    this.canUndo = function() {
+      return history.length - offset > 0;
+    };
+
+    this.canRedo = function() {
+      return offset > 0;
     };
 
     function addHistoryState(undo, redo) {
@@ -6001,6 +6060,14 @@
         offset = 0;
       }
       history.push({undo, redo});
+      fireHistoryChange();
+    }
+
+    function fireHistoryChange() {
+      gui.dispatchEvent('history_change', {
+        canUndo: history.length - offset > 0,
+        canRedo: offset > 0
+      });
     }
 
     this.undo = function() {
@@ -6013,6 +6080,7 @@
         item.undo();
         gui.dispatchEvent('undo_redo_post', {type: 'undo'});
         gui.dispatchEvent('map-needs-refresh');
+        fireHistoryChange();
       }
     };
 
@@ -6024,6 +6092,7 @@
       item.redo();
       gui.dispatchEvent('undo_redo_post', {type: 'redo'});
       gui.dispatchEvent('map-needs-refresh');
+      fireHistoryChange();
     };
 
     function getHistoryItem() {
@@ -6337,6 +6406,10 @@
       return ['info', 'selection', 'data', 'box', 'labels', 'edit_points', 'rectangles'].includes(mode);
     };
 
+    this.modeSupportsUndo = function(mode) {
+      return ['data', 'labels', 'edit_points', 'edit_lines', 'edit_polygons', 'vertices', 'rectangles'].includes(mode);
+    };
+
     this.getMode = getInteractionMode;
 
     this.setMode = function(mode) {
@@ -6479,6 +6552,214 @@
     }
   }
 
+  // A reusable floating toolbar anchored at the bottom-center of the map area.
+  //
+  // Multiple toolbars stack vertically inside a shared container, so additional
+  // per-mode toolbars (e.g. feature styling) can coexist with the edit toolbar.
+  //
+  // The DOM is structured to leave room for a future drag handle without
+  // requiring rework: the toolbar element is a flex row with a content slot,
+  // and a sibling drag-handle slot can be added later.
+  //
+  // Constructor options:
+  //   name:       optional CSS class added to the toolbar element
+  //   transition: ms for the show/hide transition (default 150)
+  //
+  // API:
+  //   toolbar.addButton(iconRef, opts) -> ToolbarButton
+  //   toolbar.addSeparator()
+  //   toolbar.show()
+  //   toolbar.hide()
+  //   toolbar.visible()
+  //   toolbar.node()
+
+  function FloatingToolbar(gui, opts) {
+    opts = opts || {};
+    var transitionMs = opts.transition || 150;
+    var root = gui.container.findChild('.mshp-main-map');
+    var stack = root.findChild('.floating-toolbar-stack');
+    if (!stack) {
+      stack = El('div').addClass('floating-toolbar-stack').appendTo(root);
+    }
+    var el = El('div').addClass('floating-toolbar');
+    if (opts.name) el.addClass(opts.name);
+    var content = El('div').addClass('floating-toolbar-content').appendTo(el);
+    var visible = false;
+    var hideTimer = null;
+
+    el.appendTo(stack);
+    el.css('display', 'none');
+
+    // Hide when this gui instance becomes inactive (e.g. multi-instance mode)
+    gui.on('active', updateVisibility);
+    gui.on('inactive', updateVisibility);
+
+    this.addButton = function(iconRef, btnOpts) {
+      return new ToolbarButton(content, iconRef, btnOpts || {});
+    };
+
+    this.addSeparator = function() {
+      return El('div').addClass('floating-toolbar-separator').appendTo(content);
+    };
+
+    this.show = function() {
+      if (visible) return;
+      visible = true;
+      updateVisibility();
+    };
+
+    this.hide = function() {
+      if (!visible) return;
+      visible = false;
+      updateVisibility();
+    };
+
+    this.visible = function() {
+      return visible;
+    };
+
+    this.node = function() {
+      return el.node();
+    };
+
+    function updateVisibility() {
+      var shouldShow = visible && GUI.isActiveInstance(gui);
+      if (shouldShow) {
+        clearTimeout(hideTimer);
+        hideTimer = null;
+        el.css('display', 'flex');
+        // wait one frame so the browser registers the initial state before
+        // the transition kicks in
+        requestAnimationFrame(function() {
+          el.addClass('visible');
+        });
+      } else {
+        el.removeClass('visible');
+        // wait for the transition to finish before hiding completely
+        clearTimeout(hideTimer);
+        hideTimer = setTimeout(function() {
+          if (!(visible && GUI.isActiveInstance(gui))) {
+            el.css('display', 'none');
+          }
+        }, transitionMs);
+      }
+    }
+  }
+
+  function ToolbarButton(parent, iconRef, opts) {
+    var btn = El('div').addClass('floating-toolbar-btn').appendTo(parent);
+    if (iconRef) {
+      var iconNode = El('body').findChild(iconRef);
+      if (iconNode) {
+        var icon = iconNode.node().cloneNode(true);
+        if (icon.hasAttribute('id')) icon.removeAttribute('id');
+        btn.node().appendChild(icon);
+      }
+    }
+    var enabled = true;
+    var clickHandlers = [];
+
+    if (opts.tooltip) setTooltip(opts.tooltip);
+
+    // Block native dblclick to avoid the map's double-click zoom
+    btn.on('dblclick', function(e) { e.stopPropagation(); });
+
+    btn.on('click', function(e) {
+      if (!enabled) return;
+      for (var i = 0; i < clickHandlers.length; i++) {
+        clickHandlers[i](e);
+      }
+    });
+
+    this.on = function(event, fn) {
+      if (event == 'click') {
+        clickHandlers.push(fn);
+      } else {
+        btn.on(event, fn);
+      }
+      return this;
+    };
+
+    this.enable = function() { return this.setEnabled(true); };
+    this.disable = function() { return this.setEnabled(false); };
+
+    this.setEnabled = function(b) {
+      enabled = !!b;
+      btn.classed('disabled', !enabled);
+      return this;
+    };
+
+    this.setTooltip = setTooltip;
+
+    this.node = function() {
+      return btn.node();
+    };
+
+    function setTooltip(text) {
+      btn.attr('data-tooltip', text);
+    }
+  }
+
+  // Floating toolbar that exposes undo/redo while the user is in an editing
+  // interaction mode. The toolbar is the first consumer of FloatingToolbar;
+  // future per-mode toolbars (e.g. feature styling) can follow the same pattern.
+
+  function EditToolbar(gui) {
+    var toolbar = new FloatingToolbar(gui, { name: 'edit-toolbar' });
+    var isMac = navigator.userAgent.includes('Mac');
+    var modKey = isMac ? '\u2318' : 'Ctrl+';
+    var shiftKey = isMac ? '\u21e7' : 'Shift+';
+
+    var undoBtn = toolbar.addButton('#undo-icon', {
+      tooltip: 'Undo (' + modKey + 'Z)'
+    }).on('click', function() {
+      gui.undo.undo();
+    });
+
+    var redoBtn = toolbar.addButton('#redo-icon', {
+      tooltip: 'Redo (' + shiftKey + modKey + 'Z)'
+    }).on('click', function() {
+      gui.undo.redo();
+    });
+
+    updateButtons();
+
+    gui.on('interaction_mode_change', function() {
+      updateVisibility();
+      // history is cleared on mode change; refresh button states next tick
+      updateButtons();
+    });
+
+    gui.on('history_change', function(e) {
+      undoBtn.setEnabled(!!e.canUndo);
+      redoBtn.setEnabled(!!e.canRedo);
+      // Visibility may also depend on history (e.g. attribute edits via popup
+      // happen in modes that don't otherwise support undo).
+      updateVisibility();
+    });
+
+    updateVisibility();
+
+    function updateVisibility() {
+      if (!gui.interaction) {
+        toolbar.hide();
+        return;
+      }
+      var mode = gui.interaction.getMode();
+      var hasHistory = gui.undo.canUndo() || gui.undo.canRedo();
+      if (gui.interaction.modeSupportsUndo(mode) || hasHistory) {
+        toolbar.show();
+      } else {
+        toolbar.hide();
+      }
+    }
+
+    function updateButtons() {
+      undoBtn.setEnabled(gui.undo.canUndo());
+      redoBtn.setEnabled(gui.undo.canRedo());
+    }
+  }
+
   function Model(gui) {
     var self = new internal.Catalog();
     var deleteLayer = self.deleteLayer;
@@ -9576,6 +9857,10 @@
 
     box.setDataCoords = function(bbox) {
       boxCoords = bbox;
+      // Box is being placed programmatically (e.g. around a pinned rectangle);
+      // enable pointer events on the handles so they can be dragged. Without
+      // this, mousedowns fall through to the map and trigger pan.
+      el.classed('hittable', true);
       redraw();
     };
 
@@ -9599,6 +9884,7 @@
     // remove the current box (if any)
     box.hide = function() {
       el.hide();
+      el.classed('hittable', false);
       boxCoords = null;
       _visible = false;
       clickStartPoint = null;
@@ -10949,8 +11235,8 @@
     function showInstructions() {
       var isMac = navigator.userAgent.includes('Mac');
       var symbol = isMac ? '⌘' : '^';
-      var msg = `Instructions: Click on the map to add points. Move points by dragging. Type ${symbol}Z/${symbol}Y to undo/redo.`;
-      alert = showPopupAlert(msg, null, { non_blocking: true, max_width: '360px'});
+      var msg = `Instructions: click on the map to add points. Move points by dragging.`;
+      alert = showPopupAlert(msg, null, { non_blocking: true, max_width: '290px'});
     }
 
     gui.on('interaction_mode_change', function(e) {
@@ -11167,9 +11453,9 @@
     function showInstructions() {
       var isMac = navigator.userAgent.includes('Mac');
       var undoKey = isMac ? '⌘' : '^';
-      var msg = `Instructions: click to start a path, click or drag to keep drawing. Drag vertices to reshape a path. Type ${undoKey}Z/${undoKey}Y to undo/redo.`;
+      var msg = `Instructions: click to start a path, click or drag to keep drawing. Drag vertices to reshape a path.`;
         alert = showPopupAlert(msg, null, {
-          non_blocking: true, max_width: '388px'});
+          non_blocking: true, max_width: '350px'});
     }
 
     function hideInstructions() {
@@ -14631,6 +14917,7 @@ GUI and setting the size and crop of SVG output.</p><div><input type="text" clas
       new SessionSnapshots(gui);
     }
     gui.interaction = new InteractionMode(gui);
+    gui.editToolbar = new EditToolbar(gui);
 
     gui.showProgressMessage = function(msg) {
       if (!gui.progressMessage) {
@@ -14755,6 +15042,7 @@ GUI and setting the size and crop of SVG output.</p><div><input type="text" clas
     new ImportControl(gui, importOpts);
     new ExportControl(gui);
     new LayerControl(gui);
+    HeaderMenu();
     gui.console = new Console(gui);
 
     startEditing = function() {};

package/www/mapshaper.js

@@ -52127,7 +52127,7 @@ ${svg}
     });
   }
 
-  var version = "0.7.1";
+  var version = "0.7.2";
 
   // Parse command line args into commands and run them
   // Function takes an optional Node-style callback. A Promise is returned if no callback is given.

package/www/page.css

@@ -170,7 +170,7 @@ body.map-view {
 	position: absolute;
 	top: 0px;
 	right: 0px;
-	margin: 0 6px 3px 0;	
+	margin: 0 3px 3px 0;
 }
 
 .btn.header-btn {
@@ -207,6 +207,63 @@ body.map-view {
 	vertical-align: -1px;
 }
 
+/* --- Hamburger menu (post-edit overflow links) --- */
+
+#header-menu-btn {
+	cursor: pointer;
+	padding: 8px 7px 4px 7px;
+	user-select: none;
+	/* All header buttons are 29px tall, so top-align the hamburger to keep its
+	   row baseline-neutral. Without this, the SVG-only button (no text) makes
+	   its inline-block baseline = bottom edge, which drags the surrounding
+	   text-containing buttons down to match. */
+	vertical-align: top;
+}
+
+#header-menu-btn svg {
+	display: block;
+	fill: currentColor;
+}
+
+#header-menu-dropdown {
+	position: absolute;
+	top: 30px;
+	right: 0;
+	min-width: 180px;
+	background-color: #fff;
+	color: #333;
+	border: 1px solid #ccc;
+	border-radius: 3px;
+	box-shadow: 0 2px 6px rgba(0, 0, 0, 0.15);
+	padding: 4px 0;
+	z-index: 50;
+}
+
+.header-menu-item {
+	display: block;
+	padding: 4px 14px;
+	color: #333;
+	font-size: 14px;
+	line-height: 1.3;
+	text-decoration: none;
+	white-space: nowrap;
+}
+
+.header-menu-item:hover,
+.header-menu-item:focus {
+	background-color: #e6f7ff;
+	color: #1A6A96;
+	outline: none;
+}
+
+.header-menu-item.header-menu-sponsor svg {
+	width: 12px;
+	height: 12px;
+	fill: #d63384;
+	vertical-align: -1px;
+	margin-right: 6px;
+}
+
 .separator {
 	border-left: 1px solid white;
 	height: 10px;
@@ -427,6 +484,14 @@ div.alert-box {
 	margin: 0 0 5px 0;
 }
 
+input[type=text]:focus,
+input[type=number]:focus,
+textarea:focus {
+	outline: none;
+	border-color: #d3aa00;
+	box-shadow: 0 0 0 2px rgba(212, 168, 0, 0.4);
+}
+
 ::placeholder {
 	color: #aaa;
 	opacity: 1;
@@ -495,13 +560,6 @@ div.alert-box {
 	padding-left: 12px;
 }
 
-.info-box,.popup {
-	border-radius: 9px;
-	border: 1px solid #d5d5d5;
-	box-shadow: 0 1px 7px rgba(0,0,0,0.18);
-	background-color: #fff;
-}
-
 .contextmenu {
 	position: absolute;
 	border-radius: 6px;
@@ -518,6 +576,12 @@ div.alert-box {
 	padding: 6px;
 }
 
+.info-box,.popup {
+	border-radius: 11px;
+	border: 1px solid #d5d5d5;
+	box-shadow: 0 1px 7px rgba(0,0,0,0.18);
+	background-color: #fff;
+}
 
 .info-box {
 	min-width: 230px;
@@ -525,7 +589,8 @@ div.alert-box {
 	text-align: left;
 	margin-top: 12px;
 	margin-right: 20px;
-	padding: 12px 16px 12px 18px;
+	/* padding: 12px 16px 12px 18px; */
+	padding: 15px 17px 13px 19px;
 	vertical-align: top;
 	display: inline-block;
 	/* border: 1px solid #aaa; */
@@ -575,7 +640,7 @@ div.alert-box {
 .info-box p {
 	white-space: pre-line;
 	margin: 0 0 6px 0;
-	line-height: 1.2;
+	line-height: 1.25;
 	/* font-size: 90%; */
 }
 
@@ -1552,6 +1617,119 @@ body.pan.panning .map-layers:not(.drawing) {
 	cursor: default;
 }
 
+/* --- FLOATING TOOLBAR --- */
+
+/*
+ * Anchored at bottom-center of the map area. Multiple toolbars stack
+ * vertically (newest on top). Designed to host buttons and other small
+ * controls; the inner content slot leaves room for a future drag handle.
+ */
+
+.floating-toolbar-stack {
+	position: absolute;
+	z-index: 25;
+	bottom: 24px;
+	left: 50%;
+	transform: translateX(-50%);
+	display: flex;
+	flex-direction: column-reverse;
+	align-items: center;
+	gap: 8px;
+	pointer-events: none;
+}
+
+.floating-toolbar {
+	pointer-events: auto;
+	display: flex;
+	align-items: center;
+	background-color: rgba(255, 255, 255, 0.96);
+	border: 1px solid #ddd;
+	border-radius: 8px;
+	box-shadow: 0 2px 12px rgba(0, 0, 0, 0.15);
+	padding: 4px;
+	opacity: 0;
+	transform: translateY(6px);
+	transition: opacity 150ms ease, transform 150ms ease;
+}
+
+.floating-toolbar.visible {
+	opacity: 1;
+	transform: translateY(0);
+}
+
+.floating-toolbar-content {
+	display: flex;
+	align-items: center;
+	gap: 0;
+}
+
+.floating-toolbar-separator {
+	width: 1px;
+	height: 18px;
+	margin: 0 4px;
+	background-color: #ddd;
+}
+
+.floating-toolbar-btn {
+	position: relative;
+	display: flex;
+	align-items: center;
+	justify-content: center;
+	width: 28px;
+	height: 28px;
+	border-radius: 5px;
+	cursor: pointer;
+	user-select: none;
+}
+
+.floating-toolbar-btn svg {
+	width: 24px;
+	height: 24px;
+}
+
+.floating-toolbar-btn svg * {
+	fill: #1385B7;
+	transition: fill 100ms ease;
+}
+
+.floating-toolbar-btn:hover:not(.disabled) {
+	background-color: #e6f7ff;
+}
+
+.floating-toolbar-btn:hover:not(.disabled) svg * {
+	fill: #166689;
+}
+
+.floating-toolbar-btn:active:not(.disabled) {
+	background-color: #cdebf9;
+}
+
+.floating-toolbar-btn.disabled {
+	cursor: default;
+}
+
+.floating-toolbar-btn.disabled svg * {
+	fill: #b8c4ca;
+}
+
+/* Tooltip shown above the button on hover */
+.floating-toolbar-btn[data-tooltip]:hover:not(.disabled)::after {
+	content: attr(data-tooltip);
+	position: absolute;
+	bottom: calc(100% + 8px);
+	left: 50%;
+	transform: translateX(-50%);
+	background-color: rgba(40, 40, 40, 0.92);
+	color: #fff;
+	font-size: 11px;
+	line-height: 1;
+	white-space: nowrap;
+	padding: 5px 7px;
+	border-radius: 4px;
+	pointer-events: none;
+	z-index: 1;
+}
+
 .zoom-box {
 	position: absolute;
 	border: 1px solid #cc6acc;