GeoTools
  1. GeoTools
  2. GEOT-1553

CRS equals comparion used by WorldImageReader isn't working

    Details

    • Type: Bug Bug
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.3.1
    • Fix Version/s: 2.7.6
    • Component/s: coveragetools, referencing
    • Labels:
      None

      Description

      When you set the MapContext to a specific CRS (a projected orthographic CRS in my case), and then try to read a georeferenced image in with the same CRS (using WorldImageReader), then it forces a reprojection, even though the source and destination CRS's are the same.

      This breaks for orthographic CRS since the orthographic reprojection isn't work anyways... (it fails if just one pixel is not projectable).

      The work around I have to use is to first read the world image in, then grab it's CRS and use it as the MapContext's CRS before adding it as a layer. This ensures the mem address of the CRS is teh same, and then it will pass the equals test. However, this doesn't work when trying to use uDig, which doesn't do this work around...

      -Judd

        Activity

        Hide
        Martin Desruisseaux added a comment -
        We need a more accurate description of the problem in order to process. I can not determine from the above if this is a "referencing module" problem or a "streaming renderer" problem.

        * Do you get a stack trace? If so, could you post that stack trace please?
        * Have you identified the code which fails to recognize the two CRS as identical? If so, could you post the class name and line number please?
        * If the bug appears to be in CRS.equalsIgnoreMetadata(...) from the org.geotools.refencing module, could you post the WKT of the 2 CRS being compared please?
        Show
        Martin Desruisseaux added a comment - We need a more accurate description of the problem in order to process. I can not determine from the above if this is a "referencing module" problem or a "streaming renderer" problem. * Do you get a stack trace? If so, could you post that stack trace please? * Have you identified the code which fails to recognize the two CRS as identical? If so, could you post the class name and line number please? * If the bug appears to be in CRS.equalsIgnoreMetadata(...) from the org.geotools.refencing module, could you post the WKT of the 2 CRS being compared please?

          People

          • Assignee:
            Simone Giannecchini
            Reporter:
            Judd Taylor
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: