[estebanzimanyi]

The route operators of a temporal network point are generated from the catalog: the group meos_npoint_route, one public MEOS function per SQL signature and argument order, is retired beside the other network point groups. Each of the twenty signatures MobilityDB declares registers under its own name, argument types and result, with its operator: overlapsRid and @@, containsRid and @?, containedRid and ?@, sameRid and @= over a route, a set of routes, a network point and a temporal network point in the orders MobilityDB declares them.

Measured: over the catalog of MobilityDB ac8feb51dc, the commit this branch's pin records, the generator writes the same registrations as before but four: containedRid(npoint, tnpoint), sameRid(npoint, tnpoint) and their operators ?@ and @=, which register nothing before; no registration is lost and none is registered twice. No hand registration of these names exists to delete. test/sql/tnpoint.test reads containedRid and sameRid with the network point first against their twins with the temporal value first, over a route both values hold and one neither holds.