[estebanzimanyi]

PyMEOS binds the four temporal types of the MEOS 1.4 families as it binds
the temporal points: TCbuffer, TNpoint, TPose and TRgeometry, each with
its instant, sequence and sequence set classes, and the base values
Cbuffer, Npoint, Nsegment and Pose with the sets CbufferSet, NpointSet
and PoseSet. The value of a temporal rigid geometry is a shapely
geometry, its reference geometry placed by the pose. The factory and the
package exports name every class.

Each temporal class implements the methods the Temporal base declares
through the typed MEOS functions of its family: from_base_time and
from_base_temporal, from_mfjson, start_value, end_value, value_set and
value_at_timestamp. TRgeometry also carries the segments, the deletion
of a time value, the restriction before or after a timestamp, to_instant
and the sequence accessors of its own trgeometry functions. The pose
accessors are yaw and quaternion, the MEOS 1.4 names.

TCbuffer and TRgeometry carry the ever and always spatial relationships
MEOS defines for them, with the names TCbuffer and TPoint use:
is_ever_contains, is_ever_covers, is_ever_disjoint,
is_ever_within_distance, ever_intersects and ever_touches with their
always twins, each against the geometries, base values and temporal
values of the same type MEOS defines it for. For a geometry or a base
value containing or covering self they carry is_ever_contained_in and
is_ever_coveredby with their always twins; coveredby is the covers
relationship with the container first, named and computed as PostGIS's
coveredby and geography_coveredby. TCbuffer carries the temporal
relationships as well. MEOS defines no spatial relationship for the
network point or the pose.

A base value is built from its text or by keyword, as
Npoint(route=1, position=0.5), Cbuffer(point=..., radius=...) and
Pose(point=..., theta=...). Its WKB output is the bytes PyMEOS-CFFI
returns, its WKB input and a set's elements are a bytes object and a
Python list whose length is their own, and a network point set takes
each element as the Npoint struct npointset_make reads. The text of a
value is its asText, as in MobilityDB: str of a pose, a circular buffer,
a network point and their sets is pose_as_text, cbuffer_as_text,
npoint_as_text and spatialset_as_text, Pose(POINT(1 1),0.5), the sets
gaining as_text, as_wkt and as_ewkt as GeoSet has them, and a temporal
rigid geometry reads its text through trgeometry_in and writes it
through trgeometry_as_text and trgeometry_as_ewkt, the reference
geometry before the poses; repr of a temporal value is the class name
around its text.

The tests cover every class: construction from text, from the base
values and from MF-JSON, the outputs, the accessors, the comparisons and
the transformations of each family.