Before a project begins.

These notes explain the website and inquiry process. A project needs its own agreed scope, price, schedule and acceptance criteria.

Service descriptions and examples

Service pages describe workflows and possible outputs. A format name, visual example or reference to a standard does not by itself confirm that a particular dataset meets your specification. Source quality, intended use and the agreed checks determine whether an output is suitable.

What an inquiry means

Submitting the form records a request for discussion. A receipt reference confirms that the website saved it; it is not a quote, booking, accepted project or delivery commitment.

What to agree in writing

Before production, define the source extent and condition, horizontal and vertical reference systems, units, required layers or classes, schema, output formats, quality checks and acceptance thresholds. Include responsibilities for missing or unsuitable source data, review rounds, corrections, pricing and delivery dates.

Sharing project material

Use the public form for a brief description. Confirm that you have permission to share source material, then agree the transfer method, access arrangements and any confidentiality requirements before transferring it.

Standards and downstream decisions

Links to external standards and software documentation help scope a workflow. Check the version required by your organization and record it in the project specification. Where data will support survey, engineering or other regulated decisions, identify the required qualified review and approval as part of that scope.

Questions or corrections

If a page is unclear or you need to confirm whether a workflow fits your project, send a question. Explain the intended use and the requirement you need clarified.