PEAU DU MONDE| postProcessor

Acceptance test · v0.99.4 · every function of the panel, scripted, in the order of the work.

tester	date	office (producer code)
QGIS version	postProcessor version (Plugin Manager)	the set

Run the scripts in order: each leaves what the next one needs. Mark a script pass when every step shows what its Expect says; fail when one does not, and write in the note what you saw; not run when the set holds nothing to run it on, and why. Where the set decides a number, the step asks for it: write it in the note. Quoted words are the panel's own; n, m:ss and the like are what your set gives.

Run it in every version: ours, and every one delivered to another office. It accepts a version, and it shows a version that works slower than the one before: the timesheet at the end takes the delivery report's times (UAT-22) beside those of the version before. Run both on the same set and the same computer, or the times do not compare. save results writes this page as you filled it in, as a new file: keep it beside the delivery report, in the product set's folder. Printed, the page is a paper form.

What you need: QGIS 4, or QGIS 3 from 3.34; the plugin's ZIP; a copy of an exchange set of your office with findings at several levels (the example of the manual, §16, has all four). For UAT-17 to UAT-20: a source of floating aids, a WFS or a point layer. For UAT-04 and UAT-21: a base cell of another producer in the set. For UAT-27 to UAT-33: a copy of an S-100 exchange set of S-101 cells and S-102 surfaces. For UAT-34: a folder of several exchange sets. For UAT-35: an Inland ENC set, and a test signing key with its certificate (without them the set goes out unsigned).

A · Before the work
01 Install and open
02 officeSettings

B · Taking the set in
03 Stage a set
04 Another office's cells

C · The review
05 Review the wetSotE
06 Read a finding
07 Decide one at a time
08 Go for a whole level

D · Writing
09 Write the solutions and the cures

E · By hand
10 Fix a finding by hand
11 What the check refuses

F · Attributes
12 The object list and the search
13 Change an attribute
14 Relocate and delete an object
15 Add an object: its attributes and SCAMIN
16 walradar

G · Floating aids from a source
17 Buoyage areas and a model
18 Run a model
19 Write suggestions
20 The ignore list

H · Another office's work
21 A copy under your own code

I · The delivery report
22 The delivery report and its times

J · After the work
23 Review the product again
24 A clean workspace at the next start

K · The audit
25 Review Full

L · The session lock
26 Lock the session

M · S-101 and S-102
27 Stage an S-100 set
28 The chart: S-101 cells and S-102 surfaces
29 Review and write an S-101 cell
30 Review Full on an S-100 set
31 An S-101 cell's attributes
32 Relocate, delete and add an S-101 object
33 Floating aids and a copy in an S-100 set

N · Many sets
34 A folder of many sets

O · Conversion
35 Convert a set to S-101

A · Before the work

UAT-01 Install and open manual §2

First QGIS 4, or QGIS 3 from 3.34, and the plugin's ZIP.

	Do	Expect
1	Plugins ▸ Manage and Install Plugins ▸ Install from ZIP, the ZIP.	Installed: Peau du Monde \| postProcessor is listed and enabled.
2	Click its toolbar button.	At the first start of a version a card stands in front of the panel: HALT under the STOP sign, and the lines on writing only under your own producer code. Its buttons: Open the quick card and Understood — the judgement is mine.
3	Open the quick card, then Understood — the judgement is mine.	The quick card opens in the browser. The panel opens with six vertical tabs, top to bottom: Content Audit Attributes Convert Edits Settings; with 2FA on, lockSession above them in red.
4	Close the panel; open it again.	The card does not come back until the next version.
5	Right-click anywhere on the panel.	Day Dusk Night Free panel (never dock) Our own title bar Quick card Manual Acceptance test. A colour table recolours the panel; each document opens in the browser. The plugin menu holds the three documents too.
6	Rest the mouse on each button of each tab.	Nothing appears: the panel has no tooltips.

pass fail not run note

UAT-02 officeSettings manual §15

First No set staged.

	Do	Expect
1	Settings ▸ officeSettings: the producer code in lower case, the agency code, the agency name, and Inland rules of your region; save.	`Saved to …\pdm_postprocess\reference.gpkg`, and under it `Nothing is written: no home directory is set.` and `Project CRS: EPSG:3857, WGS 84 / Pseudo-Mercator.` The producer code shows in capitals.
2	An agency code of 0; save.	`Refused: …. Nothing was saved.` The saved values stay.
3	Your agency code again; save.	`Saved to …`
4	Untick background map (OpenStreetMap); save.	`Saved to …` The box stays unticked.
5	home directory: choose a folder on a network share, on a USB stick, or in OneDrive; save.	`Refused: the home directory is a folder on a fixed disk of this workstation, outside OneDrive: … is a network share. Nothing was saved.` (A stick: `… is on a removable drive`; OneDrive: `… lies in a folder OneDrive keeps (…)`.)
6	choose a folder on the workstation's own disk, such as `C:\postProcessor`; save.	`Saved to …` and `Home directory: … — reviews, production, workspace.` The three folders are in it.
7	project CRS: `28992`; save. Then `abc`; save. Then `3857`; save.	`Project CRS: EPSG:28992, Amersfoort / RD New.`; then `Refused: the project CRS is an EPSG code, such as 3857: abc is not one. Nothing was saved.`; then `Project CRS: EPSG:3857, WGS 84 / Pseudo-Mercator.`

A copy delivered for one office carries its settings fixed: officeSettings says Fixed in this delivery: … and keeps its values. Then note steps 2 and 3 as not run.

pass fail not run note

B · Taking the set in

UAT-03 Stage a set manual §3

First UAT-02. A copy of an exchange set of your office.

	Do	Expect
1	Content ▸ select folder…, the set's `ENC_ROOT`; push its tile.	Its tile: a band of S-57 dark green or IENC light blue carrying the product and `usage n`, the set's folder name on white beside it. Pushed: the list at once, under back to tiles, the set named as its tile names it, and stage again; `Staging folder …`, then `Staged n files (m base cells) · one exchange set`. Note n and m.
2	Read the table.	One row per data set file: filename, issue date, edition number, standard (Inland ENC or Maritime ENC), standard edition. The base cells ticked; an update file listed, and not tickable.
3	Look at the chart.	No OpenStreetMap added: the background map is unticked (UAT-02); one your project already had stays. Every listed cell outlined in the layer `cells` by its data coverage, green and dotted, its name in the middle where it fits.
4	officeSettings: tick background map (OpenStreetMap), save; stage again.	OpenStreetMap under every layer (with an internet connection), once.
5	deselect all, then select all.	Every tick off, then on.
6	Look at the delivered set's folder.	Nothing in it changed: the set was copied into the workspace, and only the copy is read.
7	With the panel open: Project ▸ New; stage again.	QGIS's status bar reads `EPSG:3857` at once, and still once the outlines and the chart are in.
8	With the panel open, open a project that holds layers in another CRS, such as EPSG:28992.	Asked: `The CRS of this project, EPSG:28992, is not the one in your officeSettings, EPSG:3857. Switch to EPSG:3857?` Choose keep: it stays EPSG:28992. Close the panel and open it: not asked again. The same project, on switch, reads EPSG:3857.
9	Untick a cell; back to tiles; push the outlined tile.	The tiles, the staged one outlined. Pushed: its list as you left it, the cell still unticked; nothing staged again.

pass fail not run note

UAT-04 Another office's cells manual §3

Needs a base cell whose name starts with another producer's code.

	Do	Expect
1	Stage the set that holds it.	The status line adds `n base cells are another office's (XX): opened and worked here, but never written under its code (R-PP57, R-PP58).` The cell is ticked like the others.
2	officeSettings: change the agency name; save.	Content says `officeSettings changed: stage the set again to apply it.`
3	The name back; save; stage again.	As in step 1.

pass fail not run note

C · The review

UAT-05 Review the wetSotE manual §4, §6

First UAT-03, the base cells ticked.

	Do	Expect
1	Audit ▸ review wetSotE.	The status line, drawn again every second: `Reviewing k/n cells · at work: … · chart layers k/n · m:ss`. QGIS stays usable.
2	Wait for the list.	`Reviewed n cells: m findings in m:ss`; later `… layers loaded · all in m:ss`, with no soundings: show soundings is off. Note the review's m:ss.
3	Content: tick show soundings.	`… decluttering the soundings…`, then `… soundings loaded`; the soundings in the Layers panel. Untick it: they leave the chart; tick it again: back at once.
4	Read the line above the list.	`n cells reviewed · m findings · A a · B b · C c · D d`. Note the counts.
5	Look at the Layers panel.	At the top the group `Peau du Monde \| postProcessor · set`: the wetSotE per usage band and class (`U6 \| 05 Depth area (area)`, …), the depth contours, the soundings; on top `findings`, a dot per finding — A green, B amber, C red, D near-black — and `picked finding`.
6	Open a cell in the list.	Its findings, level A first. A cell that could not be reviewed reads `— not reviewed`, with the error under it.

pass fail not run note

UAT-06 Read a finding manual §5, §6

	Do	Expect
1	Pick a level-B finding.	The chart pans and zooms to it. `picked finding` shows the finding in orange, the edge as delivered red and dashed, the edge as the solution writes it green.
2	Read under the list.	The title; under it, in italics, the words of the rule it breaks, quoted from the document it cites; the standard (`S-58 78 (C)`, for one) and the level; Rule or Why no solution; Left as it is; The solution: what moves and how far, the m² of water re-stated and which area gains them, what moves along.
3	Pick a level-C finding.	Its cure drawn on the chart, its words saying what changes.
4	The dropdown: show level A … show level D, then show all.	One level at a time; a cell with nothing of it hidden; every decision as it was.

pass fail not run note

UAT-07 Decide one at a time manual §9

	Do	Expect
1	Pick a finding with a solution; go.	Its decision reads go. Edits holds a row for it — solution, the cell, what was wrong, the edit in words, saved, ticked — and its button counts it: write edits to products (n).
2	no go on the same finding.	It reads no go; its row leaves Edits, and the count drops.
3	Pick a finding without a solution.	go and no go cannot be pressed.
4	no go on a level-C finding.	It reads no go: it is the cartographer's now, and the delivery report sends it back to production.

pass fail not run note

UAT-08 Go for a whole level manual §9

	Do	Expect
1	show level A.	The button beside the dropdown reads go: every level A.
2	Press it.	Every level-A finding with a solution and no decision reads go; a decision made before is kept; no other level changes. Edits counts them all.
3	show level C; look at each cure in the chart; go: every level C.	Every level-C finding with a cure and no decision reads go.
4	show all, then show level D.	The go-every button is not there.

pass fail not run note

D · Writing

UAT-09 Write the solutions and the cures manual §10, §13

First UAT-07 and UAT-08: go's given, level C among them.

	Do	Expect
1	officeSettings: empty the home directory; save. Edits ▸ write edits to products (n).	`Not written: no home directory is set; the home directory, a folder on a fixed disk of this workstation outside OneDrive, is set in Settings ▸ officeSettings (R-PP8f)`. Nothing new in `production`. Choose the home directory again; save.
2	Edits ▸ write edits to products (n).	A clock on the status line while it writes. In the home directory's `production` a new folder, the set's name with `_alt1`, and `ENC_ROOT` in it; nothing new beside the delivered set.
3	Read the status line at the end.	`Written: n solutions, k cures to …_alt1 · catalogue: c CRCs patched`; `· cleared along with them: x` and `· refused: y` when there are; `· issue dates and edition numbers untouched in the product`; after a cure `Warning: this alters the product in a way that an update by the original production system will not match.`; `· delivery report in …\reviews`; and the time.
4	Read Audit's list.	A written finding reads written; one gone with another's solution reads cleared, and why; a refused one reads refused, and why.
5	Read Edits' rows.	Each written, cleared or refused, with why.
6	open products folder.	The `_alt1` set, with its `CATALOG.031`, and no delivery report beside `ENC_ROOT`. The delivered set is as it was.
7	Open the home directory's `reviews`.	This write's delivery report: `set_alt1_delivery_report_time.html`.

pass fail not run note

E · By hand

UAT-10 Fix a finding by hand manual §11

First A level-D finding a move in the chart can clear.

	Do	Expect
1	Pick it; edit in the chart.	The layer `hand edit · cell` on top, in editing, the Vertex Tool chosen, snapping and topological editing on. The chart shows the SotE only: soundings, findings, the cell outlines, OpenStreetMap and your own layers are hidden. Each line drawn as what it is: a depth contour dashed dark blue, an unsurveyed boundary violet, water against land ochre, a depth-area boundary magenta.
2	Move a vertex or a node so the finding clears; check edit.	`Checking the edit · m:ss`, then `The check passes: …; clears 1 finding · m:ss`. Under the list what moves, what it clears, and any Shoal safety: line.
3	Move it once more.	`Changed since the check`; save edit waits for a new check.
4	check edit, then save edit.	`Saved to Edits: …`; a row by hand in Edits. The edit layer gone, the hidden layers back, snapping and topological editing as they were.
5	write edits to products (n).	`Written: 1 by hand to …_alt1 · catalogue: 1 CRC patched · …` The finding reads by hand.
6	Another finding: edit in the chart, move something, close edit.	`Edit closed: nothing written`

pass fail not run note

UAT-11 What the check refuses manual §11

	Do	Expect
1	In an open edit, draw a new line in the edit layer; check edit.	`Refused: … · m:ss`; under the list each refusal, why and where. save edit cannot be pressed.
2	Undo it. Move a vertex so a sounding lands on the other side of the line; check edit.	Refused, the sounding named, and where.
3	close edit.	`Edit closed: nothing written`

pass fail not run note

F · Attributes

UAT-12 The object list and the search manual §12

	Do	Expect
1	Attributes, after staging.	`Listing objects k/n cells`, then `N objects in n cells`. Note N.
2	Zoom in; pan.	Only the objects on screen: under the usage band, the object layers as dataBridge names them (`Notice mark [notmrk]`), each with how many are on screen, folded.
3	Unfold an object layer; fold it.	Every object of that class in that usage band, in the whole set, thin and blue on the chart; folded, they leave.
4	In the search bar: an object's FOID; then `ORIENT=0`; then a word, a name or a class.	`n objects found`: the FOID one row, whatever cells hold its pieces; the objects that carry ORIENT 0; for the word, objects by name and classes by their meaning, each class with why. `Nothing found` when nothing is.
5	Click an object.	Red, every piece of it, as the geometry it is — a dotted line, points, striping with a dotted rim — and the view pans to it, keeping its scale.

pass fail not run note

UAT-13 Change an attribute manual §12

	Do	Expect
1	Unfold an object; double-click a value; change it.	The row reads changed. An enumerated attribute offers its values with their meanings.
2	add attribute…	Only the attributes the class may carry: mandatory, then conditional, then optional.
3	save edit (1)	`Saved to Edits: 1 object`; a row in Edits.
4	Write it.	`Written: 1 attribute edit to …_alt1 · …` The object reads written.
5	The same for an object in several cells: its FOID row says `n cells`.	Every piece with that FOID takes the change; nothing else of theirs changes.
6	A value with a character a cell cannot carry (`ü` in a cell at lexical level 0); save it and write.	Refused, with the reason; no piece of that object is written.

pass fail not run note

UAT-14 Relocate and delete an object manual §12

	Do	Expect
1	Pick a point object; relocate…; click the new place.	Where more features stand on its node, asked first: move them all, or give it a node of its own. A row in Edits, with the warning that an update will no longer match.
2	Pick a line or an area cut by a cell border; delete object.	Asked first, the cells named: it is deleted in every cell of its usage band, as one edit.
3	Write both.	Written into `_alt1`, with the warning.

pass fail not run note

UAT-15 Add an object: its attributes and SCAMIN manual §12, §15

First Inland rules of set (UAT-02); an Inland ENC set staged.

	Do	Expect
1	add object…; the class, found by name or acronym; click the place, or draw it.	A dialog asks the attributes the catalogue binds to the class, by name with the acronym, mandatory first.
2	Read its SCAMIN line.	`SCAMIN: Encoding Guide 2.4.1, the set's edition` for a set of Inland ENC 2.4 (2.5.1 for 2.5; for another, `… the latest official edition: the set declares Inland ENC x`), and the value for your region filled in.
3	A mandatory attribute left empty; Save.	Not saved: the dialog names what is still to fill.
4	Fill it in; Save.	`Saved to Edits: …`; written with the next write, under a FOID of your own agency.
5	Settings ▸ scaminValues.	The head: `Inland ENC Encoding Guide 2.4.1, the set's edition; …`; one row per class and geometry, the Encoding Guide's line beside each.
6	Your own value for the class of step 1; add object… of it again.	`SCAMIN: the office's own value (Settings → scaminValues)`, your value filled in.
7	Cancel; then empty your value in scaminValues.	Nothing is added. The list's value applies again.

pass fail not run note

UAT-16 walradar manual §12

First The office's cells hold unsurveyed areas.

	Do	Expect
1	Attributes ▸ walradar.	`walradar: reading the unsurveyed areas`, then `Saved to Edits: walradar — n unsurveyed areas → depth areas in k cells, as the set …_WALRADAR`; one row in Edits. Where the cells hold holes in the survey, the line goes on: `m areas left amid depth areas (R-PP62b)`.
2	Write it.	The status line adds `walradar: n unsurveyed areas → depth areas in …_WALRADAR`.
3	Stage `set_WALRADAR`, or open one of its cells in dataBridge.	Every unsurveyed area that touches land is a depth area, 0 – 0 where no depth area touches it. The holes in the survey — unsurveyed areas amid depth areas all round — are still unsurveyed areas, and so is one that touches neither depth nor land. Every other is a depth area 0.1 m shoaler than the shoalest depth area beside it and never below 0 m. Each replaced one has INFORM synthetic data for WALRADAR. The cells keep their names and editions. The product keeps its unsurveyed areas.

pass fail not run note

G · Floating aids from a source

UAT-17 Buoyage areas and a model manual §15

Needs a source of floating aids: a WFS, or a point layer in the project.

	Do	Expect
1	Settings ▸ buoyageSystems ▸ Copy chartProduction's areas; or a system and Draw area on the chart.	Each area listed with its system and its km². Copied twice, none is there twice.
2	Show on map.	The layer `buoyageSystems` on the chart.
3	vmbModels ▸ new model… on the source; map its columns; Register… before Check passes, with no Source ID.	Refused, with every reason.
4	Check; the Source ID; Register… under a name.	Registered: the list in vmbModels shows it.
5	export…; then import… the file.	The model as a file; imported again, the clash is asked about.

pass fail not run note

UAT-18 Run a model manual §13

Needs UAT-17.

	Do	Expect
1	Edits ▸ run model…; the model, and the layer when the model keeps no service.	`Comparing source with the cells through model`, then `n suggestions from model, unticked, in Edits · k of N source rows lie inside the chart's coverage (R-PP47)`. Note n.
2	Read the list.	A row named after the model; under it a row per kind of change that occurs, in this order: remove, add, update position, update characteristics, update both, rewrite in the right case. Each reads `n suggestions · 0 ticked`; every suggestion is unticked.
3	Tick one kind's row; then the model's row.	That kind's suggestions ticked, no other; then all of them. The counts follow.

pass fail not run note

UAT-19 Write suggestions manual §13

Needs UAT-18.

	Do	Expect
1	Tick a few of different kinds — an add, a remove, an update both where there is one; write edits to products (n).	`Written: n suggestions from a source to …_alt1 · …` Each row written, or refused with why.
2	Search the added buoy by its name in Attributes.	The buoy with its topmark and its light, the buoy their master; in the case the buoyage area says (`BOYLAT` under IALA, `boylat` under CEVNI); under a FOID of your own agency.
3	Find the aid of the update both.	Moved to the source's place, and its values set.

pass fail not run note

UAT-20 The ignore list manual §13, §15

Needs UAT-18: a suggestion to remove an aid that another asset manager keeps.

	Do	Expect
1	Right-click that suggestion ▸ to ignore list.	`name: on the ignore list, left out of the next run`; the row leaves Edits, unwritten.
2	Settings ▸ ignoreList.	`n on the ignore list`: the object with its name and class, its cell, its FOID, the model and the suggestion, and since when.
3	run model… again.	It is not suggested. The run's step in the delivery report lists `1 on the ignore list left out of the comparison (§57)`.
4	Pick it in ignoreList; take off the list; run again.	Suggested again.

pass fail not run note

H · Another office's work

UAT-21 A copy under your own code manual §13

Needs UAT-04: a cell of another producer, staged.

	Do	Expect
1	A go on a finding in that cell; write edits to products (n).	Asked first: `You are making a copy based on another office's work. You are responsible for handling licence and intellectual property.` — make the copy or Cancel.
2	Cancel.	`Nothing written: the copy under your own code was not wanted (R-PP59)`
3	Write again; make the copy.	`Written: … as 1 copy under your own code in …_alt1_copies`. Beside the product, `set_alt1_copies\ENC_ROOT` with its own `CATALOG.031`; the copy named with your producer code (`BE7XXXXX.000` becomes `1R7XXXXX.000`), edition 1, update 0, issued today. The product keeps the other office's cell as delivered.

pass fail not run note

I · The delivery report

UAT-22 The delivery report and its times manual §14

First The writes of this session, UAT-09 to UAT-21, done in the same staging.

	Do	Expect
1	Edits ▸ delivery report.	A page opens in the browser, written into the home directory's `reviews`: `set_alt1_delivery_report_time.html`, beside those each write left there, in the style of this page.
2	Read the head and part 1.	The head names the version and the computer: Measured on postProcessor, QGIS, the logical processors and each pool's workers. Above the steps a table of times: processing, per kind and in all, steps side by side counted once; production time, each write from its start in Edits to its last file written; the time in the postProcessor; the cartographer's time. Every automated step — staging, outlines, object list, review, chart, model runs, the walradar reading, checks, writes — from its start to its end, with its time; one that started and did not end says so. Under the steps, the review cell by cell.
3	The review's time against Audit's `Reviewed … in m:ss` (UAT-05); the first write's line against the clock that ended Edits' status line (UAT-09).	The same, to the second.
4	Read parts 2 to 4.	What every write changed in the product is in part 2: solutions, cures, hand edits, geometry, suggestions, attributes. What was refused is in part 3, with why. The go's not written and the suggestions left are in part 4 — per cell, and by model and kind of change — and not in part 3.
5	Copy the times into the timesheet, at the end of this page.	As the report gives them.

pass fail not run note

J · After the work

UAT-23 Review the product again manual §10

	Do	Expect
1	With the file manager, move the `_alt1` set out of `production`, to where your office keeps its sets. A go on a finding still left in this staging; write edits to products (n).	`Not written: set_alt1 is no longer in …\production: moved or removed, and what this staging wrote went with it. Stage again to write on (R-PP8i)`. Nothing new in `production`.
2	Content ▸ select folder…, the moved `_alt1` set's `ENC_ROOT`; review wetSotE.	The findings written are gone. What was left — no go, not decided, level D — is still there.
3	A go on one; write.	The next alternative, in `production`: `set_alt2`, never `_alt1_alt1`.

pass fail not run note

UAT-24 A clean workspace at the next start manual §13

First This page saved (save results, below).

	Do	Expect
1	Close QGIS. Open the home directory's `workspace\`, and `%APPDATA%\QGIS\QGIS4\profiles\default\pdm_postprocess\` (QGIS 3: `…\QGIS3\…`).	`workspace\` holds this session's stagings and `postProcessor workspace.txt`; `reference.gpkg` is in the profile's folder.
2	Start QGIS; open the panel.	`workspace\` is empty within seconds but for `postProcessor workspace.txt`; `reference.gpkg` is as it was. `production`, `reviews` and this page are as you left them.
3	Settings ▸ vmbModels and ignoreList.	The models and the list are still there: they live in the office's file, not in the workspace.

pass fail not run note

K · The audit

UAT-25 Review Full manual §4, §5, §14

First UAT-03, the base cells ticked.

	Do	Expect
1	Audit ▸ review Full.	The review as in UAT-05. When it ends the line goes on: `Reviewed n cells: m findings in m:ss · Auditing k/n checks · check … · m:ss`; the panel stays busy.
2	Wait for the line to end.	`… · audited n checks: m findings (C c · E e · W w) in m:ss`. Above the list: `… · audit: m findings · C c · E e · W w`.
3	Open a cell in the list.	Its wetSotE findings first, then a group per object layer (`Depth area (area) — 3`) holding the audit's findings, the level column C, E or W, the decision column empty. Set-wide findings under `exchange set`.
4	Pick an audit finding.	The chart pans to the object. Under the list: the title, `check n · severity · category`, the object and its cell, the catalogue it was judged by (`Inland ENC 2.4 · judged by FC 2.4`); the title ends in `(untested)` when the check is, and says it once. go and no go stay off.
5	show level A, then show all.	The audit's groups hide under any level, and are back under show all.
6	Edits ▸ delivery report.	Part 1 has the step `Audited n cells on m checks … Judged by: …` with its time and the table of times a row the audit; part 3 a table The audit: S-58, the Feature Catalogue and quality, one row per check with its findings and its cells, an untested check's finding ending in `(untested)`.

pass fail not run note

L · The session lock

UAT-26 Lock the session manual §2, §15

First UAT-01; an authenticator app on a phone.

	Do	Expect
1	Settings ▸ officeSettings: tick 2FA.	A dialog, 2FA, with a QR code and a field for six digits; confirm stays off until six digits are typed; letters do not go in.
2	cancel.	The box is unticked again: `2FA is off: no code was confirmed.`
3	Tick 2FA again. Scan the QR with the authenticator; type the six digits it shows; confirm.	`2FA is on: lockSession, above the tabs, locks the session.` The tab lockSession stands above Content.
4	Press lockSession; answer No.	First Are you sure you want to lock your session?, with No chosen. Then back on settings; every tab still there.
5	Press lockSession; answer Yes.	Only lockSession is left. The panel shows the Peau du Monde mark, PEAU DU MONDE and open source charting system; under them Enter the code from your authenticator, whole, and a field for the code; unlock stays off until six digits are typed; under a blank line, Peau du Monde \| postProcessor and its version. The whole face fits the panel, however narrow.
6	A wrong code; unlock.	`That code was not accepted. Each code opens the lock once — if you have just used it, wait for the next one.` The field is empty again.
7	Close QGIS; start it; open the panel.	The panel opens locked.
8	The code the phone shows now; Enter.	Every tab is back, and the tab you were on.
9	Settings ▸ officeSettings: untick 2FA.	`2FA is off and its code cleared: turning it on again means a new QR to scan.` lockSession is gone. Remove the entry from the phone.

pass fail not run note

M · S-101 and S-102

UAT-27 Stage an S-100 set manual §3, §17

Needs UAT-02 with the S-100 producer code saved; a copy of an S-100 exchange set holding S-101 cells — one with an update dataset — and S-102 surfaces.

	Do	Expect
1	Content ▸ select folder…, the set's `S100_ROOT`; push the S-101 tile.	A purple S-101 tile and a red S-102 tile, each band with the scale band its catalogue states. Pushed: `Staged n files: k S-101 cells · one exchange set`. Note k.
2	Read the table; then back to tiles and push the S-102 tile.	One row per dataset: filename, issue date, edition number, standard, standard edition. The base cells ticked, an update dataset listed and not tickable; on the S-102 tile the m surfaces, ticked.
3	Look at the chart, on each tile.	Every S-101 cell outlined in `cells` by its Data Coverage, every S-102 surface by its box.
4	Select a folder that holds an S-57 set and an S-100 set.	A tile for each set and product — S-57 dark green, S-101 purple, S-102 red — the newest first; nothing staged until one is pushed.

pass fail not run note

UAT-28 The chart: S-101 cells and S-102 surfaces manual §4, §17

First UAT-27: the cells on the S-101 tile, the surfaces on the S-102 tile.

	Do	Expect
1	Audit ▸ review wetSotE.	The review as in UAT-05. The chart's line ends in `m S-102 surfaces previewed`.
2	Read the Layers panel.	The S-101 layers named by scale and class, `1:22000 \| 05 Depth Area (area)`, drawn with the S-57 styles; under them `S-102 \| depth \| file` for each surface, in the depth areas' colours, and `S-102 \| uncertainty \| file`, unticked.
3	Tick an uncertainty layer.	The surface's uncertainty, light to dark red.
4	A surface whose metadata states heights (EPSG 6499), where the set has one.	Its water drawn as water, and the line names it: `stored as heights (verticalCS 6499), drawn turned: file`.

pass fail not run note

UAT-29 Review and write an S-101 cell manual §6, §10, §17

Needs UAT-28 with a finding in an S-101 cell of your office.

	Do	Expect
1	Pick the finding.	Its words name curves and points, not edges and nodes, and each type by its catalogue name (Depth Area); it cites S-158:101 (`S-158:101 101_0001 (C)`) or S-158:100, or DCEG 2.5.1.1 for a stretch drawn twice. The level and the solution as for an S-57 cell.
2	go; Edits ▸ write edits to products (n).	`Written: … to …_alt1 · written without signatures (R-PP97): n signatures that no longer held taken out of the catalogue`, and the time.
3	open products folder; open the `_alt1` set's `CATALOG.XML` in a text editor.	`S100_ROOT` as delivered; the written cell's entry without its signature value, every other entry as delivered; no catalogue signature file. The delivered set is as it was.
4	Stage the `_alt1` set; review wetSotE.	The finding written is gone.

pass fail not run note

UAT-30 Review Full on an S-100 set manual §5, §14, §17

First UAT-27: the cells on the S-101 tile, the surfaces on the S-102 tile.

	Do	Expect
1	Audit ▸ review Full; wait for the line to end.	The review, then the audit by S-158: `… · audited n checks: m findings (C c · E e · W w) in m:ss`.
2	Open an S-101 cell, then an S-102 surface in the list.	The cell's audit findings grouped by type as its catalogue names it, with its primitive (`Depth Area (area) — 3`) and under `data set`; the surface's under `the surface's metadata` or `the coverage`. C, E or W; no go. A surface not of S-102 3.0.0 told so: `S-158:102 is written for S-102 3.0.0; this surface is of e, and was audited by it all the same`, and, of 2.2, the checks that do not apply to it as written named after it.
3	Pick an audit finding.	The chart pans to it; the title ends in `(untested)` when its check is, once.
4	Edits ▸ delivery report.	Part 3's table lists every check of S-158:101, S-158:100 and S-158:102 with its outcome — failed, passed, not implemented — and 101_0001, 101_1116 and 101_1209 as wetSotE review.

pass fail not run note

UAT-31 An S-101 cell's attributes manual §12, §17

First UAT-27; for step 5, a cell with an update dataset.

	Do	Expect
1	Attributes; zoom to a cell.	Under the scale (`1:22000`) each type by its catalogue name and code (`Depth Area [DepthArea]`), with how many are on screen; under a type its objects by FOID and name.
2	Unfold an object that carries a name.	Its FOID; information and associated features where it has them; its attributes by code and name, an enumeration's value with its meaning; `featureName` a row with its name, language and nameUsage under it.
3	Double-click an enumerated value; a boolean; a text.	The enumeration offers its values with their meanings; the boolean true and false; the text is typed.
4	add attribute…, on the object and under a complex attribute.	The type's bindings, mandatory first, none already at its upper bound; under the complex attribute, its members.
5	Change a value the update dataset set; save edit (1); write.	Written into the update dataset, where the value lives; staged again, the cell reads the new value.
6	Add an attribute to an object whose record the update modifies; save.	Refused, with the reason: it would shift the positions the update's instructions address.

pass fail not run note

UAT-32 Relocate, delete and add an S-101 object manual §12, §17

First UAT-27.

	Do	Expect
1	Pick a point object on a point another feature stands on; relocate…; click the new place.	Asked first: move them all, or give it a point of its own. A row in Edits, with the warning that an update will no longer match.
2	Pick a line object; delete object.	A row in Edits; written, the object and the curves only it used are gone.
3	add object…; search a type by its name; draw it inside the cell's Data Coverage.	The catalogue's types by name, never Depth Area, Dredged Area, Land Area or Unsurveyed Area; the dialog asks the type's mandatory attributes and a name, and does not save while a mandatory one is empty.
4	Draw one partly outside the Data Coverage.	Refused, with the reason.
5	Write; stage the `_alt1` set; find the added object.	Under a FOID of your agency, with its attributes and its name.

pass fail not run note

UAT-33 Floating aids and a copy in an S-100 set manual §13, §17

Needs UAT-17's model and source over the S-100 set's area; for steps 3 and 4 an S-101 cell of another producer in the set.

	Do	Expect
1	Edits ▸ run model….	The S-101 cells' buoys compared, each with its topmark and its light: suggestions, unticked, as in UAT-18.
2	Tick an add and an update; write.	Written, or refused with why. In Attributes the added buoy carries its `topmark` attribute, and its light stands with it as its equipment.
3	A go on a finding in the other producer's cell; write edits to products (n); make the copy.	Beside the product, `set_alt1_copies\S100_ROOT`: the copy in `S-101\DATASET_FILES`, named `101` with your S-100 producer code and the rest of its name, and a `CATALOG.XML` listing it, edition 1, issued today, without a signature.
4	Stage the copies' set.	The copy is your office's; every FOID carries your agency code.

pass fail not run note

UAT-34 A folder of many sets manual §3, §5, §12

Needs A folder holding several exchange sets — the CSMART trial data, or a delivery of several sets; for step 5 a set whose audit finds an edge with vertices on the line between their neighbours.

	Do	Expect
1	Content ▸ select folder…, the folder above the sets.	A tile per set, product and usage: a band of S-57 dark green, S-101 purple, S-102 red or IENC light blue with the product and its usage or scale band written up it (`usage 5`, `1:12,000`), the set's folder name on white beside it; the newest first. The line: `n exchange sets found, t tiles: … Push a tile to stage it.`
2	Push a tile; then back to tiles.	The list at once, the set named as its tile names it; the table lists that tile's files alone. Back: the tiles, that one outlined.
3	In Attributes change an attribute and save edit; back to tiles, push another tile; answer no, then push it again and answer yes. Then change an attribute again, save edit, and stage again; answer no.	Asked first: `1 edit is saved and not yet written. Staging folder (product, usage) leaves it behind. Stage it?` On no, nothing changes; on yes, that tile is staged. stage again asks it too: `… Staging folder (product, usage) again leaves it behind. Stage it again?` On no, nothing changes.
4	Audit ▸ review Full; then show level A and show all.	Two categories, open, each with its count: `wetSotE — n` and `chartObjects — m`, the cells under each. Under a level, chartObjects hides; under show all it is back.
5	Pick An edge carries vertices that lie on the straight line between their neighbours; then another row.	The edge with every vertex: green where the check keeps it, orange where it lies on the line, a white node with a dark ring at its ends and where a vertex is a node of the set. Another row: they leave the chart.
6	In Attributes unfold two object layers; select one, then an object of the other; read the Layers panel. Then pick a finding in Audit.	The layer selected checked, the other unchecked, both still there; the picked object with its layer; `picked finding` unchecked. The finding picked: `picked finding` checked again.
7	back to tiles; type a word of a set's name in search tiles, e.g. `reissue`; then clear it.	Only the tiles whose words hold it, and beside the field `k of t`. Cleared: every tile back, no count.

pass fail not run note

UAT-35 Convert a set to S-101 manual §15, §17

Needs An Inland ENC set staged (UAT-03); the S-100 producer code saved (UAT-02); a test signing key and its certificate, PEM files — or none, and the set goes out unsigned.

	Do	Expect
1	Settings ▸ officeSettings ▸ signing certificate choose, the certificate; save. Then Convert.	The set named as its tile names it; the S-100 producer code filled, not to type; language and national language `nld`; organisation the agency name; the certificate's path; the key empty. A row per ticked cell: product, usage, compilation scale; optimum and maximum display scale filled in, minimum empty; the purpose from the usage; name tail and title. An Inland cell's last column: `n renamed, m deleted, k attributes dropped`. The line: `n charts to convert · i Inland, each through its maritime twin · unsigned: give the certificate and the key to sign.`
2	Click an Inland cell's row.	Under the table, its changes by object layer — `Bridge [bridge] (area) — n` — each object with what happens (renamed: BRIDGE, deleted: notmrk, attribute dropped: wtwdis 12.5) and the reason, naming the rule.
3	Clear a cell's maximum display scale; write. Type it back. Type `5000` as its optimum; write. Type the value it had.	`Refused: cell: the maximum display scale is the user's to set: give the maximum display scale (S-65 Annex B 2.2.6 suggests …) (R-C14). Nothing is converted.` Then `Refused: cell: the optimum display scale 5000 is not an optimum display scale of S-65 Table 2-3 / S-101 PS Table 3-1 (…) (R-C13). Nothing is converted.` Nothing new in `production`.
4	signing key choose, the key; then write.	The line ends `· signed.` Then `Converting n charts · 0:00` with the clock, the cells named in turn; at the end `Converted n charts into …\production\set_S101: n written[, k with refusals the report names]; signed with certificate id. The datasets are in S100_ROOT\S-101\DATASET_FILES, the reports beside the set; go to products opens the set's folder; stage it in Content to audit it.`
5	go to products.	The folder in the file manager: `S100_ROOT\CATALOG.XML` and `CATALOG.SIGN`, `S100_ROOT\S-101\DATASET_FILES\101XXXX….000` per cell, the cells' text and picture files under `S100_ROOT\S-101\SUPPORT_FILES` as `101XXXX….TXT`, `dataset.report.txt` beside each, `conversion.json`. A report's Refused part names each value the Feature Catalogue could not take; its Support lines each file carried and from where.
6	write again.	A fresh folder, `set_S101_2`; the first untouched.
7	Edits ▸ delivery report. Then Content ▸ select folder…, `production`; push the new S-101 tile; Audit ▸ review Full.	The report carries the conversion as a step with its time and the certificate's id. The product staged as an S-101 set (UAT-27), its catalogue verified; the audit by S-158 runs on it (UAT-30).

pass fail not run note

Timesheet

From the delivery report (UAT-22), beside the same line of the version before. A time compares only with a run of the same set on the same computer.

	this version	the version before
version
the set
measured on
staging
the review
the audit
the chart
the object list
a model's run
the walradar reading
the conversion
production time
processing time
in the postProcessor
the cartographer's time

The result

0pass0fail 0not run36not answered

this version of postProcessor is accepted accepted with remarks not accepted

date

remarks

a new file with your answers in it; keep it beside the delivery report