oapi-profile-builder 3.1.0__tar.gz → 3.2.1__tar.gz

{oapi_profile_builder-3.1.0/src/oapi_profile_builder.egg-info → oapi_profile_builder-3.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: oapi-profile-builder
-Version: 3.1.0
+Version: 3.2.1
 Summary: Authoritative tooling for creating OGC API Service Profiles (EDR, Features)
 Author-email: Shane Mill <shane.mill@noaa.gov>
 License: Apache License
@@ -41,11 +41,13 @@ Requires-Dist: pyyaml>=6.0
 Requires-Dist: requests>=2.31
 Provides-Extra: validate
 Requires-Dist: schemathesis>=3.0; extra == "validate"
+Provides-Extra: pdf
+Requires-Dist: pillow>=10.0; extra == "pdf"
 Dynamic: license-file
 
 # OGC API Service Profile Builder
 
-Generate OGC API - EDR Part 3 Service Profile artifacts from a YAML config — OpenAPI 3.1.0, AsyncAPI, AsciiDoc requirements, and conformance tests.
+Generate OGC API - EDR Part 3 Service Profile artifacts from a YAML config — OpenAPI 3.1.0, AsyncAPI, AsciiDoc requirements and conformance tests, and a publication-ready Metanorma PDF with optional custom (e.g. DGIWG) branding.
 
 [![PyPI](https://img.shields.io/pypi/v/oapi-profile-builder)](https://pypi.org/project/oapi-profile-builder/)
 [![License](https://img.shields.io/badge/license-Apache-blue)](LICENSE)
@@ -80,13 +82,16 @@ output/
 
 ## Example Profiles
 
-Three working examples are included:
+Six working examples are included:
 
 | File | What it shows |
 |---|---|
 | [`examples/minimal_profile.yaml`](examples/minimal_profile.yaml) | Smallest valid profile — one collection, one requirement |
 | [`examples/insitu_observations_profile.yaml`](examples/insitu_observations_profile.yaml) | Full meteorological profile — 8 parameters with QUDT units, CF standard names, metocean extensions, CRS listing, temporal extent, custom dimensions, `parameter_schema` |
+| [`examples/nws_connect_profile.yaml`](examples/nws_connect_profile.yaml) | PubSub profile — generates `asyncapi.yaml` alongside the OpenAPI |
 | [`examples/nwsviz_profile.yaml`](examples/nwsviz_profile.yaml) | Production profile — 13 collections, 3 OGC API Processes, PDF metadata |
+| [`examples/nwp_radar.yaml`](examples/nwp_radar.yaml) | **DGIWG-branded** profile — custom cover logo, DGIWG colours/footer/legal page, `default_output_format`, per-query CRS, vertical `positive`, DGIWG namespace |
+| [`examples/nwp_earth_observations_lightning_profile.yaml`](examples/nwp_earth_observations_lightning_profile.yaml) | DGIWG lightning profile — same branding, CF units |
 
 ---
 
@@ -115,6 +120,8 @@ Add `--pdf` to also compile an OGC-compliant PDF via the `metanorma/metanorma` D
 oapi-profile-builder generate --config my_profile.yaml --output ./output --pdf
 ```
 
+The PDF can be rebranded for another SDO (e.g. DGIWG) — custom cover logo, colours, legal page, footer, and identifier namespace — all from the profile config. See [Document generation and branding](#document-generation-and-branding).
+
 ### `validate`
 
 Validates the config without writing any files. Useful in CI before generating.
@@ -219,6 +226,29 @@ jobs:
 
 ---
 
+## Document generation and branding
+
+With `--pdf`, the builder compiles a Metanorma document (`document.adoc` + `sections/`, `requirements/`, `abstract_tests/`) into `document.pdf` using the official `metanorma/metanorma` Docker image. By default this is an OGC `draft-standard` document.
+
+Everything about the document — cover, title-page metadata, legal page, footer, colours, and even the requirement/conformance identifier namespace — is driven from the profile config, so the same tooling can produce a document branded for another SDO such as **DGIWG** with no OGC branding remaining.
+
+| What you want to change | Field | Mechanism |
+|---|---|---|
+| Cover logo + tagline (replaces the OGC cover) | `document_metadata.cover` | Generated cover image via `:coverpage-image:` full replacement |
+| Title, doc number, edition, dates, sub-title/status | `title`, `version`, `document_metadata.{doc_number, doc_type, doc_subtype, status, *_date}` | Metanorma document attributes |
+| PDF colours (titles, tables, cover, backgrounds) | `document_metadata.colors` | `:presentation-metadata-color-*:` |
+| Page-ii legal text (copyright / license / notice) | `document_metadata.boilerplate` | `:boilerplate-authority:` |
+| Footer organisation name | `document_metadata.copyright_holder` | `:copyright-holder:` |
+| Remove the OGC logo from the legal page | `document_metadata.suppress_flavor_logo` | targeted `:pdf-stylesheet-override:` |
+| Requirement / conformance identifier namespace | `spec_uri_base` | derives `req_uri` / `conf_uri` |
+| Submitter table, notice paragraph, normative refs | `document_metadata.{submitters, notice, normative_references}` | Metanorma attributes / sections |
+
+Custom branding requires Pillow for the cover image: `pip install 'oapi-profile-builder[pdf]'`. Field-by-field detail is in the [`document_metadata`](#document_metadata) reference below; [`examples/nwp_radar.yaml`](examples/nwp_radar.yaml) is a complete DGIWG-branded example.
+
+> The `suppress_flavor_logo` override reaches into the OGC Metanorma flavor's XSL (template `insertLogoPreface`) and is coupled to that flavor. Everything else uses documented Metanorma attributes. For long-term SDO adoption, a dedicated Metanorma "taste"/flavor is the most durable path.
+
+---
+
 ## Profile Config Reference
 
 A profile config is a YAML file. The full JSON Schema is at [`profile.schema.json`](profile.schema.json).
@@ -445,6 +475,61 @@ extent_requirements:
 
 At least one of `extent_crs` or `supported_crs` is required. The same applies to TRS and VRS — all are optional individually but at least one CRS constraint must be present.
 
+#### Vertical direction (`positive`)
+
+OGC API - EDR's vertical extent has no field for which way values increase. This is ambiguous for VRS like pressure levels, which different providers order top-to-bottom or bottom-to-top inconsistently (pressure increases as altitude *decreases*). Set `extent.vertical.positive` to `up` or `down` on a collection (following the CF Conventions `positive` attribute) to make the ordering explicit:
+
+```yaml
+collections:
+  - id: my_collection
+    extent:
+      spatial: { ... }
+      vertical:
+        interval:
+          - ["1000", "100"]   # hPa, surface to top of atmosphere
+        values: ["1000", "850", "700", "500", "300", "100"]
+        vrs: "http://www.opengis.net/def/crs/EPSG/0/5798"  # or similar pressure VRS
+        positive: down   # pressure increases downward, toward the surface
+```
+
+Set `extent_requirements.require_vertical_direction: true` to make `positive` mandatory on every collection with a vertical extent, so a profile can enforce one consistent convention rather than leaving it up to each collection author:
+
+```yaml
+extent_requirements:
+  minimum_bbox: [-180, -90, 180, 90]
+  extent_crs:
+    allowed: ["http://www.opengis.net/def/crs/OGC/1.3/CRS84"]
+  require_vertical_direction: true
+```
+
+---
+
+### `output_formats`
+
+Maps format names (referenced by `collections[].output_formats` and `data_queries.*.variables.output_formats`) to a media type and, optionally, a schema reference. The `schema_ref` flows into the generated OpenAPI response `content` for that format — use it to point a format at a specific schema (e.g. a DGIWG-published schema for GeoTIFF or CoverageJSON) instead of the tool's built-in default.
+
+```yaml
+output_formats:
+  - name: CoverageJSON
+    media_type: application/prs.coverage+json
+    schema_ref: https://schemas.opengis.net/covjson/1.0/coveragejson.json
+  - name: GeoJSON
+    media_type: application/geo+json
+    schema_ref: https://geojson.org/schema/FeatureCollection.json
+  - name: GeoTIFF
+    media_type: image/tiff; application=geotiff
+    # Omit schema_ref until a published schema exists for this format —
+    # the requirement/abstract test can still state the standard to conform to.
+```
+
+| Field | Required | Description |
+|---|---|---|
+| `name` | yes | Format name, referenced elsewhere as a string (e.g. `CoverageJSON`) |
+| `media_type` | yes | MIME type used as the OpenAPI response `content` key and the `f` parameter value |
+| `schema_ref` | no | URL to a JSON Schema (or other schema) for this format. When set, the generated response uses `{"$ref": schema_ref}`; when omitted, a generic/default schema is used |
+
+`schema_ref` is optional — if no schema exists yet for a format (as is currently the case for some binary formats like GeoTIFF), leave it unset and capture the required standard as a normative `requirements[]` entry instead. Add `schema_ref` later once a schema URL exists.
+
 ---
 
 ### `parameter_schema`
@@ -601,6 +686,55 @@ document_metadata:
 
 The cover-page sub-title (e.g. "Draft Standard — Implementation — Approved") is produced by Metanorma from the `doc_type`, `doc_subtype`, and `status` combination.
 
+#### Custom branding (logo + colors)
+
+Two `document_metadata` blocks let you rebrand the PDF (e.g. for DGIWG) without a custom Metanorma flavor:
+
+- **`colors`** — recolours the PDF via Metanorma's `:presentation-metadata-color-*:` attributes. Values are hex colours.
+- **`cover`** — replaces the built-in OGC cover page with a generated one: your logo plus the document's title, number, edition and date. Requires Pillow (`pip install 'oapi-profile-builder[pdf]'`). The builder renders `cover.png` into the output directory and points Metanorma at it via `:coverpage-image:` + `:presentation-metadata-full-coverpage-replacement:`.
+
+```yaml
+document_metadata:
+  doc_number: "DGIWG 134"
+  cover:
+    logo: assets/dgiwg_logo.png    # path relative to the working directory (or absolute)
+    tagline: Delivering Military Advantage through multi-national geospatial interoperability
+    background: "#FFFFFF"          # optional cover background (default white)
+    text_color: "#1F3864"          # optional cover text colour (default black)
+  colors:
+    text: "#000000"                # body text
+    cover_text: "#1F3864"          # cover text / section numbers / ToC
+    cover_lines: "#1F3864"         # preface 'crossing lines' element
+    title: "#1F3864"               # clause/table/figure titles
+    page_background: "#FFFFFF"     # cover + section page background
+    table_header: "#1F3864"        # table header background
+    table_row_even: "#EEF1F7"      # even table rows
+    table_row_odd: "#FFFFFF"       # odd table rows
+```
+
+Note: colours work against the normal OGC cover too. The `cover` block does a *full* cover replacement, so the dynamic title/number/edition/date are drawn onto the generated image (which is why the builder composes it rather than relying on Metanorma attributes — logo attributes like `:coverpage-image:` alone are not rendered by the OGC flavor).
+
+#### De-branding the rest of the document (legal page + footer + logo)
+
+Cover + colors handle the front page, but the OGC flavor also stamps its identity on the page-ii legal boilerplate, the page footer, and an OGC logo on the legal page. Three more `document_metadata` fields remove those:
+
+- **`copyright_holder`** — sets `:copyright-holder:`, which also drives the **PDF footer** organisation name (replacing "OPEN GEOSPATIAL CONSORTIUM").
+- **`boilerplate`** — replaces the page-ii legal text (copyright / license / legal notice / feedback) via `:boilerplate-authority:`. Any field left unset is synthesised from `copyright_holder`, so no OGC text leaks through.
+- **`suppress_flavor_logo`** — removes the OGC logo from the preface/legal page via a targeted PDF-stylesheet override. (Coupled to the OGC Metanorma flavor's XSL.)
+
+```yaml
+document_metadata:
+  copyright_holder: DGIWG
+  suppress_flavor_logo: true
+  boilerplate:
+    copyright: "Copyright © 2026 Defence Geospatial Information Working Group (DGIWG). All rights reserved."
+    license: "Use of this document is subject to the DGIWG terms and conditions."
+    legal: "Attention is drawn to the possibility that some elements may be subject to patent rights; DGIWG shall not be held responsible for identifying any such rights."
+    feedback: "Comments on this document should be directed to DGIWG."
+```
+
+With `cover` + `colors` + `copyright_holder` + `boilerplate` + `suppress_flavor_logo` (and `spec_uri_base` for the requirement/conformance identifiers), the generated PDF carries no OGC branding — only legitimate citations to the OGC standards the profile conforms to. See [`examples/nwp_radar.yaml`](examples/nwp_radar.yaml).
+
 ---
 
 ### `provider`, `classification`, and provenance metadata
@@ -672,6 +806,7 @@ The tool enforces these rules at build time. Violations produce clear error mess
 | Collection TRS validated | Each `extent.temporal.trs` checked against `extent_trs` |
 | `crs_details` / `crs` validated | Each `data_queries.*.variables.crs_details[].crs` and `crs[]` checked against `supported_crs` |
 | `default_output_format` validated | Each `data_queries.*.variables.default_output_format` must be one of that query's `output_formats` |
+| `require_vertical_direction` enforced | If set, every collection with a vertical extent must declare `extent.vertical.positive` as `up` or `down` |
 | Document dates format | `submission_date` / `approval_date` / `publication_date` must be `YYYY-MM-DD` |
 | Parameters need `unit` + `observedProperty` | Required by OGC API - EDR Part 3 |
 | `parameter_name_pattern` enforced | All `parameter_names` keys must match if set |

{oapi_profile_builder-3.1.0 → oapi_profile_builder-3.2.1}/README.md

@@ -1,6 +1,6 @@
 # OGC API Service Profile Builder
 
-Generate OGC API - EDR Part 3 Service Profile artifacts from a YAML config — OpenAPI 3.1.0, AsyncAPI, AsciiDoc requirements, and conformance tests.
+Generate OGC API - EDR Part 3 Service Profile artifacts from a YAML config — OpenAPI 3.1.0, AsyncAPI, AsciiDoc requirements and conformance tests, and a publication-ready Metanorma PDF with optional custom (e.g. DGIWG) branding.
 
 [![PyPI](https://img.shields.io/pypi/v/oapi-profile-builder)](https://pypi.org/project/oapi-profile-builder/)
 [![License](https://img.shields.io/badge/license-Apache-blue)](LICENSE)
@@ -35,13 +35,16 @@ output/
 
 ## Example Profiles
 
-Three working examples are included:
+Six working examples are included:
 
 | File | What it shows |
 |---|---|
 | [`examples/minimal_profile.yaml`](examples/minimal_profile.yaml) | Smallest valid profile — one collection, one requirement |
 | [`examples/insitu_observations_profile.yaml`](examples/insitu_observations_profile.yaml) | Full meteorological profile — 8 parameters with QUDT units, CF standard names, metocean extensions, CRS listing, temporal extent, custom dimensions, `parameter_schema` |
+| [`examples/nws_connect_profile.yaml`](examples/nws_connect_profile.yaml) | PubSub profile — generates `asyncapi.yaml` alongside the OpenAPI |
 | [`examples/nwsviz_profile.yaml`](examples/nwsviz_profile.yaml) | Production profile — 13 collections, 3 OGC API Processes, PDF metadata |
+| [`examples/nwp_radar.yaml`](examples/nwp_radar.yaml) | **DGIWG-branded** profile — custom cover logo, DGIWG colours/footer/legal page, `default_output_format`, per-query CRS, vertical `positive`, DGIWG namespace |
+| [`examples/nwp_earth_observations_lightning_profile.yaml`](examples/nwp_earth_observations_lightning_profile.yaml) | DGIWG lightning profile — same branding, CF units |
 
 ---
 
@@ -70,6 +73,8 @@ Add `--pdf` to also compile an OGC-compliant PDF via the `metanorma/metanorma` D
 oapi-profile-builder generate --config my_profile.yaml --output ./output --pdf
 ```
 
+The PDF can be rebranded for another SDO (e.g. DGIWG) — custom cover logo, colours, legal page, footer, and identifier namespace — all from the profile config. See [Document generation and branding](#document-generation-and-branding).
+
 ### `validate`
 
 Validates the config without writing any files. Useful in CI before generating.
@@ -174,6 +179,29 @@ jobs:
 
 ---
 
+## Document generation and branding
+
+With `--pdf`, the builder compiles a Metanorma document (`document.adoc` + `sections/`, `requirements/`, `abstract_tests/`) into `document.pdf` using the official `metanorma/metanorma` Docker image. By default this is an OGC `draft-standard` document.
+
+Everything about the document — cover, title-page metadata, legal page, footer, colours, and even the requirement/conformance identifier namespace — is driven from the profile config, so the same tooling can produce a document branded for another SDO such as **DGIWG** with no OGC branding remaining.
+
+| What you want to change | Field | Mechanism |
+|---|---|---|
+| Cover logo + tagline (replaces the OGC cover) | `document_metadata.cover` | Generated cover image via `:coverpage-image:` full replacement |
+| Title, doc number, edition, dates, sub-title/status | `title`, `version`, `document_metadata.{doc_number, doc_type, doc_subtype, status, *_date}` | Metanorma document attributes |
+| PDF colours (titles, tables, cover, backgrounds) | `document_metadata.colors` | `:presentation-metadata-color-*:` |
+| Page-ii legal text (copyright / license / notice) | `document_metadata.boilerplate` | `:boilerplate-authority:` |
+| Footer organisation name | `document_metadata.copyright_holder` | `:copyright-holder:` |
+| Remove the OGC logo from the legal page | `document_metadata.suppress_flavor_logo` | targeted `:pdf-stylesheet-override:` |
+| Requirement / conformance identifier namespace | `spec_uri_base` | derives `req_uri` / `conf_uri` |
+| Submitter table, notice paragraph, normative refs | `document_metadata.{submitters, notice, normative_references}` | Metanorma attributes / sections |
+
+Custom branding requires Pillow for the cover image: `pip install 'oapi-profile-builder[pdf]'`. Field-by-field detail is in the [`document_metadata`](#document_metadata) reference below; [`examples/nwp_radar.yaml`](examples/nwp_radar.yaml) is a complete DGIWG-branded example.
+
+> The `suppress_flavor_logo` override reaches into the OGC Metanorma flavor's XSL (template `insertLogoPreface`) and is coupled to that flavor. Everything else uses documented Metanorma attributes. For long-term SDO adoption, a dedicated Metanorma "taste"/flavor is the most durable path.
+
+---
+
 ## Profile Config Reference
 
 A profile config is a YAML file. The full JSON Schema is at [`profile.schema.json`](profile.schema.json).
@@ -400,6 +428,61 @@ extent_requirements:
 
 At least one of `extent_crs` or `supported_crs` is required. The same applies to TRS and VRS — all are optional individually but at least one CRS constraint must be present.
 
+#### Vertical direction (`positive`)
+
+OGC API - EDR's vertical extent has no field for which way values increase. This is ambiguous for VRS like pressure levels, which different providers order top-to-bottom or bottom-to-top inconsistently (pressure increases as altitude *decreases*). Set `extent.vertical.positive` to `up` or `down` on a collection (following the CF Conventions `positive` attribute) to make the ordering explicit:
+
+```yaml
+collections:
+  - id: my_collection
+    extent:
+      spatial: { ... }
+      vertical:
+        interval:
+          - ["1000", "100"]   # hPa, surface to top of atmosphere
+        values: ["1000", "850", "700", "500", "300", "100"]
+        vrs: "http://www.opengis.net/def/crs/EPSG/0/5798"  # or similar pressure VRS
+        positive: down   # pressure increases downward, toward the surface
+```
+
+Set `extent_requirements.require_vertical_direction: true` to make `positive` mandatory on every collection with a vertical extent, so a profile can enforce one consistent convention rather than leaving it up to each collection author:
+
+```yaml
+extent_requirements:
+  minimum_bbox: [-180, -90, 180, 90]
+  extent_crs:
+    allowed: ["http://www.opengis.net/def/crs/OGC/1.3/CRS84"]
+  require_vertical_direction: true
+```
+
+---
+
+### `output_formats`
+
+Maps format names (referenced by `collections[].output_formats` and `data_queries.*.variables.output_formats`) to a media type and, optionally, a schema reference. The `schema_ref` flows into the generated OpenAPI response `content` for that format — use it to point a format at a specific schema (e.g. a DGIWG-published schema for GeoTIFF or CoverageJSON) instead of the tool's built-in default.
+
+```yaml
+output_formats:
+  - name: CoverageJSON
+    media_type: application/prs.coverage+json
+    schema_ref: https://schemas.opengis.net/covjson/1.0/coveragejson.json
+  - name: GeoJSON
+    media_type: application/geo+json
+    schema_ref: https://geojson.org/schema/FeatureCollection.json
+  - name: GeoTIFF
+    media_type: image/tiff; application=geotiff
+    # Omit schema_ref until a published schema exists for this format —
+    # the requirement/abstract test can still state the standard to conform to.
+```
+
+| Field | Required | Description |
+|---|---|---|
+| `name` | yes | Format name, referenced elsewhere as a string (e.g. `CoverageJSON`) |
+| `media_type` | yes | MIME type used as the OpenAPI response `content` key and the `f` parameter value |
+| `schema_ref` | no | URL to a JSON Schema (or other schema) for this format. When set, the generated response uses `{"$ref": schema_ref}`; when omitted, a generic/default schema is used |
+
+`schema_ref` is optional — if no schema exists yet for a format (as is currently the case for some binary formats like GeoTIFF), leave it unset and capture the required standard as a normative `requirements[]` entry instead. Add `schema_ref` later once a schema URL exists.
+
 ---
 
 ### `parameter_schema`
@@ -556,6 +639,55 @@ document_metadata:
 
 The cover-page sub-title (e.g. "Draft Standard — Implementation — Approved") is produced by Metanorma from the `doc_type`, `doc_subtype`, and `status` combination.
 
+#### Custom branding (logo + colors)
+
+Two `document_metadata` blocks let you rebrand the PDF (e.g. for DGIWG) without a custom Metanorma flavor:
+
+- **`colors`** — recolours the PDF via Metanorma's `:presentation-metadata-color-*:` attributes. Values are hex colours.
+- **`cover`** — replaces the built-in OGC cover page with a generated one: your logo plus the document's title, number, edition and date. Requires Pillow (`pip install 'oapi-profile-builder[pdf]'`). The builder renders `cover.png` into the output directory and points Metanorma at it via `:coverpage-image:` + `:presentation-metadata-full-coverpage-replacement:`.
+
+```yaml
+document_metadata:
+  doc_number: "DGIWG 134"
+  cover:
+    logo: assets/dgiwg_logo.png    # path relative to the working directory (or absolute)
+    tagline: Delivering Military Advantage through multi-national geospatial interoperability
+    background: "#FFFFFF"          # optional cover background (default white)
+    text_color: "#1F3864"          # optional cover text colour (default black)
+  colors:
+    text: "#000000"                # body text
+    cover_text: "#1F3864"          # cover text / section numbers / ToC
+    cover_lines: "#1F3864"         # preface 'crossing lines' element
+    title: "#1F3864"               # clause/table/figure titles
+    page_background: "#FFFFFF"     # cover + section page background
+    table_header: "#1F3864"        # table header background
+    table_row_even: "#EEF1F7"      # even table rows
+    table_row_odd: "#FFFFFF"       # odd table rows
+```
+
+Note: colours work against the normal OGC cover too. The `cover` block does a *full* cover replacement, so the dynamic title/number/edition/date are drawn onto the generated image (which is why the builder composes it rather than relying on Metanorma attributes — logo attributes like `:coverpage-image:` alone are not rendered by the OGC flavor).
+
+#### De-branding the rest of the document (legal page + footer + logo)
+
+Cover + colors handle the front page, but the OGC flavor also stamps its identity on the page-ii legal boilerplate, the page footer, and an OGC logo on the legal page. Three more `document_metadata` fields remove those:
+
+- **`copyright_holder`** — sets `:copyright-holder:`, which also drives the **PDF footer** organisation name (replacing "OPEN GEOSPATIAL CONSORTIUM").
+- **`boilerplate`** — replaces the page-ii legal text (copyright / license / legal notice / feedback) via `:boilerplate-authority:`. Any field left unset is synthesised from `copyright_holder`, so no OGC text leaks through.
+- **`suppress_flavor_logo`** — removes the OGC logo from the preface/legal page via a targeted PDF-stylesheet override. (Coupled to the OGC Metanorma flavor's XSL.)
+
+```yaml
+document_metadata:
+  copyright_holder: DGIWG
+  suppress_flavor_logo: true
+  boilerplate:
+    copyright: "Copyright © 2026 Defence Geospatial Information Working Group (DGIWG). All rights reserved."
+    license: "Use of this document is subject to the DGIWG terms and conditions."
+    legal: "Attention is drawn to the possibility that some elements may be subject to patent rights; DGIWG shall not be held responsible for identifying any such rights."
+    feedback: "Comments on this document should be directed to DGIWG."
+```
+
+With `cover` + `colors` + `copyright_holder` + `boilerplate` + `suppress_flavor_logo` (and `spec_uri_base` for the requirement/conformance identifiers), the generated PDF carries no OGC branding — only legitimate citations to the OGC standards the profile conforms to. See [`examples/nwp_radar.yaml`](examples/nwp_radar.yaml).
+
 ---
 
 ### `provider`, `classification`, and provenance metadata
@@ -627,6 +759,7 @@ The tool enforces these rules at build time. Violations produce clear error mess
 | Collection TRS validated | Each `extent.temporal.trs` checked against `extent_trs` |
 | `crs_details` / `crs` validated | Each `data_queries.*.variables.crs_details[].crs` and `crs[]` checked against `supported_crs` |
 | `default_output_format` validated | Each `data_queries.*.variables.default_output_format` must be one of that query's `output_formats` |
+| `require_vertical_direction` enforced | If set, every collection with a vertical extent must declare `extent.vertical.positive` as `up` or `down` |
 | Document dates format | `submission_date` / `approval_date` / `publication_date` must be `YYYY-MM-DD` |
 | Parameters need `unit` + `observedProperty` | Required by OGC API - EDR Part 3 |
 | `parameter_name_pattern` enforced | All `parameter_names` keys must match if set |

{oapi_profile_builder-3.1.0 → oapi_profile_builder-3.2.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "oapi-profile-builder"
-version = "3.1.0"
+version = "3.2.1"
 description = "Authoritative tooling for creating OGC API Service Profiles (EDR, Features)"
 readme = "README.md"
 license = { file = "LICENSE" }
@@ -30,6 +30,7 @@ dependencies = [
 
 [project.optional-dependencies]
 validate = ["schemathesis>=3.0"]
+pdf = ["pillow>=10.0"]
 
 [project.urls]
 Homepage = "https://github.com/ShaneMill1/OGC-API-Service-Profile-Builder"

oapi_profile_builder-3.2.1/src/oapi_profile_builder/cover.py

@@ -0,0 +1,176 @@
+# =================================================================
+#
+# Authors: Shane Mill <shane.mill@noaa.gov>
+#
+# Copyright (c) 2026 Shane Mill
+#
+# Permission is hereby granted, free of charge, to any person
+# obtaining a copy of this software and associated documentation
+# files (the "Software"), to deal in the Software without
+# restriction, including without limitation the rights to use,
+# copy, modify, merge, publish, distribute, sublicense, and/or sell
+# copies of the Software, and to permit persons to whom the
+# Software is furnished to do so, subject to the following
+# conditions:
+#
+# The above copyright notice and this permission notice shall be
+# included in all copies or substantial portions of the Software.
+#
+# =================================================================
+"""
+Custom PDF cover-page generation.
+
+When a profile sets ``document_metadata.cover.logo``, the builder renders a
+replacement cover-page image (organisation logo + the document's title, number,
+edition and date) which Metanorma then uses in place of the built-in OGC cover
+via ``:coverpage-image:`` + ``:presentation-metadata-full-coverpage-replacement:``.
+
+Rendering uses Pillow. DejaVu fonts are bundled with Pillow and resolved by name,
+so no system font paths are required.
+"""
+
+from __future__ import annotations
+
+from datetime import datetime
+from pathlib import Path
+
+# A4 portrait at ~150 DPI.
+_PAGE_W = 1240
+_PAGE_H = 1754
+
+_COVER_FILENAME = "cover.png"
+
+
+def _load_font(bold: bool, size: int):
+    from PIL import ImageFont
+
+    name = "DejaVuSans-Bold.ttf" if bold else "DejaVuSans.ttf"
+    try:
+        return ImageFont.truetype(name, size)
+    except Exception:
+        # Last-resort fallback; not scalable but keeps rendering from failing.
+        return ImageFont.load_default()
+
+
+def _italic_font(size: int):
+    from PIL import ImageFont
+
+    try:
+        return ImageFont.truetype("DejaVuSans-Oblique.ttf", size)
+    except Exception:
+        return _load_font(False, size)
+
+
+def _format_date(iso_date: str | None) -> str | None:
+    """Format 'YYYY-MM-DD' as 'DD Month YYYY' (e.g. '15 May 2026')."""
+    if not iso_date:
+        return None
+    try:
+        dt = datetime.strptime(iso_date, "%Y-%m-%d")
+    except ValueError:
+        return iso_date
+    # %-d is not portable; strip a leading zero manually.
+    return f"{dt.day} {dt.strftime('%B %Y')}"
+
+
+def build_cover_image(profile, output_dir: Path) -> str | None:
+    """Render the cover PNG into output_dir. Returns its filename, or None.
+
+    Returns None when no cover logo is configured. Raises RuntimeError with a
+    clear message if Pillow is unavailable or the logo file cannot be found.
+    """
+    m = getattr(profile, "document_metadata", None)
+    cover = getattr(m, "cover", None) if m else None
+    if not cover or not cover.logo:
+        return None
+
+    try:
+        from PIL import Image, ImageDraw
+    except ImportError as exc:  # pragma: no cover - depends on env
+        raise RuntimeError(
+            "document_metadata.cover.logo is set but Pillow is not installed. "
+            "Install it with: pip install 'oapi-profile-builder[pdf]'"
+        ) from exc
+
+    logo_path = Path(cover.logo).expanduser()
+    if not logo_path.is_absolute():
+        logo_path = (Path.cwd() / logo_path).resolve()
+    if not logo_path.exists():
+        raise RuntimeError(f"Cover logo not found: {logo_path}")
+
+    bg = cover.background or "#FFFFFF"
+    fg = cover.text_color or "#000000"
+
+    page = Image.new("RGB", (_PAGE_W, _PAGE_H), bg)
+    draw = ImageDraw.Draw(page)
+
+    def centered(text: str, font, y: int, fill: str) -> int:
+        """Draw text horizontally centered; return the y below the text."""
+        bbox = draw.textbbox((0, 0), text, font=font)
+        tw = bbox[2] - bbox[0]
+        th = bbox[3] - bbox[1]
+        draw.text(((_PAGE_W - tw) / 2, y), text, font=font, fill=fill)
+        return y + th
+
+    y = 180
+
+    # --- Logo (centered, scaled to a target width) ---
+    logo = Image.open(logo_path).convert("RGBA")
+    target_logo_w = 420          # desired cover logo width
+    max_logo_w = 520             # hard cap
+    max_upscale = 3.0            # don't upscale tiny logos beyond this (avoids heavy blur)
+    desired = min(target_logo_w, int(logo.width * max_upscale), max_logo_w)
+    if logo.width != desired:
+        scale = desired / logo.width
+        logo = logo.resize((desired, max(1, int(logo.height * scale))))
+    logo_x = int((_PAGE_W - logo.width) / 2)
+    page.paste(logo, (logo_x, y), logo)
+    y += logo.height + 60
+
+    # --- Tagline (italic) ---
+    if cover.tagline:
+        y = centered(cover.tagline, _italic_font(30), y, fg) + 60
+
+    # --- Document number ---
+    if m and m.doc_number:
+        y = centered(m.doc_number, _load_font(True, 46), y, fg) + 40
+
+    # --- Edition ---
+    edition = getattr(profile, "version", None)
+    if edition:
+        y = centered(f"Edition {edition}", _load_font(False, 28), y, fg) + 24
+
+    # --- Date ---
+    date_str = _format_date(m.publication_date if m else None)
+    if date_str:
+        y = centered(f"Dated {date_str}", _load_font(False, 28), y, fg) + 80
+
+    # --- Title (large, bold, wrapped) ---
+    title = getattr(profile, "title", "") or ""
+    title_font = _load_font(True, 54)
+    for line in _wrap(draw, title, title_font, _PAGE_W - 240):
+        y = centered(line, title_font, y, fg) + 16
+
+    target = (output_dir / _COVER_FILENAME).resolve()
+    if not str(target).startswith(str(output_dir.resolve())):
+        raise RuntimeError(f"Refusing to write cover outside output directory: {target}")
+    page.save(target)
+    return _COVER_FILENAME
+
+
+def _wrap(draw, text: str, font, max_width: int) -> list[str]:
+    """Greedy word-wrap to fit max_width pixels."""
+    words = text.split()
+    lines: list[str] = []
+    cur = ""
+    for w in words:
+        trial = f"{cur} {w}".strip()
+        bbox = draw.textbbox((0, 0), trial, font=font)
+        if bbox[2] - bbox[0] <= max_width or not cur:
+            cur = trial
+        else:
+            lines.append(cur)
+            cur = w
+    if cur:
+        lines.append(cur)
+    return lines