Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zoom to layer extent does not work with postgis 2.0.0svn tables #14228

Closed
qgib opened this issue Sep 16, 2011 · 4 comments
Closed

zoom to layer extent does not work with postgis 2.0.0svn tables #14228

qgib opened this issue Sep 16, 2011 · 4 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@qgib
Copy link
Contributor

qgib commented Sep 16, 2011

Author Name: Daniel Araujo Miranda (@mirandadam)
Original Redmine Issue: 4291


None

@qgib
Copy link
Contributor Author

qgib commented Sep 16, 2011

Author Name: Daniel Araujo Miranda (@mirandadam)


how to reproduce:
add a layer from postgis into qgis
right click on the layer name and select "zoom to layer extent"
nothing happens

Bug is not always reproducible. Seems to work on generic geometry layers, but not with geometry(Polygon,4326), for example. (postgis 2 notation).

Ubuntu 11.04
qgis 1.7 wroclaw (1.7.0~natty1, MD5sum: ae3fc6b49d8e82acd8a97d515bad00bc)
postgis 2.0.0 svn 7856, Last Changed Date: 2011-09-15 14:43:57
postgresql 9.1

@qgib
Copy link
Contributor Author

qgib commented Sep 19, 2011

Author Name: Steven Mizuno (Steven Mizuno)


This appears to be a PostGIS 2.0 problem - does st_estimated_extent(schema,table,geom_column) return a reasonable value for the tables in question?

@qgib
Copy link
Contributor Author

qgib commented Sep 20, 2011

Author Name: Daniel Araujo Miranda (@mirandadam)


Steven, as you said, st_estimated extent was returning nonsense.

I reported it as postgis bug #11260, which I just checked and seems to be fixed in r7868 (see http://trac.osgeo.org/postgis/ticket/1200).

Thanks for taking a look at this.
I did not close it saturday because if the postgis guys would not get around it quickly, I believe qgis would have to implement a workaround.

How do I close this bug?

@qgib
Copy link
Contributor Author

qgib commented Sep 20, 2011

Author Name: Giovanni Manghi (@gioman)


closed now. Fixed upstream.


  • resolution was changed from to invalid
  • status_id was changed from Open to Closed

@qgib qgib added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

No branches or pull requests

1 participant