FME, which sources from GEOS
(https://cdn.safe.com/resources/fme/FMEDesktop_Legal_Notices_2019.0.pdf),
did not handle the measurement with its Clipper transformer until about
two years ago. Wonder if they achieved this through direct update the
GEOS lib or through post-GEOS enhancement.
On 5
Not exactly the same thing - I believe that ticket is referring to just the
WKB format handling?
I can make a ticket for measure handling by the overlay operations if there
isn't one already.
On Mon, May 6, 2019 at 11:31 AM Darafei "Komяpa" Praliaskouski <
m...@komzpa.net> wrote:
> It's in backl
It's in backlog for 6 years already I believe:
https://trac.osgeo.org/geos/ticket/466
пн, 6 мая 2019, 19:33 карыстальнік Martin Davis
напісаў:
> It should be possible to post-process GEOS results to re-populate the M
> values if present. Linear interpolation could be used to estimate values
> a
It should be possible to post-process GEOS results to re-populate the M
values if present. Linear interpolation could be used to estimate values
at intra-segment points. We can put this on the list for future
development.
On Mon, May 6, 2019 at 4:48 AM Darafei "Komяpa" Praliaskouski
wrote:
> H
Hi,
GEOS operations do not preserve M, but sometimes preserve Z. You can try
ST_SwapOrdinates(ST_Intersection(ST_SwapOrdinates(geom, 'zm'),...), 'zm').
On Thu, May 2, 2019 at 5:19 AM Bo Guo wrote:
> Hi there,
>
> I was trying to cut a portion of the LRS route with an area using
> ST_Intersectio
1. What values do you want to assign to intersections of lines and
polygons (if not on vertices)?
2. You can try with ST_DumpPoints, but this will "recreate" only those
segments that are completely within intersecting polygon:
with
l as ( -- linestringm
select st_makeline(st_makepointm(1,
Hi there,
I was trying to cut a portion of the LRS route with an area using
ST_Intersection. However the resulting route no longer carries measure
value. The behavior is the same for version 9.6 or the latest version
11. Anyone has any suggestions?
Thanks!
Bo
