bugGNU Octave - Bugs: bug #61086, [octave forge] (octproj) UTM zone...

 
 

bug #61086: [octave forge] (octproj) UTM zone needs to be specified with PROJ 8.1.1RC1

Submitter:  Rafael Laboissière <rlaboiss>
Submitted:  Fri 27 Aug 2021 07:49:41 AM UTC
   
 
Category:  Octave Package Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Unexpected Error or Warning
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * other Operating System:  * Any
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Mon 07 Nov 2022 12:41:26 PM UTC, comment #3: 

Closing as fixed according to comment #2.

Markus Mützel <mmuetzel>
Group administrator
Mon 07 Nov 2022 12:20:28 PM UTC, comment #2: 

OctPROJ works now with PROJ 9.x series and passes all tests

José Luis García Pallero <jgpallero>
Mon 30 Aug 2021 05:21:51 PM UTC, comment #1: 

cc-ing maintainer

Philip Nienhuis <philipnienhuis>
Group Member
Fri 27 Aug 2021 07:49:41 AM UTC, original submission:  

When the octproj package is built against the release candidate 8.1.1RC1 of the PROJ library, the first unit test in inst/op_transform.m file fails with the following error message:


octave:1> pkg load octproj
octave:2> test op_transform
proj_create: Invalid zone number
***** test
  [x,y,h,t]=op_transform(-6,43,1000,10,...
                         '+proj=latlong +ellps=GRS80',...
                         '+proj=utm +lon_0=3w +ellps=GRS80');
  [lon,lat,H,T]=op_transform(x,y,h,t,'+proj=utm +lon_0=3w +ellps=GRS80',...
                           '+proj=latlong +ellps=GRS80');
  assert(x,255466.98,1e-2)
  assert(y,4765182.93,1e-2)
  assert(h,1000.0,1e-15)
  assert(lon,-6,1e-8)
  assert(lat,43,1e-8)
  assert(H,1000.0,1e-15)
  assert(T,10.0,1e-15)
!!!!! test failed

        In function op_transform:
        In function _op_transform:
        Error in definition parameters
        +proj=latlong +ellps=GRS80
        +proj=utm +lon_0=3w +ellps=GRS80
        Unknown error (code 4096)


It seems that the UTM zone must be explicitly specified when option +proj=utm is used. The patch attached to this bug report fixes the problem. I empirically discovered that the correct value for the UTM zone is 30, hence the added options +zone=30 in the patch. It seems that this value (30) was taken as default for versions of PROJ previous to 8.1.1.

Rafael Laboissière <rlaboiss>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #51825:  specify-utm-zone.patch added by rlaboiss (7KiB - text/x-patch)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by jgpallero (Posted a comment)
  • -email is unavailable- added by philipnienhuis
  • -email is unavailable- added by philipnienhuis
  • -email is unavailable- added by rlaboiss (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-11-07 mmuetzel StatusNone Fixed
        Open/ClosedOpen Closed
    2022-01-05 philipnienhuis Carbon-Copy- Added jgpallero
    2021-08-30 philipnienhuis Carbon-Copy- Added -email is unavailable-
    2021-08-27 rlaboiss Attached File- Added specify-utm-zone.patch, #51825

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code