Hugh I think we have a JTS 1.16.1 taking shape for you, any chance you can
confirm it fixes your issues before we roll ahead with wider announcements?
--
Jody Garnett
On Tue, 12 Feb 2019 at 21:05, Hugh Saalmans
wrote:
> Is LinestringM a valid geometry type in Geotools 21-RC or is my code
> miss
Can you confirm you have setup the geometryFactory with the correct
dimensions?
If the GeometryFactory and Coordinates do not match I would like the
coordinates to cause a problem, or be converted to the format used for
internal storage, during creation ... rather than cause a problem later.
--
J
Hi Hugh,
This looks like it is a bug in JTS. I'll try and look it more when I
get a chance. Support for Z and M dimensions has been added in recent
updates to JTS.
I entered a JTS issue here: https://github.com/locationtech/jts/issues/370.
Cheers,
Jim
On 2/12/19 11:48 PM, Hugh Saalmans w
Is LinestringM a valid geometry type in Geotools 21-RC or is my code missing
something?
I can create a LinestringM object from an array of CoordinateXYM objects. But
calling a function on the geom (e.g. line.getLength()) causes the following
error. (I’m using Java 11).
Exception in thread "MyA
One surprise found in our research was how loosely defined the JTS
"dimension" is:
*ordinate: Returns the ordinate of a coordinate in this sequence. Ordinate
indices 0 and 1 are assumed to be X and Y. Ordinates indices greater than 1
have user-defined semantics (for instance, they may contain othe
Thank you for the overview. I will see what my organization can do.
Jim Hughes schrieb am Di. 3. Juli 2018 um 04:36:
> Hi all,
>
> As a note, one of my medium-terms goals for JTS is to support reading and
> writing Geometries with Z's and M's. Once we get this in JTS, then it'd be
> possible to
Hi all,
As a note, one of my medium-terms goals for JTS is to support reading
and writing Geometries with Z's and M's. Once we get this in JTS, then
it'd be possible to start wiring up PostGIS's trajectory support into
GeoTools.
Jody and I were working on this some over the last week and we
Hi Georg,
as far as I know, support for "M" is missing, no data source supports
reading it, and
upper levels (processing, rendering) would be confused by finding a 3rd (or
4th)
ordinate, if 3rd it may be treated as Z by mistake.
Output encoding/write support is also missing, although in some format
Hi,
what is the state of linestringM support in GeoTools?
I would be interested in trajectory support in general as well and would
like it to perform analytics similar to
https://anitagraser.com/2018/04/16/movement-data-in-gis-12-why-you-should-be-using-postgis-trajectories/
Best,
Georg
--
