OSDC.Drilling.EarthGeodesy.WebPages 2.0.2

OSDC.Drilling.EarthGeodesy.WebPages

This release targets MudBlazor 9.9.0 and the matching OSDC shared web component packages.

Reusable Blazor pages for the OSDC EarthGeodesy catalog and stateless coordinate transformation service.

The package includes unit-aware coordinate transformation, searchable reference-ellipsoid and geodetic-datum catalog pages, read-only provenance displays for built-ins, create/edit/delete flows for custom catalog definitions, catalog information, and refreshable usage statistics. Latitude and longitude inputs and results are shown simultaneously as degrees-minutes-seconds and as decimal angles in the unit selected through the OSDC unit system; both input representations edit the same SI-radian value. Ellipsoid axes and datum-ensemble accuracy use selected length units, while prime-meridian longitude uses the selected geodesic-angle unit. All service calls retain SI radians and metres.

On the transformation page, completing latitude and longitude filters source and target datums through the directed graph of operations whose structured EPSG areas contain the position and which the deployed PROJ runtime can execute in the required direction. A coordinate change clears and explains any selection that is no longer usable. The statistics page presents refreshable summary totals and a sortable table separating REST transforms, MCP transforms, catalog reads, and catalog writes. The service retains these totals across restarts when its persistent /home volume is retained.

The ellipsoid editor uses the dedicated InverseFlattening quantity (meaningful display precision 1e-9) through OSDC unit components 3.4.4. The unit-conversion service must provide this quantity. Generated clients carry the SemanticCatalogue 0.5.0 contract explanations; SI values are not rounded when stored or submitted. Imported EPSG operation parameters retain their own declared units, as explained on Home and in SEMANTICS.md.

Author: Eric Cayeux
Company: NORCE Research

Bounded light discovery

Catalog discovery uses the existing bounded POST /ReferenceEllipsoid/Search, /GeodeticDatum/Search, and /GeodeticTransformation/Search summary contracts (default 25, maximum 100). The unbounded full-definition GET lists are removed. MCP catalog list tools already use these bounded summary searches. Read one selected definition by UUID before editing.

Pages contain Items, Offset, Limit, TotalCount, and NextOffset; NextOffset is null on the final page. Offset pages are individually consistent reads, not a snapshot spanning requests: concurrent inserts/deletes can change later pages. Refresh discovery when the underlying collection changes. EarthGeodesy's existing search pages instead expose Items[].Value, Offset, Limit, and TotalCount.

Single-record reads, result/chunk reads, and deliberate backup/export/restore operations are preserved. Backups can still contain complete resources and should be treated as explicit bulk operations.

This is a breaking REST/MCP contract change: update generated clients, UIs, and external integrations together with the service release. Removed heavy-list names are not compatibility aliases. No persisted engineering shapes, database names, or storage volumes are changed. Historical usage counters are retained; bounded discovery has a separate additive DiscoveryRequestsPerDay history in resource services.

Tables/selectors use light discovery. Editors retrieve the selected complete resource; category options load only for chosen or already assigned definitions. Slot context uses paginated light locations, and rig-history context reads the selected wellbore. Backup selection uses discovery while the dedicated export/restore APIs retain full backup semantics.

Package release 2.0.0

This release packages the current WebPages and generated contracts. Update consuming WebApps to OSDC.Drilling.EarthGeodesy.WebPages version 2.0.0 after it is available on nuget.org. This is a major update for the bounded light discovery contracts; rebuild consumers together with their updated service clients.

Trusted NuGet publishing

The publish-webpages-nuget.yml workflow authenticates with GitHub OIDC through NuGet/login@v1; no long-lived NUGET_API_KEY secret is used. Set NUGET_USER to the nuget.org profile username as a repository variable (a repository secret is also accepted). The publishing job requests contents: read and id-token: write and obtains its temporary credential immediately before uploading.

On nuget.org, the package owner must configure a trusted-publishing policy for Open-Source-Drilling-Community/EarthGeodesy, workflow filename publish-webpages-nuget.yml, with permission to push new versions of OSDC.Drilling.EarthGeodesy.WebPages. Leave the policy environment empty because the workflow does not declare a GitHub environment. Trigger the workflow manually with the intended version or push a webpages-v* tag. Already published versions are skipped.

Package release 2.0.1

Requires OSDC.UnitConversion.DrillingRazorMudComponents 3.4.9 so embedded unit selectors consume bounded UnitSystem discovery pages. Rebuild consuming WebApps after upgrading this package.

Package release 2.0.2

Preserves the nested reference-ellipsoid UUID when projecting lightweight datum search summaries into display references. Datum lists can resolve the ellipsoid name without fetching every full datum.