docs: realign the roadmap on the ADRs#70
Merged
Conversation
emmanuelmathot
approved these changes
Jul 17, 2026
A CoverageJSON Trajectory requires a `t` coordinate in every composite tuple, so a spatial-only path is a MultiPoint coverage, not a Trajectory. That makes /trajectory a temporal verb, and MultiPoint the non-temporal multi-position capability, served by the EDR Position verb (/position accepting a MULTIPOINT). Record the decision in ADR-0005, amend ADR-0004 (which had listed /trajectory among the non-temporal verbs), and index it.
Doc 02's banner listed point, transect, tile, time series, and info as "not yet redesigned": point shipped as /position (#44), tile is dropped (ADR-0004), and transect is reclassified as the temporal /trajectory (ADR-0005). Record where each stands, and flag the /transect example as a schema-invalid Trajectory (its tuples lack `t`). Doc 08 kept a second copy of the same status and had drifted the same way; point it at doc 02's banner instead.
ADR-0004 dropped Story 7 (/tiles) and ADR-0005 reclassifies Story 6 (transect) as temporal; the live plan is now the milestones and the ADRs, not this file. Retire it additively: keep the stories as the historical record, add a table mapping each of the 13 to its current home, lead the banner with the retirement, and drop the stale promise that the roadmap "will be re-planned". Note the same in ADR-0001, appended to its Status since the ADR corpus is append-only.
Two of Section 3's seven query patterns are now decided elsewhere: tile is dropped (ADR-0004) and transect is the temporal /trajectory (ADR-0005). Name both in the banner and point onward to the ADRs and the README rather than restating a status here, which is how doc 08's copy drifted. Mark the roadmap retired in the document-set index.
chuckwondo
force-pushed
the
docs/roadmap-realignment
branch
from
July 17, 2026 10:29
9fd294c to
b2366f4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The CoverageJSON Trajectory domain requires a
tcoordinate, so/trajectoryis a temporal verb, and the non-temporal multi-position capability is MultiPoint via/positionwith aMULTIPOINTgeometry. ADR-0005 records that and amends ADR-0004.That leaves the roadmap describing a plan the ADRs and milestones have superseded, so it is retired additively: the stories stay as the historical record, with a table mapping each of the 13 to its current home.
Reconciling the rest turned up stale status claims in docs 01, 02, and 08, and a README that listed
/positionas planned though it shipped in #44. Each now points at one source of truth rather than keeping its own copy.