Bug report #2426

On-the-fly projection issues with large extents

Added by Maxim Dubinin over 10 years ago. Updated about 9 years ago.

Status:Closed
Priority:Low
Assignee:nobody -
Category:Projection Support
Affected QGIS version: Regression?:No
Operating System:All Easy fix?:No
Pull Request or Patch supplied: Resolution:fixed
Crashes QGIS or corrupts data: Copied to github as #:12486

Description

When I'm trying to project the whole Russian Federation layer, there is some weird behaviour.

1. Take sample from http://gis-lab.info/data/vmap0/bounds-correct.7z
2. Add new projection (Albers based):
+proj=aea +lat_1=52 +lat_2=64 +lat_0=0 +lon_0=105 +x_0=18500000 +y_0=0 +ellps=krass +units=m +no_defs
3. Load country boundary from sample
4. Select created projection and make zoom to layer
Everything disappears
5. Zoom out a little
Data shows up as expected.

Note: this projection works fine in Arcview, ArcGIS etc and used for the whole country indeed .

Screenshot.png (193 KB) Giovanni Manghi, 2010-02-09 11:29 AM

Associated revisions

Revision c131ea3a
Added by Jürgen Fischer about 9 years ago

fix #2426: dateline split

git-svn-id: http://svn.osgeo.org/qgis/trunk/[email protected] c8812cc2-4d05-0410-92ff-de0c093fc19c

Revision 79c0c470
Added by Jürgen Fischer about 9 years ago

fix #2426: dateline split

git-svn-id: http://svn.osgeo.org/qgis/[email protected] c8812cc2-4d05-0410-92ff-de0c093fc19c

History

#1 Updated by Giovanni Manghi over 10 years ago

Hi,
I just followed the steps and I cannot replicate the behaviour on both windows xp and linux using qgis trunk.

The vector seems correctly projected in the system you have posted (see attached image), and I cannot see any problem zooming in/out or to full extent.

#2 Updated by Maxim Dubinin over 10 years ago

Thanks for testing, please check out this video
http://www.screencast.com/users/gislab/folders/Jing/media/43dc0347-d657-434d-9a03-e7072dd75f15

the point when layer appears is actually when zoom out with the mouse wheel

#3 Updated by dr - over 10 years ago

Replying to [comment:2 gislab]:

Thanks for testing, please check out this video
http://www.screencast.com/users/gislab/folders/Jing/media/43dc0347-d657-434d-9a03-e7072dd75f15

the point when layer appears is actually when zoom out with the mouse wheel

Confirmed.

#4 Updated by Giovanni Manghi over 10 years ago

Well, you are right. I made a slightly different test:

The vector you posted is defined in wgs84 crs and I exported it with "ftools" (I misunderstood your steps) to the system you describe, so I had obviously no problems.

Now... your vector is geographically really wide(!), defined in a geographic crs, and what you do is to reproject it in a projected crs. Maybe the result cannot be the expected one, especially if/when the vector crosses/nears the 180◦ longitude line? Really not sure.

[See also paragraph 5.2.6 of the qgis 1.3 user manual if you want to avoid to see the features crossing the 180º lon line separated from the others]

Somehow related to #2349 ?

In any case if you need the vector in the projected crs you describe, and the project in the same crs, an easy workaround is to export it to this projection with ftools, instead of having qgis reproject it on the fly.

I'm not sure how arcview works, but I believe that gvsig (the only other gis program I can test now) works like it, but actually I can't understand its logic:

I created a view and defined its projection as the crs you describe, then added to the view your vector "bnd-political-boundary-a". The vector shows fine (and no zoom problems), the only "detail" is that is not reprojected. It shows as in a wgs84 qgis project, but in the properties the vector crs is the one of the view.

#5 Updated by Maxim Dubinin over 10 years ago

Thanks for testing it again, glad it was confirmed.

I'm aware of other ways of reprojecting it permanently, but I am still interested in having it fixed while using usual logic. Well, Russia is a big country and we do want to store our shape-files in lat/long. I hope someone will have a look at it.

#6 Updated by Maxim Dubinin about 9 years ago

related to #3508

#7 Updated by Markus Neteler about 9 years ago

Perhaps an issue of the global wrap around not handled correctly? See my comment in #3508

#8 Updated by Jürgen Fischer about 9 years ago

  • Resolution set to fixed
  • Status changed from Open to Closed

fixed in 79c0c470 (SVN r15755).

Also available in: Atom PDF