{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-xct-033","code":"wm-xct-033-geometry-coordinate-reference","url":"https://ver.cy/models/wm-xct-033-geometry-coordinate-reference/","name":"Geometry / Coordinate Reference","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Cross-cutting context","entryKind":"mixin","plane":"","domain":["XCT.GEO"],"industry":["Cross-industry"],"navPath":"NAV.XCT.GEO","tags":["geometry","coordinate","reference","xct.geo"],"facets":{}},"whatItIs":"WM-XCT-033 defines the semantics of a geometry value bound to a host thing, together with the coordinate-reference context needed to interpret that value and the declared provenance and quality of any transformation that produced it. Geometry here is mathematical and structural, not a file: WKT, WKB, GeoJSON, GML, database geometry columns and vendor APIs are projections of the value, never its canonical form. The mixin governs how geometry is typed, structured, bounded, asserted valid and disclosed within an adopting Dimension; it does not own the host, the CRS register, the computation engine or any operational evaluation, transformation execution or audit record held by a referenced system.","purpose":"Supply a reusable, encoding-neutral geometry and coordinate-reference mixin that lets any host thing carry a well-defined spatial shape: its type, coordinate structure, dimensionality, extent, state, declared quality and the coordinate reference system under which its numbers mean anything.","scope":{"in":["Geometry value semantics independent of any storage format or access interface","Primitive typing (point, curve, surface) and aggregate/multipart/collection membership","Coordinate sequences, ordinate ordering, minimum vertex counts, precision and declared spatial resolution","Topological dimension, coordinate dimension and spatial dimension, including Z and M ordinate handling","Ring structure: closure, orientation conventions, exterior rings and interior rings (holes)","Empty, absent, unknown and deliberately suppressed geometry states","Declared envelopes, extents and derived summary points such as centroids, with their provenance","Validity, simplicity and repair assertions recorded against a named validity profile","Declared spatial relations recorded as assertions with their evaluation context","Binding of the geometry value to a host thing, including role, cardinality and default-geometry designation","Binding of the geometry value to a referenced CRS, including axis order, longitude-range convention and coordinate-epoch reference for dynamic CRS","Declared quality, accuracy statement and provenance of coordinates produced by an externally executed coordinate transformation","Governance of geometry values inside an adopting Dimension: ownership, canonical form, access, disclosure control and retention"],"out":["Identity, classification and lifecycle of the host feature, place, asset or object that carries the geometry","The coordinate reference system register itself: CRS and datum definitions, ellipsoid and prime-meridian parameters, deprecation and supersession of CRS codes","Execution of coordinate operations and derivation of transformation parameters; this model carries only the reference to the operation used and the resulting quality statement","Geometry computation engines: overlay, buffering, simplification, triangulation, predicate evaluation and topology construction","Address, gazetteer, postal and place-name semantics","Cartographic styling, symbolization, generalization for display and map portrayal","Raster, coverage, point-cloud and gridded data models","Observation, survey campaign and sensor-measurement semantics that produced the coordinates","Route, network, linear-referencing and turn-restriction topology semantics","Selection of a canonical storage format, database schema or API surface","Audit-trail, enforcement and access-decision records owned by referenced runtime services"],"boundaries":[{"neighbor":"Host feature, place or object model","distinction":"A Spatial Thing is disjoint from its geometry: the lighthouse is not the polygon. The host owns real-world identity, classification and lifecycle; this mixin owns only the shape value and its binding role, and never asserts that a geometry identifies a thing."},{"neighbor":"Coordinate reference system register / authority model","distinction":"Coordinates are only interpretable against a CRS, but the register that defines CRSs, datums and their versions is a separate authority. This model carries a CRS reference by URI plus axis order and coordinate epoch; it does not define, version or deprecate CRSs."},{"neighbor":"Coordinate operation / transformation service","distinction":"The referenced service executes transformations and derives parameters. This model records only which operation was referenced, the resulting storage CRS and the declared positional-quality statement carried with the transformed value."},{"neighbor":"Geometry computation and spatial predicate engine","distinction":"Relation families (Simple Features, Egenhofer, RCC8, DE-9IM) and validity checks are evaluated by an external engine. This model records the asserted verdict, its profile and evaluation context as reference data, and never owns evaluation, enforcement or the evaluator's audit trail."},{"neighbor":"Encoding and serialization profile model","distinction":"WKT, WKB, GeoJSON geometry objects, GML geometry elements, JSON-FG place members and database geometry columns are projections. The encoding profile model owns encoding rules and conformance classes; this model owns which semantics must survive a projection and which are lossy."},{"neighbor":"Raster, coverage and gridded data model","distinction":"This mixin covers vector geometry only. Grid geometry, cell alignment and coverage domain semantics belong to the coverage model, even though both reference the same CRS context."},{"neighbor":"Route, network and linear-referencing model","distinction":"A LineString here is a shape, not a traversable edge. Connectivity, direction of travel, turn restrictions and measure-based linear referencing along a network belong to the network model; only the M ordinate as a stored value is in scope."},{"neighbor":"Vertical reference / height system model","distinction":"The Z ordinate is in scope as a stored spatial ordinate; the vertical datum, geoid model and height-system definition against which Z is meaningful is referenced, not defined here."}]},"distinguishingFeatures":["Treats geometry as a mathematical value with a coordinate reference, not as a file or encoding.","Requires explicit axis order, units and reference system for every value.","Records provenance and accuracy of any transformation that produced a geometry.","Leaves rasters, coverages and network routing to neighbouring models."],"structure":{"bundles":[{"id":"geo-core-bundle-value-structure","name":"Geometry Value and Structure","description":"What a geometry value is, what it is bound to, how it is typed and dimensioned, and how its coordinate sequences and ring structures are composed.","layers":[{"id":"geo-core-layer-identity-binding","name":"Geometry Identity and Reference Binding","description":"How a geometry value is identified through its host binding and how it references the coordinate reference system that makes its numbers interpretable.","findings":[{"id":"geo-core-finding-weak-identity","name":"Host-dependent weak identity of a geometry value","description":"A geometry has no independent real-world identity. It is a value bound to a host Spatial Thing with a declared role, and is identified through that binding (host identifier plus role plus version) or, where an independent handle is unavoidable, by a digest of its canonical form. The Spatial Thing persists across resurvey while its geometry is replaced, so a geometry identifier must never be presented as the identifier of the thing.","questions":[{"text":"Does this geometry carry an independent identifier, or is it identified only through its host binding, role and version?","id":"geo-core-q-weak-identity-handle","kind":"identity"},{"text":"Which Spatial Thing does this geometry represent, and is that thing recorded as distinct from the geometry object itself?","id":"geo-core-q-weak-identity-thing","kind":"definition"},{"text":"What binding role and cardinality apply - is this the default geometry, an alternative representation, or a derived generalization?","id":"geo-core-q-weak-identity-role","kind":"composition"},{"text":"If content-derived identity is used, which canonical form and digest algorithm produce it, and is it treated as a deduplication handle rather than a public identifier?","id":"geo-core-q-weak-identity-fingerprint","kind":"provenance"},{"text":"Which event time and which observation or ingestion time apply to this geometry value, separately from the host's own validity period?","id":"geo-core-q-weak-identity-time","kind":"temporal"}]},{"id":"geo-core-finding-crs-binding","name":"Coordinate reference system binding of the geometry value","description":"Coordinates are uninterpretable without a CRS. Every geometry value carries a resolvable CRS reference, an explicit axis-order statement matching the referenced coordinate system, a longitude-range convention where applicable, and, for a dynamic CRS, a coordinate-epoch reference. The register that defines those CRSs and any transformation between them is external; only the reference, the binding and subject-specific parameters are carried here.","questions":[{"text":"Which resolvable CRS identifier is bound to this geometry, and which authority resolves it?","id":"geo-core-q-crs-ref","kind":"authority"},{"text":"In which axis order are the coordinate tuples stored, and does that order follow the referenced coordinate system axes or an overriding delivery convention?","id":"geo-core-q-crs-axis-order","kind":"constraint"},{"text":"If the referenced CRS is dynamic, which coordinate epoch do these coordinates belong to?","id":"geo-core-q-crs-epoch","kind":"temporal"},{"text":"When no CRS reference is present, which default applies, and is that default asserted in the record or merely assumed by the consumer?","id":"geo-core-q-crs-default","kind":"interoperability"},{"text":"If these coordinates resulted from a coordinate transformation, which operation was referenced and what positional-quality statement accompanies the result?","id":"geo-core-q-crs-transform-quality","kind":"quality"}]}]},{"id":"geo-core-layer-type-system","name":"Geometry Type System and Dimensionality","description":"Primitive classes, aggregate and multipart membership, and the three distinct dimension concepts together with Z and M ordinate semantics.","findings":[{"id":"geo-core-finding-primitive-types","name":"Geometric primitive classes and edge interpolation","description":"The primitive classes are point (dimension 0), curve (dimension 1) and surface (dimension 2). A curve is defined by an ordered position sequence plus an interpolation rule connecting consecutive positions; the classical simple-feature and GeoJSON profiles assume straight linear interpolation, while richer schemas admit circular arcs, geodesics and other segment types. The interpolation rule is therefore a declared property of the geometry, not an implicit constant.","questions":[{"text":"Which primitive class does this geometry belong to - point, curve or surface - and which concrete type name expresses it?","id":"geo-core-q-primitive-class","kind":"classification"},{"text":"Which interpolation rule connects consecutive positions along a curve or a surface boundary?","id":"geo-core-q-primitive-interpolation","kind":"definition"},{"text":"Is a self-intersecting curve permitted here, and is a closed curve treated as a ring or merely as a closed line?","id":"geo-core-q-primitive-simple-closed","kind":"constraint"},{"text":"Which of these primitive types survive projection into the target encoding profile, and which degrade or fail?","id":"geo-core-q-primitive-encoding-fit","kind":"interoperability"}]},{"id":"geo-core-finding-aggregate-multipart","name":"Aggregate, multipart and collection membership","description":"Geometry values may aggregate parts: homogeneous multipart types (multi-point, multi-curve, multi-surface) and heterogeneous collections. Membership semantics must state whether parts are addressable, whether part order carries meaning, whether nesting is permitted, and whether parts are required to be disjoint. A single-part collection and a bare primitive are not interchangeable without an explicit rule.","questions":[{"text":"Is this value a homogeneous multipart aggregate or a heterogeneous geometry collection, and which part types does it admit?","id":"geo-core-q-aggregate-kind","kind":"classification"},{"text":"Are nested collections permitted, and if so to what depth?","id":"geo-core-q-aggregate-nesting","kind":"composition"},{"text":"Are individual parts separately addressable, and is part order semantically meaningful or incidental?","id":"geo-core-q-aggregate-part-order","kind":"identity"},{"text":"Must the parts be mutually disjoint or non-overlapping, and which party asserts that condition?","id":"geo-core-q-aggregate-disjoint","kind":"relationship"},{"text":"Is a single-part aggregate normalized to a bare primitive, and does that normalization change the recorded type?","id":"geo-core-q-aggregate-singleton","kind":"decision"}]},{"id":"geo-core-finding-dimension-zm","name":"Topological dimension, coordinate dimension and Z/M ordinates","description":"Three dimension concepts must be kept apart: topological dimension (0, 1, 2 or 3 for solids), coordinate dimension (the number of ordinates in each position) and spatial dimension (the count of spatial ordinates only). A third ordinate may be a spatial Z interpreted against a referenced vertical reference, or the ordinate set may include a non-spatial M measure; presence of Z and M is an explicit declared flag, not something inferred from tuple length.","questions":[{"text":"What are the topological dimension, coordinate dimension and spatial dimension of this geometry, and do they agree with its declared type?","id":"geo-core-q-dimension-triple","kind":"measurement"},{"text":"Is the third ordinate a spatial Z value or a non-spatial measure, and against which vertical reference is Z interpreted?","id":"geo-core-q-dimension-z-meaning","kind":"definition"},{"text":"Must Z and M be present on every position of the value, or may they be partially populated?","id":"geo-core-q-dimension-partial","kind":"constraint"},{"text":"What measure semantics and unit apply to the M ordinate, and who defines them?","id":"geo-core-q-dimension-m-semantics","kind":"measurement"},{"text":"How are Z and M carried, dropped or defaulted when the value is projected into an encoding that does not support them?","id":"geo-core-q-dimension-projection-loss","kind":"interoperability"}]}]},{"id":"geo-core-layer-coordinate-structure","name":"Coordinate Sequences and Ring Structure","description":"The ordered tuples that carry position, their cardinality and resolution constraints, and the ring structures that bound areas.","findings":[{"id":"geo-core-finding-coordinate-sequence","name":"Coordinate sequences, cardinality and resolution","description":"A geometry's positions form an ordered sequence of coordinate tuples with a uniform ordinate set. Each declared type imposes a minimum position count; repeated consecutive positions, stored ordinate precision and declared spatial resolution are separate properties that must not be confused with survey accuracy. Any serialized form of this sequence is a projection of the value.","questions":[{"text":"What is the minimum number of positions required for the declared geometry type, and does this value meet it?","id":"geo-core-q-sequence-minimum","kind":"constraint"},{"text":"What ordinate precision is stored and what spatial resolution is declared, and are these kept distinct from positional accuracy?","id":"geo-core-q-sequence-precision","kind":"quality"},{"text":"Are repeated consecutive positions permitted in the sequence, and how are they treated on validation and canonicalization?","id":"geo-core-q-sequence-duplicates","kind":"validation"},{"text":"Which encoding projection carried this coordinate sequence, and is that projection lossless for the declared ordinate set and precision?","id":"geo-core-q-sequence-encoding","kind":"interoperability"}]},{"id":"geo-core-finding-rings-orientation","name":"Rings, closure, orientation and interior boundaries","description":"An area is bounded by rings: a closed, simple curve. Closure may be explicit (a repeated final position) or implied by the encoding. Orientation conventions differ between standards - some require exterior rings counterclockwise and holes clockwise, others impose no orientation - so the model must record whether orientation is normative for the value or only a delivery convention. Interior rings (holes) are associated with exactly one exterior ring and must lie within it.","questions":[{"text":"Is ring closure represented by an explicit repeated final position, or implied by the encoding rules?","id":"geo-core-q-ring-closure","kind":"constraint"},{"text":"Which orientation convention applies to exterior and interior rings, and is that convention normative for this value or only a property of the delivery encoding?","id":"geo-core-q-ring-orientation","kind":"definition"},{"text":"How is each interior ring associated with its exterior ring, and may holes be nested, touch the exterior, or split the interior?","id":"geo-core-q-ring-holes","kind":"composition"},{"text":"Does a reversed or unclosed ring make the geometry invalid, or merely non-canonical and subject to normalization?","id":"geo-core-q-ring-invalidity","kind":"validation"}]}]}]},{"id":"geo-core-bundle-state-quality","name":"Geometry State, Extent and Declared Quality","description":"Whether a geometry exists at all, what extent summarizes it, and what validity, simplicity and relation assertions are carried with it.","layers":[{"id":"geo-core-layer-emptiness-extent","name":"Presence State and Declared Extent","description":"Distinguishing empty, absent, unknown and suppressed geometry, and recording envelopes and derived summary points with their provenance.","findings":[{"id":"geo-core-finding-empty-vs-absent","name":"Empty, absent, unknown and suppressed geometry","description":"An empty geometry is a typed value that carries no coordinate data yet retains its type and CRS binding; an absent geometry means no geometry is bound to the host at all, which standards permit for features without spatial properties. Unknown location and deliberately withheld location are further distinct states. Sentinel coordinates such as (0,0) must never stand in for any of these.","questions":[{"text":"Is the geometry empty with a retained type, absent from the host binding, unknown, or deliberately suppressed?","id":"geo-core-q-presence-state","kind":"state"},{"text":"Does an empty geometry retain its declared type, CRS binding and ordinate declarations?","id":"geo-core-q-empty-retains","kind":"constraint"},{"text":"How are sentinel or placeholder coordinates prevented from being read as a real position?","id":"geo-core-q-empty-sentinel","kind":"exception"},{"text":"Where location is generalized or withheld for privacy, safety or security reasons, is that recorded as suppression rather than as absence?","id":"geo-core-q-empty-suppression","kind":"privacy"}]},{"id":"geo-core-finding-envelope-extent","name":"Envelope, bounding box and derived summary points","description":"An envelope is an axis-aligned extent in the geometry's own CRS; a bounding box may instead be expressed in a delivery CRS with its own axis ordering. Both are derived summaries and must carry their derivation provenance and containment guarantee. Extents that cross the antimeridian invert the usual west-east ordering, and pole-containing extents use extreme latitudes; these are recorded conventions, not computations. Centroids and representative points are derived summary geometries under the same rules.","questions":[{"text":"Is the recorded extent an envelope in the geometry's own CRS or a bounding box expressed in a separate delivery CRS?","id":"geo-core-q-extent-frame","kind":"definition"},{"text":"How is an extent that crosses the antimeridian encoded, and how is a pole-containing extent expressed?","id":"geo-core-q-extent-antimeridian","kind":"exception"},{"text":"Was the extent computed from the coordinates, declared independently, or inherited from a parent collection?","id":"geo-core-q-extent-derivation","kind":"provenance"},{"text":"Is the extent guaranteed to contain the geometry, or is it an approximation subject to a stated tolerance?","id":"geo-core-q-extent-containment","kind":"quality"},{"text":"Which derived summary point is recorded - a mathematical centroid or a guaranteed interior representative point - and can it fall outside the geometry?","id":"geo-core-q-extent-summary-point","kind":"classification"}]}]},{"id":"geo-core-layer-validity-assertions","name":"Validity and Declared Relations","description":"Validity, simplicity and topological relations recorded as assertions against a named profile, with evaluation performed elsewhere.","findings":[{"id":"geo-core-finding-validity-simplicity","name":"Validity, simplicity and repair assertions","description":"Simplicity (no anomalous self-intersection) and validity (conformance to structural assertions such as ring closure, non-self-intersecting boundaries and correctly nested holes) are verdicts produced against a named rule profile at a stated tolerance. This model records the profile reference, the verdict, when it was assessed and which evaluator produced it; evaluation, repair execution and the evaluator's own audit trail belong to the referenced engine.","questions":[{"text":"Against which named validity profile and version was this geometry assessed, and what verdict was returned?","id":"geo-core-q-validity-profile","kind":"validation"},{"text":"Which evaluator produced the verdict, and is the verdict held here only as a reference to that external assessment?","id":"geo-core-q-validity-evaluator","kind":"evidence"},{"text":"What tolerance or snapping distance was applied when assessing coincident and near-coincident positions?","id":"geo-core-q-validity-tolerance","kind":"measurement"},{"text":"If the geometry was repaired or normalized, what changed and which prior value does the current one supersede?","id":"geo-core-q-validity-repair","kind":"provenance"},{"text":"At what observation time was validity last assessed, and does that assessment still apply to the current coordinate payload?","id":"geo-core-q-validity-staleness","kind":"temporal"}]},{"id":"geo-core-finding-declared-relations","name":"Declared spatial relations between geometry values","description":"Spatial relations may be recorded as assertions of record: a predicate from a named relation family (Simple Features, Egenhofer, RCC8, or a dimensionally extended nine-intersection pattern) between two geometry values, together with the CRS, dimensionality and tolerance under which the assertion holds. Recording an assertion never confers ownership of predicate evaluation, which stays with the referenced engine.","questions":[{"text":"Which relation family and predicate name is asserted between the two geometry values?","id":"geo-core-q-relation-predicate","kind":"relationship"},{"text":"Under which CRS, dimensionality and tolerance was the relation asserted?","id":"geo-core-q-relation-context","kind":"constraint"},{"text":"Is the relation an asserted fact of record, or a cached result of an external evaluation that may be recomputed and invalidated?","id":"geo-core-q-relation-status","kind":"evidence"},{"text":"Do the two related geometries share a CRS binding, and if not, how is that mismatch declared rather than silently resolved?","id":"geo-core-q-relation-crs-mismatch","kind":"interoperability"}]}]}]},{"id":"geo-core-bundle-boundary-cases","name":"Non-Planar and Extended Geometry Boundary Cases","description":"The cases where the planar, linear, two-dimensional default silently breaks: edge interpretation on a curved earth, the antimeridian and poles, curved segments, surface patches and solids.","layers":[{"id":"geo-core-layer-non-planar","name":"Non-Planar Interpretation and Extended Types","description":"Edge interpretation and wraparound handling, and the curved, patch-based and volumetric types beyond the linear planar core.","findings":[{"id":"geo-core-finding-edge-interpretation","name":"Planar, geodesic and wraparound edge interpretation","description":"Whether an edge between two positions is a straight line in the CRS coordinate space or a geodesic on the reference ellipsoid changes the shape on the ground and is not decidable from the coordinates alone. GeoJSON fixes edges as straight Cartesian lines in longitude/latitude and requires antimeridian-crossing geometry to be cut in two; other practice interprets the same tuples spherically. The interpretation, the antimeridian strategy, the longitude-range convention and the polar handling must all be declared.","questions":[{"text":"Are edges interpreted as straight lines in the CRS coordinate space or as geodesics on the reference ellipsoid?","id":"geo-core-q-edge-interpretation","kind":"definition"},{"text":"How does this geometry cross or avoid the antimeridian - by being cut into parts, by longitude values outside the normal range, or by a spherical interpretation?","id":"geo-core-q-edge-antimeridian","kind":"exception"},{"text":"Does the geometry enclose, touch or approach a pole, and which convention expresses that region?","id":"geo-core-q-edge-poles","kind":"spatial"},{"text":"Which interpretation prevails when the encoding profile's convention and the declared edge rule disagree?","id":"geo-core-q-edge-conflict","kind":"decision"}]},{"id":"geo-core-finding-curved-solid-extended","name":"Curved segments, surface patches and solid geometry","description":"Beyond linear planar types, OGC encodings admit circular strings, compound curves and curve polygons, patch-based surfaces such as polyhedral surfaces, triangulated networks and triangles, and volumetric solids expressed as polyhedra or prisms bounded by closed shells. Validity assertions written for planar simple features do not fully determine correctness for non-planar surfaces or solids, so the applicable rule set and any fallback linearization must be declared.","questions":[{"text":"Does the geometry use curved segments, a patch-based surface, or a volumetric solid beyond the linear simple-feature types?","id":"geo-core-q-extended-type","kind":"classification"},{"text":"For a solid, how are its bounding shells declared, and must each shell be closed and consistently orientable?","id":"geo-core-q-extended-solid-shells","kind":"constraint"},{"text":"Which validity rules apply to non-planar surfaces and solids, given that planar simple-feature assertions do not fully cover them?","id":"geo-core-q-extended-validity","kind":"validation"},{"text":"What fallback or linearized representation is offered to consumers that cannot process curved or volumetric geometry, and at what tolerance?","id":"geo-core-q-extended-fallback","kind":"interoperability"}]}]}]},{"id":"geo-crsid-bundle-identity","name":"CRS Identity, Authority and Registry Binding","description":"How a coordinate reference system is named, cited, resolved against its custodian, snapshotted with provenance, and status-checked - so that a CRS reference is verifiable and reproducible rather than a label.","layers":[{"id":"geo-crsid-layer-authority-binding","name":"Authoritative identification, carriage and provenance","description":"Which authority governs the definition, what code it issued, in what form the reference travels, whether a full definition is carried alongside it, and against which registry release it was resolved and pinned.","findings":[{"id":"geo-crsid-finding-authority-identifier","name":"Authoritative CRS identifier and authority binding","description":"The identifier of record for a CRS: the governing authority's registered token plus the code it issued, carried as an authority/code pair or as an OGC definition URI - never as a bare number or a label.","questions":[{"text":"Which authority issued the identifier of record for this CRS, and what exact code did it issue?","id":"geo-crsid-q-authid-issuer","kind":"identity"},{"text":"Is the cited authority the custodian that governs this definition, or a downstream mirror or vendor catalogue?","id":"geo-crsid-q-authid-custodian","kind":"authority"},{"text":"In what resolvable URI form is the identifier expressed for exchange, and does that URI carry a real registry version or the wildcard token?","id":"geo-crsid-q-authid-uri","kind":"interoperability"},{"text":"What rule forbids treating a bare code, a projection nickname or a vendor string as sufficient identification here?","id":"geo-crsid-q-authid-bare","kind":"constraint"},{"text":"Which secondary identifiers describe the same CRS, and which one prevails when they disagree?","id":"geo-crsid-q-authid-secondary","kind":"relationship"}]},{"id":"geo-crsid-finding-registry-snapshot","name":"Registry version, pinned snapshot and provenance","description":"The registry release a definition was read from and, where a copy is retained, its status as a provenance-bearing pinned snapshot with integrity evidence rather than a local registration.","questions":[{"text":"Which registry release and which retrieval event produced the definition currently held for this CRS?","id":"geo-crsid-q-snap-release","kind":"provenance"},{"text":"How is the observation time of the snapshot kept separate from the authority's own publication and revision dates?","id":"geo-crsid-q-snap-eventtime","kind":"temporal"},{"text":"What integrity evidence proves the held snapshot has not drifted from the authority record?","id":"geo-crsid-q-snap-integrity","kind":"evidence"},{"text":"Who may re-pin the snapshot, how long is the superseded pin kept, and what remains after it is reduced?","id":"geo-crsid-q-snap-repin","kind":"retention"},{"text":"What is recorded when the registry is unreachable and only a cached definition is available?","id":"geo-crsid-q-snap-degraded","kind":"exception"}]},{"id":"geo-crsid-finding-definition-carriage","name":"Reference by URI versus carried definition","description":"Whether a record carries only a resolvable CRS reference, a full definition, or both, what a carried definition must contain to be usable offline, and what is known to be lost in each carriage mode.","questions":[{"text":"Is the CRS carried by reference only, by full definition, or both, and what drove that choice?","id":"geo-crsid-q-carry-mode","kind":"decision"},{"text":"When both a reference and a full definition are present, which one prevails and how is divergence detected?","id":"geo-crsid-q-carry-precedence","kind":"composition"},{"text":"Which elements must a carried definition contain before it can be used without contacting the registry?","id":"geo-crsid-q-carry-required","kind":"requirement"},{"text":"Which version of the exchange form is declared, so that a consumer parses the carried definition against the right grammar?","id":"geo-crsid-q-carry-exchange","kind":"interoperability"},{"text":"What metadata is known to be absent when a definition travels as a well-known text string rather than as a registry record?","id":"geo-crsid-q-carry-loss","kind":"quality"}]}]},{"id":"geo-crsid-layer-record-status","name":"Names, aliases and registry record status","description":"How a CRS's human-facing labels are kept separate from its definition identity, and how validity, deprecation and supersession observed at the authority are represented locally.","findings":[{"id":"geo-crsid-finding-names-aliases","name":"Definition identity versus display names and aliases","description":"Separation of the authoritative definition identity from official names, display labels, aliases, legacy and vendor strings - none of which may be used to identify a CRS.","questions":[{"text":"What is the authority's official name for this CRS, and how does it differ from the label shown to users?","id":"geo-crsid-q-name-official","kind":"definition"},{"text":"Which recorded strings are authority aliases, which are legacy or vendor labels, and which are unclassified?","id":"geo-crsid-q-name-classify","kind":"classification"},{"text":"What rule prevents any name, alias or label from being resolved back to a definition on its own?","id":"geo-crsid-q-name-nonidentifying","kind":"constraint"},{"text":"Do two distinct CRS records share a name or alias here, and how is that ambiguity resolved?","id":"geo-crsid-q-name-collision","kind":"relationship"}]},{"id":"geo-crsid-finding-deprecation-supersession","name":"Deprecation, supersession and replacement chain","description":"Validity status observed from the authority - deprecated flags, replacement pointers, superseded realizations - and what a consumer must do when a referenced CRS is no longer valid.","questions":[{"text":"What validity status does the authority currently assign to this CRS record?","id":"geo-crsid-q-dep-status","kind":"state"},{"text":"Which record supersedes this one, and is the supersession a correction, a re-realization or a policy replacement?","id":"geo-crsid-q-dep-replacement","kind":"lifecycle"},{"text":"From when is the deprecation effective, and how does that relate to data already captured in the deprecated CRS?","id":"geo-crsid-q-dep-effective","kind":"temporal"},{"text":"Under what conditions may a deprecated CRS still be referenced, and who approves that?","id":"geo-crsid-q-dep-continued","kind":"exception"},{"text":"Which national or regional modernization programme drives this supersession, and what coordinate change does it imply?","id":"geo-crsid-q-dep-programme","kind":"relationship"}]}]}]},{"id":"geo-crsid-bundle-definition","name":"CRS Definition Content and Coordinate-System Semantics","description":"The substantive content of a static CRS definition: the reference frame it is tied to, the geodetic constants it uses, the coordinate system and axes that give a tuple meaning, its subtype and composition, and the extent over which its use is valid.","layers":[{"id":"geo-crsid-layer-datum-and-cs","name":"Datum, geodetic constants and coordinate system","description":"The two required components of a CRS definition - the datum that ties it to the object and the coordinate system that gives its tuples meaning - together with the ellipsoid and prime meridian constants the datum depends on.","findings":[{"id":"geo-crsid-finding-datum-ensemble","name":"Datum, datum ensemble and dynamic reference frame","description":"Which reference frame the CRS is tied to, whether it is a single realization, an ensemble of realizations, or a dynamic frame with a reference epoch, and what each choice implies for coordinate comparability.","questions":[{"text":"Which datum or reference frame does this CRS use, and by what authority code is that frame identified?","id":"geo-crsid-q-datum-which","kind":"identity"},{"text":"Is the referenced frame a single named realization, a datum ensemble, or a dynamic reference frame?","id":"geo-crsid-q-datum-kind","kind":"classification"},{"text":"If the frame is dynamic, what is its frame reference epoch and what coordinate epoch applies to the coordinates themselves?","id":"geo-crsid-q-datum-epoch","kind":"temporal"},{"text":"What comparability limit follows from citing an ensemble instead of a named realization?","id":"geo-crsid-q-datum-comparability","kind":"constraint"},{"text":"Which global or plate-fixed frame is this datum aligned to, and at what epoch was that alignment made?","id":"geo-crsid-q-datum-alignment","kind":"relationship"}]},{"id":"geo-crsid-finding-ellipsoid-primem","name":"Ellipsoid and prime meridian","description":"The geometric reference surface and the meridian from which longitudes are measured - the two constants that silently shift every coordinate value if assumed rather than read.","questions":[{"text":"Which ellipsoid parameters define the reference surface, and in which length unit are they expressed?","id":"geo-crsid-q-ellip-params","kind":"measurement"},{"text":"Which prime meridian does the CRS use, and what is its longitude offset from Greenwich?","id":"geo-crsid-q-primem-offset","kind":"identity"},{"text":"How is it verified that these constants match the authority record rather than an implementation default?","id":"geo-crsid-q-ellip-verify","kind":"validation"},{"text":"What is recorded when a CRS uses a non-Greenwich prime meridian or a spherical approximation?","id":"geo-crsid-q-primem-exception","kind":"exception"}]},{"id":"geo-crsid-finding-cs-axis","name":"Coordinate system type, dimension and axis definition","description":"The coordinate system that gives a tuple meaning - its type and axis count - and, per axis, the name, abbreviation, direction, explicit order, unit and range that must be read from the authority definition and never inferred from a code, label or encoding convention.","questions":[{"text":"Which coordinate system type does this CRS use, and how many axes does it declare?","id":"geo-crsid-q-cs-type","kind":"classification"},{"text":"For each axis, what are its name, abbreviation, direction, unit of measure and declared range?","id":"geo-crsid-q-axis-attributes","kind":"measurement"},{"text":"What is the authority-defined position of each axis in the coordinate tuple, and in which element was that order read explicitly?","id":"geo-crsid-q-axis-order","kind":"spatial"},{"text":"Where a serialization or interface imposes its own axis order, how is the divergence from the authority order recorded and reconciled?","id":"geo-crsid-q-axis-interface","kind":"interoperability"},{"text":"What evidence shows that a producing system's tuple length and axis order actually match the authority definition?","id":"geo-crsid-q-axis-evidence","kind":"validation"}]}]},{"id":"geo-crsid-layer-subtype-applicability","name":"CRS subtype, composition and declared applicability","description":"Which subtype of CRS is in play, how projected, derived and compound CRS are composed from their parts, and the scope and domain of validity that bound legitimate use.","findings":[{"id":"geo-crsid-finding-crs-subtype","name":"CRS subtype, base CRS and compound composition","description":"The subtype of the definition - geodetic or geographic, projected, vertical, engineering, compound or derived - with the base CRS and defining-conversion reference for derived and projected CRS, and the ordered component list for compound CRS.","questions":[{"text":"Which CRS subtype does this definition instantiate, and which element states it?","id":"geo-crsid-q-sub-which","kind":"classification"},{"text":"For a projected or derived CRS, which base CRS and which defining conversion does it reference?","id":"geo-crsid-q-sub-base","kind":"composition"},{"text":"For a compound CRS, which component CRS are combined, in which order, and what does each contribute?","id":"geo-crsid-q-sub-compound","kind":"relationship"},{"text":"For a vertical or engineering CRS, what is the height or local reference and what must not be assumed about it?","id":"geo-crsid-q-sub-vertical","kind":"constraint"},{"text":"When a subject needs horizontal and vertical position together, is a compound CRS or two separate references used, and why?","id":"geo-crsid-q-sub-decision","kind":"decision"}]},{"id":"geo-crsid-finding-scope-extent","name":"Scope and domain of validity","description":"The authority-stated purpose of the CRS and the geographic, vertical and temporal extent over which its use is valid, plus the applicability profile the adopting Dimension declares on top of it.","questions":[{"text":"What scope does the authority state for this CRS, and does the intended use fall inside it?","id":"geo-crsid-q-scope-fit","kind":"requirement"},{"text":"What is the declared domain of validity, and in which CRS is the bounding box itself expressed?","id":"geo-crsid-q-scope-extent","kind":"spatial"},{"text":"What follows when coordinates fall outside the declared domain of validity?","id":"geo-crsid-q-scope-outside","kind":"constraint"},{"text":"Which CRS are permitted for a given subject or collection, and who approved that list?","id":"geo-crsid-q-scope-permitted","kind":"ownership"},{"text":"How is the applicability profile expressed so a consumer knows which CRS it may ask for?","id":"geo-crsid-q-scope-advertise","kind":"interoperability"}]}]}]},{"id":"geo-crsdyn-time-dependent-reference","name":"Time-Dependent Reference Frame Context","description":"Context establishing whether a coordinate reference evolves with time, which frame realization or ensemble applies, which epochs are in force, and which deformation model reference governs movement between epochs.","layers":[{"id":"geo-crsdyn-frame-and-epoch","name":"Reference Frame Dynamics and Epoch Declaration","description":"Whether the underlying reference frame is static, plate-fixed or dynamic, the frame reference epoch that defines a dynamic frame, the coordinate epoch attached to coordinate values, and the strict separation of these geodetic instants from record time.","findings":[{"id":"geo-crsdyn-frame-dynamics","name":"Reference frame dynamics classification","description":"Declares explicitly whether the reference frame underlying a coordinate reference is static, plate-fixed or dynamic in the ISO 19111 sense that its defining parameters include time evolution, and records the frame reference epoch when the frame is dynamic. Frame dynamics is never inferred from a CRS name or code.","questions":[{"text":"Is the underlying reference frame static, plate-fixed or dynamic, and which defining clause or register attribute establishes that?","id":"geo-crsdyn-q-frame-kind","kind":"classification"},{"text":"What frame reference epoch defines this dynamic reference frame, and in which notation is it expressed?","id":"geo-crsdyn-q-frame-epoch-value","kind":"temporal"},{"text":"Which authority defines and publishes this frame realization, under which document and at which version?","id":"geo-crsdyn-q-frame-authority","kind":"authority"},{"text":"What evidence justifies treating the frame as static for the subject's stated positional tolerance?","id":"geo-crsdyn-q-frame-static-justification","kind":"evidence"}]},{"id":"geo-crsdyn-coordinate-epoch-binding","name":"Coordinate epoch and coordinate metadata binding","description":"Binds a coordinate set to its coordinate reference and, when that reference is dynamic, to the coordinate epoch, at an explicitly declared binding scope. Records the carrier that conveys the epoch and the disposition when no epoch is available.","questions":[{"text":"Is a coordinate epoch required for this coordinate set, and which rule or policy makes it required?","id":"geo-crsdyn-q-epoch-requirement","kind":"requirement"},{"text":"At which scope is the coordinate epoch bound — dataset, layer, feature or individual coordinate tuple?","id":"geo-crsdyn-q-epoch-binding-scope","kind":"composition"},{"text":"Which coordinate epoch value applies to these coordinates, in decimal year and as an RFC 3339 instant?","id":"geo-crsdyn-q-epoch-value-recorded","kind":"temporal"},{"text":"What disposition is recorded when a dynamic reference is used but no coordinate epoch can be established?","id":"geo-crsdyn-q-epoch-absent","kind":"exception"},{"text":"Which carrier field conveys the coordinate epoch in the chosen encoding, and what is lost if the carrier is absent?","id":"geo-crsdyn-q-epoch-carrier","kind":"interoperability"}]},{"id":"geo-crsdyn-epoch-time-semantics","name":"Separation of epoch and record time semantics","description":"Keeps coordinate epoch, observation time, transformation reference epoch, definition publication time and ingestion time as distinct recorded roles, so that a geodetic reference instant is never read as a record timestamp and a record timestamp is never substituted for an epoch.","questions":[{"text":"Which distinct time roles are recorded for this coordinate set, and how is each one defined?","id":"geo-crsdyn-q-time-role-definitions","kind":"definition"},{"text":"Does the observation time of these coordinates differ from their coordinate epoch, and what reconciled them?","id":"geo-crsdyn-q-observation-versus-epoch","kind":"temporal"},{"text":"When was the cited reference or deformation-model definition published, and when was this record ingested?","id":"geo-crsdyn-q-definition-and-ingest-time","kind":"provenance"},{"text":"Which validation prevents a coordinate epoch from being stored or interpreted as a record creation timestamp?","id":"geo-crsdyn-q-epoch-misread-guard","kind":"validation"}]}]},{"id":"geo-crsdyn-realization-and-deformation","name":"Datum Realization and Deformation Model References","description":"Whether a coordinate reference resolves to a specific datum realization or to a datum ensemble, and which published deformation or point-motion model reference a consumer must apply to move between epochs.","findings":[{"id":"geo-crsdyn-datum-ensemble-resolution","name":"Datum ensemble versus specific realization","description":"Records whether the reference resolves to a datum ensemble of multiple realizations treated as not significantly different, or to one named realization member, together with the published ensemble accuracy and the admissibility decision for the subject's tolerance.","questions":[{"text":"Does this coordinate reference resolve to a datum ensemble or to a single named realization member?","id":"geo-crsdyn-q-ensemble-or-member","kind":"identity"},{"text":"What ensemble accuracy is published for this ensemble, and does it satisfy the subject's positional tolerance?","id":"geo-crsdyn-q-ensemble-accuracy","kind":"measurement"},{"text":"Which realization members belong to the ensemble, and which member actually produced these coordinates?","id":"geo-crsdyn-q-ensemble-members","kind":"relationship"},{"text":"Under which constraint is ensemble-level referencing prohibited for this subject?","id":"geo-crsdyn-q-ensemble-prohibition","kind":"constraint"}]},{"id":"geo-crsdyn-deformation-model-reference","name":"Deformation and point-motion model reference","description":"Cites the deformation or point-motion model a consumer must apply to propagate coordinates between epochs, with identifier, publisher, version and declared spatial and temporal extent, and records what happens outside that extent. No displacement is computed, interpolated or stored here.","questions":[{"text":"Which deformation or point-motion model, at which published version, governs epoch propagation for this reference?","id":"geo-crsdyn-q-deformation-citation","kind":"provenance"},{"text":"What spatial and temporal extent bounds the cited deformation model's declared validity?","id":"geo-crsdyn-q-deformation-extent","kind":"spatial"},{"text":"Which authority publishes, versions and evaluates the cited deformation model?","id":"geo-crsdyn-q-deformation-ownership","kind":"ownership"},{"text":"What is recorded when the subject location or required epoch falls outside the cited model's declared extent?","id":"geo-crsdyn-q-deformation-out-of-extent","kind":"exception"}]}]}]},{"id":"geo-crsdyn-composite-and-nonregister","name":"Composite, Temporal and Non-Register Definition Context","description":"Context for references that are not a single current horizontal register entry: temporal and vertical components, compound composition and ordering, and definitions that are unknown, custom, engineering-local, superseded or preserved as governed snapshots.","layers":[{"id":"geo-crsdyn-temporal-and-vertical","name":"Temporal and Vertical Reference Components","description":"The non-horizontal components a position may be referenced against: a temporal axis with its datum origin, unit, calendar and time scale, and a vertical frame with its dynamics and geopotential realization.","findings":[{"id":"geo-crsdyn-temporal-reference","name":"Temporal reference, datum origin and time scale","description":"Records the temporal datum origin, the temporal axis kind and unit, the calendar in use, and the time scale the axis realizes, together with the leap-second exposure that follows from choosing a rotation-linked scale.","questions":[{"text":"What is the temporal datum origin of this axis, and in which calendar is it expressed?","id":"geo-crsdyn-q-temporal-origin","kind":"definition"},{"text":"Which time scale does the temporal axis realize, and which authority maintains that scale?","id":"geo-crsdyn-q-time-scale-realized","kind":"authority"},{"text":"Is the temporal axis a date-time, a temporal count or a temporal measure, and what unit does it use?","id":"geo-crsdyn-q-temporal-axis-kind","kind":"classification"},{"text":"How are leap seconds and the decided future change to the maximum UT1-UTC difference handled on this axis?","id":"geo-crsdyn-q-leap-second-exposure","kind":"constraint"}]},{"id":"geo-crsdyn-vertical-reference","name":"Vertical reference component and its dynamics","description":"Records the vertical reference frame heights or depths refer to, whether that frame is static or dynamic with its own frame reference epoch, the axis direction and unit, and the geoid or geopotential model version through which the frame is realized.","questions":[{"text":"Which vertical reference frame do these heights or depths refer to?","id":"geo-crsdyn-q-vertical-frame-identity","kind":"identity"},{"text":"Is the vertical reference frame static or dynamic, and does it carry its own frame reference epoch distinct from the horizontal frame?","id":"geo-crsdyn-q-vertical-dynamics","kind":"state"},{"text":"Through which geoid or geopotential model version is the vertical frame realized?","id":"geo-crsdyn-q-vertical-realization","kind":"provenance"},{"text":"Is the vertical axis a height with up positive or a depth with down positive, and in what unit?","id":"geo-crsdyn-q-vertical-axis-sense","kind":"measurement"}]}]},{"id":"geo-crsdyn-compound-composition","name":"Compound Reference Composition","description":"How independent component references are combined into one compound coordinate reference, in what declared order, and what axis sequence and epoch applicability result.","findings":[{"id":"geo-crsdyn-compound-components","name":"Compound reference components and ordering","description":"Enumerates the component references of a compound coordinate reference, their declared sequence, the resulting axis order and units, the independence condition that admits the combination, and how a coordinate epoch scopes across components.","questions":[{"text":"Which component coordinate references make up this compound reference?","id":"geo-crsdyn-q-compound-components","kind":"composition"},{"text":"In which order are the components declared, and what axis sequence and units result from that order?","id":"geo-crsdyn-q-compound-order","kind":"constraint"},{"text":"What evidence shows the components are independent, as a compound reference requires?","id":"geo-crsdyn-q-compound-independence","kind":"evidence"},{"text":"If any component is dynamic, does the coordinate epoch apply to that component alone or to the whole compound reference?","id":"geo-crsdyn-q-compound-epoch-scope","kind":"relationship"},{"text":"How is the compound reference degraded or rejected when a consumer supports only one component?","id":"geo-crsdyn-q-compound-degradation","kind":"interoperability"}]}]},{"id":"geo-crsdyn-nonregister-definitions","name":"Non-Register, Custom and Pinned Definitions","description":"References that are not resolvable as a current register entry — unknown, custom, engineering-local, deprecated or superseded — and the governed snapshots that keep historic coordinates interpretable.","findings":[{"id":"geo-crsdyn-nonregister-sufficiency","name":"Unknown, custom and engineering definition sufficiency","description":"Tests whether a non-register reference carries a resolvable definition or a complete governed snapshot sufficient to interpret coordinates without external lookup. A bare local name or a numeric code alone is insufficient and produces an unresolved state that blocks positional use.","questions":[{"text":"Is this reference unknown, custom, engineering-local, or a deprecated or superseded register entry?","id":"geo-crsdyn-q-nonregister-kind","kind":"classification"},{"text":"Does this reference carry a resolvable definition or a complete governed snapshot sufficient to interpret coordinates without external lookup?","id":"geo-crsdyn-q-definition-sufficiency","kind":"validation"},{"text":"For an engineering or local reference, which anchor point, orientation and carrier object define it, and does that carrier move?","id":"geo-crsdyn-q-engineering-anchor","kind":"spatial"},{"text":"Which state is recorded when a definition cannot be resolved, and which uses are then prohibited?","id":"geo-crsdyn-q-unresolved-state","kind":"state"},{"text":"Who may register, amend or approve a custom definition for the adopting Dimension?","id":"geo-crsdyn-q-custom-definition-approval","kind":"access"}]},{"id":"geo-crsdyn-pinned-snapshot","name":"Pinned definition snapshot and register provenance","description":"Preserves the exact canonical definition text, register authority, code and register version in force when coordinates were produced, with an integrity value, so that later register revisions, deprecations or supersessions do not silently change how historic coordinates are interpreted.","questions":[{"text":"Which register authority, register version and code identify the definition in force for these coordinates?","id":"geo-crsdyn-q-register-identity","kind":"identity"},{"text":"Which canonical form and integrity value fix the pinned definition text against silent drift?","id":"geo-crsdyn-q-snapshot-integrity","kind":"quality"},{"text":"How is a pinned snapshot marked when the register later deprecates or supersedes the entry?","id":"geo-crsdyn-q-snapshot-supersession","kind":"lifecycle"},{"text":"How long must a pinned snapshot be retained relative to the coordinates that cite it, and who executes disposal?","id":"geo-crsdyn-q-snapshot-retention","kind":"retention"}]}]}]},{"id":"geo-xform-operation-chain","name":"Coordinate Operation Chain and Reproducibility","description":"Everything needed to state, without ambiguity, which referencing context a coordinate came from, which it was moved to, by which ordered operations and pinned resources, and how the original can still be recovered.","layers":[{"id":"geo-xform-endpoints","name":"Operation Endpoints, Epoch and Applicability","description":"The referencing context at each end of the chain, its temporal qualification, and whether the chain is applicable to the subject geometry at all.","findings":[{"id":"geo-xform-crs-binding","name":"Source and target coordinate reference system binding","description":"The chain's endpoints, each carried as a resolvable governed reference to a registry-held CRS definition, plus any interpolation CRS the method requires.","questions":[{"text":"Which governed identifier names the source coordinate reference system and which names the target?","id":"geo-xform-q-endpoint-identity","kind":"identity"},{"text":"Is each coordinate reference system carried by resolvable reference rather than as a locally redefined description?","id":"geo-xform-q-crs-by-reference","kind":"interoperability"},{"text":"From which registry authority and dataset version were the endpoint definitions taken?","id":"geo-xform-q-crs-registry-version","kind":"provenance"},{"text":"Does any step require an interpolation coordinate reference system distinct from its source and target?","id":"geo-xform-q-interpolation-crs","kind":"composition"}]},{"id":"geo-xform-epoch","name":"Coordinate epoch and dynamic-frame qualification","description":"The epoch to which input and output coordinates are referenced, whether either endpoint is dynamic, and what happens when an epoch is required but absent.","questions":[{"text":"To which coordinate epoch are the input coordinates referenced, and to which epoch are the output coordinates referenced?","id":"geo-xform-q-epoch-values","kind":"temporal"},{"text":"Is either endpoint a dynamic coordinate reference system, so that coordinates without an epoch are ambiguous?","id":"geo-xform-q-dynamic-endpoint","kind":"state"},{"text":"Is a point-motion or deformation step required to move coordinates between the source and target epochs?","id":"geo-xform-q-point-motion-need","kind":"process"},{"text":"What outcome is recorded when a dynamic reference system is in use and no coordinate epoch is supplied?","id":"geo-xform-q-epoch-missing","kind":"exception"}]},{"id":"geo-xform-applicability","name":"Area of use, applicability test and ballpark or fallback status","description":"Whether the chain is declared valid where the subject actually lies, which spatial test was used, and whether the chain is a ballpark or null fallback with unknown accuracy.","questions":[{"text":"What area of use bounds each step of the chain, and does the subject geometry lie inside it?","id":"geo-xform-q-extent-fit","kind":"spatial"},{"text":"Which spatial test governed selection: strict containment of the area of interest or mere intersection?","id":"geo-xform-q-spatial-test","kind":"decision"},{"text":"Is the selected chain a ballpark, null or copy operation whose accuracy is unknown?","id":"geo-xform-q-ballpark-status","kind":"quality"},{"text":"What outcome is recorded when coordinates fall outside the declared area of use?","id":"geo-xform-q-out-of-area","kind":"exception"}]}]},{"id":"geo-xform-chain","name":"Operation Classification, Order and Method Pins","description":"What kind of operations make up the chain, in what order and direction they apply, and the exact method and parameter values that fix their behaviour.","findings":[{"id":"geo-xform-operation-class","name":"Conversion, transformation, point-motion and concatenation classification","description":"The classification of each step by whether it changes datum, changes epoch, or only re-expresses coordinates, and whether the whole is a single or a concatenated operation.","questions":[{"text":"Is each step a conversion, a transformation, a point-motion operation or a pure axis and unit change?","id":"geo-xform-q-step-class","kind":"classification"},{"text":"Do the source and target of a step share the same datum, making that step a conversion rather than a transformation?","id":"geo-xform-q-datum-change","kind":"definition"},{"text":"Is the chain a single operation or a concatenated operation, and which constituent operations form it?","id":"geo-xform-q-concatenation","kind":"composition"},{"text":"Which registry-held definition does each step cite, and was that definition current or superseded when pinned?","id":"geo-xform-q-definition-currency","kind":"relationship"}]},{"id":"geo-xform-method-pin","name":"Method, parameter, step order and direction pins","description":"The method identifier, the complete parameter set with units, the applied step order and the forward or inverse direction of each step, recorded so the chain can be rebuilt exactly.","questions":[{"text":"Which operation method identifier and version pin each step of the chain?","id":"geo-xform-q-method-identity","kind":"identity"},{"text":"Are all method parameter values recorded with explicit units and no implied or engine-defaulted values?","id":"geo-xform-q-parameter-completeness","kind":"constraint"},{"text":"In what order are the steps applied, and which of them are applied in the inverse direction?","id":"geo-xform-q-step-order-direction","kind":"process"},{"text":"Which operation version label identifies the parameter set, so that the same chain can be rebuilt later?","id":"geo-xform-q-operation-version","kind":"provenance"}]}]},{"id":"geo-xform-provenance","name":"External Resource Pins and Derived-Geometry Lineage","description":"The external resources and toolchain a result depended on, and the record that keeps the original geometry and CRS recoverable from any derived one.","findings":[{"id":"geo-xform-resource-pin","name":"Grid, model and toolchain resource pins","description":"Identity, version, integrity value and availability state of every correction resource a step depends on, plus the engine and registry dataset versions in force when the result was produced.","questions":[{"text":"Which grid, triangulated-network or deformation-model resources does the chain require, and how is each identified and versioned?","id":"geo-xform-q-resource-identity","kind":"identity"},{"text":"What integrity value binds this record to the exact resource content that was used?","id":"geo-xform-q-resource-integrity","kind":"evidence"},{"text":"What outcome is recorded when a required resource is unavailable at evaluation time?","id":"geo-xform-q-resource-missing","kind":"exception"},{"text":"Which transformation engine version and registry dataset version were in force when the result was produced?","id":"geo-xform-q-toolchain-pin","kind":"provenance"}]},{"id":"geo-xform-derived-lineage","name":"Original preservation and derived-geometry lineage","description":"The rule that a derived geometry never displaces its original, and the lineage record that ties the derived geometry back to the original geometry, original CRS and the chain that produced it.","questions":[{"text":"Which original geometry and original coordinate reference system does this derived geometry come from?","id":"geo-xform-q-original-preserved","kind":"provenance"},{"text":"Which representation is authoritative when the original and a derived geometry disagree?","id":"geo-xform-q-authoritative-geometry","kind":"ownership"},{"text":"When was the derived geometry produced, and is that time kept separate from the time the geometry itself was valid?","id":"geo-xform-q-derivation-times","kind":"temporal"},{"text":"Is the recorded lineage sufficient to reproduce the derived geometry from the original?","id":"geo-xform-q-lineage-sufficiency","kind":"validation"}]}]}]},{"id":"geo-xform-accuracy-quality","name":"Accuracy, Normalization and Declared Outcomes","description":"How good the resulting coordinates are, how they were normalized and reshaped, and what must be told to a consumer before the result is trusted.","layers":[{"id":"geo-xform-accuracy","name":"Stated Accuracy and Positional Uncertainty","description":"The accuracy the defining authority states for the operations used, and the positional uncertainty and numeric precision that qualify the resulting coordinates.","findings":[{"id":"geo-xform-stated-accuracy","name":"Stated operation accuracy of the chain","description":"The accuracy values declared by the defining authority for each step, how a chain-level figure is derived, and the mandatory unknown state when any step lacks one.","questions":[{"text":"What accuracy value does the defining authority state for each step, and in what unit?","id":"geo-xform-q-stated-accuracy-values","kind":"measurement"},{"text":"How is a single accuracy figure derived for the whole chain from its per-step values?","id":"geo-xform-q-chain-accuracy-rule","kind":"quality"},{"text":"Which authority stated the accuracy, and is it a published statement rather than a local estimate?","id":"geo-xform-q-accuracy-authority","kind":"authority"},{"text":"Is chain accuracy marked unknown whenever any step lacks a published accuracy or is a fallback?","id":"geo-xform-q-accuracy-unknown","kind":"constraint"}]},{"id":"geo-xform-uncertainty","name":"Positional uncertainty, precision and resolution of the result","description":"The uncertainty attached to output coordinates, its components and confidence basis, and the stored numeric precision and resolution that can silently dominate it.","questions":[{"text":"What positional uncertainty is attached to the output coordinates, split into horizontal and vertical components?","id":"geo-xform-q-uncertainty-values","kind":"measurement"},{"text":"At what confidence level and by what evaluation method is the uncertainty expressed?","id":"geo-xform-q-uncertainty-basis","kind":"quality"},{"text":"Does the uncertainty come from a per-point local error estimate or from a single blanket figure for the whole operation?","id":"geo-xform-q-uncertainty-source","kind":"evidence"},{"text":"What stored numeric precision and coordinate resolution are used, and is stored precision coarser than the stated uncertainty?","id":"geo-xform-q-precision-vs-uncertainty","kind":"constraint"}]}]},{"id":"geo-xform-normalization","name":"Axis, Unit, Dimension and Geometry Treatment","description":"The normalizations applied before and after the chain, and the shape-level treatment that changes a geometry without any datum change.","findings":[{"id":"geo-xform-axis-unit-dimension","name":"Axis order, unit and dimensionality normalization","description":"Which axis order and units the coordinates are written in, where that ordering came from, and whether the chain adds, drops or reinterprets an ordinate.","questions":[{"text":"In which axis order are the coordinates written, and does that order come from the CRS definition or from an encoding rule?","id":"geo-xform-q-axis-order-source","kind":"interoperability"},{"text":"Which unit applies to each ordinate, and were units normalized before the operation was applied?","id":"geo-xform-q-unit-normalization","kind":"constraint"},{"text":"Does the chain change coordinate dimensionality, for example dropping a height ordinate or adding a time ordinate?","id":"geo-xform-q-dimension-change","kind":"classification"},{"text":"What outcome is recorded when the input dimensionality is not supported by a step of the chain?","id":"geo-xform-q-dimension-unsupported","kind":"exception"}]},{"id":"geo-xform-geometry-treatment","name":"Densification, clipping, wrapping and antimeridian or polar handling","description":"Shape-level treatment applied around the operation: added vertices, clipped or wrapped extents, and how geometries crossing the antimeridian or approaching the poles were handled.","questions":[{"text":"Was the geometry densified before the operation, and to what deviation tolerance?","id":"geo-xform-q-densification","kind":"process"},{"text":"How was a geometry crossing the antimeridian treated, and was it split rather than left spanning?","id":"geo-xform-q-antimeridian","kind":"spatial"},{"text":"Was any clipping or longitude wrapping applied, and what extent governed it?","id":"geo-xform-q-clip-wrap","kind":"constraint"},{"text":"How is behaviour near the poles and near projection singularities declared?","id":"geo-xform-q-polar-handling","kind":"quality"}]}]},{"id":"geo-xform-outcomes","name":"Declared Outcomes and Exceptions","description":"The single outcome status of an applied chain, the named exceptions that may qualify it, and the limits that must be stated before a consumer relies on the result.","findings":[{"id":"geo-xform-outcome-exception","name":"Outcome status, exception taxonomy and lossy or round-trip declaration","description":"One coded status per applied chain, the named exception set that can accompany it, the tolerance actually tested, and an honest statement of round-trip and export limits.","questions":[{"text":"What single outcome status does the record carry for the applied chain as a whole?","id":"geo-xform-q-outcome-status","kind":"state"},{"text":"Which named exception applies: missing resource, out-of-area, epoch mismatch, axis ambiguity, unsupported dimension, invalid geometry, tolerance breach or lossy export?","id":"geo-xform-q-exception-taxonomy","kind":"exception"},{"text":"Which declared tolerance was tested against the result, and did the result breach it?","id":"geo-xform-q-tolerance-test","kind":"validation"},{"text":"Is any round-trip claim limited to chains that are bijective, non-iterative and unrounded?","id":"geo-xform-q-roundtrip-claim","kind":"requirement"},{"text":"What must a consumer be told before treating the derived geometry as fit for its purpose?","id":"geo-xform-q-consumer-disclosure","kind":"quality"}]}]}]},{"id":"geo-govctl-authority-provenance-bundle","name":"Authority, Identity and Provenance Control","description":"Who is accountable for a geometry and coordinate-reference attachment, who may change it, how it is identified and versioned, and what evidence supports the values it asserts.","layers":[{"id":"geo-govctl-roles-authority-layer","name":"Accountable Roles and Decision Authority","description":"Advisory role assignment for the attachment and the authority to select a CRS, correct geometry and set transformation policy for this subject.","findings":[{"id":"geo-govctl-accountable-roles","name":"Advisory accountability roles for the attachment","description":"Names the parties accountable for a geometry and coordinate-reference attachment - host-object owner, geometry steward, CRS/geodetic authority liaison, producer, independent reviewer and approver - and records that these assignments are advisory attributes, not authorization grants.","questions":[{"text":"Which named party holds each accountable role for this geometry and coordinate-reference attachment?","id":"geo-govctl-q-role-holder","kind":"ownership"},{"text":"Are the recorded role assignments advisory attributes rather than access grants?","id":"geo-govctl-q-role-advisory-status","kind":"authority"},{"text":"How is the independent reviewer kept distinct from the producer and the approver of the same attachment?","id":"geo-govctl-q-role-independence","kind":"constraint"},{"text":"What applies when a role is vacant, delegated, or the host object changes owner?","id":"geo-govctl-q-role-continuity","kind":"exception"},{"text":"Which role covers the case where the geodetic authority sits outside the adopting organisation?","id":"geo-govctl-q-role-external-authority","kind":"relationship"}]},{"id":"geo-govctl-change-authority","name":"Authority over CRS selection, geometry correction and transformation policy","description":"Records who may choose or change the coordinate reference system for the host object, who may authorise a geometry correction, and who sets the permitted transformation methods, grids and accuracy limits for this subject.","questions":[{"text":"Who is authorised to select or change the coordinate reference system bound to this host object?","id":"geo-govctl-q-crs-selection-authority","kind":"authority"},{"text":"Which decision record justifies the chosen CRS, transformation path and grid?","id":"geo-govctl-q-crs-decision-basis","kind":"decision"},{"text":"Does a coordinate correction proceed as an in-place correction or as a new approved version?","id":"geo-govctl-q-correction-route","kind":"process"},{"text":"Which transformation methods, grids and minimum accuracy are permitted for this subject?","id":"geo-govctl-q-transformation-constraints","kind":"constraint"},{"text":"What escalation applies when the geodetic authority deprecates or replaces a referenced definition?","id":"geo-govctl-q-authority-escalation","kind":"exception"}]}]},{"id":"geo-govctl-identity-version-layer","name":"Host-Bound Identity, Version and Supersession","description":"How an attachment is identified relative to its host object, and how versions, effective intervals and supersession of both the attachment and the definitions it cites are governed.","findings":[{"id":"geo-govctl-host-bound-identity","name":"Host-dependent identity of the attachment","description":"Establishes how a geometry and coordinate-reference attachment is identified when its identity depends on the host object, and how the coordinate reference system itself is cited so the citation remains resolvable.","questions":[{"text":"What identifier distinguishes this attachment from other geometry attachments on the same host object?","id":"geo-govctl-q-attachment-identifier","kind":"identity"},{"text":"Does an authoritative master-system identifier already exist for this geometry, and is it recorded?","id":"geo-govctl-q-master-identifier","kind":"provenance"},{"text":"How is the coordinate reference system cited so that the citation stays unambiguous and resolvable?","id":"geo-govctl-q-crs-citation","kind":"interoperability"},{"text":"Does attachment identity survive host-object merge, split or re-identification?","id":"geo-govctl-q-identity-survival","kind":"lifecycle"}]},{"id":"geo-govctl-version-supersession","name":"Version, effective interval and supersession","description":"Governs versioning of the attachment and handling of superseded or deprecated definitions it cites, including which version is current and over what interval a version is asserted to hold.","questions":[{"text":"Which version of this attachment is current, and which are retained but no longer current?","id":"geo-govctl-q-current-version","kind":"state"},{"text":"Over what effective interval is this version asserted to hold?","id":"geo-govctl-q-effective-interval","kind":"temporal"},{"text":"Which prior version does this record supersede and on what stated ground?","id":"geo-govctl-q-supersession-reason","kind":"lifecycle"},{"text":"How is a deprecated or retired CRS definition handled without breaking existing citations?","id":"geo-govctl-q-deprecated-definition","kind":"interoperability"},{"text":"What distinguishes a non-substantive correction from a change that requires a new version?","id":"geo-govctl-q-change-significance","kind":"classification"}]}]},{"id":"geo-govctl-provenance-review-layer","name":"Provenance and Independent Review Evidence","description":"Where the geometry came from, which definitions, operations and grids produced it, and what independent review and approval evidence supports its release.","findings":[{"id":"geo-govctl-derivation-provenance","name":"Provenance of source and derived geometry","description":"Records the source geometry or survey, the CRS definition version, coordinate operation and grid used to derive the current geometry, the agent that performed the derivation, and the separation of observation time from ingestion time.","questions":[{"text":"Which source geometry, survey or dataset was this geometry derived from?","id":"geo-govctl-q-source-geometry","kind":"provenance"},{"text":"Which definition version, coordinate operation and grid file were used to produce the current values?","id":"geo-govctl-q-derivation-inputs","kind":"relationship"},{"text":"When was the geometry observed or surveyed, and when was it captured into this record?","id":"geo-govctl-q-observation-vs-ingestion","kind":"temporal"},{"text":"Which agent, software version and parameter set performed the derivation?","id":"geo-govctl-q-derivation-agent","kind":"evidence"},{"text":"What residual positional uncertainty is asserted for the derived geometry?","id":"geo-govctl-q-residual-uncertainty","kind":"measurement"}]},{"id":"geo-govctl-review-approval-evidence","name":"Independent review and approval evidence","description":"Captures the evidence that an independent reviewer examined the geometry and its CRS binding, which checks were required, who approved release, and how rejection or conditional approval is recorded.","questions":[{"text":"What evidence shows an independent reviewer examined this geometry and its coordinate-reference binding?","id":"geo-govctl-q-review-evidence","kind":"evidence"},{"text":"Which checks must pass before release, and which are advisory only?","id":"geo-govctl-q-required-checks","kind":"validation"},{"text":"Who approved release of this version and under what authority basis?","id":"geo-govctl-q-approval-authority","kind":"authority"},{"text":"How are rejection and conditional approval recorded and resubmitted?","id":"geo-govctl-q-rejection-handling","kind":"process"}]}]}]},{"id":"geo-govctl-exposure-records-bundle","name":"Exposure, Rights and Records Control","description":"What may be released about a location and at what precision, under which licence and attribution obligations, how long the record is kept, and which external profiles and governance records it points to.","layers":[{"id":"geo-govctl-release-control-layer","name":"Release Control: Sensitivity, Rights and Licensing","description":"Classification of sensitive locations with the matching precision-reduction policy, and the licence, attribution and redistribution obligations attached to definitions, grids and source geometries.","findings":[{"id":"geo-govctl-sensitive-location-control","name":"Sensitive-location classification and precision reduction","description":"Classifies whether a location is sensitive, records who determined that, fixes the generalization method and the released precision against the precision retained internally, and requires the generalization to be disclosed and periodically re-reviewed.","questions":[{"text":"On what basis is this location classified as sensitive, and which party determined it?","id":"geo-govctl-q-sensitivity-basis","kind":"classification"},{"text":"Which generalization method applies, and what precision is released compared with the precision retained?","id":"geo-govctl-q-generalization-method","kind":"privacy"},{"text":"How is the fact and degree of generalization disclosed to downstream consumers?","id":"geo-govctl-q-generalization-disclosure","kind":"quality"},{"text":"When is the sensitivity classification reviewed again, and what triggers an earlier review?","id":"geo-govctl-q-sensitivity-review-cycle","kind":"temporal"},{"text":"Which recipients may receive full precision, and which component decides that?","id":"geo-govctl-q-full-precision-recipients","kind":"access"}]},{"id":"geo-govctl-rights-licensing-control","name":"Rights, licensing and redistribution obligations","description":"Declares the licence and attribution conditions attached to each input - CRS definitions, transformation grids and source geometries - and to the derived geometry, and keeps read access strictly distinct from redistribution rights.","questions":[{"text":"Under which licence is each input held - CRS definition, transformation grid and source geometry?","id":"geo-govctl-q-input-licences","kind":"ownership"},{"text":"May the derived geometry be redistributed, and under what conditions?","id":"geo-govctl-q-derived-redistribution","kind":"constraint"},{"text":"Which attribution or acknowledgement notices must accompany a published copy?","id":"geo-govctl-q-attribution-notices","kind":"requirement"},{"text":"Does the ability to read a grid, definition or source geometry imply any right to redistribute it?","id":"geo-govctl-q-access-versus-redistribution","kind":"access"}]}]},{"id":"geo-govctl-records-external-layer","name":"Retention Control and External Governance References","description":"Retention class, legal hold and tombstone markers for the attachment's own records, and the declared interoperability profiles and references to externally held audit, decision and registry records.","findings":[{"id":"geo-govctl-retention-hold-tombstone","name":"Retention class, legal hold and tombstone marking","description":"Records the retention class applying to the attachment and its supporting evidence, whether a hold suspends disposition, what a tombstone asserts after removal, and which external component executes destruction or transfer.","questions":[{"text":"What retention class applies to this attachment and to its supporting evidence records?","id":"geo-govctl-q-retention-class","kind":"retention"},{"text":"Is this record under a hold that suspends disposition, and who imposed it?","id":"geo-govctl-q-legal-hold","kind":"constraint"},{"text":"What remains visible after removal, and what does the tombstone assert?","id":"geo-govctl-q-tombstone-content","kind":"state"},{"text":"Which component executes destruction or transfer, and on whose authority?","id":"geo-govctl-q-disposition-executor","kind":"authority"},{"text":"What happens to the attachment when the host object is retired or transferred?","id":"geo-govctl-q-host-retirement","kind":"lifecycle"}]},{"id":"geo-govctl-interop-profile-external-refs","name":"Declared interoperability profile and external governance references","description":"Declares which interoperability profile or encoding contract the attachment claims, distinguishes alignment from evidenced conformance, and holds resolvable references to externally owned audit, decision and registry records.","questions":[{"text":"Which interoperability profile or encoding contract does this attachment declare?","id":"geo-govctl-q-declared-profile","kind":"interoperability"},{"text":"Is the declaration an alignment statement or an evidenced conformance claim?","id":"geo-govctl-q-alignment-versus-conformance","kind":"evidence"},{"text":"Which externally held audit, decision or registry records does this attachment point to?","id":"geo-govctl-q-external-record-references","kind":"relationship"},{"text":"How is a conflict between two declared external specifications recorded?","id":"geo-govctl-q-profile-conflict","kind":"exception"}]}]}]},{"id":"geo-svc-context-operations","name":"Coordinate Context Operation Lifecycle","description":"Operations that resolve, bind, correct and retire a geometry together with its coordinate reference context on a host record, expressed without reference to any storage engine or interface protocol.","layers":[{"id":"geo-svc-resolution-and-binding","name":"Resolution and Host Binding","description":"How a caller determines which geometry and coordinate reference context apply at a stated instant, how that context is attached to a host record, and which preconditions a request must satisfy before any mutation is proposed.","findings":[{"id":"geo-svc-as-of-read","name":"As-of resolution of geometry and coordinate reference context","description":"Determines which geometry version and which coordinate reference context version apply for a stated instant, which registry release and coordinate epoch qualify the returned coordinates, and what must be returned when no context is in force. Resolution never falls back to an implied default coordinate reference system.","questions":[{"text":"Which instant governs this read: the event time the geometry is asserted to describe, or the observation time at which the record became known?","id":"geo-svc-q-asof-selector","kind":"temporal"},{"text":"Is the resolved reference frame dynamic, and if so which coordinate epoch qualifies the returned coordinates?","id":"geo-svc-q-asof-epoch","kind":"state"},{"text":"Which registry release was in force for the resolved context, and what was the status of the referenced code at that release?","id":"geo-svc-q-asof-registry","kind":"provenance"},{"text":"Which authorization reference accompanied the read, and which external decision reference was returned for it?","id":"geo-svc-q-asof-auth","kind":"access"},{"text":"What is reported when no context version is in force at the requested instant?","id":"geo-svc-q-asof-fail","kind":"exception"}]},{"id":"geo-svc-host-binding","name":"Binding a geometry and coordinate reference context to a host record","description":"Establishes the attachment between a host record and a geometry with its coordinate reference context: which identifier binds them, what role the geometry plays for the host, how many such geometries may coexist, which reference frame kind is bound, and which storage coordinate reference system is declared.","questions":[{"text":"Which identifier binds this geometry and coordinate reference context to its host, and which authority issued that identifier?","id":"geo-svc-q-binding-identity","kind":"identity"},{"text":"What role does this geometry play for the host, and how many geometries of that role may coexist?","id":"geo-svc-q-binding-role","kind":"composition"},{"text":"Which kind of coordinate reference system is bound, and is its datum a single realization or an ensemble?","id":"geo-svc-q-binding-crs-kind","kind":"classification"},{"text":"Which coordinate reference system is declared as the storage CRS for this binding, and which others may it be served in?","id":"geo-svc-q-binding-storage-crs","kind":"interoperability"}]},{"id":"geo-svc-request-preconditions","name":"Operation preconditions, idempotency and explicit failure","description":"The precondition envelope that every geometry or coordinate reference operation carries: the idempotency key that makes a repeated request safe, the version precondition that rejects a stale write, the authorization reference resolved by an external decision point, and the failure vocabulary that forbids silent defaulting.","questions":[{"text":"Which idempotency key scopes a repeated create or correction request, and over what window must the same key yield the same reported outcome?","id":"geo-svc-q-precond-idempotency","kind":"constraint"},{"text":"Which version precondition must a mutating request carry so that a stale write is rejected rather than merged?","id":"geo-svc-q-precond-concurrency","kind":"requirement"},{"text":"Which authorization reference and policy reference must accompany the request, and which external point returns the decision?","id":"geo-svc-q-precond-authority","kind":"authority"},{"text":"Which distinct failure codes are emitted for an unresolvable CRS, a missing coordinate epoch, an unavailable transformation resource, a precondition mismatch and a hold conflict?","id":"geo-svc-q-precond-failure","kind":"exception"}]}]},{"id":"geo-svc-correction-and-closure","name":"Correction by Supersession and Closure","description":"How a geometry or coordinate reference context is corrected without mutating an original, and how a binding is marked for closure with disposition readiness reported to the party that owns retention.","findings":[{"id":"geo-svc-supersession-correction","name":"Correction by supersession over immutable originals","description":"Governs how a geometry value or a coordinate reference context is corrected: originals remain immutable, every correction is a new version that names what it supersedes and why, and every host reference or derived geometry affected by the correction is reported so referential integrity can be restored by their owners.","questions":[{"text":"Which states may a geometry and coordinate reference context version occupy between issue and supersession?","id":"geo-svc-q-supersede-states","kind":"lifecycle"},{"text":"Which prior version does this correction supersede, and what reason and evidence justify it?","id":"geo-svc-q-supersede-reason","kind":"provenance"},{"text":"Which host references and derived geometries must be re-pointed or re-derived once this version is superseded?","id":"geo-svc-q-supersede-impact","kind":"relationship"},{"text":"Which classes of change require a new version rather than an annotation on the existing one?","id":"geo-svc-q-supersede-threshold","kind":"decision"}]},{"id":"geo-svc-tombstone-readiness","name":"Tombstone marking and disposition readiness","description":"Marks a binding as invalidated and reports whether it is ready for disposition: which retention policy governs it, whether a hold is asserted, which incoming references would break, and what minimal residual payload may survive. Execution of destruction is never performed here.","questions":[{"text":"Which retention rule governs disposition of this binding, and where is the governing policy defined?","id":"geo-svc-q-tombstone-policy","kind":"retention"},{"text":"Is a legal or regulatory hold asserted against this binding, and by which reference?","id":"geo-svc-q-tombstone-hold","kind":"state"},{"text":"Which incoming references would break on destruction, and what minimal residual payload must survive as a tombstone?","id":"geo-svc-q-tombstone-integrity","kind":"relationship"},{"text":"Which coordinate precision or locational attributes must be removed or generalised before any residual record is kept?","id":"geo-svc-q-tombstone-privacy","kind":"privacy"}]}]}]},{"id":"geo-svc-computation-operations","name":"Geometry Computation, Comparison and Export","description":"Operations that check, derive, relate and project geometry values: validating structure and coordinate reference context, pinning a transformation for external execution with reproducible evidence, gating comparison on compatible spatial semantics, and reporting loss on export into any binding.","layers":[{"id":"geo-svc-validation-and-transformation","name":"Validation and Pinned Transformation","description":"How a geometry and its coordinate reference context are checked for completeness and structural admissibility, and how a coordinate transformation is specified so that an external engine can execute it and return re-derivable evidence.","findings":[{"id":"geo-svc-context-validation","name":"Validation of geometry structure and coordinate reference context completeness","description":"Defines the checks that must pass before a geometry is published or used: structural admissibility for the declared geometry kind, mandatory and conditionally mandatory coordinate reference context fields, agreement between declared axes, units and coordinate tuples, and containment within the area of validity of the referenced CRS and operation.","questions":[{"text":"Which structural conditions must a geometry satisfy for its declared geometry kind, and which failures are non-recoverable?","id":"geo-svc-q-validate-structure","kind":"validation"},{"text":"Which coordinate reference context fields are mandatory before publication, and which become mandatory only for a dynamic reference frame?","id":"geo-svc-q-validate-context","kind":"constraint"},{"text":"Do the declared axis units, axis order and coordinate dimension agree with the actual coordinate tuples?","id":"geo-svc-q-validate-units","kind":"measurement"},{"text":"Does the geometry fall within the stated area of validity of the referenced CRS and of any pinned operation?","id":"geo-svc-q-validate-extent","kind":"spatial"},{"text":"Which validation severities are distinguished, and which of them block publication rather than warn?","id":"geo-svc-q-validate-severity","kind":"quality"}]},{"id":"geo-svc-pinned-transformation","name":"Externally executed transformation under a pinned operation with reproducibility evidence","description":"Specifies a coordinate transformation as an explicit pin set rather than a request to convert: which operation, which engine and version, which registry release, which grid or deformation resources with checksums, which source and target epochs, and what accuracy is claimed. Execution belongs to an external engine; this finding governs what must be declared beforehand and what evidence must return.","questions":[{"text":"Which coordinate operation is pinned for this transformation, and which candidate operations were considered and rejected?","id":"geo-svc-q-pin-operation","kind":"process"},{"text":"Which engine, registry release and transformation resources must be recorded so that the result can be re-derived exactly?","id":"geo-svc-q-pin-resources","kind":"provenance"},{"text":"What accuracy is claimed for the pinned operation, and is that claim taken from the registry or asserted by the executing engine?","id":"geo-svc-q-pin-accuracy","kind":"measurement"},{"text":"What must be reported when a required grid is unavailable and only a lower-quality or ballpark operation remains?","id":"geo-svc-q-pin-degraded","kind":"exception"},{"text":"Which party executes the pinned operation, and what does this model return when execution is delegated?","id":"geo-svc-q-pin-ownership","kind":"ownership"}]}]},{"id":"geo-svc-comparison-and-export","name":"Comparison Preconditions and Export Loss","description":"How two geometries are judged comparable before any spatial relation or measurement is admitted, and how a geometry is projected into a target binding with every loss itemised.","findings":[{"id":"geo-svc-comparability-gate","name":"Compatibility preconditions for comparing or relating geometries","description":"States the preconditions that must hold before a topological relation, distance, area or aggregation between two geometries is admissible: a common resolvable coordinate reference context, a compatible edge interpretation, an agreed epoch basis, and a relation family whose assumptions the geometries satisfy. Failure is reported, not silently repaired.","questions":[{"text":"Which conditions must hold before a topological or metric relation between two geometries is admitted?","id":"geo-svc-q-compare-preconditions","kind":"constraint"},{"text":"Are the edges of the two geometries interpreted as planar or spherical, and does the chosen relation family assume one of these?","id":"geo-svc-q-compare-edges","kind":"classification"},{"text":"When the two operands carry different coordinate epochs, at which epoch is the comparison performed?","id":"geo-svc-q-compare-epoch","kind":"temporal"},{"text":"Does equality of the two CRS references actually establish equality of realization, or is one of them a datum ensemble?","id":"geo-svc-q-compare-ensemble","kind":"identity"},{"text":"What is reported when comparability fails, and may a result ever be returned with a qualification instead?","id":"geo-svc-q-compare-failure","kind":"exception"}]},{"id":"geo-svc-export-loss","name":"Export and redaction into a target binding with loss reporting","description":"Governs projection of a geometry and its coordinate reference context into a target serialization, database or interface binding. Each binding carries a different subset of the semantics, so the export declares the target, itemises every loss with its magnitude, records any redaction applied, and identifies loss classes that must block the export outright.","questions":[{"text":"Which target binding is requested, and which parts of the coordinate reference context can that binding not carry?","id":"geo-svc-q-export-target","kind":"interoperability"},{"text":"Which specific losses occurred on this export, and what is the magnitude of each?","id":"geo-svc-q-export-losses","kind":"evidence"},{"text":"Which redaction or coordinate generalisation was applied before export, and under which reference?","id":"geo-svc-q-export-redaction","kind":"privacy"},{"text":"Which loss classes must block an export rather than merely be reported?","id":"geo-svc-q-export-blocking","kind":"requirement"}]}]}]}]},"agentConduct":{"may":["Bind a geometry to a host with its coordinate reference system.","Resolve a CRS reference against an authoritative registry and pin the snapshot.","Project a geometry to GeoJSON, WKT or GML.","Record validity checks and declared extent."],"mustNot":["Assume WGS 84 or longitude-latitude order when the CRS is not stated.","Transform coordinates without recording the operation and its accuracy.","Mix horizontal and vertical references silently.","Report computed precision beyond the source accuracy.","Publish precise locations of protected people, species or sites."],"requiresHuman":["Releasing precise locations of sensitive sites or people.","Accepting a transformation for safety-critical navigation or construction."]},"ethics":{"considerations":["Location data can reveal where people live and move.","Exact locations of endangered species or heritage sites can lead to their harm.","Boundary geometries can carry political claims."],"affectedParties":["People whose locations are recorded","Owners of land and sites","Users who navigate or build from the data"]},"owners":{"steward":"The adopting Dimension must designate a single accountable owner package for WM-XCT-033 instances and name a geometry steward per host-object class before any attachment is created.","roles":[{"name":"Host-object owner","responsibilities":["Accountable for the host object that carries the attachment and for its disposition outcome","Confirms that a geometry attachment is required and names its purpose discriminator","Approves sensitivity determinations for locations belonging to the host object"]},{"name":"Geometry steward","responsibilities":["Maintains the attachment record, its versions, effective intervals and supersession chain","Ensures every cited definition, operation and grid is recorded with its version and status","Raises escalation when a cited definition is deprecated or retired"]},{"name":"CRS and geodetic authority liaison","responsibilities":["Tracks the authoritative registry and the applicable national or regional reference-frame programme","Maintains the pinned registry dataset version and the review interval for that pin","Advises on permitted coordinate operations, grids and accuracy floors without redefining registry content"]},{"name":"Producer","responsibilities":["Performs the survey, capture or derivation that yields the geometry","Records derivation inputs, agent, software version, parameters and asserted uncertainty","Records observation time and ingestion time as separate values"]},{"name":"Independent reviewer","responsibilities":["Examines the geometry, its CRS binding, its provenance and its rights declarations","Records blocking and advisory check outcomes without executing the checks personally where an external validation component is used","Remains distinct from the producer and the approver, or records the exception when unavoidable"]},{"name":"Approver","responsibilities":["Authorises release of a specific version under a stated authority basis","Records conditions attached to a conditional approval and their resolution","Authorises the change class for substantive changes and supersessions"]},{"name":"Records custodian","responsibilities":["Holds the retention schedule reference applied to attachment records","Imposes and releases holds and instructs the executing records component","Confirms tombstone content after a disposition or transfer is executed elsewhere"]}],"masterSystems":[]},"relations":[{"target":"WM-XCT-010 Location Referencing / Address (registry parent candidate)","type":"child","note":"Registry metadata places this entry beneath WM-XCT-010 Location Referencing / Address, but no relationship contract was supplied. Treat the edge as a candidate composition link: WM-XCT-010 may consume this mixin for coordinate-backed locations and addresses, while this model retains geometry and CRS semantics until the boundary is formally adjudicated."},{"target":"Host feature, place, asset or object model","type":"composes","note":"Geometry is mixed into any host thing as a property with a declared role. The host model owns real-world identity, classification and lifecycle; this mixin supplies the shape value and its binding only."},{"target":"Coordinate reference system register / authority model","type":"references","note":"Carry the resolvable CRS reference, axis-order statement and coordinate-epoch parameter for each geometry value. The register's CRS definitions, datum parameters, versioning and deprecation lifecycle remain entirely with the target."},{"target":"Coordinate operation and positional accuracy model","type":"references","note":"Record which coordinate operation produced a transformed geometry and the resulting positional-quality statement. Parameter derivation, operation selection and transformation execution stay with the target."},{"target":"Geometry computation and spatial predicate evaluation service","type":"references","note":"Reference the evaluator that produced validity verdicts and relation results, and store the verdict as reference data. Evaluation, overlay, repair execution, enforcement and the evaluator's audit trail are owned by the target."},{"target":"Geometry encoding and serialization profile model","type":"references","note":"Name the encoding profile used for a projection and record its losslessness. Encoding grammar, conformance classes and parser behaviour belong to the target; this model states only which semantics must survive a projection."},{"target":"Vertical reference and height system model","type":"references","note":"Reference the vertical datum or height system against which a Z ordinate is interpreted, without defining geoid models or height-system realizations."},{"target":"OGC Simple Feature Access Part 1 / ISO 19125-1 geometry model","type":"aligned","note":"Align primitive typing, aggregate structure, simplicity and validity assertions and topological predicates with the simple-feature architecture, recording where the linear planar assumptions of that model do not hold rather than claiming conformance."},{"target":"OGC GeoSPARQL 1.1 geometry vocabulary","type":"aligned","note":"Align the separation of feature from geometry and the distinct topological, coordinate and spatial dimension properties, emptiness, simplicity, spatial resolution and the named relation families."},{"target":"IETF RFC 7946 GeoJSON geometry profile","type":"aligned","note":"Align ring closure, right-hand-rule winding, antimeridian cutting and bounding-box conventions as one named profile, while recording its fixed WGS 84 CRS, straight Cartesian edges and three-ordinate limit as profile constraints rather than universal geometry rules."},{"target":"ISO 19111 / OGC Abstract Specification Topic 2 referencing by coordinates","type":"aligned","note":"Align coordinate tuple, coordinate set, axis order and coordinate epoch terminology so that CRS references carried on a geometry value are interpreted consistently with the referencing standard."},{"target":"ISO 19107 spatial schema","type":"aligned","note":"Align the abstract vector geometry and topology concepts that sit above simple features, including primitives, aggregates, curve interpolation and solids, subject to the recorded paywall limitation on clause-level verification."},{"target":"Coordinate operation and transformation model (datum transformation, map projection conversion, grid shifts, operation accuracy)","type":"references","note":"Carry the reference to a projected or derived CRS's defining conversion, and to any operation applied downstream, together with subject-specific parameters such as required tolerance. Operation method definitions, parameter application, execution and accuracy budgets stay with that model."},{"target":"Units of measure register (authority unit-of-measure definitions)","type":"references","note":"Axis units, ellipsoid length units and prime meridian angle units are referenced from a unit authority using the same definition URI template; unit definitions and conversion factors are not restated here."},{"target":"EPSG Geodetic Parameter Dataset (IOGP) as external CRS authority","type":"aligned","note":"Align local CRS references to the custodian's codes and URI form and record the registry release; the custodian owns code issuance, revision, deprecation and dataset publication, and codes are never removed there."},{"target":"OGC Naming Authority definition registers (OGC Definitions Server)","type":"aligned","note":"Align identifier expression to the OGC definition URI template and its controlled authority and version tokens; the OGC register owns the authority token list and the persistence guarantee."},{"target":"Geometry encoding and serialization model (GeoJSON, WKT, GML, WKB, database geometry types)","type":"references","note":"Record which encoding a coordinate value arrives in and any axis order that encoding imposes, as an interface fact bound to the reference. Encoding grammar, parsing, validity and conversion between encodings belong to that model."},{"target":"Temporal reference model","type":"references","note":"Record timestamps, calendars and duration semantics are referenced from the temporal model; only geodetic epochs expressed as decimal years are held here, explicitly distinguished from record time."},{"target":"Any coordinate-bearing subject model in the adopting Dimension","type":"composes","note":"Attach an explicit CRS reference, an explicit axis order statement and, for dynamic frames, a coordinate epoch to every subject that carries coordinates, without importing that subject's own lifecycle, ownership or operational functions."},{"target":"National geodetic authority publications (modernized NSRS, GDA2020 and equivalents)","type":"aligned","note":"Align regional frame identity, reference epochs and supersession expectations to the responsible national authority. Frame realization, publication, rollout scheduling and the associated transformation products remain with those authorities."},{"target":"Any adopting subject model whose records carry coordinates","type":"composes","note":"As a mixin, this entry is attached to subject models that hold positional data, contributing reference identification, frame dynamics, epoch binding and definition sufficiency context. It introduces no subject identity, no subject lifecycle and no subject-specific business rules."},{"target":"ISO 19111:2019 / OGC Abstract Specification Topic 2: Referencing by coordinates (18-005r5)","type":"aligned","note":"Declared alignment of this entry's vocabulary to the ISO 19111 conceptual schema for dynamic reference frame, frame reference epoch, coordinate epoch, coordinate metadata, datum ensemble, point motion operation, compound, temporal, vertical and engineering CRS. Alignment is asserted at element level and is not a conformance claim; conformance would require the standard's own conformance-class evidence."},{"target":"OGC Well-known text representation of coordinate reference systems (ISO 19162:2019 / OGC 18-010 series)","type":"aligned","note":"Encoding alignment for pinned definition snapshots and compound composition records. The WKT version used is recorded per snapshot because element sets differ between WKT-CRS 2.0.6 and 2.1. This entry does not define or extend the grammar."},{"target":"EPSG Geodetic Parameter Dataset (IOGP Geomatics Committee register)","type":"references","note":"Carry register authority, definition code, register version, canonical snapshot and digest as reference context. Entry creation, revision, deprecation, data-management policy and publication of the register remain wholly with IOGP; this entry never mirrors the register or acts as a second register."},{"target":"IERS ITRS realization series (ITRF) and national frame realizations","type":"references","note":"Carry the realization identity, its defining authority and its frame reference epoch as a reference. Computation, adjustment, publication and post-seismic modelling of realizations remain with IERS and the national geodetic agencies."},{"target":"Deformation model publications (OGC Topic 24 functional model and national agency deformation products)","type":"references","note":"Reference the governing deformation or point-motion model with its version and declared extent. Element decomposition, spatial and time function evaluation, grid interpolation, distribution and version release stay with the publishing authority and with the coordinate-operation model that executes them."},{"target":"Coordinate operation and transformation model","type":"references","note":"Record the transformation reference epoch and the citation of an applicable coordinate operation or point motion operation. Operation selection, parameterization, pipeline construction, execution, accuracy assessment and the audit trail of executed transformations belong entirely to that model."},{"target":"Adopting Dimension temporal and calendar model","type":"composes","note":"Compose time-scale realization, leap-second tables and calendar arithmetic from the Dimension's temporal model. This entry records only which time scale a temporal axis realizes and the temporal datum origin; it neither realizes nor converts between time scales."},{"target":"Adopting Dimension retention, access and disposition policy","type":"references","note":"Reference the policy that owns retention periods, legal holds, erasure decisions and their execution for records that cite this entry's definitions. This entry records disposition state and the owning policy reference only, and does not execute or audit disposal."},{"target":"Host subject model requiring located geometry","type":"composes","note":"Attach geometry, CRS reference, coordinate epoch, operation lineage and quality statements to a host subject without asserting the host's identity, lifecycle, authority or permissions."},{"target":"EPSG Geodetic Parameter Dataset (IOGP) and equivalent geodetic parameter registries","type":"aligned","note":"Cite CRS, operation, method, parameter, extent and stated-accuracy definitions by code or URI, and record the dataset version pinned. The registry owns those definitions and their deprecation and supersession lifecycle; this model carries references and subject-specific pins only."},{"target":"ISO 19111 / OGC Abstract Specification Topic 2 referencing-by-coordinates conceptual schema","type":"aligned","note":"Use the standard's vocabulary for coordinate operation, conversion, transformation, concatenated and point-motion operation, coordinate epoch, operation accuracy and domain of validity. Alignment only; conformance is not claimed without recorded evidence."},{"target":"Coordinate transformation engine","type":"references","note":"Carry an engine name and version as a reproduction pin, together with the binding needed to rebuild the declared chain. The engine owns execution, run-time candidate ranking, resource resolution and its own release lifecycle; none of that is modelled here."},{"target":"Geodetic grid and deformation-model distribution service","type":"references","note":"Carry resource identity, version and content checksum, plus the availability state observed. Hosting, licensing, redistribution and retraction of resources remain with the distributor."},{"target":"Positional data-quality model","type":"aligned","note":"Bind accuracy and uncertainty values to a specific geometry and chain using external quality vocabulary. Measure definitions, evaluation procedures and conformance levels stay in the quality model."},{"target":"Encoding and interchange profiles for geospatial data","type":"aligned","note":"Map inline data onto encoding rules for CRS reference, axis order, coordinate epoch, precision and antimeridian handling, and record which rule was applied as a treatment declaration. Encodings own their serialization constraints."},{"target":"Host object model consuming the mixin","type":"composes","note":"Attach geometry and coordinate-reference facts to a host object whose identity, lifecycle and business semantics remain owned by the host."},{"target":"Authoritative CRS and geodetic parameter registry (EPSG Dataset and OGC Naming Authority definition server)","type":"references","note":"Cite CRS, datum and coordinate-operation definitions by governed identifier and dataset version. Registry authorship, versioning, deprecation and maintenance remain with the registry operator; this model records only the citation, the version used and subject-specific parameters."},{"target":"National or regional geodetic authority reference-frame programme","type":"references","note":"Track authority-declared reference frames and their replacement so that effective intervals and supersession of cited frames stay current. Frame definition and realisation remain the authority's."},{"target":"Access-control and authorization policy model","type":"references","note":"Supply sensitivity labels, role assignments and access-rights references as attributes. Policy administration, decision and enforcement remain with the external policy components; no allow or deny outcome is modelled here."},{"target":"Provenance and audit-record model (W3C PROV)","type":"aligned","note":"Express derivation facts using entity, activity and agent semantics for interchange. Audit-trail generation, storage and integrity remain with the provenance and audit systems."},{"target":"Records-management, retention and disposition model","type":"references","note":"Bind retention class, hold and tombstone markers to an external schedule. Schedule authorship, disposition execution, destruction and transfer are performed by the records system under the adopting Dimension's policy."},{"target":"Catalogue and rights metadata model (DCAT-3 with dcterms and ODRL)","type":"aligned","note":"Interchange licence, access-rights, versioning and qualified-attribution statements using established properties, keeping access rights distinct from licence terms."},{"target":"Sensitive-location generalization practice for occurrence and location data","type":"aligned","note":"Adopt graded sensitivity categories, grid-based coordinate rounding and generalization disclosure terms, while the determination of sensitivity stays with the data provider or host-object owner."},{"target":"ISO 19111 / OGC Abstract Specification Topic 2 conceptual model for referencing by coordinates","type":"aligned","note":"Align terminology and structure for CRS, datum ensemble, dynamic reference frame, coordinate epoch, coordinate operation accuracy and operation version. Alignment is declared; conformance is claimed only where test evidence exists."},{"target":"Transformation grid distribution and geodetic tooling project","type":"references","note":"Reference grid files by identifier, version, provider and licence status. Grid acquisition, hosting, mirroring and redistribution rights remain with the grid provider and the tooling project."},{"target":"Host feature or subject record model adopting the mixin","type":"composes","note":"Attaches geometry and coordinate reference context to a host record. A spatial thing is disjoint from its geometry and may carry several geometries of differing accuracy or time, so identity, classification and lifecycle of the thing remain entirely with the host."},{"target":"Authoritative geodetic registry model (EPSG Geodetic Parameter Dataset and equivalent national registries)","type":"references","note":"Carries the CRS, reference frame and coordinate-operation code, its issuing authority, the registry release in force and the record status. Registry curation, correction, deprecation decisions and terms-of-use administration remain with the registry authority."},{"target":"Coordinate transformation execution service model (geodetic engine and resource catalogue)","type":"references","note":"Carries the pinned operation, engine identity and version, and resource digests, and validates the evidence returned. Candidate discovery heuristics, numerics, resource acquisition and execution belong wholly to the engine. Required only where a derived coordinate value is produced."},{"target":"Provenance and evidence record model","type":"aligned","note":"Shapes derivation, revision and invalidation assertions using entity, activity, agent, used, wasGeneratedBy, wasDerivedFrom and wasRevisionOf so that evidence is portable. Storage, immutability, correlation and retention of the provenance and audit trail are owned by that model; alignment is asserted, conformance is not claimed."},{"target":"Records retention, legal hold and disposition model","type":"references","note":"Carries the retention policy reference and any asserted hold reference, and consumes them to report disposition readiness. Retention schedules, hold administration, disposition approval and physical destruction are executed entirely by that model."},{"target":"Authorization policy and decision model","type":"references","note":"Carries the authorization reference presented with a request and the decision reference returned. Policy authoring, evaluation and enforcement are performed by that model; this model neither evaluates nor enforces and holds no policy state."},{"target":"Temporal reference model (instants, intervals and calendars)","type":"references","note":"Supplies the semantics of instants and intervals used for event time, observation time and effective intervals, recorded as RFC 3339 date-times. Coordinate epoch remains local to this model because it is a geodetic reference time, not a calendar instant."},{"target":"Unit of measure and quantity model","type":"references","note":"Supplies units for coordinate system axes, accuracy values, tolerances and generalisation radii. Unit definitions, conversion factors and dimensional analysis belong to that model; this model carries unit references on axes and quantities."},{"target":"Serialization and interface binding profiles (WKT/WKB, GeoJSON, GML, GeoParquet, database and API bindings)","type":"aligned","note":"Aligns the model's semantics with each binding's expressive range and records what each binding cannot carry. No binding is canonical, and a binding's fixed defaults are recorded as losses on export rather than adopted as model semantics."},{"target":"National geodetic authority reference-frame and deformation-model resources","type":"references","note":"Carries references to plate-fixed frames, geopotential datums and velocity or deformation models as versioned external resources, and records the re-derivation obligation their replacement creates. Frame definition, publication and rollout timing belong to the national authority."},{"target":"Spatial relation and topological query model","type":"extends","note":"Specialises only the coordinate-reference precondition on spatial relations: which relation family may be applied, under which common reference basis, edge interpretation and epoch alignment. The relation vocabularies, their algebra and their evaluation remain defined and executed by that model."},{"target":"Host feature, place or object model","type":"neighbor","note":"A Spatial Thing is disjoint from its geometry: the lighthouse is not the polygon. The host owns real-world identity, classification and lifecycle; this mixin owns only the shape value and its binding role, and never asserts that a geometry identifies a thing."},{"target":"Coordinate reference system register / authority model","type":"neighbor","note":"Coordinates are only interpretable against a CRS, but the register that defines CRSs, datums and their versions is a separate authority. This model carries a CRS reference by URI plus axis order and coordinate epoch; it does not define, version or deprecate CRSs."},{"target":"Coordinate operation / transformation service","type":"neighbor","note":"The referenced service executes transformations and derives parameters. This model records only which operation was referenced, the resulting storage CRS and the declared positional-quality statement carried with the transformed value."},{"target":"Geometry computation and spatial predicate engine","type":"neighbor","note":"Relation families (Simple Features, Egenhofer, RCC8, DE-9IM) and validity checks are evaluated by an external engine. This model records the asserted verdict, its profile and evaluation context as reference data, and never owns evaluation, enforcement or the evaluator's audit trail."},{"target":"Encoding and serialization profile model","type":"neighbor","note":"WKT, WKB, GeoJSON geometry objects, GML geometry elements, JSON-FG place members and database geometry columns are projections. The encoding profile model owns encoding rules and conformance classes; this model owns which semantics must survive a projection and which are lossy."},{"target":"Raster, coverage and gridded data model","type":"neighbor","note":"This mixin covers vector geometry only. Grid geometry, cell alignment and coverage domain semantics belong to the coverage model, even though both reference the same CRS context."},{"target":"Route, network and linear-referencing model","type":"neighbor","note":"A LineString here is a shape, not a traversable edge. Connectivity, direction of travel, turn restrictions and measure-based linear referencing along a network belong to the network model; only the M ordinate as a stored value is in scope."},{"target":"Vertical reference / height system model","type":"neighbor","note":"The Z ordinate is in scope as a stored spatial ordinate; the vertical datum, geoid model and height-system definition against which Z is meaningful is referenced, not defined here."},{"target":"WM-XCT-010","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier issued by the system of record for the subject - the host object's master system, the records system for disposition records, or the geodetic authority for a cited definition - always takes precedence and is recorded verbatim with its issuing system.","Governed global identifier or IRI issued under a controlled naming authority, including persistent definition IRIs whose version appears in the identifier path, used when no master-system identifier exists.","UUID or ULID minted by the adopting Dimension in its own namespace, used only when neither of the preceding forms is available, and recorded together with the reason no higher-priority identifier applied.","A date, a timestamp, a version label, a licence name, a file name or a display name is never used as an identifier, and no identifier may embed a date-like component as its distinguishing part."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A geometry value has a type, coordinates, a CRS reference, axis order and units.","Often confused with an address, a place name and a map image."]},"capabilities":{"applicability":"required","items":["Bind geometry value to host: Attach a geometry value to a host Spatial Thing with a declared role and cardinality, establishing the weak identity of the value without asserting any identity for the host.","Declare CRS binding: Record the resolvable CRS reference, axis order, longitude-range convention and, for a dynamic CRS, the coordinate epoch under which the coordinate tuples are to be read.","Classify geometry type and dimensionality: Assign the primitive or aggregate type, the interpolation rule, and the topological, coordinate and spatial dimensions together with the Z and M presence flags.","Record declared extent: Store an envelope or bounding box with its CRS, axis ordering, derivation method, containment guarantee and antimeridian or polar convention flags.","Record validity assertion: Store an externally produced validity or simplicity verdict against a named profile version, with tolerance, evaluator reference and assessment time.","Record declared spatial relation: Store an asserted topological relation between two geometry values with its relation family, predicate, evaluation context and assertion status.","Project geometry value to an encoding: Produce or consume a serialized projection of the geometry value under a named encoding profile, reporting which declared semantics the projection cannot carry.","Set geometry presence state: Declare whether a host binding holds an empty typed geometry, no geometry, an unknown location or a deliberately suppressed or generalized location.","Resolve a CRS reference to an authoritative definition: Take an authority/code pair or definition URI and obtain the governing authority's record, reporting the registry release actually served.","Pin a registry snapshot with provenance: Capture one resolved authority definition as an immutable snapshot carrying registry version, retrieval URL, retrieval time and a content digest.","Materialize explicit axis order and units: Read axis name, abbreviation, direction, order, unit and range from the authoritative definition and record them explicitly, refusing to infer any of them from a code, label or encoding convention.","Check definition completeness against required elements: Compare a CRS definition against the elements ISO 19111 requires for its subtype and report what is missing.","Observe registry record status and replacement pointers: Read the authority's current validity status for a referenced record and record it with a separate observation time.","Assess a use against the declared domain of validity: Compare an intended use and a subject's extent against the CRS scope and domain of validity, and report fit.","Compare two CRS definitions for equivalence: Compare two definitions element by element - datum, ellipsoid, prime meridian, coordinate system, axis order and units - and report agreement, difference, and difference in axis order alone.","Declare coordinate reference binding: Attach a resolvable coordinate reference to a subject's coordinate set and, where the underlying frame is dynamic, attach the coordinate epoch and its binding scope, producing a coordinate metadata record.","Validate epoch completeness and time-role separation: Check that a dynamic reference carries a coordinate epoch at a declared scope, and that coordinate epoch, observation time, transformation reference epoch, definition publication time and ingestion time are held in distinct roles with correct notation.","Resolve and pin a reference definition: Resolve a coordinate reference against the cited register or a supplied definition, normalize it to a canonical form, and store it as a pinned snapshot with register authority, version, code and integrity digest. The register itself is read, never maintained.","Record a deformation model reference: Record the identifier, publisher, version label and declared spatial and temporal extent of the deformation or point-motion model a consumer must apply, together with the out-of-extent disposition. No displacement is computed, interpolated or stored.","Assess compound reference composition: Enumerate the component references of a compound coordinate reference, verify the declared order and the independence condition, derive the resulting axis sequence with directions and units, and determine the epoch applicability scope.","Classify and gate a non-register definition: Decide whether an unknown, custom, engineering-local, deprecated or superseded reference is sufficiently defined for use, or must be held as unresolved, and route custom definitions to the approving role.","Assemble declared operation chain record: Build a complete, ordered chain declaration from supplied endpoint references, operation references, method and parameter pins, and report which pins are missing. Records only; performs no coordinate evaluation and queries no registry at run time.","Validate area-of-use applicability: Compare the subject geometry extent with the declared area of use of every step under a stated spatial test and report the applicability outcome.","Validate coordinate epoch consistency: Determine whether an epoch is required by either endpoint, whether the supplied epochs are consistent with the chain, and whether a point-motion step is needed.","Verify external resource and toolchain pins: Check that every grid, triangulated-network or deformation-model dependency carries an identifier, version and checksum, and that engine and registry version pins are present and internally consistent.","Calculate conservative chain accuracy and uncertainty summary: Derive a single accuracy and uncertainty summary for the chain from per-step stated values and any supplied local error estimates, forcing an unknown result whenever a step lacks a published value or is a fallback.","Validate axis, unit and dimensionality declarations: Compare the written axis order, ordinate units and coordinate dimension with the endpoint CRS definitions and the applicable encoding rule, and report ambiguity or unsupported dimensionality.","Validate residuals against declared tolerance: Test supplied residuals, including round-trip residuals, against a declared tolerance and report a breach, without asserting that any chain is exactly reversible.","Report chain outcome and consumer disclosures: Compose the transformation report: one outcome status, the exception set, the accuracy and uncertainty summary, lineage pointers to the original geometry and CRS, and any lossy-export or round-trip qualification.","Record accountable role assignment: Record or update the advisory assignment of an accountability role for a geometry and coordinate-reference attachment.","Record CRS and transformation decision: Capture a decision that selects or changes the coordinate reference system, permitted coordinate operations, grids and accuracy floor for a subject.","Issue attachment version and mark supersession: Create a new version of a geometry and coordinate-reference attachment, set its effective interval and mark the prior version superseded.","Record independent review outcome: Record the outcome of an independent review of a geometry and its CRS binding, including check results, conditions and the release decision.","Classify sensitive location and set released precision: Assign a sensitivity category to a location, select the generalization method and released precision, and set the next review date.","Declare rights, licences and redistribution state: Declare the licence and acknowledgement obligations of each input and compute the resulting redistribution state of the derived geometry.","Mark retention, hold or tombstone state: Apply a retention class, impose or release a hold, or place a tombstone marker on an attachment record.","Resolve coordinate context as of an instant: Selects the geometry version and coordinate reference context version in force for a stated event or observation instant and reports what was resolved, including the coordinate epoch and registry release. Never substitutes a default CRS.","Compose a host binding proposal: Assembles a complete, checkable binding of a geometry and coordinate reference context to a host record and reports whether it is admissible. Commitment to storage is performed by an external system.","Check operation preconditions: Evaluates idempotency, optimistic concurrency and authorization-reference presence for a proposed operation and reports a precondition determination with a specific failure code where any precondition is unmet.","Plan a correction by supersession: Computes the supersession chain for a proposed correction, classifies the change, and reports every incoming reference and derived geometry that will require re-pointing or re-derivation."]},"hazards":{"applicability":"required","items":["Axis order swaps put features in the wrong place.","Datum errors of metres to hundreds of metres in navigation or construction.","Exposure of sensitive locations."]},"interfaces":{"applicability":"required","items":["ISO 19111 referencing by coordinates (OGC Topic 2).","ISO 19107 spatial schema and OGC Simple Features (ISO 19125).","RFC 7946 GeoJSON.","OGC GeoSPARQL.","EPSG Geodetic Parameter Dataset."]},"context":{"applicability":"required","items":["No jurisdiction-specific legal regime is assumed. Where precise location is personal data, the applicable erasure and disclosure obligations are set by the adopting Dimension's jurisdiction and are executed by the referenced retention and privacy policy, not here.","Vertical datums and height systems are national or regional realizations; the Z ordinate is meaningless without an explicit vertical reference, which this model references rather than defaults.","The longitude-range convention (-180 to 180 versus 0 to 360) is a delivery convention that differs between communities and is recorded per value rather than assumed globally.","Suppression thresholds and generalization resolutions for sensitive locations are jurisdiction- and sector-specific and must be supplied by the adopting Dimension's disclosure policy.","Dynamic reference frames and plate-motion-driven coordinate change matter most in tectonically active regions; the coordinate epoch field is required only where the referenced CRS is dynamic.","United States coordinates are assumed to be in NAD 83 or NAVD 88 only until the modernized NSRS frames NATRF2022, PATRF2022, CATRF2022 and MATRF2022 and the new geopotential datum replace them. NGS states NAD 83 is off-centre by about 2.2 m, NAVD 88 is biased and tilted, and every existing horizontal and vertical value will change by as much as four metres; no rollout date was confirmed in the material reviewed.","Australian data is assumed to follow GDA2020, a realisation of ITRF2014 at epoch 2020.0. Plate motion of roughly 7 cm per year produced about 1.8 m of divergence from GDA94 and about 9 cm of ellipsoidal height difference; datasets mixing the two without transformation are wrong by those amounts.","European realizations of ETRS89 and the European Vertical Reference System were not verified from EUREF sources during this research and are treated as an open regional gap rather than assumed.","Vertical datums are national and gravity-related. No assumption is made that heights from different national datums are comparable, and gravity-related and ellipsoidal heights are flagged separately.","Dynamic reference frames require a coordinate epoch to travel with the data. In plate-fixed regional frames local practice often leaves the epoch implicit; it is still recorded explicitly here.","North America: NOAA NGS plans four plate-fixed dynamic terrestrial reference frames (NATRF2022, PATRF2022, CATRF2022, MATRF2022) each defined relative to ITRF2020, plus a gravity-based geopotential datum realized through an updated geoid model. The published implementation timeline was not independently confirmed here, so these frame names are recorded as references rather than as effective defaults.","New Zealand: NZGD2000 is a semi-dynamic datum aligned to ITRF96 at epoch 2000.0, with a versioned deformation model comprising a secular velocity component and earthquake patches. Its versions are named by approximate publication date (for example 20180701), a convention this model stores verbatim as a version label and explicitly refuses to treat as an identifier or a coordinate epoch.","Australia: a two-frame approach pairs a static plate-fixed datum with a time-dependent frame, with a plate motion model used to propagate between epochs. This was observed only through secondary summaries because the primary national committee pages redirected or timed out during research, so it is held as an unverified regional note rather than a grounded structural claim.","Europe: ETRS89 practice is addressed by an EPSG guidance note identified but not retrieved. Plate-fixed European practice is assumed to follow the same plate-fixed pattern as the North American and Australian cases and is flagged as unverified.","Global versus regional realization: ITRF2020 has reference epoch 2015.0 while national frames adopt their own reference epochs, so a coordinate epoch is meaningful only together with the frame it qualifies; cross-region merging without both is treated as unsafe.","Extraterrestrial and planetary bodies, and marine or airborne moving-platform frames, are outside the researched evidence base; regional assumptions here concern terrestrial Earth-referenced practice only.","The geodetic-agency evidence used here is United States specific, covering a national spatial reference system, its grid-based horizontal and vertical transformations and its plate-fixed frame family. Other jurisdictions maintain their own frames, grids, tools and accuracy conventions, and none of the region-scoped statements generalize.","Grid and deformation-model resources carry different licences by jurisdiction; availability from a public distribution network does not imply a right to use, and a Dimension must record its own licensing position.","Decimal-year epoch conventions, and the treatment of leap seconds when converting between a timestamp and an epoch, differ between agencies and are not harmonized here.","Transformations are region-scoped: a national transformation set spans a fixed set of regions and is undefined outside them, so area-of-use testing is mandatory rather than advisory.","Regional public authorities issue binding technical guidance constraining which coordinate reference systems may be used and how they are identified; the model carries a regional-mandate element and a deviation justification, but does not encode any specific regional CRS list.","National geodetic authorities replace reference frames on their own timetables, so effective intervals and supersession of cited frames are region-specific and must be tracked by the adopting Dimension's liaison role.","Retention periods, disposition rules and legal-hold triggers are jurisdiction-specific; the retention class here references an externally maintained schedule and asserts no period of its own.","Sensitivity thresholds for location data differ by jurisdiction and by subject matter; the graded categories are adopted as a structure, while the category boundaries are set by the adopting Dimension.","Grid licence conditions vary by country, and some national grids are obtainable only through provider-specific channels; redistribution state must therefore be evaluated per grid and per region.","North American reference-frame modernisation replaces a horizontal datum misaligned from the geocentre by roughly two metres and a vertical datum biased and tilted at the metre level, with four plate-fixed frames and a geopotential datum. Adopting Dimensions in that region must expect a re-derivation obligation across existing bindings; the timeline is set by the national authority, not by this model.","Europe, Australasia and Japan use differing conventions for plate-fixed versus globally aligned frames and for whether coordinates are held at a fixed epoch or propagated. Epoch policy is therefore declared per adopting Dimension and per host collection rather than assumed globally.","National grid and deformation model resources differ in availability, versioning cadence and redistribution permission. A pin set that is reproducible in one jurisdiction may be unreproducible in another because the pinned resource cannot be obtained.","Location-privacy obligations and the threshold at which coordinates become personal or sensitive vary substantially by jurisdiction. Generalisation radii and sensitivity classifications must be set by the adopting Dimension against local law.","Access to the principal geodetic registry requires acceptance of terms of use, which some organisations and jurisdictions treat as a procurement or compliance precondition. The model records this as a licensing hold rather than assuming open access."]}},"sources":[{"title":"RFC 7946: The GeoJSON Format","url":"https://www.rfc-editor.org/rfc/rfc7946.html","note":"Internet Engineering Task Force (IETF)"},{"title":"OGC GeoSPARQL - A Geographic Query Language for RDF Data (22-047r1)","url":"https://docs.ogc.org/is/22-047r1/22-047r1.html","note":"Open Geospatial Consortium"},{"title":"OGC Abstract Specification Topic 2: Referencing by coordinates Corrigendum (18-005r5)","url":"https://docs.ogc.org/as/18-005r5/18-005r5.html","note":"Open Geospatial Consortium / ISO TC 211 (consistent with ISO 19111:2019)"},{"title":"OGC API - Features - Part 1: Core Corrigendum (17-069r4)","url":"https://docs.ogc.org/is/17-069r4/17-069r4.html","note":"Open Geospatial Consortium"},{"title":"OGC Features and Geometries JSON (JSON-FG) - Part 1: Core (21-045r1)","url":"https://docs.ogc.org/is/21-045r1/21-045r1.html","note":"Open Geospatial Consortium"},{"title":"Spatial Data on the Web Best Practices","url":"https://www.w3.org/TR/sdw-bp/","note":"World Wide Web Consortium (W3C) / Open Geospatial Consortium"},{"title":"OGC GeoPackage Encoding Standard (12-128r19)","url":"https://docs.ogc.org/is/12-128r19/12-128r19.html","note":"Open Geospatial Consortium"},{"title":"OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture (06-103r4)","url":"https://docs.ogc.org/is/06-103r4/06-103r4.pdf","note":"Open Geospatial Consortium (adopted as ISO 19125-1)"},{"title":"ISO 19107:2019 Geographic information - Spatial schema","url":"https://www.iso.org/standard/66175.html","note":"International Organization for Standardization (ISO/TC 211)"},{"title":"OGC Geography Markup Language (GML) Encoding Standard","url":"https://www.ogc.org/standards/gml/","note":"Open Geospatial Consortium"},{"title":"OGC API - Features - Part 2: Coordinate Reference Systems by Reference corrigendum (18-058r1)","url":"https://docs.ogc.org/is/18-058r1/18-058r1.html","note":"Open Geospatial Consortium"},{"title":"Geographic information - Well-known text representation of coordinate reference systems","url":"https://docs.ogc.org/is/18-010r7/18-010r7.html","note":"Open Geospatial Consortium"},{"title":"WKT Coordinate Reference Systems - OGC Standard Representation","url":"https://www.ogc.org/standards/wkt-crs/","note":"Open Geospatial Consortium"},{"title":"OGC Name Type Specification - definitions - part 1 - basic name","url":"https://docs.ogc.org/pol/09-048r7.html","note":"Open Geospatial Consortium"},{"title":"EPSG and OGC URIs","url":"https://iogp.georepository.com/ogc_uri.html","note":"International Association of Oil and Gas Producers (IOGP) - EPSG Geodetic Parameter Dataset registry"},{"title":"New Datums - Modernized National Spatial Reference System","url":"https://geodesy.noaa.gov/datums/newdatums/index.shtml","note":"NOAA National Geodetic Survey"},{"title":"Geocentric Datum of Australia 2020 (GDA2020)","url":"https://www.ga.gov.au/scientific-topics/positioning-navigation/geodesy/datums-projections/gda2020","note":"Geoscience Australia"},{"title":"PROJ Frequently Asked Questions","url":"https://proj.org/en/stable/faq.html","note":"PROJ / OSGeo"},{"title":"ISO 19111:2019 Geographic information — Referencing by coordinates","url":"https://www.iso.org/standard/74039.html","note":"International Organization for Standardization"},{"title":"OGC Abstract Specification Topic 24: Functional Model for Crustal Deformation","url":"https://docs.ogc.org/as/22-010r4/22-010r4.html","note":"Open Geospatial Consortium (with IAG Commission 1 Working Group 1.3.1)"},{"title":"ITRF2020 — International Terrestrial Reference Frame","url":"https://itrf.ign.fr/en/solutions/itrf2020","note":"IERS ITRS Centre, Institut national de l'information géographique et forestière (IGN)"},{"title":"New Zealand Geodetic Datum 2000 deformation model","url":"https://www.linz.govt.nz/guidance/geodetic-system/coordinate-systems-used-new-zealand/geodetic-datums/new-zealand-geodetic-datum-2000-nzgd2000/new-zealand-geodetic-datum-2000-deformation-model","note":"Land Information New Zealand (LINZ)"},{"title":"Geomatics Guidance Note 25 — Dynamic versus static CRSs and use of the ITRF (IOGP Report 373-25)","url":"https://www.iogp.org/bookstore/product/geomatics-guidance-note-25-dynamic-versus-static-crss-and-use-of-the-itrf/","note":"International Association of Oil & Gas Producers (IOGP) Geomatics Committee"},{"title":"EPSG Geodetic Parameter Dataset — Guidance Notes and Registry","url":"https://iogp.georepository.com/guidance-notes.html","note":"IOGP Geomatics Committee (EPSG registry, GeoRepository)"},{"title":"OGC GeoPackage Encoding Standard 1.4.0","url":"https://www.geopackage.org/spec140/","note":"Open Geospatial Consortium"},{"title":"PROJJSON specification","url":"https://proj.org/en/stable/specifications/projjson.html","note":"PROJ project (OSGeo)"},{"title":"Coordinate epoch support","url":"https://gdal.org/en/stable/user/coordinate_epoch.html","note":"GDAL project (OSGeo)"},{"title":"Resolution 4 of the 27th CGPM (2022) — On the use and future development of UTC","url":"https://www.bipm.org/en/cgpm-2022/resolution-4","note":"Bureau International des Poids et Mesures (BIPM) / Conférence Générale des Poids et Mesures"},{"title":"PROJ documentation — Coordinate operations","url":"https://proj.org/en/stable/operations/index.html","note":"PROJ project (OSGeo)"},{"title":"PROJ documentation — Transformation pipelines (+proj=pipeline)","url":"https://proj.org/en/stable/operations/pipeline.html","note":"PROJ project (OSGeo)"},{"title":"PROJ documentation — projinfo","url":"https://proj.org/en/stable/apps/projinfo.html","note":"PROJ project (OSGeo)"},{"title":"PROJ documentation — Glossary","url":"https://proj.org/en/stable/glossary.html","note":"PROJ project (OSGeo)"},{"title":"PROJ documentation — Resource files","url":"https://proj.org/en/stable/resource_files.html","note":"PROJ project (OSGeo)"},{"title":"PROJ documentation — Transformations (usage)","url":"https://proj.org/en/stable/usage/transformation.html","note":"PROJ project (OSGeo)"},{"title":"PROJ documentation — Transformation operations catalogue","url":"https://proj.org/en/stable/operations/transformations/index.html","note":"PROJ project (OSGeo)"},{"title":"NGS Coordinate Conversion and Transformation Tool (NCAT)","url":"https://geodesy.noaa.gov/NCAT/","note":"NOAA National Geodetic Survey"},{"title":"New Datums — modernization of the National Spatial Reference System","url":"https://www.ngs.noaa.gov/datums/newdatums/index.shtml","note":"NOAA National Geodetic Survey"},{"title":"NADCON 5.0: Geometric Transformation Tool for points in the National Spatial Reference System (NOAA Technical Report NOS NGS 63)","url":"https://repository.library.noaa.gov/view/noaa/55451","note":"NOAA National Geodetic Survey"},{"title":"EPSG Geodetic Parameter Dataset Terms of Use","url":"https://iogp.georepository.com/terms-of-use.html","note":"International Association of Oil & Gas Producers (IOGP) Geomatics Committee"},{"title":"OGC Naming Authority - Procedures","url":"https://docs.ogc.org/pol/09-046r6.html","note":"Open Geospatial Consortium"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium (W3C)"},{"title":"Guide to Attribute Based Access Control (ABAC) Definition and Considerations","url":"https://csrc.nist.gov/pubs/sp/800/162/upd2/final","note":"National Institute of Standards and Technology (NIST)"},{"title":"Universal Electronic Records Management (ERM) Requirements","url":"https://www.archives.gov/records-mgmt/policy/universalermrequirements","note":"U.S. National Archives and Records Administration (NARA)"},{"title":"Current Best Practices for Generalizing Sensitive Species Occurrence Data","url":"https://docs.gbif.org/sensitive-species-best-practices/master/en/","note":"Global Biodiversity Information Facility (GBIF Secretariat)"},{"title":"eXtensible Access Control Markup Language (XACML) Version 3.0","url":"https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html","note":"OASIS"},{"title":"Data Catalog Vocabulary (DCAT) - Version 3","url":"https://www.w3.org/TR/vocab-dcat-3/","note":"World Wide Web Consortium (W3C)"},{"title":"INSPIRE Data Specification on Coordinate Reference Systems - Technical Guidelines","url":"https://knowledge-base.inspire.ec.europa.eu/publications/inspire-data-specification-coordinate-reference-systems-technical-guidelines_en","note":"INSPIRE Maintenance and Implementation Group / European Commission"},{"title":"RFC 3339: Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339.html","note":"Internet Engineering Task Force"},{"title":"Computation of coordinate operations between two CRS - PROJ documentation","url":"https://proj.org/en/stable/operations/operations_computation.html","note":"PROJ project (OSGeo)"},{"title":"OGC Testbed-18: Reference Frame Transformation Engineering Report","url":"https://docs.ogc.org/per/22-038r2.html","note":"Open Geospatial Consortium"},{"title":"Geodesy - EPSG Geodetic Parameter Dataset","url":"https://www.iogp.org/workstreams/engineering/geomatics/geodesy/","note":"International Association of Oil and Gas Producers (IOGP), Geomatics Committee"},{"title":"GeoParquet Specification 1.1.0","url":"https://geoparquet.org/releases/v1.1.0/","note":"GeoParquet / Open Geospatial Consortium community standard"},{"title":"OGC Simple Features Access - Part 1: Common Architecture","url":"https://www.ogc.org/standards/sfa/","note":"Open Geospatial Consortium"}],"openQuestions":["Verify European ETRS89/EUREF static-vs-dynamic frame practice and retrieve IOGP Guidance Note 25 and EPSG Guidance Note 7-7 in full, since both were identified only at page level and the model currently treats European practice as an unverified analogy to the North American and Australian pattern.","Investigate whether planetary/non-Earth CRS families and moving-platform or orbital reference frames should be explicitly brought into WM-XCT-033's scope or formally assigned to a sibling model, since the current evidence base did not examine them at all.","Retrieve EPSG Dataset terms-of-use, licensing conditions, and the current released dataset version directly from the custodian once automated access is no longer refused, to confirm the redistribution constraints asserted here.","Establish whether Vercy should standardize the chain-accuracy aggregation rule and densification/polar-handling conventions across all XCT geometry-adjacent models rather than leaving each as a per-Dimension local computation, since no primary source normatively defines either.","ISO 19107:2019 is paywalled; only the catalogue scope statement was retrievable, so no clause-level claim is made from it and the abstract primitive/solid concepts are supported indirectly through OGC sources.","OGC 06-103r4 is published as PDF only and its text layer was not machine-extractable in this pass; its content is used only where corroborated by GeoSPARQL 1.1 and the GeoPackage Encoding Standard, and the DE-9IM matrix detail is therefore referenced rather than reproduced.","GML clause-level detail (curve segment interpolation types, solid shell structure, srsDimension semantics) was retrievable only at the standards landing page level; the curved and solid finding is consequently supported mainly by JSON-FG and GeoPackage.","Topology as a distinct structure (shared edges, node-arc-face complexes, planar graph enforcement) is not modelled; only geometry as a value is in scope.","Spatial indexing structures, tiling schemes and discrete global grid systems are not modelled, although they consume the extents defined here.","Positional accuracy models and error ellipses are referenced as quality statements only; their derivation and statistical semantics are not defined.","M-ordinate semantics vary widely by domain and no single authoritative vocabulary was located; the model records unit and semantics as declarations rather than constraining them.","Geometry simplification and generalization algorithms are excluded even though generalized geometry appears as a disclosure control output.","Coordinate operation definitions, transformation accuracy, grid-shift files and late-binding operation selection are not modelled; only the reference to a projected CRS's defining conversion is carried.","Parametric and temporal CRS subtypes are named but their definition content is not elaborated.","Planetary and non-Earth CRS families served by the OGC definition registers were not examined.","The full ISO 19111:2019 text is paywalled and iso.org refused automated access; the openly published OGC Abstract Specification Topic 2 corrigendum was used as the equivalent text, so no clause-level citation of the ISO document itself is claimed.","The EPSG Dataset terms of use, redistribution licensing and current released dataset version could not be retrieved from epsg.org, which refused automated access; only the registry's published URI guidance was verified.","The IOGP Guidance Note 373-07 series, which carries the dataset's deprecation rules and entity structure, was not machine-readable and is therefore not cited at clause level; deprecation behaviour here rests on the registry's URI guidance and the OGC naming policy instead.","Vertical datum modelling beyond identity and non-interchangeability - geoid models, height system realization, orthometric height computation - is left to geodetic authorities.","Height and depth sign conventions and their interaction with axis direction are only partially covered.","Coordinate precision, resolution and rounding as data quality concerns are not modelled here.","Parametric CRS and parametric datum are not developed as their own finding, although ISO 19111 admits spatio-parametric compound CRS; a parametric component would currently be carried only as a generic compound component.","Derived CRS and projected CRS conversion parameters, and map-projection method context, are captured only inside the pinned definition snapshot and are not decomposed into their own findings.","Bound CRS and the embedded hub-transformation pattern found in legacy definitions are not modelled; such definitions would be classified as non-register or superseded and pinned as text.","Non-Earth, planetary, inertial and orbital reference frames are outside the retrieved evidence base and are not covered by the frame dynamics classification as scoped.","Moving-platform engineering frames (vessel, vehicle, robot base) are admitted through the engineering-definition finding, but the kinematic chain and its own time semantics are not modelled here.","Sounding, tidal and chart datums are covered only generically under the vertical reference finding; hydrographic-specific practice was not researched to primary sources.","IOGP Guidance Note 25 and EPSG Guidance Note 7-7 on ETRS89 were identified at page level but their full texts were not retrieved, so European regional practice is cited by reference only.","No primary source was found that normatively specifies a densification tolerance rule or polar and projection-singularity handling; both are recorded as declarations with an explicit gap marker.","ISO 19157-1 data-quality text was not retrievable at an openly accessible URL, so positional-quality vocabulary is aligned indirectly through the referencing standard's operation-accuracy concept and through agency uncertainty material rather than cited directly.","The EPSG guidance notes 7-1, 7-2, 7-5 and 7-6 were not machine-extractable at fetch time; only the authoritative guidance-note index with titles, versions and dates is cited, so formula-level and null-transformation detail is acknowledged rather than quoted.","Vertical datums, geoid models and the conversion between ellipsoidal and orthometric heights are treated only as a dimensionality and height-type boundary, not as a modelled subject.","Raster and coverage regridding, resampling kernels and pixel-centre conventions are out of scope; only vector geometry is addressed.","Uncertainty correlation between neighbouring vertices of one geometry is not modelled; only per-coordinate or per-operation values are carried.","The parent model WM-XCT-010 boundary is asserted from registry metadata alone, since no relation rationale was supplied.","No normative threshold is given for when a coordinate change becomes substantive; the criteria element exists but the numeric threshold must be set per adopting Dimension and is unsupported by the cited sources.","Legal-hold semantics are grounded in general records-management lifecycle requirements rather than in a jurisdiction-specific litigation-hold rule; the authoritative regulation text could not be retrieved and the hold rule is therefore stated as a marker plus external ownership.","Detailed geodetic content - operation method parameters, ellipsoid and prime-meridian handling, WKT and encoding grammars - is intentionally left to the conceptual and encoding standards and is not restated here.","No pricing, procurement or contractual mechanics for licensed grids are modelled; only licence status and redistribution state are carried.","Machine-readable policy expression for the sensitivity and rights rules is referenced as an external capability and not specified.","Cross-border transfer controls on location data are not modelled; they are treated as an adopting-Dimension legal question.","No uncertainty propagation model across concatenated coordinate operations, and no rule for combining operation accuracy with source coordinate uncertainty.","No treatment of raster or coverage grid geometry, tiling schemes or discrete global grid cell identifiers beyond noting that some serializations can carry them.","No model of geometry simplification, topological cleaning or conflation, which are transformations of shape rather than of reference frame.","No treatment of moving-object or trajectory geometry where position varies continuously with time as a first-class value rather than as a versioned snapshot.","No treatment of measured or linear referencing along a route, which requires a linear reference system distinct from a coordinate reference system.","No model of the licence terms themselves for registry, grid and deformation resources; only the presence of a constraint is recorded.","No enumeration of database-specific spatial type limits beyond the general statement that database bindings are lossy projections.","No rule for reconciling a geometry whose host record and geometry disagree about which real-world thing is being located."],"resources":{"spec":"/models/wm-xct-033-geometry-coordinate-reference/spec.yaml","agents":"/models/wm-xct-033-geometry-coordinate-reference/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-xct-033"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-xct-033-geometry-coordinate-reference/spec.yaml","ver-cy/world-models/card-supplements/wm-xct-033-geometry-coordinate-reference.json"],"providers":["Claude"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-04T01:26:49Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}