BACK BOTTOM clipt computeMaxBorderCode computeRegionCode FRONT INSIDE LEFT liangBarskyClip point_force2d RIGHT tgeo_at_geom tgeo_at_stbox tgeo_at_value tgeo_minus_geom tgeo_minus_stbox tgeo_minus_value tgeo_restrict_geom tgeo_restrict_stbox tgeo_value_at_timestamptz tgeoinst_restrict_geom tgeoinst_restrict_geom_iter tgeoinst_restrict_stbox tgeoinst_restrict_stbox_iter tgeoseq_disc_restrict_geom tgeoseq_disc_restrict_stbox tgeoseq_restrict_geom tgeoseq_restrict_stbox tgeoseq_step_restrict_geom tgeoseq_step_restrict_stbox tgeoseqset_restrict_geom tgeoseqset_restrict_stbox TOP tpoint_at_geom tpoint_at_stbox_segm tpoint_at_value tpoint_force2d tpoint_minus_geom tpoint_minus_value tpointinst_restrict_geom_iter tpointinst_restrict_stbox_iter tpointsegm_timestamp_at_value1_iter tpointseq_at_stbox_segm tpointseq_interperiods tpointseq_linear_at_geom tpointseq_linear_at_stbox_xyz tpointseq_linear_restrict_geom tpointseq_linear_restrict_stbox tpointseq_timestamp_at_value tpointseqset_at_stbox_segm XMAX YMAX ZMAX

tpointseq_linear_at_geom() static TSequenceSet * tpointseq_linear_at_geom ( const TSequence *  seq, const GSERIALIZED *  gs  ) static Return a temporal point sequence with linear interpolation restricted to a geometry. The computation is based on the PostGIS function ST_Intersection which delegates the computation to GEOS. The geometry must be in 2D. When computing the intersection the Z values of the temporal point must be dropped since the Z values "are copied, averaged or interpolated" as stated in https://postgis.net/docs/ST_Intersection.html After this computation, the Z values are recovered by restricting the original sequence to the time span of the 2D result. Precondition The arguments have the same SRID, the geometry is 2D and is not empty. This is verified in tgeo_restrict_geom