From a lake to a stack
How do I find a lake, fetch its map and cut it as sheets?
A real lake - or a town on the water - cut from a real map. You find it by name, the studio fetches its map and its depth once, and then it cuts the land and the water as a registered stack of sheets, in one of three styles. In Lake Topo the front sheet is the land, with every road round the lake scored into it, its towns, route numbers and neighbouring lakes named, the lake's name in an engraved title block and a nautical compass with its latitude and longitude, bottom right or wherever you drag it; under it the water steps down, a sheet per depth step, painted from light to dark; and each of the map's road bridges is part of that front sheet, wood across the water with its road scored across it. In City Lattice and Lattice + Depth the front sheet is the streets themselves, cut as a raised lattice with the bridges in it, the map's names engraved on small solid tags of it - each road name along its own street - and Lake Topo's compass on a solid plate of it; the land shows through the blocks between the streets, and the water is behind - one colour, or stepping down by depth. The sheets are glued together by their outside edges, marks hidden under each sheet show where the next one goes, and the design is made in up to three sizes for your laser bed.
Everything after the fetch - every setting, every build and every download - works from the map and the depth the lake keeps, and is free to redo.
The whole thing in one paragraph
One search, one download, then arithmetic. The search reads one country's list of named lakes and reservoirs - or, for a map of a town, its towns, cities and villages: in the United States the U.S. Geological Survey's, for one state, and in every other country GeoNames'. Choosing a result starts a piece of that lake or place. Fetch the map downloads the lake's shoreline - from USGS in the United States, from OpenStreetMap everywhere else - and the land, roads and other water round it from OpenStreetMap, for the area your frame shows, and in the US asks the state and NOAA depth surveys that cover the lake for its depth; for a place, every bit of water comes from OpenStreetMap. Build Sheets fits the lake into the frame, settles the style, lays the streets out as a lattice when the style has one, splits the water into colours at the depth steps you chose, cuts the land sheet with the water as its opening, burns the roads, names, title and compass into it, cuts a sheet for every depth step under it, adds the marks that line the sheets up, checks every sheet, and draws the paint guide and the back label.
The four steps
The strip under the lake bar is the way through, and each step changes what the centre shows.
- 1Find the Lake
Choose a country - and in the United States a state - then pick the lake from the lists: County (outside the US, Region) lists every one with how many lakes it has, and Lake every lake in the one you chose, A to Z; choosing one shows it under the lists, and Start this lake starts the piece. Or press Type the name instead and start typing the lake's name in Lake or reservoir name: from the second letter a list of the lakes that match appears under it and narrows with each letter you type, so you choose yours from the list rather than typing it all (Search and Enter search at once). Each result shows its county and state, or outside the US its region and country, and a US lake its area. Choosing one starts a new piece of that lake, called by its name; a lake already open stays exactly as it is, in the list. For a map of a town or city, set Look for to Place before you search; the step then reads Find the Place - see Framing a place.
- 2Map
Set the frame, then Fetch the map. The fetch also finds the lake's depth, and the Depth section says which survey it chose. The centre shows the area that was fetched, with the piece outlined on it and - in light blue - where the depth data reaches and its contour lines. If you make the frame bigger or add padding afterwards, the map can stop covering it: the badge says frame past the map · fetch again, and pressing it - or Fetch again - downloads the larger area. For a place the step's note reads Fetch its streets and water.
- 3Build Sheets
Cut the sheets: the Small, which is your design, and - when you want them - the Medium and Large made from it for your laser bed. The centre shows the Small stacked, exploded and in 3D, coloured as it will be painted, with the map beside it to compare.
- 4Check & Export
One sheet as it will be cut, in its laser colours, and the paint guide. The check and the download are here.
The pane on the left follows the same steps, in three numbered sections: Find the Lake (or the Place), Map - the frame and the fetch - and Build. Moving to a step opens its section and folds the others, and any section opens or folds by its heading. Build holds the sheets once there are some - a row for each, front first: click one to see it as cut, its eye hides it in the views, and its arrow downloads its SVG, with combined above them for the file of all of them - then every setting the build reads, under Before you build, and the paint, under After it is built.
Finding the lake
Country starts on the United States, or the country you searched last. In the US the search needs a state because lake names repeat: there are dozens of Mud Lakes in Michigan alone. It reads that state's list once and keeps it, so a second search is quick. For any other country the State box is hidden and the search reads that country's list from GeoNames, the free world gazetteer, once, and keeps it. Its results name the region they are in - "Taupo, Waikato Region, New Zealand" - and give no area. Choosing a lake outside the US starts a piece of it like a US lake, with its depths in metres unless you chose feet on a lake before (see Lakes outside the US). GeoNames lists the larger lakes of most countries but misses many small ones: search for a town on the lake with Look for Place instead - its map takes every bit of water in the frame, the lake included. It matches the start of each word, so "gun" finds Gun Lake and "big star" finds Big Star Lake. The list shows the best 50 matches - exact names first - so with a common name, type another letter or word to bring yours into it. The first search of a country can take a few seconds while its list is downloaded; after that each letter answers quickly. A lake search lists only lakes and reservoirs. Whether a lake has depth data is known only once its map is fetched, so the search results do not say.
Choosing from the lists. Once the country - and in the US the state - is chosen, County lists every county in the state, A to Z, with how many lakes are filed under it - "Barry (156)" - and Lake then lists every one of them, A to Z, so you can find a lake without knowing how its name is spelt. Outside the US the first list is Region, the country's regions, and a lake is listed under the region of its nearest town: GeoNames keeps its towns' regions better than its lakes', so Lake Taupo is under Waikato Region, where a New Zealander looks for it, rather than nowhere. A country with a single region skips straight to Lake. Where two lakes in the list have the same name, each is followed by its latitude and longitude. A county or region with more than a thousand - Quebec has over 50,000 - adds a Names list that takes them a thousand at a time, each part named by its first and last lake, "Lac Adler – Lac Annabel". Choosing a lake does not start a piece by itself - a list changes with the arrow keys, and starting a piece can cost a credit: it appears right under the lists, with its area in the US, and Start this lake starts the piece. With Look for Place the lists are of towns and cities instead, and the button is Start this town.
Typing the name instead. The name box is folded away while the lists can be used: Type the name instead, under them, opens it. It is there for a lake whose name you know: the search matches the start of each word, so a few letters find it without going through the county. The lists and the search read the same names, so a lake missing from one is missing from the other. In the Windows app without a licence key there are no lists, and the box shows from the start.
Look for Place searches the same state's towns, cities and villages instead - the places USGS lists as populated places - for a piece like a city tile, its streets raised over the river. The name box is then Town or city name, and a result shows its county and the word "place", with no area: "Louisville" in Kentucky finds nothing as a lake, and as a place lists Louisville (Jefferson County) first. Choosing it starts a piece titled with the place's name and subtitled with its state - Louisville over Kentucky - and while it is open the first section is called Place and its card says "a place" where a lake's gives its area. Rivers are not a search of their own, because USGS files a river at its mouth - the Ohio's is 329 km from Louisville; search for the town and the river comes with it. See Framing a place.
A lake on a state line is filed under one state only, and not always the one you would guess - try the other. The subtitle starts as the state it is filed under; change it under Engraving if that is not what the piece should say.
A piece is one lake - or, for a city map, one place. The frame is fitted to the lake you chose - you can drag the piece off its middle afterwards, see Frame - and its depth is that lake's alone: other water in the frame is cut, and named where there is room, but in the shallowest colour, with no depth steps of its own. So a lake's piece is never several lakes in depth: the five Great Lakes together, say, is not something the studio makes, and each is a piece of its own. A city map's water is all the place's, so there Stylized depth - an estimate - steps down from every shore in it; see Framing a place.
Fetching the map
The search and the fetch are the only steps that use the internet. The fetch takes the lake's outline from USGS's hydrography service - outside the US, from OpenStreetMap, as Lakes outside the US explains - OpenStreetMap's land, roads and water from OpenFreeMap's map tiles, for the window your frame shows plus a margin all round, and the lake's depth from the depth services below. The bar in the pane says what it is doing; Cancel stops it at its next step, and a fetch that is stopped or fails saves nothing - the map and the depth you had stay.
The map and the depth are kept with the lake. Building never downloads anything, and neither does the download. What the studio downloads is also kept on the server, apart from your account - the map for up to 30 days, the depth for up to 90 - so fetching the same area again soon is quicker. Importing a survey and Stylized depth download nothing more, but both need the lake's map first, because they are cut to its shoreline: fetch it once, then choose them.
Close the tab while it fetches and nothing is lost: open the lake again and the studio waits for the same fetch.
One map downloads at a time for each account. Pressing Fetch the map, Fetch again or use this on a survey while another of your lakes - or this one - is still downloading is refused, and changes nothing: "A map is already downloading for this account. Wait for it to finish, then try again." Importing a survey is not held up by it.
A place has no lake to outline, so its fetch asks USGS for nothing: it takes the streets and every bit of water in the area - the river, lakes, ponds and reservoirs - from the same OpenStreetMap tiles, leaving out swimming pools, names each water that has a name, and asks no depth service. Its credits are OpenStreetMap's and, for the place's name and point, the USGS gazetteer's - or, outside the US, GeoNames'. A frame with no water in it at all is refused - "There is no water in this frame." - so move or widen it; the map you had stays.
Lakes outside the US
USGS outlines only American lakes, so outside the US the lake's outline comes from OpenStreetMap, the same map as its land and roads. The fetch first looks at a small piece of the map round the point GeoNames gives for the lake and takes the water there - or, when the point is on the shore, the nearest lake within a kilometre - widening the look a few times for a large lake. It frames the map on that outline, downloads the map as for any lake, and then takes the lake's outline again at the map's full detail. Lake Taupō, over 600 km², is found this way, and so is Lake Louise in Alberta, under 1 km². The lake's name on the map is OpenStreetMap's, so it may differ from the search's - "Lake Taupō" with its macron.
A lake too big to find this way is refused - "Lake Taupo is too big to outline from OpenStreetMap's map tiles." - and a point with no lake near it says "OpenStreetMap has no lake at ...'s point."; in both cases search for a town on its shore under Place, whose map takes all the water in the frame. Nothing is saved, and deleting the lake before its map has arrived gives its credits back, as for any lake.
The depth services are all American - the state surveys and NOAA's - so none is asked about a lake abroad, and its Depth card offers Stylized depth or importing a survey file of your own, which works for any lake. A new piece of a lake outside the US starts in metres; Units still switches it to feet. Its credits are OpenStreetMap's and GeoNames', with no USGS line.
Where the depth comes from
The Depth section, under the frame, says where the lake's depth comes from and lets you choose. Its card names the survey in use, the spacing of its lines (for Lake Harriet, "5 ft to 20 ft, then 10 ft"), the deepest water, the date of the survey when it gives one, how much of the lake it leaves without a depth, and its credit.
There are four choices:
- Survey - a lake survey from a state or from NOAA. The fetch asks every service that covers the lake, keeps the best one's depths, and lists them all, best first. A state's survey of the lake ranks above NOAA's charts, and a fuller one above a part. The one in use says in use; another with data says use this, and pressing it downloads that one's depths in place of the lake's. A service that has nothing for the lake says none - so does one whose map of it has only the shoreline, or a chart with only shoreline lines and depth areas over it, which give no depths to cut - and one that could not be asked says failed with the reason, and try again under it asks that one service again on its own, without fetching the map again. If it answers, its line is rewritten with what it says now - in use when it had depths - and the old failure goes.
- Import - a survey file of your own; see Importing a survey.
- Stylized - depth estimated from the shape of the shoreline, for a lake nobody has surveyed; see Stylized depth.
- Flat - one water colour, whatever depth the lake has. Its depth data is kept: choosing Survey or Import again uses it.
A lake with no survey starts on Stylized depth: when its first map fetch finds no survey and nothing was imported, the depth is set to Stylized with its deepest water at 65 ft and its average at 15 ft - 19.81 m and 4.57 m on a lake in metres - so the piece has depth steps from the start, labelled as estimated like any Stylized depth. Type the lake's own depths over them when you know them. A lake with a survey starts on its survey, a later fetch never changes the depth, and a place - a town - still starts flat. Flat makes the water one colour instead. A lake started before version 1.3.3 with no survey stays flat until you choose otherwise, and the Depth section says why in so many words: "No depth survey covers Lake of the Ozarks, so the piece is land over a painted backer (2 layers). For depth layers choose Stylized depth and type its deepest water; its average depth, if you know it, shapes the slope." Use Stylized depth under it is that one step. When a service that might have the lake's survey could not be reached, the section says that instead - the survey may be there, so press try again on its line; Stylized depth is a fallback, not the answer.
The services asked, by where they cover:
- Minnesota - the Minnesota DNR's lake survey contours, in feet.
- Michigan - the Michigan DNR Fisheries Division and Institute for Fisheries Research lake maps, in feet. Their small spot depths are used as single soundings, and the deepest point as the deepest water: Gun Lake is surveyed at 5, 10, 20, 30, 40, 50 and 60 ft, to 68 ft. Their credit says the maps are not for navigation, and the README, credits.txt and the back label say so with it.
- Indiana - the Indiana DNR's lake survey contours, in feet.
- New Hampshire - the New Hampshire DES and Fish and Game lake surveys, in feet, rounded to 5 ft. Their licence asks that the data be used "for planning purposes only; distribution is discouraged"; the card, the check, credits.txt and the note with every download carry it.
- Connecticut - the Connecticut DEEP lake surveys, in feet.
- The Great Lakes - NOAA's NCEI depth grid of each lake, in metres, offered only for the Great Lake itself and downloaded only when you choose it; and NOAA's nautical charts (ENC), in metres, which cover harbours and the water near the shore rather than whole lakes. A chart's depths are not for navigation, and the check says how much of the lake they cover. Its deepest water is the deepest sounding in the lake itself, never one in a river or harbour beside it. NCEI's grid also covers the land round the lake, and that land stays land: a point or a spit the grid shows above the water, such as Long Point or Presque Isle on Lake Erie, is never filled in with the depth of the water beside it.
A survey's own shoreline is not the piece's. The shore cut is always USGS's (outside the US, OpenStreetMap's), and a survey's outline only says where its depths apply; depth data that lies beyond USGS's shore is left out, and the check says how much. The water shallows to nothing only at USGS's shore: where a chart's coverage ends out in open water, the water there keeps the depth the chart gives it.
Fetch again asks the services again and keeps the survey you chose while it is still offered. It never replaces an imported file: only another import, choosing a survey, or Remove the import does.
Threshold modes
The water is split into colours at depth steps: the first colour from the surface to the first step, the next to the second, and the deepest colour, on the backer, from the last step to the bottom. Threshold mode says how the steps are chosen.
- Even steps - one round step from the surface down - 1, 2, 2.5, 5, 10, 15, 20, 25, 30, 40, 50, 75, 100 and so on - whichever gives the number of Water colours nearest the one you asked for. A 141 ft lake at six colours steps by 25 ft: 0–25, 25–50, 50–75, 75–100, 100–125 and 125–141 ft. A deepest band thinner than a quarter of a step joins the one above.
- Survey lines - the depths the survey drew its own lines at, so the cuts follow them. When there are more lines than depth sheets, every second, third... line is used, the fewest skipped that still fit Water colours: Gun Lake's seven lines at six colours cut at 5, 20, 40 and 60 ft. Turn Choose for this piece off to set Every k-th line yourself. A piece cuts at most 24 steps: choose more lines than that - every line of a survey drawn every 2 ft, say - and the shallowest 24 are cut, the deepest band runs to the bottom, and the note under the chart names the lines left out. A grid, a set of soundings or Stylized depth has no lines of its own, so this mode uses even steps for it, and says so under the chart. When every line is at or past the deepest water, none is a step and the lake is one colour; the note under the chart says that too.
- Balanced - depths that give each colour about the same area of water, rounded to round numbers. For a lake with a wide shallow shelf and a small deep hole, where even steps would spend most of the colours on the hole.
- Custom - the depths you type in Depths (ft), shallowest first, separated by commas: 5, 10, 20, 40, 80. It takes up to 24: type more and the box keeps the shallowest 24 and says how many deeper ones it left out - "Custom depths takes up to 24 depths, so the first 24 are kept and the 6 deepest are left out." - and a save of more is refused, with nothing changed: "Custom depths takes up to 24 depths." (
too_many_depths). Switching to Custom starts the box with the steps on screen. A depth at or past the deepest water is left out, and the check says so.
Water colours runs from 1 to 12; the piece has one sheet per colour below the land. Even steps keep to a step that prints, and Balanced and Survey lines merge what would print alike, so the colours planned can differ from the number asked, and the build's cleanup can merge bands too thin to cut as well. Before a build the slider says how many the plan allows at most - "11 asked · up to 14"; once the sheets are cut, and while they still match the settings, it counts them - "11 asked · 14 planned · 8 cut". With Custom, or with Every k-th line set, the depths decide, and the slider shows the colours they make and cannot be moved. Above 10 colours the check notes it, in the README in the download: the steps get hard to see and to glue square.
Depth units is how depths are written on the paint guide and in the check, feet or metres. Changing it converts the depths you typed - custom depths and Stylized's deepest water - so 40 ft becomes 12.19 m rather than 40 m, and back to exactly 40 ft. The depths box shows them to the hundredth; adding a depth there in metres keeps the others exactly as they were, so they still come back as typed. Sheets already cut keep the unit they were cut in, in the sheet list, until you build again.
The depth chart
Under the steps, a chart shows how much of the lake lies at each depth, from the surface on the left to the deepest water on the right, with the steps drawn over it as lines and the colours they make in a strip underneath. Hover over a bar for its depths and its share of the water. Under it, each colour's depths are listed.
It is of the whole lake, before a build, and it follows a change of settings a second after it is saved.
Stylized depth
For a lake with no survey, Stylized makes depth from the shoreline: the water deepens with the distance from the nearest shore, to the deepest water you type, smoothed so the steps run as rounded offsets of the shore. It is an estimate, and everything says so.
- Deepest water (your estimate) is required. A lake that started on Stylized because it has no survey starts at 65 ft (19.81 m); otherwise nothing guesses it. It is reached at the point furthest from every shore. A fishing map or the lake's association often gives it. Build refuses Stylized without it.
- Average depth (optional) is the lake's average depth, when you know it - a lake association, a fishing guide or the dam's operator often gives it, or it is the lake's volume divided by its area. When it is typed, the studio works out the shore profile that makes the estimated water average that deep, and Shore profile is not used: the slider says the profile is solved from the average when you build, and after a build it stands at the profile the build found. It has to be shallower than the deepest water, or the build refuses it and says so. Lake of the Ozarks has no public survey - USGS, the Missouri Department of Conservation, Missouri DNR, Ameren, the Corps of Engineers and ArcGIS Online were all checked - and its known figures are 130 ft deepest and about 37 ft on average: typed as those two, a 300 mm piece's build solves the profile to about 0.8 and its water averages 37.0 ft, as the lake's does. The profile depends on the piece's size and frame, because a finer grid sees more of the lake's narrow arms, so it is solved at each build and not before.
- Shore profile shapes the bed when no average is typed: 1 deepens evenly from the shore; below 1 the bed drops off steeply near the shore; above 1 a wide shallow shelf runs out before it deepens.
Where the frame cuts the lake, the cut edge is not treated as a shore.
_stylized), in every SVG, on the paint guide and in credits.txt, and the studio marks the depths "est.". Say so on the piece too, wherever it is shown or sold.Importing a survey
Import a survey, in the Import choice, takes a survey file of your own - or drop the file on it. The studio reads it, then asks how to read it, with everything the file says already filled in and what it does not say marked check:
- Depth from - the column that holds the depth. A file's own heights (a Shapefile's Z) are listed as "z (geometry)". A grid has one value per cell and no column to choose.
- Units - feet or metres, filled in only when the file says: a vertical unit in its .prj or a GeoTIFF's vertical datum, a unit in the depth column's name (DEPTH_FT, DEPTH_M) or in a KML's depths ("10 ft"), or an FGDC metadata .xml in the zip that gives the depth's or elevation's unit (USGS's ScienceBase surveys carry one, and say feet). When the file says none of these, nothing is filled in and Use these depths waits until you choose - a survey in feet read as metres comes out more than three times too deep, and nothing else on the page would show it.
- The numbers are - depths, deeper is larger; negative depths; or elevations, the height of the lake bed above a datum, as a reservoir's survey gives them.
- Water level - for elevations only: the level the depths are measured below, on the same datum as the file - a reservoir's conservation pool, for example. Depth is the water level less the elevation. It is never guessed. Texas's 1997 survey of Squaw Creek Reservoir - Comanche Creek Reservoir in the search, the name the U.S. gazetteer gives it now - gives elevations, and its conservation pool, 775.0 ft, makes them depths.
- Coordinates - read from the file's .prj or its own tags when it has them. When it does not, say whether they are longitude and latitude, a UTM zone, or paste the .prj text.
Use these depths reads the file with those answers. Only what lies within the lake's box, plus a tenth each side, is kept: lines become contours, points become soundings, a grid becomes the depth grid, and anything at or above the water is left out. The file is then the lake's depth, in place of any survey, and the sheets are stale until you rebuild. The check notes an elevation turned into depth.
The files it reads:
- a zipped Shapefile - lines, points or polygons, with its .prj, one Shapefile per zip
- GeoJSON, GeoPackage, KML and KMZ
- CSV, TXT or XYZ - longitude, latitude and depth, or x, y and depth with a coordinate system
- an ESRI ASCII grid, a GeoTIFF (32-bit float or integer, first image only) and NetCDF-3
- any of those in a .gz or .tar.gz
Coordinate systems: longitude and latitude, UTM, Transverse Mercator, Lambert Conformal Conic (most US State Plane zones), Albers and Web Mercator, in metres, feet or US survey feet. NAD83 is read as WGS84, about a metre apart. NAD27 is read as WGS84 too, which moves it by tens of metres, and the check warns. A .prj in any other projection is refused, naming it.
Refused, with the reason: a GeoTIFF of 64-bit floats (export it as 32-bit float), NetCDF-4 (export it as NetCDF-3, a GeoTIFF or an ASCII grid), a zip with two Shapefiles in it, a zipped Shapefile without its .dbf when its shapes carry no depth of their own (no Z), a Shapefile with a record whose length is below zero, a NetCDF-3 file listing more than 16 variables or dimensions (or more than 256 attributes in one list), a table of more than 256 columns or fields, a text line - or a row running over several lines inside quotes - longer than 16,384 characters, and anything that unpacks to far more than its size.
How large: on the website, a file of up to 64 MB, a grid of up to 64 million cells, up to 5 million points, a table of up to 20 million values (rows times columns), and up to 256 MB once unpacked, every layer of a .gz inside a .gz counted together. In the Windows app, a file of up to 1024 MB, with no limit on cells or points and up to 4 GB once unpacked. A file larger than the limit is refused before it is sent; crop it to the lake, or zip it.
The frame
- Width and Height are the finished piece - the Small, which is your design - from 50 mm each way. Nothing stops a piece bigger than your laser bed: the check warns, and Sizes makes the bigger sizes to fit the bed.
- Border is how wide the plain wood is all round the piece - 7 mm on a new lake. The map fills the whole piece, as the picture does in Stepped Layers and Landscape, and the border is laid over its outer edge on every sheet - under a lattice, it is the lattice's solid frame. It always leaves a window at least 20 mm across, so on a 50 mm piece it is 15 mm at most. The title goes in the map when it fits there, and otherwise on a deeper top border; under a lattice it is always on the lattice's frame - in a deeper top border over the depths, as one line along the bottom on City Lattice - see The title.
- Padding is the air between the lake and the border, as a share of the window. More padding shows more of the land and the roads round the lake; none fits the water edge to edge. A place has no padding: its map width says how much ground it shows.
The map runs north up to the edge of the piece, under the border, and the lake is fitted inside the border - in the part the border leaves showing - as large as the padding allows, so none of its water is hidden. The Map view shows one box, the piece.
Moving the piece off the lake. In the Map view, press inside the bright box - the piece - and drag the map under it, as you would slide a photo under a frame: to take in a town on the shore, say, or one arm of a long lake. The piece keeps the size the fit gave it; Padding still sets that. When you let go the piece's middle moves by as much ground and is saved, and the map is drawn again round it. Dragged far enough, the piece cuts off some of the lake, and its depth with it. Dragging outside the box moves the view, as everywhere else. Under Padding, Centre on the lake fits the lake in the piece again. On the website the piece's middle stays within 25 km of the lake's search point, or for a big lake twice the side of a square of its area - 482 km for Lake Michigan - and a drag past that is not kept. Moving further than the map that was fetched shows frame past the map · fetch again.
Framing a place
A place - a town or a city found with Look for Place - is framed by its middle and by how much ground the piece shows, rather than by fitting a lake into it. Choosing it from the search centres the map on the place's point. Under Frame, Padding is hidden for a place and two controls take its room:
- Map width is the ground the piece's longer side covers, in km, border and all - the map runs under the border to the edge - with the scale it makes beside it - "1:22,000". Left empty it is 22 m of ground for every millimetre of that side, and the box shows what that comes to: "6.6 (22 m per mm)" on a 300 mm piece, 4.4 km on a 200 mm piece, whatever the border. A top border grown deeper for the title takes its extra depth off the map, so on a tall piece the map width is measured on what is left. That is the street scale a lattice reads at - see Styles. A narrower map shows fewer streets, each wider; a wider one packs more in, until the blocks between them are too small to cut and the check says so. It takes 0.3 to 300 km.
- Drag the map in the Map view to choose the area: press inside the bright box, the piece, and drag the map under it, as you would slide a photo under a frame. When you let go the centre moves by as much ground and is saved, and the map is drawn again round the new piece. Dragging outside the box moves the view, as everywhere else. A drag that would take the centre more than 25 km from the place is not kept, on the website. Moving further than the map that was fetched shows frame past the map · fetch again. A lake's piece is dragged the same way - see Frame.
- Centre is the map's middle, in latitude and longitude. Its arrows - ↑ ← → ↓, with the map's width between them - move it a tenth of that width north, west, east or south. Once it has moved, the line under it says how far it is from the place, and Back to the place - Back to Louisville - puts it back.
Moving the middle or widening the map past the area that was fetched reaches past the map: the Map view says frame past the map · fetch again, as it does when a lake's frame grows, and Fetch again downloads the new area. A build of a frame the map does not cover is refused - "The map data does not cover this frame." - until it is fetched again.
A place has no lake survey, so its water starts flat, one colour - City Lattice, or Lake Topo on flat water - unless you choose Stylized depth for it, which steps down from every shore and is labelled as estimated, as it is for a lake. It has no deepest water or area to give either, so it has no facts line.
On the website a piece keeps to the place it was started from: one project is one place. Its middle can move up to 25 km from the place's point, measured on the ground, which is room for any frame of a town and its river. An arrow that would take it further is greyed - "Not more than 25 km from Louisville: start a new project for another place." - and a change that does is refused: "This is too far from the place this project is for." To map somewhere else, start a new piece from the search. The limit is the website's; a lake's dragged piece has one too, 25 km or more for a big lake - see Frame.
Styles
The Style section, between Map and Frame, says what kind of piece the map becomes: four tiles, each with a line under it. Sheet 1 is always the front.
- Lake Topo - "The land on top, the roads scored". The land sheet in front (sheet 1), with its roads scored and its names, title and compass engraved; behind it the water steps down, a sheet per depth step, to the backer. A large lake at a small scale - a whole reservoir on one piece - reads best this way. A new lake starts on Lake Topo (since version 1.3.3); a lake started before then keeps the style it had.
- City Lattice - "Raised streets over painted water". The streets themselves, cut as a raised lattice in front (sheet 1): the roads are wood and the blocks between them are open. Behind it the land (sheet 2), and behind that a backer painted in one water colour. The look of a city tile, for a town on a river, or a lake with no depth.
- Lattice + Depth - "Raised streets over the depths". The lattice in front (sheet 1), the land behind it (sheet 2), then the water stepping down by depth, a sheet per step, to the backer, as in Lake Topo.
- Auto - "Chosen from the map when it is built", and how a place - a town - starts. It picks a lattice when the map is at street scale - 1:30,000 or finer, so that a millimetre of the piece is 30 m of ground or less - and the window holds at least 20 streets of the kinds a lattice is made of: Lattice + Depth when the piece has depth (a survey, an import or Stylized), City Lattice when its water is flat. Otherwise it picks Lake Topo. The 20 streets keep a lake with no roads near it from becoming a lattice that is only its border.
After a build the Auto tile and the section's heading say what Auto picked - "Auto: Lattice + Depth"; choosing that style, or another, yourself is one click. Auto reads the map as the window is first framed, before a title's top border grows. With Auto chosen, Gun Lake on a 300 mm piece is about 1:22,300 then, with 34 lattice streets in the window, and Lake Harriet in Minneapolis about 1:5,800 with 60, so both build as Lattice + Depth; Lake of the Ozarks on a 300 mm piece is about 1:318,000 and builds as Lake Topo, though its window holds over 1,500 such streets. Louisville at its default width builds as City Lattice. Auto decides on the Small, and the Medium and Large keep its choice although they are at a finer scale - see Sizes.
A lattice style chosen by hand for a map with fewer than 20 such streets still builds, and the check warns - see Too few streets for a lattice.
Lakes saved before the styles came were moved to Auto, like a new lake, and read settings changed · rebuild once: a saved Gun Lake now builds as Lattice + Depth. Choose Lake Topo to build it as it was.
The street lattice
The lattice is the streets cut as a sheet of their own: each road is a strip of wood as wide as its kind, the border is a solid frame round them, and everything between - the blocks, and the water - is cut away, so the land shows through it. It is one piece, held together through the border.
- Which streets. Motorways, trunk, primary, secondary and tertiary roads and minor streets always; service roads - alleys, car parks, driveways - only at 1:10,000 or finer, where they have room. That is read on the Small's own scale, once its title's top border has grown: a 200 mm Lake Harriet, at 1:10,985, has no service roads, and a 300 mm one, at 1:6,887, keeps them; a Medium or Large carries the Small's streets. Railways and footpaths are not part of it, except where they cross the water on a bridge; tracks never are, even on a bridge. Tunnels are left out. Every street stops at the land sheet's shore unless it is on a bridge.
- How wide. Motorways 2.5 mm, trunk and primary roads 2.0 mm, secondary 1.6 mm, tertiary 1.4 mm, minor streets 1.2 mm and service roads 1.0 mm - and never narrower than a tenth more than Narrowest wood, plus 0.05 mm (0.93 mm at the default 0.8 mm). On a Medium or Large the strips widen with the piece.
- Bridges are part of the lattice, at its height: a road, railway or footpath that crosses the water on a bridge is a strip of the lattice over the water, at least 1.5 mm wide, held by the streets at both ends. There is no separate bridge piece - see Bridges.
- The openings. The blocks are cleaned as the water is - no wood narrower than Narrowest wood, no opening narrower than half of it - and an opening smaller than Smallest opening (4 mm², shown under the style when it is a lattice) is left as wood, rather than cut out as a speck to be lost. The outlines are then smoothed to within 0.05 mm, far under a kerf, which leaves a city's lattice about a tenth of the points it would otherwise have, so its file stays a manageable size.
- Loose pieces. A bit of street cut off from the rest - by the water, or by the edge of the window - is kept when it is at least 8 mm² and rests on the land at one place of at least 2 mm², or at two when more than 1 mm² of it is over water. It is outlined in orange on the land sheet, to be glued on there, and named L1, L2 and so on. A smaller one, one with nowhere to rest, or a bridge deck whose own streets end at the shore is left out, and falls away with the opening round it. The check lists both - see The lattice.
A lattice reads at street scale. The strips are a fixed width while the blocks shrink as the map widens. Round Lake Harriet the middle-sized block is about 200 mm² on a 300 mm piece (1:6,887) and about 120 mm² on a 200 mm one (1:10,985); in downtown Louisville, with 8 km of ground across a 300 mm piece (1:28,986), it is about 12 mm², and by about 1:36,000 it is 8 mm² - wood with holes in it rather than streets. The check warns when half the blocks are under 10 mm² - see Lattice blocks too small to cut well. A narrower map, a bigger piece, or Lake Topo is the cure.
Under a lattice the map's names are engraved on the lattice itself. A street of the lattice is 1.2 to 2.5 mm wide and a name's capitals 2.5 to 2.8 mm, so a name cannot sit on its own street; instead the names - towns, route markers, road names, neighbouring lakes - are placed as they are on Lake Topo, on the land before the lattice is laid out, with the streets the lattice carries as the roads, so a road name runs along its own street and a route marker sits on it. The lattice keeps a small solid tag under each: the name's box and its clear space, with half a millimetre more round it so no letter is nearer a cut than on the land, its corners rounded so that the tags of names close together are one piece. The name is engraved on its tag, and the land under it is left bare. The streets run into the tags; a tag that no street reaches is a loose piece, glued on the land like any other. Downtown Louisville on a 200 mm City Lattice has ten street names, three US shields and a repeat marker on its tags, where before it had none. The land sheet keeps the depth legend and the facts line, placed clear of the lattice's strips with half a millimetre to spare, so they show through the blocks; it scores only the roads the lattice does not carry - on Gun Lake the service roads and the footpaths. A lake built before 24 October 2026 keeps its names on the land, where a block was big enough to show them, until it is built again. The title goes on the lattice's border instead: in City Lattice one line along the bottom, as on a city tile; in Lattice + Depth the title block in the top border, which grows to hold it as it does on land. The compass is Lake Topo's on every style: the same disc, in the same place and at the same size, with its coordinates under it, placed on the land before the lattice is laid out, with the streets not in the way - bottom right, or where you drag it (see The compass and coordinates) - and the names keep off it. The lattice keeps solid wood under it - a round plate the streets run into, with 3 mm of plain wood round the rose - and the rose and the coordinates are engraved on that plate, on the lattice, with the land under it left bare. A plate that no street reaches is a loose piece, glued on the land like any other. With no land in the map for even the 34 mm rose, as on Lake Topo, it goes, smaller, in the bottom-right corner of the lattice's border, then the top-right, with its coordinates beside it.
Engraving
What is burned into the land sheet rather than cut through it: the roads scored, the names, title and compass engraved. All of it stays clear of the water and of every cut edge - but for a road scored across a bridge - and nothing else is engraved over a bridge. Under a lattice it also stays clear of the lattice's strips, the roads the lattice carries are not scored, and the title, the map's names and the compass are engraved on the lattice instead - see The street lattice. The depth legend and the facts line are engraved here too - see The depth legend and facts line.
Roads
Roads scores every road the map carries, at every size of piece - motorways down to tracks and paths - in three groups, so the laser can run the minor ones lighter: main roads on score, minor and service roads on score-2, tracks and paths on score-3. Piers and ferries are left out. Roads stop short of the title, the compass and every label, and are scored over water only on a bridge, across it from shore to shore - see Bridges. A road in a tunnel is not scored at all. A road keeps 0.3 mm from every cut edge, a bridge's edges among them - closer than the rest of the engraving, which keeps 0.5 mm - so the roads down a narrow point or along a shore still read; only a road on land narrower than about 0.7 mm is left off. On Lake of the Ozarks at 300 mm about seven tenths of the map's road length is scored; the rest lies under the title, the compass and the labels, on land the cut takes away, within those 0.3 mm of a cut, or among a town's thinned streets.
In a town the streets run so close together that, scored at full density, they burn into a dark patch. Street spacing (0.6 mm) thins the minor streets so that two seldom run side by side closer than that for more than 2 mm - on Lake of the Ozarks the longest such run left is under 3 mm, in tangles of short curving streets; which one goes is decided the same way on every build. Main roads are never thinned. 0 keeps every street.
Scoring every road costs laser time. Lake of the Ozarks at 300 mm scores about 24 m of road, against about 4 m when only motorways to secondary roads were drawn, as before this update - at 30 mm/s, about 11 minutes more.
Labels on the map
Place names, route numbers and the names of other lakes are engraved on the land, in Cinzel capitals, each in a clear space of its own. Under a lattice they are placed by the same rules and engraved on solid tags of the lattice - see The street lattice.
- Places - Towns and villages by default: towns at 3.4 mm with a 1.8 mm dot, ringed for a county seat, then villages at 2.8 mm. Towns leaves the villages off; Every place adds hamlets at 2.5 mm, last, where there is room - a large lake has hundreds. None names no places. A name that cannot sit beside its dot is moved further out, onto two lines, made smaller, or drawn with a dotted leader; a town's leader can bend round a shore (tried for up to eight towns on a piece).
- Route markers - All markers by default: Interstate and US shields, state route ovals (Missouri's MO 5, MO 7), lettered-route boxes (Missouri's J, KK) and, on a long route, a repeat marker every 110 mm or so - up to four, at least 90 mm apart. Numbered routes keeps the shields and ovals only. None leaves the route numbers off. A marker sits on its road, and only on a road the sheet actually scores - under a lattice, a street of the lattice.
- Road names - Major roads by default: primary to tertiary roads, named along the road where the name fits beside it. Every road adds minor roads. None engraves no road names. A name that only repeats the route number - "MO 5", "J-107" - is not engraved as a name; the marker says it.
- Neighbouring lakes - the names of other lakes in the frame, in italics. The lake's own name is the title, so it is not repeated.
Labels never sit over water, a cut, a bridge, the title or the compass, and they keep 0.8 mm apart; two names side by side keep a capital's height apart wherever their letters share any of their height - on one line, or part of a line above or below each other - so that neighbouring towns never read as one place ("Novi Detroit"). Water too narrow to cut, which is engraved instead, gives way to them: it is trimmed round each label and its 0.5 mm of clear space, as the roads are, so a town on a marshy shore is still named. The same name twice - two Mill Creeks - is allowed, but not within 20 mm. They are placed in a fixed order, and a label placed earlier always wins: towns, US shields, villages, state ovals, neighbouring lakes, lettered routes, repeat markers, road names, hamlets. Within each kind the biggest places go first - by the map data's own ranking, then capitals and county seats, cities before towns, then nearest the lake - so where two compete for the same room the bigger one gets it. Every build places the same labels in the same places. A label left off a crowded map is not a finding in the check.
Why street names need a zoomed-in piece. A whole lake is a small scale: Lake of the Ozarks on a 300 mm piece is about 1:318,000, 88 km across. Of the 35 named major roads on it, 34 have no stretch straight enough and as long as their own name - the middle road is 7.4 mm long and the middle name 28.8 mm - and the last has no room left beside it, so at the defaults none is named along its road. At that size the route markers name the roads, as on a state highway map; a piece of one arm of the lake, or a smaller lake, has the room for street names, and Road names places them there.
A lake whose map was fetched before the studio kept road names and route numbers says Fetch again to add road names and route numbers, under Map and under the labels. It still builds, with its towns and lakes named and no markers or road names, until it is fetched again.
The title
Title and subtitle engraves the lake's name in a title block: Cinzel Bold (SIL Open Font License) in capitals, the first letter of each word full height - except short words such as "of" and "the", which are small capitals throughout - and the rest as small capitals, over an engraved divider - a double rule with scrolls and a central lozenge - with the subtitle letter-spaced beneath. On a 300 mm piece the capitals are 12 mm, scaled with the shorter side of the piece, up to 17.5 mm.
- Style - Auto picks by the size of the capitals: Hatched at 10 mm and up - outlined letters filled with a fine diagonal score 0.5 mm apart, with an engraved drop shadow; Shaded from 8 mm - solid engraved letters with a scored shadow line; Plain below 8 mm - solid engraved letters. Choosing one keeps it whatever the size.
- Placement - Auto puts the title in the map, at the top centre, 6 mm in, with 4 mm of clear land round it that roads, labels and engraved water keep out of - but only where that clear space misses the water the land sheet cuts. If it does not fit there at full size it tries 10 mm capitals, and if that does not fit either the top border grows to hold the title block and the lake is fitted again under it - unless you typed a Top border, which never grows. In the map tries capitals down to 8 mm before it gives up and puts it on the border, with a note in the check. Top border always puts it on the border, which grows to hold it unless you typed a Top border.
- Top border - empty, the top border is the same as the others and grows only when the title needs it. A number keeps it at that depth, title or not. If it is deep enough for the title block with 8 mm above and below it - about 54 mm on a 300 mm piece with a subtitle, 46 mm without one, more on a bigger piece - the title goes in it whatever Placement says. If not, the title goes in the map where Placement allows (Auto or In the map), and otherwise in your border as large as it fits: a smaller block, or one line. The size it was set at is said under the title's controls, and the check notes a one-line title. A border grown for the title never takes more than half the piece's height, and the Map view frames the lake under the border the last build grew while nothing that moves the title has changed.
Where the last build put it, at what size and in which style, is said under the title's controls.
The compass and coordinates
Compass engraves an eight-point nautical rose on the land, bottom right, 6 mm in from the corner of the map with 3 mm of clear land round it; if the corner is water it takes the nearest clear spot in that quarter of the map, then a smaller rose - down to 34 mm - and only then the border, where a small rose needs a border about 11.5 mm wide: on a narrower one - a new lake's is 7 mm - it is left off, and the check says so. Under a lattice it is placed the same way and engraved on a solid plate of the lattice (see The street lattice). It is 18% of the piece's shorter side - 54 mm on a 300 mm piece. Under 53 mm it drops the NE, SE, SW and NW letters; under 34 mm it is a simple four-point rose; under 20 mm there is no compass, and the check says so.
Putting it where you want it. In the Stacked view, press on the compass and drag it where you want it, on any style: a dashed ring follows the pointer, and when you let go the sheets are built again with the compass there. Dropped on clear land, its centre stays exactly where you let go. Dropped over water, a cut, a bridge, the title or the border, it goes to the nearest place in the map where it fits with its 3 mm of clear land, and the note under Compass style says how far it moved when that is 2 mm or more - "The compass is 33 mm from where it was put: the nearest place it fits on clear land, off the water and the cuts." If it fits nowhere in the map at its full size it is made smaller, as above, and placed as near as it fits; only with no clear land in the map for even the smallest does it go in the border, and the note says so. While the compass is in the border or left off, the dashed ring waits bottom right on the preview: drag it into the map to place it. A placed compass searches the whole map rather than the bottom-right quarter, so on a new lake's 7 mm border a compass the corner had no room for can still be put on the land. Bottom right, beside the note, puts it back where the rules put it at the next build. A Medium and a Large put it at the same place on the piece, at the Small's size scaled up. Under a lattice its plate goes with it, and the names keep off it. The compass can be dragged once the sheets have been built, while nothing is building.
- Compass style - Navy disc: an engraved disc with the star and letters left in bare wood, which the paint guide suggests painting navy. Wood: the star and letters engraved on bare wood, with no disc.
- Coordinates are the middle of the map - the centre of the window the lake is fitted into, so they move a little with the frame and the padding - engraved under the compass, centred, 3.2 mm below it. Written as Both (the default) puts degrees, minutes and seconds at 3.2 mm over decimal degrees at 2.5 mm - 38°09’03” N 92°57’54” W over 38.1510° N 92.9649° W on Lake of the Ozarks; or one of the two on its own. The choices show your own lake's latitude, as the last build engraved it. With the compass off, the coordinates go on the border, where there is room for one line: Both is then degrees, minutes and seconds alone. A compass with the coordinates under it that finds no room in the map tries the rose alone there, with the coordinates on the border.
Smallest letters (mm) is the smallest capital height engraved for the title, the coordinates and the names on the map: a name or route number whose own size is smaller is engraved at this height instead, so raising it makes the small names larger rather than leaving them off. The title and the compass shrink to fit, as above; a title, coordinates or compass that will not fit even at its smallest is left off rather than engraved too small to read, and the check says so - see A label left off the land sheet.
Cut limits and engraved water
Under Material, Cut limits are what the laser can leave and cut. The defaults keep a lake's coves and points; most pieces never need them changed.
- Narrowest wood (0.8 mm) - the thinnest land the land sheet keeps, with a tenth to spare. Thinner land - a strip, a point or a neck - is cut away with the water, and land a thin neck held on to the shore is left as a loose piece, like an island (or goes with the water, if it is too small to keep). Only where land pinches to just about this width between two curves of water is the water cut back a little, so the land stays at least this wide.
- Narrowest water slot (0.3 mm, about twice a kerf) - the narrowest water the land sheet cuts out. Narrower water - the last of a cove's tip, a creek - is closed in the cut.
- Narrowest depth band (1.0 mm) - the thinnest ring of one water colour a depth sheet keeps; a thinner one is merged into its neighbour.
- Engrave water too narrow to cut (on) - the map's water that the cut leaves out is engraved on the land sheet instead, so the shoreline and the creeks still read: the tips of coves, ponds too small to cut, a channel narrower than the slot. Water inside the title's or the compass's clear space, or under a label and its clear space, is not engraved. The check notes how much was engraved - see Water too narrow to cut, engraved instead.
On Lake of the Ozarks at 300 mm these limits keep about 400 of the map's 917 cove tips, against 142 at the old 1.2 mm wood and water, and cut 95% of the map's water; the rest, about 130 mm², is engraved in about 1,400 places, apart from about 2 mm² inside the title's and the compass's clear space and about 13 mm² under the labels.
Lakes saved before this update move to the new cut limits (0.8 mm wood, 1.0 mm bands) and coordinate format unless you had changed them; rebuild to see the finer coves.
Bridges
The map's own bridges are always part of the piece; there is nothing to set. Where a road the land sheet scores crosses the water on a bridge, the bridge is left uncut in the land sheet: wood across the water at the sheet's thickness, with its road scored across it from shore to shore, so the road runs over the lake in one piece with the land. There is nothing to cut separately and nothing to glue. A bridge is as wide as its road is drawn - 2.5 mm for a motorway, 2.0 mm for a main road, 1.5 mm for a minor one - and never narrower than Narrowest wood, and it runs 3 mm onto the land at each end. Bridges that follow one another on one route are one bridge, and so are two carriageways side by side; two roads' bridges that meet are one bridge carrying both roads. Nothing but the road is engraved on a bridge: names, the compass and engraved water keep off it.
A bridge is kept when both its ends - the first and last places it lands, not an island it crosses on the way - land on the land sheet's wood; an end on a narrow sliver of land is enough, and the water past where it lands, which its road does not cross, stays water. A bridge the map stops out in the water, one to an island too small to cut, one that would cross the title's clear space, or one so close beside a bigger bridge that it would be too narrow, is left out, and its road stops at the water; the check lists each one and why - see A bridge left off the piece.
Under a lattice - City Lattice and Lattice + Depth - the bridges are strips of the lattice, cut with it at its height, and they include railway and footpath bridges as well as the roads' - never a track's. See The street lattice.
Tunnels are never drawn, on any style, and neither are piers or ferries. The map of the fetched area leaves them off too, so a road you see crossing the water there is on a bridge.
The sheets are glued together, so there are no dowel holes - see Putting it together. A lake built before 24 Oct 2026 keeps the sheets it was built with, without its bridges, until it is built again.
Paint
Shallowest water and Deepest water are the two ends of the water's colours: one colour per band between them, the shallowest on the first water sheet and the deepest on the backer. With flat water there is one water colour, and it is the shallowest. A paint change repaints the preview at once, and the paint guide and the download a second or two later - colours picked while a repaint is running are painted as soon as it finishes, so the guide always ends in the last colour chosen. It never touches a cut and never makes the sheets stale. If a repaint is stopped or fails, the Paint guide view says the guide is in the old colours and offers Repaint. The back label's table of layers is repainted with it, and so is every size already built: a Medium or Large whose colours changed since it was cut is repainted before its zip downloads ("Repainting the Medium"). With the navy disc compass, the paint guide suggests painting the disc navy.
Each colour belongs to its depths, not to a sheet: a band is painted the colour of its place among the depth steps the design chose, so a band the cleanup merges away on one size leaves every other band its colour, and the same depth is the same paint on the Small, the Medium and the Large. Under a lattice the paint guide has a row for the lattice - "natural or stained wood, no paint" - and City Lattice's backer is the one water colour: all the water is that colour. With the depth legend on, it has a row for the legend's boxes too, each to be painted the colour of the band it stands for.
Building
Build Sheets queues a job on the server, as every studio's build does, and the overlay names the stage it is on. It reads only the fetched map and the lake's depth, so it is free, and you can rebuild as often as you like. A small lake builds in seconds; a large one with every road and label takes longer - on a 4-core test machine, Lake of the Ozarks at 300 mm took about two minutes. A lattice adds to it: there, Lake Harriet at 300 mm built in under half a minute, and downtown Louisville at its default width in under a minute. A Great Lake is the slowest of all: Lake Erie took about 4 minutes at the Small and about 7 at the Large. The website's server can take longer when it is busy. A build that runs past 15 minutes is stopped within a few minutes of it, and says so: build a smaller size, or fewer depth steps, or try again when the server is less busy. Change anything but the paint after a build and the bar says settings changed · rebuild - the back label's Maker line and map credit included, since they are cut into its file. New depth - another survey, an import - makes the sheets stale too. Build Sheets builds the Small, your design; the Medium and Large are built from Sizes. Two of the overlay's steps are the lattice and the marks that line the sheets up: Laying out the streets..., which takes a moment only when the style has a lattice, and Adding the assembly marks....
A lake build also needs room in the server's memory, and a big lake at a big size needs a lot of it. While other lakes are building, a build that would not fit beside them waits - the overlay says Waiting for room in the server's memory... - for up to 20 minutes; if room has not come by then it gives up, building nothing and changing nothing, and says so: try again in a few minutes. A size that needs more memory than the server can give any one build is refused at once, with nothing built, and the message says what does fit - a smaller size ("Build the Medium (520 x 520 mm) instead: it fits."), or the largest piece that would. The Windows app has neither limit. Each refusal, with what to do, is in When the website turns a lake away.
Sizes
Your design is the Small: the piece at the Width and Height you set. From it the studio makes a Medium and a Large for your laser bed - the same map, the same ground, bigger. The Sizes section, under Putting it together, has the bed - Bed width and Bed height, in the frame's units, 47 × 30 inches (1193.8 × 762 mm) to start with, or the bed you last set (see Workshop settings) - and a card for each size.
- Large is the biggest piece of the same proportions that fits the bed with 10 mm to spare on every side, turned a quarter if it fits better that way. Its longer side is rounded down to a whole 5 mm and its shorter side follows exactly, to a tenth of a millimetre, so it frames exactly the ground the Small does.
- Medium is halfway between the Small and the Large, rounded the same way.
- On the 47 × 30 inch bed: a 300 × 300 mm design makes a 520 mm Medium and a 740 mm Large; a 200 × 200 mm design a 470 mm Medium and the same 740 mm Large; a 300 × 200 mm design 705 × 470 and 1110 × 740 mm; a 200 × 300 mm one 470 × 705 and 740 × 1110 mm, the Large turned; a 400 × 250 mm one 785 × 490.6 and 1170 × 731.2 mm.
- When the Large would be less than 1.15 times the Small there is no Medium or Large, and the section says so: "Your design already fills the bed: a Large would be less than 1.15 times the Small, so there is no Medium or Large." A 600 × 600 mm design still gets them (670 and 740 mm); a 1000 × 700 mm one does not. A design bigger than the bed, even turned, has only its Small, with a warning: it still builds, and needs a bigger laser or cutting in parts.
- A Large is also held below a border 400 mm wide (600 mm for a top border grown for the title) and below 20 times the Small. Only a design with an unusually deep border reaches that, and the section says so when it does.
Each card gives the size's name, its measurements (hover for the other unit), "the design" for the Small or how many times the Small it is - "×1.73" - and whether it fits the bed: fits, fits turned 90° or bigger than the bed. Under that is its state - not built, built, settings changed · rebuild, building…, or queued while it waits for the size before it - with Build (it reads Rebuild once built) and .zip. Below the cards, Build all three builds each size not yet built with the settings as they are, the Small first - all three when the Small is to be built, since the others are read from it. With some built it says what is left - Build the Large, or Build the Medium and Large - and with all three built it reads Rebuild all three. Download all three downloads them in one zip once all three are built with the settings as they are.
What grows and what does not. Everything that is design grows with the piece - the border, the title and its top border, the compass and its coordinates, the names on the map, the lattice's streets and the bridges, the hidden labels, the legend and the facts line - so a Large looks like the Small, bigger. What the laser and the wood decide stays in millimetres at every size: Narrowest wood, Narrowest water slot, Narrowest depth band, the smallest piece and opening, and the kerf. So a Large keeps detail the Small has to leave out - the tips of coves, islands, a narrow band - and its check can differ: a Small can warn where its Large does not, and the other way round. Each size is checked on its own. The map's own small water is the exception: a pond too small to be cut out of the Small is not cut out of the Medium or Large either, although they would have room for it, so the land round it stays as clear as on the Small; and a pond the Small cuts, they cut too - even one the Small's cut made of bits of water a few tenths of a millimetre apart.
The style, the lattice's streets, the depth steps, where the title goes and its style, and where the compass, the coordinates under it and the depth legend sit are decided once, on the Small, and every size puts them there first - the compass at the Small's size scaled up, and a compass you dragged at the same place on the piece - so the three agree. Where a bigger size has no room there, its compass tries smaller in the same place and then the border, and its legend looks where the Small's would; and the same depth is the same paint colour at every size.
A Medium or Large is made from the Small's last build, so it needs the Small built with the same settings: building one while the Small is out of date builds the Small first. A Large takes one and a half to two times as long to build as the Small. The sheet list and the views show the Small.
Each size has its own zip - lake-harriet_medium_520x520mm.zip - and every file in it carries the size too, as small_300x300mm or large_740x740mm, so the three never mix on a disk or in LightBurn. The three together come as lake-harriet_all_sizes.zip: a folder for each size - small_300x300mm/, medium_520x520mm/, large_740x740mm/ - each holding that size's files but its paint guide, and one lake-harriet_all_sizes_paint-guide.csv for all of them, with a row for each colour and a column for the sheet it is on at each size. Each size is checked against your bed - it fits, fits turned, or does not fit - as the Small is.
The views
- Map - the fetched area, the piece outlined on it, and in light blue where the depth data reaches and its contour lines. Outside the piece is dimmed: it is the margin the fetch takes round the piece, so you can see what is just outside it, and none of it is cut. Drag the map inside the piece to move it - see Frame, and for a place Framing a place. When the last build grew the top border for the title, the map is placed under that border, as the sheets were cut and the next build will cut them, and the bar above says so - until you change something that can move the title: the size of the piece or its borders, Padding, the title and its settings, Smallest letters (mm), Narrowest wood or the map. Units, colours, roads and depth leave it. For framing; nothing in it is cut.
- Stacked and Exploded - every sheet in its colour, the land and the lattice in wood, every sheet's roads and words drawn in a burn colour. The marks hidden under each sheet - the alignment scores and hidden labels - are not drawn, as they do not show on the piece. The eye on a sheet's row hides it; opacity fades the sheets in front.
- 3D - the stack as a solid, each sheet at its own thickness, with its roads, words, title and compass on its face. A sheet with more than 20,000 points or 300 openings - a city's lattice - is drawn from a copy simplified to 0.05 mm, so even downtown Louisville opens in under 2 seconds. Drag to turn it; explode pulls the sheets apart, less per sheet the more sheets there are, so the stack stays in view.
- As cut - one sheet's cut file in its laser colours: inner cuts black, the perimeter red, scored roads blue, engraving green, the alignment scores orange, the hidden labels magenta. The back label is a file of its own and is not shown; it is in the download.
- Paint guide - which colour goes on which sheet and the depths it stands for, as it is in the download.
The download
Download All (.zip) holds one SVG per sheet - the files to cut; the back label's file, when it is on; and a combined file with every sheet side by side, numbered, which is for looking at, never for cutting. With them come the previews, the paint guide as a picture and a spreadsheet, a README with the order of assembly and the LightBurn settings for each colour, and credits.txt. Every file name starts with the piece's name and its size - lake-harriet_small_200x200mm_layer_01_of_08_lattice.svg - and a Stylized piece's carry _stylized as well. The Medium and Large each have a zip of their own, and the three sizes come in one zip too - see Sizes.
Material and the cutter are the same job in every studio and are written once: Your material, Exporting your files and On the cutter. Kerf is the one difference: the lake's files are not offset for it, and LightBurn does it - see Kerf in LightBurn.
Putting it together
Islands and shoals
An island on the land sheet, and a shoal - a patch of shallower water - on a depth sheet, is cut free when its sheet is cut: a piece of its own, glued back in by hand on its orange outline on the sheet behind, with the jig below. Nothing is added across the water to hold it - no tab or strip of wood that is not on the map - so the water round an island stays open, as it is on the map; only the map's own bridges cross the water (see Bridges). A lake built before 24 October 2026, when islands were held by short tabs, keeps them until it is built again. The lattice's own loose bits of street are glued on the land the same way - see The street lattice.
Gluing the stack
Every sheet has the same outer edge, and the stack goes together from the back: the backer first, then each sheet in front of it in turn, forward to sheet 1. The piece carries the marks that make that quick and square, all of them hidden once it is together: an orange line on each sheet where the one in front of it goes, and a label in each border saying which sheet it is. They are set in the Putting it together section, after Material, with the depth legend, the facts line and the back label, and all but the scale bar are on by default. The README in the download gives the same steps for your piece's own sheets.
- 1Cut
Cut every sheet, with LightBurn's kerf offset set as below. When a sheet with loose pieces is cut - its islands or shoals - keep the piece of water that drops out of its opening: it is the jig for them.
- 2Engrave the back label
Before anything is glued, flip the backer into its hole in the stock and run the back label on it - see The back label.
- 3Sort
Lay the sheets out by their hidden labels, from the backer to the front.
- 4Stack
Glue each sheet onto the one behind it in turn, its outside edges flush with the sheets behind, so that it just covers the orange line on the sheet behind.
- 5Loose pieces
Once a sheet with islands or shoals is glued down, set its water piece back into the opening, where it fits like a jigsaw piece: its holes are exactly where the sheet's loose pieces go. Glue each loose piece into its hole, onto the sheet behind, then lift the water piece out, keeping glue off it.
- 6The front
Glue the front sheet on last. A lattice goes on by its outside edges, flush with the sheets behind; then its loose pieces, on their orange outlines on the land.
Kerf in LightBurn
The studio draws every cut at the size it should finish and offsets none of them; there is no kerf compensation switch in the lake studio. Let LightBurn do it: in the cut settings of the black layer (#000000, inner cuts) and the red layer (#FF0000, the perimeter), set Kerf Offset to half your kerf - 0.075 mm for the default 0.15 mm. LightBurn then moves each outline outward and each hole inward by that much, so the land, the lattice and the openings come out the size they are drawn. Leave the scores and the engraving without an offset.
Kerf, under Material, is still worth setting to your machine's real kerf: the line under it and the README give the offset to type - half of it - and the alignment scores sit half of it further inside each edge. Your material says how to measure it; its Apply kerf compensation belongs to the other studios.
Alignment scores
Alignment scores scores an orange line (#FF8000) on each sheet, just inside where the edge of the sheet in front will sit - 0.3 mm plus half the kerf under that sheet's wood, 0.375 mm at the default kerf. Lay the sheet in front so it just covers the line all round and it is square; once it is down, no line shows. Loose pieces - the islands and shoals - are outlined the same way on the sheet behind them, so each goes back exactly where it was cut from. Behind a lattice only the lattice's loose pieces are outlined, since its outside edges place the lattice itself. Run the orange layer at a low power: it only has to be seen. On the 200 mm Lake Harriet the orange lines come to about 1.7 m in all.
Hidden labels
Hidden labels engraves each sheet's number and what it shows in its bottom border, where the sheet in front covers it: "L8 · 75–80 ft · LAKE HARRIET" on the backer of the 200 mm Lake Harriet. Under a lattice the land sheet's reads "L2 · LAND · LAKE HARRIET", and a flat painted backer says "WATER"; the front sheet - the lattice, or Lake Topo's land - has none, since nothing covers it. Sort the sheets by them before gluing: a label that reads the right way up means the sheet is face up and the right way round.
They are magenta (#FF00FF), in DejaVu Sans Bold capitals three tenths of the border's depth - from 2 mm up to 3.5 mm, and on a Medium or Large up to 3.5 mm times its scale - starting at the window's left edge. Where the bottom border has no room the label is tried smaller, a quarter of a millimetre at a time down to 2 mm, then in the top border, then without the lake's name. Where it still does not fit, that sheet has none and the check says so: pencil its number on its back.
The depth legend and facts line
Depth legend engraves a key on the land sheet: "DEPTH IN FEET" - "DEPTH IN METRES" in metres - over a row of boxes, one for each water colour, 9 × 4 mm each, down to 7.65 × 3.4 mm (85%) and 6.48 × 2.88 mm (72%) where room is short, scored round and left bare for you to paint each the colour of its band, with the depths under the boxes' edges. It is drawn only when the piece has surveyed depth sheets: flat water, and so City Lattice, has one colour and no legend, and Stylized depth has none either, as its depths are estimates - the facts line says STYLIZED instead.
Facts line engraves the deepest water and the lake's area - "MAX DEPTH 80 FT · 340 ACRES" on Lake Harriet. The area is the whole lake's, from its USGS shoreline - or outside the US its OpenStreetMap one: acres for a piece in feet, and for one in metres square kilometres - "11.2 KM²" - or hectares under one. Stylized depth adds "STYLIZED" after the depth; flat water gives the area alone; a place has neither, so it has no facts line, and the check notes it.
Scale bar, off by default, adds a scale bar to them, up to 60 mm long, in a round number of miles for a piece in feet or kilometres for one in metres. The scale itself is always on the back label.
They go as one block of Cinzel capitals, as large as fits somewhere: at full size, then with the facts on two lines, then at 85% and at 72%, each size is tried 6 mm in from the window's bottom-left corner, then elsewhere in that quarter, then anywhere on the land, then in a border, as a column or as one row; then without the scale bar; and last the facts line alone. Under a lattice they look for land in a block big enough, and otherwise go in the lattice's border: on the 200 mm Lake Harriet they sit in one row along the bottom border, at 85%. When nowhere takes them they are left off, and the check says so.
The back label
Back label file adds a file of its own to the download, ending _back_label.svg, to engrave on the back of the backer. From the top it has the title; the coordinates, in degrees, minutes and seconds over decimal degrees; the facts with the number of layers and the scale - "MAX DEPTH 80 FT · 340 ACRES · 8 LAYERS · 1:6,887" on a 300 mm Lake Harriet (the facts only while Facts line is on); a table headed "LAYERS, FRONT TO BACK" with each sheet's depths and paint; the map's credits; your Maker line; and when the map was fetched - "MAP DATA RETRIEVED OCTOBER 2026".
- Maker line takes up to 80 characters - your name, a shop, a date or a dedication - and is engraved in capitals. It is saved when you leave the box or press Enter.
- Map credits on it - © OpenStreetMap contributors, USGS (outside the US, GeoNames) and the depth survey's, on by default - is the simplest way to carry the credit on a piece you sell.
- A label too big for the backer is tried smaller, down to half size, then without the table - the paint guide has it - then without the coordinates. If even that does not fit, there is no back label file.
- A paint change repaints its table, as it does the paint guide.
The file is engrave only. Its lettering is green (#00E000), the land's engraving colour, so one LightBurn fill setting serves both. The backer's outline, seen from the back, is cyan (#00FFFF), a guide to line the job up and not a cut: set the cyan layer to Output off. Run it before gluing up: cut the backer, then, without moving the stock, flip the backer left to right - its top stays at the top - drop it back into its hole in the stock and run the back label at the same origin. Its text reads the right way round on the back, and its outline, drawn mirrored, sits over the backer's.
Lakes are saved as you work
Settings are saved a moment after you change them. The picker at the top left lists every lake you have, and the account page lists them too, under Your projects, to open from any browser. Close lake puts the open lake away: from then on this browser sends nothing that would change it, until you choose it from the list again. Deleting asks once - the row says Delete for good? - and then cannot be undone. A lake's depth data and any file imported into it go with it. On Pay as you go, a lake deleted before its map arrived gives back the credits it cost, and one deleted after does not; the row says which when it asks - "No map yet: any credits it cost come back." or "Credits it cost are not returned."
You can keep up to 200 lakes, and up to 2 GB of them in all; at the limit, starting another says so, and deleting one makes room straight away. A lake is its map, its depth and every size built - a few MB for most, about 20 MB for Gun Lake with all three sizes, about 90 MB for the Lake of the Ozarks. At 2 GB the studio also refuses to fetch a map or a depth, import a survey or build a size a lake has not built yet - "This account's lakes already take 2.1 GB, and one account can keep 2.0 GB of lakes." - until you delete lakes you no longer need. Rebuilding the sizes a lake has, repainting and downloading are never held.
Workshop settings
Some settings belong to your workshop rather than to one lake: the sheets and stock you buy, your laser's bed, the paint you like. Change one of these on any lake and it is kept, and every new lake you start here begins with the last value you chose:
- Sheet thickness
- Depth units, feet or metres
- Shallowest water and Deepest water, the paint at both ends
- Bed width and Bed height, your laser's bed
- Smallest letters (mm)
- how the coordinates are Written as
- the Maker line
A saved lake keeps the settings it was made with: opening one changes none of its settings and none of the kept ones. Nothing about a map or a lake is kept - its frame, width, style, depth, title and subtitle - so a new lake still takes its name and state from the search; nor is Kerf. Reset to defaults, at the foot of the settings, puts a lake back to how a new lake starts here: the defaults, with your workshop settings, keeping the lake's own title and subtitle. The footer says it too - hover over workshop settings there for the list.
They are kept in this browser, not in your account: another browser, or a phone, starts from the defaults until you change them there. The frame's mm or in is remembered in this browser as well.
Common questions
Does any of this cost credits?
On Studio, and during its free trial, no: Lake Map Layers is included. On Pay as you go, starting a lake costs 100 credits, once per lake: choosing a lake or a town from the search starts one, and the line under the results says what it costs - Starting one: 100 credits - before you choose. Each lake is its own charge, so the same lake started twice is charged twice. A lake the studio cannot make is not charged, and with too few credits nothing is started: the line says how many you have, with Buy credits. After that the lake is free - fetching its map and depth, choosing another survey or importing one, every setting, building every size, rebuilding, repainting and every download, however often you do them. Lake Map Layers makes no AI call, so your own OpenAI key changes none of this.
Delete a lake before its map has arrived - the wrong lake, or a map that could not be fetched - and its credits come back; once its map has arrived, deleting it gives nothing back. The row says which when it asks. Your account page lists the charge as "Created a lake project: Gun Lake (pay as you go)", and a refund as "Refunded: lake project deleted before its map was fetched".
A lake you started while you had Studio or its trial is waiting to be paid for once you are on Pay as you go: the studio says "This lake was made while Lake Map Layers was free for you", and fetching, building or downloading it costs 100 credits once. Pay for this lake pays it, and it is free after that. Until then you can still open it, look at its previews and its paint guide, rename it and delete it.
Still stuck? Write to hello@mandalalayers.com — a person reads it, and a photograph of what came off your cutter helps more than a description.