Skip to content

Read the surface of the service against what MobilityDB declares - #88

Merged
estebanzimanyi merged 2 commits into
masterfrom
test/surface-against-the-catalog
Nov 19, 2026
Merged

estebanzimanyi merged 2 commits into
masterfrom
test/surface-against-the-catalog

Conversation

@estebanzimanyi

Copy link
Copy Markdown
Member

Read the function a handler names at run time through a catalog gate

A handler that picks a function by name at run time passes the name through a
catalog gate (typeHas, boxHas, rasterHas, needRaster) before applying it, as
the raster query picks rasterValue or rasterTileValue and the coverage its
negotiated writer. Below a function that calls a gate, the surface reads a
string literal that is a function's bare name as that function, besides the
calls it reads everywhere. A bare name that names a type or a resource of the
service (raster, stbox, the EDR query trajectory) is read as such, both sets
taken from the generated tables and the route table. The generated tables are
the catalog the gates read and no code a route runs, so the walk does not
enter them.

Measured. The query route and the four EDR queries gain rasterValue and
rasterTileValue, the coverage asCoverageJSON and asTIFF, and no other route
changes; go test passes.

Read the surface of the service against what MobilityDB declares

ats_surface_catalog_test.go reads api/surface.json against the generated
tables. A route serves the types of the collections it reads: a Coverages or
EDR route a raster collection, a collection-level route (/collections,
/collections/{cid}) a collection of either kind, every other route a moving
feature's temporal value; each also serves the box and span types, the bounds
a query is given and the extent a collection states. Every function a route
applies is one MobilityDB states over a type it serves, and the check refuses
a raster writer on a moving-feature route and a trajectory function on a
raster route. Per spatial temporal type it reports the input and output
functions and the raster functions the moving-feature routes reach, and how
many routes a collection of the type answers in full, every function they
apply being stated over it; a route a type does not answer in full refuses
that collection by name.

MobilityAPI is measured by this test rather than by the binding matrices of
MobilityDB (tools/raster_matrix.py, tools/io_matrix.py), which read an object
layer a server has none of.

Measured. Every function of the 45 routes is stated over a type its route
serves; every spatial type reaches asBinary and asMFJSON, tgeompoint alone the
raster readers rasterValue and rasterTileValue, and tgeompoint is answered in
full by 18 of the 19 moving-feature routes that apply a function; go test
passes.

A handler that picks a function by name at run time passes the name through a
catalog gate (typeHas, boxHas, rasterHas, needRaster) before applying it, as
the raster query picks rasterValue or rasterTileValue and the coverage its
negotiated writer. Below a function that calls a gate, the surface reads a
string literal that is a function's bare name as that function, besides the
calls it reads everywhere. A bare name that names a type or a resource of the
service (raster, stbox, the EDR query trajectory) is read as such, both sets
taken from the generated tables and the route table. The generated tables are
the catalog the gates read and no code a route runs, so the walk does not
enter them.

Measured. The query route and the four EDR queries gain rasterValue and
rasterTileValue, the coverage asCoverageJSON and asTIFF, and no other route
changes; go test passes.
ats_surface_catalog_test.go reads api/surface.json against the generated
tables. A route serves the types of the collections it reads: a Coverages or
EDR route a raster collection, a collection-level route (/collections,
/collections/{cid}) a collection of either kind, every other route a moving
feature's temporal value; each also serves the box and span types, the bounds
a query is given and the extent a collection states. Every function a route
applies is one MobilityDB states over a type it serves, and the check refuses
a raster writer on a moving-feature route and a trajectory function on a
raster route. Per spatial temporal type it reports the input and output
functions and the raster functions the moving-feature routes reach, and how
many routes a collection of the type answers in full, every function they
apply being stated over it; a route a type does not answer in full refuses
that collection by name.

MobilityAPI is measured by this test rather than by the binding matrices of
MobilityDB (tools/raster_matrix.py, tools/io_matrix.py), which read an object
layer a server has none of.

Measured. Every function of the 45 routes is stated over a type its route
serves; every spatial type reaches asBinary and asMFJSON, tgeompoint alone the
raster readers rasterValue and rasterTileValue, and tgeompoint is answered in
full by 18 of the 19 moving-feature routes that apply a function; go test
passes.
@estebanzimanyi
estebanzimanyi merged commit 8387ca0 into master Nov 19, 2026
2 checks passed
@estebanzimanyi
estebanzimanyi deleted the test/surface-against-the-catalog branch November 19, 2026 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant