Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 8.0-M0
    • Fix Version/s: None
    • Component/s: referencing
    • Labels:
      None

      Description

      With the changing of the guard (hi Andrea) I think I can finally implement the most popular request for new users getting used to GeoTools.

      Can we add methods to MathTransform to support JTS:

      • Coordinate
      • Coordinate[] (not sure about this)
      • CoordinateSequence (want this to be a simple wrapper?)

      The adoption of an ISO Geometry model is stalled out by a simple lack of funding; persisting in complicating the use of the reference module by hobbling it to a ship that is not coming in is not doing us any favours.

      I believe we can add new methods besides those already in place for ISO Geometry model. I do not even want to deprecate these methods as I would like to see Geometry chased if sufficient resources is put in place for the work.

        Activity

        Hide
        Andrea Aime added a comment -
        Nope, I disagree on this development, rather put these methods in CRS or JTS helper classes. Let's discuss this on the mailing list?
        Show
        Andrea Aime added a comment - Nope, I disagree on this development, rather put these methods in CRS or JTS helper classes. Let's discuss this on the mailing list?
        Hide
        Jody Garnett added a comment -
        The methods are already in the JTS utility class.

        Could we move JTS class (and its friend ReferencedEnvelope) to gt-referencing as a "provided" dependency?
        It makes sense as these two classes bridge from JTS to CoordianteReferenceSystem.

        Largely what is needed is an acknowledgement that JTS is our Geometry model.

        I agree that the CRS and JTS classes almost completely hide MathTransform. Still at some point in every code example we use CRS to look up a MathTransform between two CoordianteReferenceSystems. And at that point users look at what they can do with a MathTransform and start getting confused with the ISO Geometry model.
        Show
        Jody Garnett added a comment - The methods are already in the JTS utility class. Could we move JTS class (and its friend ReferencedEnvelope) to gt-referencing as a "provided" dependency? It makes sense as these two classes bridge from JTS to CoordianteReferenceSystem. Largely what is needed is an acknowledgement that JTS is our Geometry model. I agree that the CRS and JTS classes almost completely hide MathTransform. Still at some point in every code example we use CRS to look up a MathTransform between two CoordianteReferenceSystems. And at that point users look at what they can do with a MathTransform and start getting confused with the ISO Geometry model.
        Hide
        Andrea Aime added a comment -
        So are we dropping the ball on switching to a more generic geometry model? Switching the class in referencing is easy now, but may prove nastier to remove it when we switch to a more generic geom model...
        Show
        Andrea Aime added a comment - So are we dropping the ball on switching to a more generic geometry model? Switching the class in referencing is easy now, but may prove nastier to remove it when we switch to a more generic geom model...

          People

          • Assignee:
            Jody Garnett
            Reporter:
            Jody Garnett
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: