Changes between Initial Version and Version 2 of Ticket #2809


Ignore:
Timestamp:
Jan 29, 2009, 9:49:25 AM (15 years ago)
Author:
warmerdam
Comment:

I have observed that the primary problem with this file is that the GCPs span the international dateline, and that the ones west of the dateline are positive (~179). The mechanisms in GDAL for doing GCP based regressions do not model the wraparound nature of the geographic coordinate systems and this gets treated as a discontinuity and the transform attempts to drag part of the map across the rest.

One potential solution is a heuristic to use values < -180 for GCPs to the west of the dateline. But this might be hard to do properly for large maps (as this one is).

So instead, I will continue to look into deriving the proper mercator coordinate system.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2809

    • Property Keywords BSB added
    • Property Owner changed from Warmerdam to warmerdam
    • Property Status newassigned
  • Ticket #2809 – Description

    initial v2  
    1 I have a BSB dataset containing 100+ GCPs. The GCPs generate a very poor fit to
    2 a 2nd order polynomial (also fail to generate a valid geotransform
    3 in GDALGCPsToGeoTransform). As the result, computed extent in GCS based
    4 the GCPs is out of place. The same dataset looks fine in a BSB viewer from
    5 maptech.
     1I have a BSB dataset containing 100+ GCPs. The GCPs generate a very poor fit to a 2nd order polynomial (also fail to generate a valid geotransform in GDALGCPsToGeoTransform). As the result, computed extent in GCS based the GCPs is out of place. The same dataset looks fine in a BSB viewer from maptech.
    62
    7 I placed the test dataset, 530_1.kap at ftp://GDAL@ftp.esri.com. Could you take
    8 a look? Maybe the GCPs are read wrong or there is another source of georeferencing
    9 info in the file.
     3I placed the test dataset, 530_1.kap at ftp://GDAL@ftp.esri.com. Could you take a look? Maybe the GCPs are read wrong or there is another source of georeferencing info in the file.
    104