It listens for events that might indicate that the project_summary
materialised view needs to be refreshed and schedules a refresh.
Refreshes are throttled to a maximum of one every throttlePeriod
milliseconds so that things don't get too crazy for instance when
importing a lot of data.
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.
It checks if a request has a `filename` search parameter and if
so, set the Content-Disposition response header to attachment
with the provided filename.
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.
Resolve "Consolidate handling of project data in the Project component rather than in individual tab components"
Closes#280
See merge request wgp/dougal/software!48
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.
