Opened 16 years ago

Closed 16 years ago

Last modified 15 years ago

#1231 closed bug (fixed)

When creating a new GRASS location, QGIS fails loading predefined regions

Reported by: marcopx Owned by: telwertowski
Priority: critical: causes crash or data corruption Milestone:
Component: GRASS Version: Trunk
Keywords: Cc:
Must Fix for Release: Yes Platform: All
Platform Version: Awaiting user input: no

Description

When creating a new GRASS location, QGIS fails loading predefined regions. For every nation selected (from Afghanistan to Zimbabwe) it loads the following region values:

North=South=-90 East=West=-39

Marco

Change History (5)

comment:1 by pcav, 16 years ago

Probably the same thing:

When setting up a new region, it fails:

Cannot reproject selected region. Impossible to set a new region based on a nation, or draw a rectangle

For Italy, the coor shown are wrong: N and S -9.99829e+06 E and W 1.5e+06

Probably because of:

OGR can't parse PROJ.4-style parameter string: OGR Error code was 5 pm.isNull() = 0 ... Warning: Throwing exception /usr/local/src/qgis/2008-07-23_0.11.0/0.11.0~gfossit20080723/qgis-0.11.0~gfossit20080723/src/core/qgscoordinatetransform.cpp502

QGIS 0.11 from debian.gfoss.it.

comment:2 by marcopx, 16 years ago

Platform: WindowsAll
Platform Version: Vista Home Premium
Version: 0.11.0HEAD

The bug still applies on latest trunk builds. Changed from Win Platform to All (see above)

Marco

comment:3 by telwertowski, 16 years ago

Owner: changed from nobody to telwertowski

The problem was introduced between 0.10 and 0.11 (tested using Mac builds).

The "can't parse" error appears to be unimportant -- it occurs because there is no initial selection when the projection list is first shown. The routine is called again when a projection is selected.

The problem, which I don't understand yet, is that QgsCoordinateTransform is returning the same output point for any input point. Perhaps some parameter is so far off that every input point is transformed into the same output point.

comment:4 by telwertowski, 16 years ago

Resolution: fixed
Status: newclosed

Magic numbers were not updated when the srs.db was updated in r8720. Fixed by r9296.

comment:5 by (none), 15 years ago

Milestone: Version 1.0.0

Milestone Version 1.0.0 deleted

Note: See TracTickets for help on using tickets.