mirror of
https://github.com/lrnselfreliance/wrolpi.git
synced 2026-11-20 23:16:17 -05:00
* The map can choose a 1:24,000 quadrangle to export (#971) The first part of exporting a map as a PDF: a grid of 7.5-minute quadrangles is drawn over the map, and a click chooses one. The grid is arithmetic, so it needs no data. Exporting itself is not here yet; the button is disabled. Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * A quadrangle of the map is exported as a PDF with a layer for each map layer (#972) * A quadrangle of the map is exported as a PDF with a layer for each map layer The browser draws the quadrangle off the screen at the size of a 1:24,000 sheet, once for each layer which is on, and the API puts the images in a PDF, each in a layer of its own which a reader can show and hide. A layer in which nothing is drawn is left out. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * The exported map's canvas keeps what was drawn, and an export's memory is bounded - The drawing buffer is asked for where this MapLibre reads it (canvasContextAttributes); as an option of the map it was ignored, so the canvas could be read after it was cleared. - Each layer's pixels are compressed in the PDF as the layer is added. PyMuPDF kept them uncompressed until the PDF was written: about 90 MB a layer of a quadrangle, all at once. - The pixels of all the layers together are limited, before any image is decoded. - pymupdf is imported when a PDF is made, not when the API starts. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * An exported map says where on the Earth it is (#973) * An exported map says where on the Earth it is The PDF's page has a geospatial viewport (ISO 32000-2): the page is the map in Web Mercator, with the latitude and longitude of each corner. The corners are the edges of the picture the browser drew, read from the map which drew it. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * A map whose edge is the antimeridian can be exported The map's arithmetic puts the east edge of the last quadrangle before the antimeridian a rounding error past 180 degrees, and the export was refused. An edge within 1e-8 of a degree of 180 is at 180 (it is not wrapped to -180); a map which is really across the antimeridian is still refused. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * An exported map is on a sheet: a margin, a grid, scale bars and notes (#974) * An exported map is on a sheet: a margin, a grid, scale bars and notes The map is put on a larger page with what a topographic map has around it: a title, the latitude and longitude of its corners and of ticks between them, scale bars (kilometers, miles, feet), and notes of the projection, the grid and where the map's data is from. Over the map is a 1,000 meter UTM grid, each line named in the margin. The grid and the margin are PDF layers of their own. The PDF says where the map is, not where the page is. The picker has a box to export the map alone. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * The scale of a narrow map is written under its name, not over it A quadrangle near a pole is two inches wide, which is not room for its name and its scale on one line. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * An exported map says where a compass points (#975) * An exported map says where a compass points The sheet has a diagram of the three norths (true, grid and magnetic) beside its scale bars, and a note of how far magnetic north is from true north on the day the map was made, and how fast it moves. The declination is from the World Magnetic Model 2025 (NOAA NCEI and the British Geological Survey; public domain), whose coefficient file is shipped: nothing is downloaded. The model is good until 2030; outside its years nothing is said of a compass. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * A corner of an exported map is not also a tick The edges of the picture the browser draws are a hair outside the quadrangle's, so the quadrangle's own edges were taken for ticks inside the map, and each was written over the coordinate of its corner. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * A compass which passes due south has moved a little, not most of the way around Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * A map can be exported at 400 DPI (#976) The picker has a choice of 300 or 400 DPI. A map is drawn less sharp than was asked for, rather than refused, when it would be more pixels than the API makes a PDF of: a quadrangle near the equator, or one with many layers on. The picker says so while it draws. Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * An exported quadrangle goes by the name the USGS gives it (#977) * An exported quadrangle goes by the name the USGS gives it The picker says what the chosen quadrangle is called, and the sheet's title, the PDF's title and the file's name have it. Where the USGS has no name, which is most of the world, a quadrangle goes by where it is, as before. The names are an index of the 65,600 7.5 minute quadrangles of The National Map (U.S. Geological Survey; public domain), which is shipped: nothing is downloaded. In Alaska a USGS quadrangle is wider than 7.5 minutes, so a quadrangle of the picker's grid there is "Part of" the one which has its middle. The places the tests of the map export are of are changed for others. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * An area half of which is the last quadrangle of the land is a part of it The middle of such an area is on the quadrangle's east or north edge, with no quadrangle beyond it, and it was given no name. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * The PDF of a map is made by a Job, which the browser watches (#978) * The PDF of a map is made by a Job, which the browser watches A PDF of a quadrangle is a minute or two of work on a Raspberry Pi 4, and the request which waited for it was cut off after a minute: only the smallest quadrangles could be exported there. Now the browser describes the map, sends the image of each layer in a request of its own, and starts a Job; it watches the Job, shows how far along it is, and fetches the PDF when the Job is done. Cancel stops the Job. The images are kept on disk until the PDF is made of them, and an export is removed when it is an hour old. The credits on the sheet are no longer cut off: an attribution which names many sources is each of them. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * A cancelled map export stops, and is removed - A cancelled Job is not over until the thread making the PDF has stopped, so the next Job does not start beside it; the work can also be stopped while the sheet is drawn and the PDF written. - DELETE /api/map/export/<id> stops an export at any step and removes what was sent; the browser calls it when the person exporting cancels, while layers are sent as well as while the PDF is made. - An export whose Job is waiting or running is not removed for being old; one whose Job was cancelled is removed at once. - Cancel while the map is drawn stops the drawing between two layers. - Exports are kept in a directory made for this user alone, which is refused when it is a link or is another user's; only what is an export there is removed. - A request for the finished PDF which is lost is made again. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * An overlay's areas and lines go under the map's labels, and its own labels over them (#979) An overlay was drawn whole over the basemap, so an area it filled covered the names of what is in it. Labels are now always on top: the areas, lines and pictures of every overlay are under the basemap's labels, and the text, icons and points of every overlay are over them. It is so in the map, the standalone viewer, and an exported PDF, where an overlay with both is two layers ("Towers" and "Towers (labels)"). Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * An overlay's ground is over the ground of every basemap file (#980) * An overlay's ground is over the ground of every basemap file On a map of several basemap files, the ground of an overlay was put before the first label of the first file, which is under the land, water and roads of every file after it: an overlay's areas and lines were hidden, and in an exported PDF its layer was just above the background. It goes where the basemap's labels begin: the first of the labels which are over all of the basemap's ground. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * The labels of every basemap file are over the ground of every file A map of several basemap files was their layers one file after another, so only the labels of the last file were on top: the labels of the others were under the land, water and roads of the files after them, and under the ground of an overlay. Both viewers now draw the ground of every file and then the labels of every file. The contour lines are drawn after the basemap's labels and are not of the basemap: an overlay's ground goes under the basemap's labels, not under the contours instead. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * Contours are drawn from as deep as the terrain file goes (#981) The map read a terrain file to zoom 8, which is how deep the terrain WROLPi offers goes, however deep the file was. It now reads a file as deep as the file says it goes, in both viewers, and draws finer contour lines from a deeper file: every 40 feet (or 20 meters) from zoom 11, as a 1:24,000 sheet has. A file which goes to zoom 8 is drawn as it was. Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * An exported map names its small roads (#982) * An exported map names its small roads A quadrangle is drawn at about zoom 13. The basemap's style names small roads from zoom 15, and its tiles have no names for them below zoom 14, so the streets of a town were printed as lines with no names. Before the map is drawn, the tiles of zoom 14 which the quadrangle is in are read, and the roads in them which have a name are given to the export map as a source of its own. The layer which names small roads draws from that source, as its style says to. At the scale of a sheet most streets are shorter than their names, and a map writes a name along a line only where the line is longer. Such a road is named over its middle, turned as the road goes; a road in pieces is named once. A source whose tiles can not be read is exported as before. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * The names of small roads are placed by the export, at every latitude A quadrangle nearer the equator is drawn at a little over zoom 14, where the names were not read and the style still kept them for zoom 15: such a map had no names of small roads. They are now read wherever a layer would not name roads. Every name of a small road is now a point: over the middle of its road, turned as the road goes under it, again every 400 pixels of a long road. Before, a road long enough was left for the map to name along its line, which the map often does not (the line bends, or is in pieces), and a short piece beside it was named too. One place decides where a road is named, so a road in pieces is named once, and a piece of another kind of road does not take the name. Reading the names can be cancelled. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * A sheet has a bar of meters, its norths in mils, and how far apart its contour lines are (#983) Under the map are bars of kilometers, meters, miles and feet. How far the grid's north and a compass's north are from true north is written in mils as well as in degrees, in the diagram and in the notes: a compass may be marked in either. A map which is exported with its contour lines says how far apart they are (CONTOUR INTERVAL 40 FEET), under the bars. The browser knows: it is the interval of the tiles the lines are made for at the zoom of the sheet, in the unit the map measures in. It says so with the sheet, and what is not an interval is not written. Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * A sheet says what the quadrangles around it are called (#984) * A sheet says what the quadrangles around it are called Under the scale bars is a diagram of nine squares, the map the middle one, and beside it what the USGS calls each of the eight around it: the sheets to print to carry on off the edge of this one. The names are from the index of quadrangles which names the sheet itself. A quadrangle with no name (out to sea, or over a border) has no number; a map of where the USGS names nothing, and a map too narrow for the diagram, go without. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * A sheet is never beside itself Where a quadrangle of the USGS is wider than the map (Alaska), the area the size of the map to its east or west is often more of the quadrangle the map is in, and the diagram named the sheet as its own neighbor. The quadrangle on a side is now the next one which is not the map's own. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * A sheet has a legend of the lines of its map (#985) * A sheet has a legend of the lines of its map Under the scale bars is what each kind of line of the map is: highway, major road, minor road, path, railway, boundary, contour and index contour, each a piece of the line as the map draws it, on the color of the map's land. The map's style says how a line is drawn at each zoom, and a sheet is drawn at one. The browser, which has the style, says what each line's color, width, dashes and edges are at that zoom; the API draws them. A line is in the legend when its layer is exported and draws something at that zoom. What the browser sends is made into lines before it is kept: what is not a line is left out, and the map is exported. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * A legend has no line too thin to see, and no name longer than its room A style brings a line in from nothing as the map is zoomed in: a path is a few hundredths of a point wide on a quadrangle near the equator. It was in the legend, drawn several times wider than on the map. A line under a tenth of a point is now left out, by the browser and by the API. What a line is called is cut to the room beside its line, as the name of an adjoining quadrangle is. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * Fixes to the map PDF export: wrong neighbors, leftover exports, exports which outlive the map (#989) * A sheet names what is around it, and its edges, by where they are and not a hair from there The edges the browser gives of a map are a hair outside its quadrangle. The quadrangles around a map whose middle is on the edge two share (every other map of Alaska) were those around the map west of it, and one of them was the map itself. An edge a hair south of the equator was 0 degrees south, a map which ended where the UTM zones do had no grid, and a sheet dated in the last year there is could not be made. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * An export is removed when it is over, and its work stops when the API does The images and the PDF of an export were kept until the next export began, however long that was. The browser now has the export removed however it ends, and old exports are removed when a PDF is made too. The work of a Job which ended because the API was stopping went on to the end of the PDF, with the API waiting for it. What is said of an export, and each image, is written whole. Text which is no text is taken out when an export begins, not found by the Job. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * An export stops with its map, and waits for a page which can not be seen Leaving the map while it was exported left the export going, to fail or to hand a PDF to another page; so did closing the picker, which is now left open. A PDF which arrives after the export was stopped is not saved. The time a page is behind another tab is not counted against a map which is drawing. The name of a road is one line. A photograph which ends a little inside the map is not made a JPEG with a black strip. An accent in the name of a quadrangle is not a gap in the name of its file. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * A PDF is not kept from who made it by a server slow to remove the export Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * An exported map has its water over its parks (#990) * A sheet names what is around it, and its edges, by where they are and not a hair from there The edges the browser gives of a map are a hair outside its quadrangle. The quadrangles around a map whose middle is on the edge two share (every other map of Alaska) were those around the map west of it, and one of them was the map itself. An edge a hair south of the equator was 0 degrees south, a map which ended where the UTM zones do had no grid, and a sheet dated in the last year there is could not be made. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * An export is removed when it is over, and its work stops when the API does The images and the PDF of an export were kept until the next export began, however long that was. The browser now has the export removed however it ends, and old exports are removed when a PDF is made too. The work of a Job which ended because the API was stopping went on to the end of the PDF, with the API waiting for it. What is said of an export, and each image, is written whole. Text which is no text is taken out when an export begins, not found by the Job. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * An export stops with its map, and waits for a page which can not be seen Leaving the map while it was exported left the export going, to fail or to hand a PDF to another page; so did closing the picker, which is now left open. A PDF which arrives after the export was stopped is not saved. The time a page is behind another tab is not counted against a map which is drawing. The name of a road is one line. A photograph which ends a little inside the map is not made a JPEG with a black strip. An accent in the name of a quadrangle is not a gap in the name of its file. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * An exported map has its water over its parks A layer of the PDF was one image, drawn where the topmost of its layers is. The parks of Land Cover are under the water on the map and its piers are over it, so all of Land Cover was drawn over the water: a lake in a park, or among houses, was not on the PDF. A second basemap file put its water over the first's buildings. A layer is now as many images as it must be, each where it is on the map, in one layer of the PDF: a part which fills an area stays where it is, and a part which is only lines is drawn with the next. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * A PDF is not kept from who made it by a server slow to remove the export Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * A map file which is of somewhere else is not drawn when a map is exported Each basemap file is several images of an exported map, and most files of a library are of other places: each was an image of nothing, counted against how many images an export may be and how sharp it may be. A file whose own edges are outside the quadrangle is now left out before the layers are counted. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * An exported map has its streams (#991) A basemap draws streams from zoom 14, and service roads and taxiways from 13. A quadrangle is drawn a little short of that (zoom 13.8 at 40 degrees, 13.2 at 61), from tiles which have them: none were on the PDF. What is drawn from a zoom no deeper than a quadrangle's detail is drawn. Names are left as they are. Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * An export which is cancelled stops at once, in the middle of a request (#993) * An export which is cancelled stops at once, in the middle of a request An export was stopped between two requests. The image of a layer is tens of megabytes, which is a long request on a slow connection, and a request to a server which has stopped answering never ends: the export said it was stopping until then. Cancel, and leaving the map, now end the request. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * The requests an export makes after its layers are sent are seen to be stopped too Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * A map is exported as it is printed: on white, in dark lines (#996) * A map is exported as it is printed: on white, in dark lines The light and dark maps are made for a screen. On paper their roads are white on pale gray and their streams half a pixel of pale blue. The printed map is a third look, of the map's own: white ground, dark road edges and names, blue streams wide enough to see, paths drawn, brown contours. It is what a map is exported in unless Light or Dark is chosen where the quadrangle is, and the choice is remembered in the browser. While a quadrangle is chosen the map is shown in the look it will be exported in. The light and dark maps are as they were. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * Changing the look of the map does not move it What is done when a new style is in place was asked for after the style was set. A style which only differs from the one the map has is in place before that, so it was done at the next change of style instead, with where the map had been at this one: the map went back there when a quadrangle was chosen, and again when it was not. It is asked for first, and the map is not moved at all. An export no longer waits for the map to be still, which it need not and which nothing ended. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * The colors of the printed map are chosen where its layers are (#997) * The colors of the printed map are chosen where its layers are While a quadrangle is chosen and the map is shown as it is printed, each layer of the layer control has its color beside it, to be changed: one for most, three for the land (what grows, what was built, sand and ice) and two for names (the name, and what is around it). A basemap has several colors where one is chosen, which are shades of it. The edge of a road stays dark. What is chosen is remembered in the browser, and can be put back. The map on the screen is as it was. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * A ramp on a bridge is the color of a major road, as it is off one A basemap draws a ramp on a bridge in the color of a minor road on a bridge: on the printed map it was white where the rest of the ramp is yellow, and followed the color chosen for minor roads. What puts the colors back is a button, which a keyboard reaches. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * A layer with nothing in it does not make an exported map less sharp (#1001) * A layer with nothing in it does not make an exported map less sharp How sharp a map may be depends on how many images it is, and every group of layers was counted: a basemap file with no runway, highway or boundary in the quadrangle was images of nothing, drawn, sent, and counted against the rest. A map of 23 images asked for at 400 DPI was made at 330. The groups are now looked at first, on a small map, and only those with something in them are drawn, as sharp as that many may be. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * An image which arrives after its export was removed is not kept, and one mil is a mil Stopping an export while an image was on its way left the image behind it, in a directory nothing would remove for an hour. An angle of one mil was "1 mils" on the sheet. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * The map which is exported from is made as sharp as it is to be (#1002) * The map which is exported from is made as sharp as it is to be The groups of a map are looked at on a small map, which was then made larger to draw them. A browser lets a canvas be larger when it is made than it lets one be made larger afterwards: a quadrangle asked for at 400 DPI was 33 million pixels, 288 DPI at 40 degrees, less than before the groups were looked at first. The small map is now removed, and the map which is exported from is made in its place. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * A canvas the browser stopped drawing on is not a layer with nothing in it A canvas whose drawing was taken away by the browser reads as clear, and a group looked at then was left out of the PDF without a word: the export fails instead. An export stopped as the last group is looked at does not make the map it would have been drawn on. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * An exported map says where it is in a projection Adobe Acrobat knows (#1003) * An exported map says where it is in a projection Adobe Acrobat knows The page was said to be in Web Mercator, which it is drawn in. Acrobat does not know Web Mercator, in the words of the standard or in Esri's: it took the page for a map, and put every place on it at 0, 0. The page is now said to be Mercator on the WGS 84 ellipsoid, which it reads, with the same corners. Between the corners the two differ by under three centimeters on the ground. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * How well a page is said to be where it is, is measured from what the PDF says The test of it measured two formulas of its own. It now reads the corners and the projection from the PDF and does a reader's sum with them. The few centimeters are of a quadrangle: a taller page is less well said, by the square of how tall it is, which the comment now says and a test measures. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> * The help says how a map is exported as a PDF (#1004) The help of the map is five pages, one of them the PDF export. Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
397 lines
17 KiB
JavaScript
397 lines
17 KiB
JavaScript
// Which map files a viewer draws, and how it draws the ones that are not a Protomaps basemap.
|
|
//
|
|
// SHARED by the map viewer of the app and the standalone viewer (modules/map/static/index.html),
|
|
// which loads the copy in modules/map/static/js/. It must stay a plain ES module a browser can
|
|
// load as it is: no imports from packages, and relative imports with their `.js`. After changing
|
|
// it, run `npm run sync:map-shared`; a test fails while the copy differs.
|
|
//
|
|
// What differs between the viewers is passed in as `urls`: `{pmtiles(file), style(file)}`, the
|
|
// URL of an overlay's PMTiles file (`pmtiles://...`) and of the style beside it.
|
|
//
|
|
// The API says what each PMTiles file is (`kind`): a `basemap` is drawn with the basemap theme,
|
|
// `terrain` becomes hillshade and contours, and an `overlay` is any other vector or raster file.
|
|
// An overlay has no style of its own, so its layers are drawn generically: one color per layer,
|
|
// as fills, lines or circles.
|
|
|
|
export function escapeHtml(value) {
|
|
return String(value)
|
|
.replace(/&/g, "&")
|
|
.replace(/</g, "<")
|
|
.replace(/>/g, ">")
|
|
.replace(/"/g, """)
|
|
.replace(/'/g, "'");
|
|
}
|
|
|
|
// Every MapLibre source and layer of an overlay starts with this, so the basemap's layer groups
|
|
// (which match layer names like "water") never touch them.
|
|
export const OVERLAY_PREFIX = "overlay:";
|
|
export const STORAGE_KEY_OVERLAYS = "wrolpi-map-overlays";
|
|
|
|
const RASTER_SUFFIX = "raster";
|
|
const VECTOR_TYPES = ["fill", "line", "circle"];
|
|
// Readable on both the light and dark basemaps.
|
|
const OVERLAY_COLORS = [
|
|
"#e6194b", "#3cb44b", "#4363d8", "#f58231", "#b455e0", "#17a2a2",
|
|
"#f032e6", "#b07a3b", "#d1495b", "#8a9a1b", "#5b7fff", "#e6a700",
|
|
];
|
|
const POPUP_MAX_FEATURES = 3;
|
|
const POPUP_MAX_PROPERTIES = 12;
|
|
|
|
// Detect full planet files: "planet-20260329.pmtiles" or bare date like "20260329.pmtiles".
|
|
export function isPlanetFile(name) {
|
|
if (name.startsWith("planet-")) return true;
|
|
return /^\d{8}\.pmtiles$/.test(name);
|
|
}
|
|
|
|
// A path as part of a URL: each of its parts is encoded (a `#` or `?` in a file name would
|
|
// otherwise end the path).
|
|
export function encodePath(path) {
|
|
return String(path).split("/").map(encodeURIComponent).join("/");
|
|
}
|
|
|
|
// Sort the map files into what the viewer does with each. Ignored files (`visible: false`) and
|
|
// unreadable files are left out. A planet file covers everything, so it replaces the regional
|
|
// extracts; overlays and terrain are drawn either way.
|
|
export function planMapFiles(files) {
|
|
const visible = (files || []).filter(f => f.visible !== false);
|
|
const basemaps = visible.filter(f => f.kind === "basemap");
|
|
let planet = null;
|
|
for (const f of basemaps) {
|
|
if (isPlanetFile(f.name) && (!planet || f.size > planet.size)) planet = f;
|
|
}
|
|
const terrains = visible.filter(f => f.kind === "terrain");
|
|
return {
|
|
planet,
|
|
regions: planet ? [] : basemaps,
|
|
terrain: terrains.length ? terrains[terrains.length - 1] : null,
|
|
overlays: visible.filter(f => f.kind === "overlay"),
|
|
};
|
|
}
|
|
|
|
export function isRasterOverlay(file) {
|
|
return file.tile_type !== "mvt";
|
|
}
|
|
|
|
// Whether the overlay is drawn with a style which came beside the file (see mapOverlayStyle.js).
|
|
export function isStyledOverlay(file) {
|
|
return !isRasterOverlay(file) && Array.isArray(file.styleLayers) && file.styleLayers.length > 0;
|
|
}
|
|
|
|
// The layers of a vector overlay the user can show and hide: all of them, or with its own style
|
|
// only those the style draws.
|
|
export function overlayToggleLayers(file) {
|
|
if (isRasterOverlay(file)) return [];
|
|
const layers = file.vector_layers || [];
|
|
if (!isStyledOverlay(file)) return layers;
|
|
const drawn = new Set(file.styleLayers.map(l => l["source-layer"]));
|
|
return layers.filter(l => drawn.has(l.id));
|
|
}
|
|
|
|
function fileStem(name) {
|
|
return String(name).replace(/\.pmtiles$/, "");
|
|
}
|
|
|
|
// What to call an overlay: the name the file gives itself, else its file name. Files which would
|
|
// share a label also show where they are.
|
|
export function overlayLabel(file, files = []) {
|
|
const base = f => (f.title && f.title.trim()) || fileStem(f.name);
|
|
const label = base(file);
|
|
const shared = files.some(f => f.map_path !== file.map_path && base(f) === label);
|
|
return shared ? `${label} (${file.map_path})` : label;
|
|
}
|
|
|
|
// A stable color for a layer: the same layer name is the same color in every file and session.
|
|
export function overlayColor(layerId) {
|
|
let hash = 5381;
|
|
for (const c of String(layerId)) hash = ((hash * 33) ^ c.charCodeAt(0)) >>> 0;
|
|
return OVERLAY_COLORS[hash % OVERLAY_COLORS.length];
|
|
}
|
|
|
|
// --- What the user chose to see. {[map_path]: {enabled: bool, layers: {[layerId]: bool}}} ---
|
|
|
|
export function loadOverlayState() {
|
|
try {
|
|
const saved = JSON.parse(localStorage.getItem(STORAGE_KEY_OVERLAYS));
|
|
if (saved && typeof saved === "object" && !Array.isArray(saved)) return saved;
|
|
} catch (e) { /* ignore */ }
|
|
return {};
|
|
}
|
|
|
|
export function saveOverlayState(state) {
|
|
try { localStorage.setItem(STORAGE_KEY_OVERLAYS, JSON.stringify(state)); } catch (e) { /* ignore */ }
|
|
}
|
|
|
|
// An overlay is hidden until the user turns it on.
|
|
export function isOverlayEnabled(state, file) {
|
|
return state?.[file.map_path]?.enabled === true;
|
|
}
|
|
|
|
// The layers of the schemas a basemap is commonly made in (Protomaps, which the map's own basemap
|
|
// is, and OpenMapTiles). A file which also has other things often carries these too, and drawing
|
|
// them again over the basemap doubles every road and label.
|
|
const BASEMAP_LAYERS = new Set([
|
|
// Protomaps
|
|
"earth", "water", "roads", "landuse", "landcover", "buildings", "boundaries", "places", "pois",
|
|
"transit", "natural", "physical_line", "physical_point",
|
|
// OpenMapTiles
|
|
"waterway", "water_name", "landuse", "landcover", "park", "boundary", "aeroway", "aerodrome_label",
|
|
"transportation", "transportation_name", "building", "place", "poi", "mountain_peak",
|
|
]);
|
|
|
|
// Whether a layer of an overlay is of something the basemap already draws.
|
|
export function isBasemapLayer(layerId) {
|
|
return BASEMAP_LAYERS.has(String(layerId ?? "").toLowerCase());
|
|
}
|
|
|
|
// Once a file is on, each of its layers is as the user chose. A layer the user has not chosen for
|
|
// is drawn, unless the basemap already draws the same thing.
|
|
export function isOverlayLayerEnabled(state, file, layerId) {
|
|
const chosen = state?.[file.map_path]?.layers?.[layerId];
|
|
return typeof chosen === "boolean" ? chosen : !isBasemapLayer(layerId);
|
|
}
|
|
|
|
export function setOverlayEnabled(state, file, enabled) {
|
|
return {...state, [file.map_path]: {...state?.[file.map_path], enabled}};
|
|
}
|
|
|
|
export function setOverlayLayerEnabled(state, file, layerId, enabled) {
|
|
const entry = state?.[file.map_path] || {};
|
|
return {...state, [file.map_path]: {...entry, layers: {...entry.layers, [layerId]: enabled}}};
|
|
}
|
|
|
|
export function setAllOverlayLayersEnabled(state, file, enabled) {
|
|
const layers = {};
|
|
for (const l of overlayToggleLayers(file)) layers[l.id] = enabled;
|
|
return {...state, [file.map_path]: {...state?.[file.map_path], layers}};
|
|
}
|
|
|
|
// --- MapLibre style ---
|
|
|
|
export function overlaySourceId(file) {
|
|
return `${OVERLAY_PREFIX}${file.map_path}`;
|
|
}
|
|
|
|
export function isOverlayLayerId(layerId) {
|
|
return String(layerId).startsWith(OVERLAY_PREFIX);
|
|
}
|
|
|
|
// MapLibre puts a source's attribution in the page as HTML, and this text comes from a file
|
|
// someone downloaded: only its text is kept.
|
|
function attributionText(attribution) {
|
|
if (!attribution) return undefined;
|
|
const text = new DOMParser().parseFromString(String(attribution), "text/html").body.textContent || "";
|
|
return text.trim() ? escapeHtml(text.trim()) : undefined;
|
|
}
|
|
|
|
export function buildOverlaySource(file, urls) {
|
|
const source = {type: isRasterOverlay(file) ? "raster" : "vector", url: urls.pmtiles(file)};
|
|
if (isRasterOverlay(file)) source.tileSize = 256;
|
|
const attribution = attributionText(file.attribution);
|
|
if (attribution) source.attribution = attribution;
|
|
return source;
|
|
}
|
|
|
|
// The geometry a generator recorded for a layer ("Point", "LineString", "Polygon") names the one
|
|
// way to draw it. Without that, the layer is drawn all three ways, each limited to its geometry.
|
|
const TYPE_OF_GEOMETRY = {Polygon: "fill", LineString: "line", Point: "circle"};
|
|
const GEOMETRY_OF_TYPE = {fill: "Polygon", line: "LineString", circle: "Point"};
|
|
|
|
function paintOf(type, color) {
|
|
if (type === "fill") return {"fill-color": color, "fill-opacity": 0.25, "fill-outline-color": color};
|
|
if (type === "line") return {"line-color": color, "line-width": 1.5};
|
|
return {
|
|
"circle-color": color, "circle-radius": 4,
|
|
"circle-stroke-color": "#ffffff", "circle-stroke-width": 1,
|
|
};
|
|
}
|
|
|
|
// The style layers of an overlay file, each already visible or hidden as `state` says; a source
|
|
// with no visible layer requests no tiles.
|
|
export function buildOverlayLayers(file, state) {
|
|
const source = overlaySourceId(file);
|
|
const enabled = isOverlayEnabled(state, file);
|
|
const visibility = on => (on ? "visible" : "none");
|
|
|
|
if (isRasterOverlay(file)) {
|
|
return [{
|
|
id: `${source}:${RASTER_SUFFIX}`, type: "raster", source,
|
|
layout: {visibility: visibility(enabled)},
|
|
}];
|
|
}
|
|
|
|
if (isStyledOverlay(file)) {
|
|
// The file came with its own style: its layers, each shown when the file and its source
|
|
// layer are on (and the style does not itself hide it).
|
|
return file.styleLayers.map(layer => ({
|
|
...layer,
|
|
layout: {
|
|
...layer.layout,
|
|
visibility: visibility(enabled && layer.layout?.visibility !== "none"
|
|
&& isOverlayLayerEnabled(state, file, layer["source-layer"])),
|
|
},
|
|
}));
|
|
}
|
|
|
|
const styleLayers = [];
|
|
for (const layer of file.vector_layers || []) {
|
|
const color = overlayColor(layer.id);
|
|
const known = TYPE_OF_GEOMETRY[layer.geometry];
|
|
for (const type of known ? [known] : VECTOR_TYPES) {
|
|
const styleLayer = {
|
|
id: `${source}:${layer.id}:${type}`,
|
|
type,
|
|
source,
|
|
"source-layer": layer.id,
|
|
layout: {visibility: visibility(enabled && isOverlayLayerEnabled(state, file, layer.id))},
|
|
paint: paintOf(type, color),
|
|
};
|
|
if (!known) styleLayer.filter = ["==", "$type", GEOMETRY_OF_TYPE[type]];
|
|
styleLayers.push(styleLayer);
|
|
}
|
|
}
|
|
return styleLayers;
|
|
}
|
|
|
|
// Whether a layer of an overlay is of its labels: its text, its icons, and the points it marks. The
|
|
// rest of an overlay is its ground: areas, lines, pictures.
|
|
export function isOverlayLabelLayer(layer) {
|
|
return layer?.type === "symbol" || layer?.type === "circle";
|
|
}
|
|
|
|
// The style layers of every overlay, in the order they are drawn. Labels are always on top: the
|
|
// ground of every overlay goes under the basemap's labels (`under`), so an area an overlay fills
|
|
// does not cover the name of what is in it, and the labels of every overlay go over them (`over`).
|
|
// In each, a raster is lowest, then an overlay with its own style in that style's order, then the
|
|
// generic ones, fills under lines under points.
|
|
export function orderOverlayLayers(overlays, state) {
|
|
const rasters = [];
|
|
const styled = [];
|
|
const generic = {fill: [], line: [], circle: []};
|
|
for (const file of overlays || []) {
|
|
const layers = buildOverlayLayers(file, state);
|
|
if (isStyledOverlay(file)) {
|
|
styled.push(...layers);
|
|
continue;
|
|
}
|
|
for (const layer of layers) {
|
|
if (layer.type === "raster") rasters.push(layer);
|
|
else generic[layer.type].push(layer);
|
|
}
|
|
}
|
|
const vectors = [...styled, ...generic.fill, ...generic.line, ...generic.circle];
|
|
return {
|
|
under: [...rasters, ...vectors.filter(layer => !isOverlayLabelLayer(layer))],
|
|
over: vectors.filter(isOverlayLabelLayer),
|
|
};
|
|
}
|
|
|
|
// The layers of a basemap with every label over all of its ground: the ground in the order it was
|
|
// in, then the labels in the order they were in.
|
|
//
|
|
// A map of several basemap files is their layers one file after another, so the labels of each file
|
|
// but the last are under the land, the water and the roads of the files after it, and under
|
|
// anything which is put under "the labels". Labels are always on top.
|
|
export function labelsOverGround(layers) {
|
|
layers = layers || [];
|
|
return [...layers.filter(l => l.type !== "symbol"), ...layers.filter(l => l.type === "symbol")];
|
|
}
|
|
|
|
// The source of the contour lines both viewers draw from the terrain. They are added to a style
|
|
// after the basemap's labels, lines and labels both, and are not of the basemap.
|
|
const CONTOUR_SOURCE = "contours";
|
|
|
|
// Where the basemap's labels begin: the index of the first of the labels which are over all of the
|
|
// basemap's ground. Where no label is over its ground, the index after the last of its ground.
|
|
//
|
|
// Not the map's first label: a map of several basemap files has the labels of the first file under
|
|
// the ground of the next, and an overlay put there would be under the land and the water of every
|
|
// file after the first. Nor before the last layer which is not a label: the contour lines are
|
|
// drawn after the basemap's labels, and an overlay put under them would be over every label.
|
|
export function basemapLabelsStart(layers) {
|
|
layers = layers || [];
|
|
const ofBasemap = layer => !isOverlayLayerId(layer.id) && layer.source !== CONTOUR_SOURCE;
|
|
let lastGround = -1;
|
|
for (let i = layers.length - 1; i >= 0; i--) {
|
|
if (ofBasemap(layers[i]) && layers[i].type !== "symbol") {
|
|
lastGround = i;
|
|
break;
|
|
}
|
|
}
|
|
for (let i = lastGround + 1; i < layers.length; i++) {
|
|
if (ofBasemap(layers[i]) && layers[i].type === "symbol") return i;
|
|
}
|
|
return lastGround + 1;
|
|
}
|
|
|
|
// Add the overlays to a style's sources and layers (the basemap's are already there).
|
|
export function addOverlaysToStyle(styleSources, allLayers, overlays, state, urls) {
|
|
for (const file of overlays || []) {
|
|
styleSources[overlaySourceId(file)] = buildOverlaySource(file, urls);
|
|
}
|
|
const {under, over} = orderOverlayLayers(overlays, state);
|
|
allLayers.splice(basemapLabelsStart(allLayers), 0, ...under);
|
|
allLayers.push(...over);
|
|
}
|
|
|
|
// Add the overlays to a map whose style has loaded, a layer at a time. For a viewer which cannot
|
|
// check a layer before giving it to MapLibre: MapLibre refuses a whole style over one layer it
|
|
// cannot draw, but refuses only that layer when it is added by itself.
|
|
// Returns how many layers of each file (by `map_path`) were refused.
|
|
export function addOverlaysToMap(map, overlays, state, urls) {
|
|
const refused = {};
|
|
for (const file of overlays || []) {
|
|
const id = overlaySourceId(file);
|
|
if (!map.getSource(id)) map.addSource(id, buildOverlaySource(file, urls));
|
|
}
|
|
const mapLayers = map.getStyle()?.layers || [];
|
|
const firstLabel = mapLayers[basemapLabelsStart(mapLayers)];
|
|
const {under, over} = orderOverlayLayers(overlays, state);
|
|
const add = (layer, before) => {
|
|
if (map.getLayer(layer.id)) return;
|
|
try {
|
|
map.addLayer(layer, before);
|
|
} catch (e) { /* refused; counted below */ }
|
|
if (!map.getLayer(layer.id)) {
|
|
const mapPath = (overlays || []).find(f => layer.source === overlaySourceId(f))?.map_path;
|
|
refused[mapPath] = (refused[mapPath] || 0) + 1;
|
|
}
|
|
};
|
|
for (const layer of under) add(layer, firstLabel?.id);
|
|
for (const layer of over) add(layer, undefined);
|
|
return refused;
|
|
}
|
|
|
|
// --- Popup ---
|
|
|
|
// The popup HTML of the overlay features under a click, or null when there are none. An overlay's
|
|
// attributes are whatever its author chose, so they are listed as they are.
|
|
export function overlayPopupHtml(features) {
|
|
const seen = new Set();
|
|
const blocks = [];
|
|
for (const feature of features || []) {
|
|
const layerId = feature.sourceLayer || feature.layer?.["source-layer"];
|
|
const properties = feature.properties || {};
|
|
if (!layerId) continue;
|
|
const key = JSON.stringify([layerId, properties]);
|
|
if (seen.has(key)) continue;
|
|
seen.add(key);
|
|
if (blocks.length >= POPUP_MAX_FEATURES) break;
|
|
|
|
const entries = Object.entries(properties).filter(([, v]) => v !== null && v !== undefined && v !== "");
|
|
const name = properties.name;
|
|
const rows = entries
|
|
.filter(([k]) => k !== "name")
|
|
.slice(0, POPUP_MAX_PROPERTIES)
|
|
.map(([k, v]) => `<br/><small>${escapeHtml(k)}: ${escapeHtml(v)}</small>`);
|
|
const more = entries.length - (name !== undefined ? 1 : 0) - rows.length;
|
|
blocks.push(
|
|
`<div style="font-size:13px">` +
|
|
`<strong>${escapeHtml(name !== undefined && name !== "" ? name : layerId)}</strong>` +
|
|
(name !== undefined && name !== "" ? `<br/><small>${escapeHtml(layerId)}</small>` : "") +
|
|
rows.join("") +
|
|
(more > 0 ? `<br/><small>… ${more} more</small>` : "") +
|
|
`</div>`
|
|
);
|
|
}
|
|
return blocks.length ? blocks.join('<hr style="margin:4px 0"/>') : null;
|
|
}
|