-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Postgis raster shows random data with out-db image data #17471
Comments
Author Name: asdf asdf (asdf asdf) Forgot to add details of the used version. QGIS version 2.0.1-Dufour |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: asdf asdf (asdf asdf) I'm not sure if this is duplicate of the #17362, this might actually be a just problem created by me by creating overviews manually as I have overviews for other use and didn't want to duplicate static raster data indb. As a consequence of this self made overviews rasters are not indb and the overview query will fail as it relies that the data is always indb. Anyways the question is should the overview query always expect indb data or not. |
Author Name: Giovanni Manghi (@gioman)
better ask this in the developers mailing list and eventually close this as invalid. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: asdf asdf (asdf asdf)
Original Redmine Issue: 8765
Affected QGIS version: 2.0.1
Redmine category:db_manager
Out-db rasters from postgis database are shown as random data and sometimes crashes QGIS.
The problem might come from the way the database is queried.
Query made by QGIS taken from the server:
SELECT st_band(rast, 3), st_width(rast), st_height(rast), ....
As far as I have tested "st_band" in queries return data as out-db referenced rasters and contain no pixel data.
If there are no modification to the data like st_union or something like that, rasters stays as file references, which obviously cannot be used by the client over the network.
Related issue(s): #17362 (duplicates)
Redmine related issue(s): 8628
The text was updated successfully, but these errors were encountered: