It operates in one of these modes:
* facet="bars" (default): shows a barplot.
* facet="lines": shows a lineplot.
* facet="area": shows a lineplot where the area between the
line(s) and y=0 is filled with a colour.
The component takes a list of shots and operates in one of these
modes:
* facet="scatter" (default): shows a scatterplot of every shot
where x is the crossline and y are the inline errors.
* facet="crossline": shows a line graph depicting the crossline
error along the line, x is the shotpoint and y is the crossline
error.
* facet="2dhist": shows the crossline error as a 2D histogram.
The z value is the density (number of samples in the bin) and
x and y are the bin centres.
* facet="c-o": provided that the shot data comes from a final
sequence, shows the difference between final and raw positions
along the inline / crossline axes.
The log until now offered a download control only in sequence
view mode. With this change, download is available (albeit not
in all formats) for the entire log.
To download events for a selection of dates (constrained by day,
week or month) the user should use the Calendar view instead.
This is a refactoring of <dougal-event-edit/> focusing on the
preset remark selection combo box and context menu with the
addition of support for structured values via the
<dougal-event-properties/> component.
The Project component is now responsible for fetching and
updating the data used by most project tabs, with the
exception of ProjectSummary, QC, Graphs and Map. It is
also the only one listening for server events and reacting
to them.
Individual tabs are still responsible for sending data to
the server, at least for the time being.
A ‘Timed’ button is shown when a new (not edited) event is in
the event entry dialogue and the event has sequence and/or
point values. Pressing the button deletes the sequence/point
information and sets the date and time fields to current time.
Fixes#277.
Use https://open-meteo.com/ as a weather forecast provider.
This code is intended for demonstration only, not for
production purposes.
(issue #157)
(cherry picked from commit cc4bce1356)
The map view limits the size of layers (both user and regular) in
order to keep the system responsive, as Leaflet is not great at
handling large layers.
