Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jts-dev] proposing an api change
The 1.16 release is taking shape now, thanks for everyone providing RC feedback
--
Jody Garnett


On Fri, 24 Aug 2018 at 11:09, Landon Blake <sunburned.surveyor@xxxxxxxxx> wrote:
Thanks for your work on this Jody. It will be great to get built-in Z and M support.

Landon

On Tue, Aug 7, 2018 at 8:13 PM Jody Garnett <jody.garnett@xxxxxxxxx> wrote:
Thanks for the feedback everyone, at some point during the development I made a small blog post on the changes:


--
Jody Garnett


On Tue, 17 Jul 2018 at 14:13, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:
LocationTech has a monthly meeting of project leads, and today we used the opportunity to discuss making an API change to JTS.

Currently we reply on client code to track the use of optional Z and M measurements (with javadoc noting that dimensions hight then 2 are up to client code to manage).

To support formats that include optional Z and M measurements I am proposing an API change. Adding CoordinateSequence.getNumberOfMeasures(), and adding Coordinate.getM().

I intended to take advantage of java interface "default" methods to update the interfaces without introducing an API break:

  default int  getNumberAttributes(){
       return 0;
  }

_______________________________________________
jts-dev mailing list
jts-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/jts-dev


--
_______________________________________________
jts-dev mailing list
jts-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/jts-dev

Back to the top