Reading the lake check
The check on my lake says something. What does it mean?
Every build of a lake ends with a check. The studio does not list what it finds: the badge at the foot of the studio says whether the check passed, and every finding - errors, warnings and info - is written under THE CHECK in the README.txt in the download, each with its code, the sheet it is about when it is about one, and where on the sheet when it has a place. Each code has its section here.
Errors are things that will not cut, or will not line up, and the check fails while there is one. Warnings cut, and are things to know before you start the machine. A few findings are info: the studio telling you what it decided, with nothing for you to do. They are listed here with the warnings.
Wood and openings
Wood narrower than the minimum
errorthin_materialSomewhere on the sheet the wood is narrower than it can safely be cut. Where that narrow wood holds a part beyond it - a strip of land between the lake and a bay, a peninsula joined by a neck - it is an error, because the part can snap off while you weed the sheet. Where it is the tip of a point, held by the sheet behind, it is a warning.
The fixes, cheapest first: a larger piece, which widens everything; less Padding, which makes the lake larger in the same piece; a larger Narrowest wood under Cut limits, which, before the check, cuts away the land thinner than it - land a thin neck held on is left as a loose piece - and widens the pinches just about as wide as it; or a thicker material, which is stiffer at the same width.
A loose piece under the minimum size
warningtiny_pieceA piece of wood comes away from the sheet on its own and is smaller than the minimum - usually an island in the lake. Islands and shoals are cut loose on purpose and glued in place on the sheet behind - nothing is added across the water to hold them - and this one is small enough to lose in the weeding. Find it before you clear the bed, or make the piece larger so it is too.
An opening under the minimum size
warningtiny_holeA hole in the wood smaller than the minimum - a pond the size of a speck. It may not cut cleanly, and if it does it reads as a burn mark. A larger piece makes it larger; less padding does too.
A deeper opening reaches past the one in front of it
errornestingEach water sheet's opening has to sit inside the opening of the sheet in front of it, or the colours step the wrong way. This is a fault in the build, not in your settings: rebuild, and if it stays, send the lake's download to support.
The water
A band of water too narrow to read
warningnarrow_bandA ring of one water colour is narrower here than the minimum, so its colour may not read from a normal distance. It cuts and holds - the wood runs on behind the sheet in front - it just may not show. Fewer water colours, or a larger piece, widens it.
The deepest water is very small
warningdeepest_band_smallInformation. The deepest colour covers so little of the lake that it hardly shows, or was too small to cut at all and was merged into the one above. The message gives the deepest depth, so it can be engraved by hand at the deepest point if you want it seen.
A depth step cut away from its depth
warningdepth_movedWhere depth steps lie closer together on the piece than a band can be cut, each deeper step is pushed inside the one above it so that every band stays wide enough. This step was pushed far enough to notice. The message says how far and how much water it shows in a shallower colour. Fewer water colours, or a larger piece, follows the depths more closely. On a Stylized piece the depths are the studio's own estimate from the shoreline, so the steps it moved are one line of information instead, naming the steps and how many places; fewer water layers keep the steps where the estimate puts them.
Two depth steps merged
warningband_mergedInformation. A depth step was too narrow everywhere to cut, so it was merged into its neighbour and the piece has one colour fewer than asked for. The message names the depths.
How the depth steps were chosen
warningthresholds_noteInformation. A note on how the water was divided into colours: that fewer came out than Water colours asked for, and why; the even step that was used; or that a depth asked for is not shallower than the deepest water and was left out. With no depth data it says the water is one colour. Nothing to do.
Places the depth data does not cover
warningdepth_gapsPart of the lake has no depth in the data, and those places took the nearest depth it does give. The steps there are a guess. The message gives the share of the water it affects. A fuller survey fixes it: another one in the Depth section's list, or a file of your own through Import - see Where the depth comes from.
Depths estimated, not surveyed
warningstylized_depthThe depths come from the shape of the shoreline, not from a survey. The download says so in its file names, in every SVG, on the paint guide and in credits.txt. Say so on the piece too, wherever it is shown or sold.
The depth data
What the studio noticed about the depth data itself - a survey, a chart, a grid or a file you imported. Most of these are information: what it decided, so that a piece made from the data can be checked against the survey it came from.
Depth data covers only part of the lake
warningdepth_partial_coverageThe depth data describes only part of the lake on this piece - the message gives the share. The rest has no depth, so it is cut as water in the shallowest colour. NOAA's nautical charts are like this on the Great Lakes: they cover harbours and the water near the shore, not the open lake. The share is of the lake's water inside the frame, so a frame on just the surveyed part has none of it. A fuller survey, if the Depth section lists one, or a file of your own through Import, covers the rest.
Shoal depths the survey leaves uncertain
warningdepth_hump_ambiguousMichigan's lake maps draw a shoal - a hump rising from deeper water - with the same rings as a hole, and on some lakes the lines alone do not say which one a ring is. The studio read them both ways, and they disagree at the depths the message names, so those shallows may be cut a step too deep or too shallow. Check them against the survey's printed map before you cut; if they are wrong, Custom depths that skip that step, or another survey, avoid it.
Spot depths read as soundings
warningdepth_spots_as_soundingsInformation. The survey marks some single depths as tiny rings rather than lines - a spot sounding. They were used as single measured depths, not as contour lines, which is what they are. The message gives how many. Nothing to do.
Elevations turned into depths
warningdepth_elevation_convertedInformation. The data gave the height of the lake bed above a datum rather than a depth, and the depths were taken below the water level the message names - the one you typed for an import, or the lake's low water datum for a Great Lakes grid. If that level is wrong every depth is off by the same amount: import the file again with the right one.
Which way the grid's numbers run, read from the data
warningdepth_sign_inferredInformation. A Great Lakes depth grid does not say whether its numbers are depths, depths written as negative numbers, or elevations - heights above a datum. The studio read it from the values near the shore, and the message says which it took. If the deepest water on the paint guide looks like the shallowest, that reading was wrong; send the lake's download to support.
A note in the depth data's licence
warningdepth_licence_noteInformation. The service the depth came from attaches a note to its licence, quoted in the message - New Hampshire's surveys are "for planning purposes only; distribution is discouraged". It is in credits.txt too. Read it before you sell a piece made from that survey.
Data on the old NAD27 datum
warningdatum_shift_ignoredThe imported file is on the old North American Datum of 1927, and was used as if it were WGS84, which moves it by about the distance the message gives - tens of metres. On a large lake that is far less than a band; on a small one it can show as depths that sit off the shore. Check the depths line up with the shore on the map view; a copy of the file on NAD83 or WGS84 avoids it.
Depth data beyond the shoreline
warningdepth_outside_shoreInformation. Part of the depth data lies outside the lake's shoreline from USGS, which is the shore the piece is cut to, and was not used - the message gives the share. A survey drawn to a slightly different shoreline always has a little of this. Nothing to do unless the share is large, which means the survey and the shoreline are of different water.
The stack and the bed
A sheet whose outer edge differs
errorregistrationEvery sheet is cut with exactly the same outer edge, so the stack lines up when it is glued. This sheet's differs, or has none. This is a fault in the build, not in your settings: rebuild, and if it stays, send the lake's download to support.
The piece and the laser bed
warningbed_fitThe piece is larger than the laser bed the studio checks against, or fits it only turned 90 degrees. Turned is fine: turn it when you place it in your cutting program. Too large means a smaller Width or Height, or a larger machine. Each size is checked against the bed on its own; the Medium and Large are made to fit it with 10 mm to spare, so a Small that does not fit is the one to make smaller - see Sizes.
A tall stack
warningstack_heightSo many water colours that the stack is very thick, and the steps between them get hard to see and hard to glue square. Fewer water colours reads better.
Engraving
A label left off the land sheet
warningengraving_skippedYou asked for a title, coordinates or a compass and it could not go where it should: it was left off rather than engraved too small to read, or it went on the border. The message says which. A title placed In the map that does not fit even at 8 mm goes on the border; Top border or a shorter title makes room for words. A title too long for the border even at Smallest letters (mm) is left off, and the message says what makes room: a shorter title, or a wider border when the border is too shallow for the letters. A compass under 20 mm across - a piece under about 110 mm on its shorter side - is too small to read and is left off; one with no clear land in the bottom-right quarter of the map, even at 34 mm, goes on the border, or is left off when the border is narrower than about 11.5 mm, as a new lake's 7 mm is. Dragging the compass onto the land puts it there instead: a compass you placed looks for room in the whole map, and goes on the border only when there is none anywhere - see The compass and coordinates. More Padding leaves more land round the lake for it, and a wider Border makes room in the border. Under a lattice the compass is placed as on Lake Topo, on a solid plate of the lattice; one that finds no land goes in the bottom-right corner of the lattice's border, or the top-right. Lowering Smallest letters (mm) fits more, at the risk of letters that fill in.
The names on the map - towns, route markers, road names, lakes - are not findings: a crowded map always leaves some off.
Water too narrow to cut, engraved instead
warningwater_engravedInformation. Some of the map's water was too narrow or too small for the land sheet to cut - narrower than Narrowest water slot, like the tips of coves and creeks, or a pond under the smallest opening (on a Medium or Large, any pond the Small could not cut either: the message gives that size's limit, 12.2 mm² on a 740 mm Large made from a 300 mm design) - so the land sheet does not cut it out; it is engraved on the land instead, so the shoreline still reads. The message gives how much and in how many places. Nothing to do. To cut more of it, lower Narrowest water slot towards your kerf; to leave it bare wood, turn off Engrave water too narrow to cut - see Cut limits and engraved water.
Bridges
The map's own bridges are part of the land sheet - its wood, with each road scored across - and are checked with it; under a lattice they are strips of the lattice, checked with it. See Bridges.
A bridge left off the piece
warningbridge_left_outInformation. A bridge in the map is not on the piece, so its road stops at the water, and the message says why: one end does not reach the land sheet's wood (a bridge to an island too small to cut, one that runs off the frame, or one the map stops out in the water), it would cross the title's clear space, it lies inside a bigger bridge - another road's bridge that already covers it - or it runs so close beside a bigger bridge that, trimmed clear of it, it would be narrower than Narrowest wood. A bridge is joined to another road's bridge it meets, both roads scored across, rather than trimmed clear of it, unless the two could not be kept as one - and never when the map stops it out in the water; a bridge whose crossing lies on a bigger one, far enough in from its edges for its road to be scored, is part of that one and not listed. Nothing to do.
The lattice
The street lattice of the City Lattice and Lattice + Depth styles is checked as a sheet of its own - see The street lattice. Its thin wood and its openings are checked as every sheet's are, under Wood and openings; these are the lattice's own.
A loose piece of the lattice
warninglattice_loose_pieceInformation. A bit of street is cut off from the rest of the lattice - by the water, or by the edge of the window - so it comes away when the lattice is cut. It was kept, because it is at least 8 mm² and rests on the land where it can be glued, and its outline is scored in orange on the land sheet. The message names it and gives its size - "Lattice piece L1 (12 mm²) is not joined to the rest of the lattice: glue it on its orange outline on the land sheet." Glue it there once the lattice is on.
A lattice piece left out
warninglattice_piece_droppedInformation. A bit of street cut off from the rest of the lattice was left out rather than kept loose. It falls away with the opening round it. The message says why, which is one of these:
- it is under the 8 mm² smallest piece;
- it has no landing of 2 mm² on the land to glue it by;
- part of it lies over the water and it lands on the land at one end only, where it needs both, so that nothing hangs over the water by one end;
- it is a bridge deck whose own streets end at the shore, so no street of the lattice holds either end.
Nothing to do.
Lattice blocks too small to cut well
warninglattice_blocks_smallHalf the blocks between the streets are smaller than the size the message gives, under the 10 mm² a block needs to read, so the lattice reads as wood with holes in it rather than as streets, and it takes a long time to cut. The streets are a fixed width while the blocks shrink as the map takes in more ground. For a place, make the Map width narrower; for a lake, less Padding does the same. A bigger piece, or Lake Topo, cures it too.
Too few streets for a lattice
warninglattice_no_roadsA lattice style was chosen by hand for a map with fewer than 20 streets of the kinds a lattice is made of - "The map has 7 lattice streets, under the 20 a lattice needs to read as streets" - so the lattice is little more than its border. Auto would not have picked a lattice here: Lake Topo suits this map better, or a map that takes in more of the town.
Assembly marks
The alignment scores, hidden labels, depth legend and facts line, all set under Putting it together - see Putting it together.
An assembly mark that would show
errorassembly_mark_exposedAn alignment score or a hidden label is not wholly under the sheet in front of it, so it would show on the finished piece. The message names the sheet and how much of the mark is out. Widen the Border, or turn Alignment scores or Hidden labels off. If it stays with a wide border, send the lake's download to support.
The depth legend left off
warninglegend_skippedInformation. There was no room for the depth legend on clear land or in a border, even at its smallest, so it was left off. The message says whether the facts line went on without it. Less Padding, a wider Border or a bigger piece makes room; the paint guide says which colour goes on which sheet either way.
The facts line left off
warningfacts_skippedInformation. The facts line - the deepest water and the lake's area - was left off, and the message says why: there was no room for it on clear land or in a border, or the piece is of a place, which has no lake to measure. When it was left off for want of room, the back label still carries the facts, if it is on.
The cut files
Four checks look at the SVG files themselves - an element a cutter cannot cut, a transform, a grey that is not an operation, and a cut that does not close. They are the same checks Stepped Layers makes, and they are explained once, on its page: the cut files. On a lake they are all errors. Score lines are meant to be open and are never counted as unclosed cuts. The back label's file is checked the same way.
When the website turns a lake away
These are not findings of the check: they are a build, a download or a new lake that the website refused, or stopped, before it was done. The website shares one server among everybody building on it, so a lake is held to a few limits the Windows app does not have. Each message says what happened and what to do, and none of them changes the lake or charges anything.
A build that ran too long
"This build ran for more than 15 minutes, the longest one build may run on the server, so it was stopped. The sheets are as they were before." (build_timed_out) A build stops at the next point it can stop cleanly, which for the largest lakes can be two or three minutes after the 15, so the overlay may stay up a little longer before this message comes. Build a smaller size, or fewer depth steps - fewer Water colours - or try again when the server is less busy.
A build too big for the server's memory
"Building the Large (… x … mm) needs about … GB of memory, more than this server can give one build (… GB). Nothing was built." (build_too_big) The memory a lake build needs grows with the size of the piece, and a size that needs more than the server can give any one build is refused before it starts. The message says what does fit: a smaller size - "Build the Medium (520 x 520 mm) instead: it fits." - or, when no size does, the largest piece that would: "Make the piece no larger than … x … mm and build it again." When no piece would, it says "This server cannot build this lake. Try it in the Windows app.", which builds on your own PC.
Waiting for room in the server's memory
While other lakes are building, a build that would not fit beside them waits, and the overlay says Waiting for room in the server's memory.... When room comes it builds as usual, and Cancel stops the wait. If none has come within 20 minutes it gives up: "Waited 20 minutes for room in the server's memory, which other builds are using." (server_busy) Nothing was built or charged, and your lake is unchanged: try again in a few minutes.
A map already downloading
"A map is already downloading for this account." (fetch_running) One map or depth download runs at a time for each account - Fetch the map, Fetch again or use this on a survey, for any of your lakes. Wait for it to finish, then press it again; nothing has changed. Importing a survey of your own is not held up by it.
The server busy with other maps
"The server is fetching other maps." (server_busy) The server downloads two maps at a time for everybody using it, and a few more wait their turn. Yours found no place within two minutes, or the line was already full. Nothing has changed: press it again in a moment.
As many lakes as an account can keep
"This account already keeps 200 lakes, which is as many as one account can." or "This account's lakes already take 2.0 GB, and one account can keep 2.0 GB of lakes." (shelf_full) An account keeps up to 200 lakes, and up to 2 GB of them in all - a lake is its map, its depth and every size built. At 200 a new lake is refused; at 2 GB so are fetching a map or a depth, importing a survey and building a size a lake has not built yet. Delete lakes you no longer need from the picker at the top left, then try again: the room comes back straight away. Rebuilding the sizes a lake has, repainting and downloading are never refused for it.
A lake waiting to be paid for
"This lake was made while Lake Map Layers was free for you (on Studio or its trial)." (lake_not_paid) A lake started while it was included costs 100 credits once on Pay as you go, the first time you fetch, build or download it. Press Pay for this lake to carry on with it, or choose Studio, where Lake Map Layers is included. See Does any of this cost credits?
Not enough credits for a new lake
"Creating a lake project costs 100 credits on pay as you go, and you have 40." (insufficient_credits) Nothing is started. Buy a pack on your account page - fetching its map, building it and downloading it afterwards are free - or choose Studio, where Lake Map Layers is included. Pay for this lake says the same when the account is short: "Carrying on with this lake on pay as you go costs 100 credits once, and you have 40."
Too far from the place
"This is too far from the place this project is for." (centre_too_far) A piece started from a town keeps its middle within 25 km of it. Start a new lake project from the search for a different place - see Framing a place.
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.