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

cannot build geodeticCRS 4326: SQLite error... #43680

Closed
aloboa opened this issue Jun 10, 2021 · 7 comments
Closed

cannot build geodeticCRS 4326: SQLite error... #43680

aloboa opened this issue Jun 10, 2021 · 7 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Feedback Waiting on the submitter for answers

Comments

@aloboa
Copy link

aloboa commented Jun 10, 2021

As soon as I do not use EPSG:4326, I get:

No transform is available between UTM Zone 31, Northern Hemisphere and EPSG:25831 - ETRS89 / UTM zone 31N.
proj_create_operations: cannot build geodeticCRS 4326: SQLite error on SELECT name, ellipsoid_auth_name, ellipsoid_code, prime_meridian_auth_name, prime_meridian_code, area_of_use_auth_name, area_of_use_code, publication_date, deprecated FROM geodetic_datum WHERE auth_name = ? AND code = ?: no such column: publication_date

qgis info: https://www.dropbox.com/s/8g03klgzr2bj069/Screenshot%20from%202021-06-10%2018-35-35.png?dl=0

@aloboa aloboa added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Jun 10, 2021
@gioman gioman added the Feedback Waiting on the submitter for answers label Jun 10, 2021
@gioman
Copy link
Contributor

gioman commented Jun 10, 2021

@aloboa unclear what this issue is about and how to replicate, would you mind adding all the requested info?

https://github.com/qgis/QGIS/issues/new?assignees=&labels=Bug&template=10_bug_report.md&title=

Describe the bug

How to Reproduce

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error -->

QGIS and OS versions

Additional context

Also add a sample project+data if possible.

@aloboa
Copy link
Author

aloboa commented Jun 10, 2021

Describe the bug
As soon as I do not use EPSG:4326, I get:

No transform is available between UTM Zone 31, Northern Hemisphere and EPSG:25831 - ETRS89 / UTM zone 31N.
proj_create_operations: cannot build geodeticCRS 4326: SQLite error on SELECT name, ellipsoid_auth_name, ellipsoid_code, prime_meridian_auth_name, prime_meridian_code, area_of_use_auth_name, area_of_use_code, publication_date, deprecated FROM geodetic_datum WHERE auth_name = ? AND code = ?: no such column: publication_date

How to Reproduce

  1. Start qgis with epsg:4326 as default.
  2. Add any layer in any other CRS, eg, add OpenStreetMap
  3. Error "No transform available between EPSG:3857 and Custom CRS" appears in red at the top of the map. Click Details and get
No transform is available between EPSG:3857 - WGS 84 / Pseudo-Mercator and Custom CRS: GEOGCRS["unknown",DATUM["unknown",ELLIPSOID["WGS 8….
proj_create_operations: cannot build projectedCRS 3857: cannot build geodeticCRS 4326: SQLite error on SELECT name, ellipsoid_auth_name, ellipsoid_code, prime_meridian_auth_name, prime_meridian_code, area_of_use_auth_name, area_of_use_code, publication_date, deprecated FROM geodetic_datum WHERE auth_name = ? AND code = ?: no such column: publication_date

https://www.dropbox.com/s/rbjugiegews14tg/Screenshot%20from%202021-06-10%2021-28-29.png?dl=0

QGIS 3.8.13
OS Pop!_OS 20.10 (based on Ububtu 20.10)

Additional context:
https://www.dropbox.com/s/8g03klgzr2bj069/Screenshot%20from%202021-06-10%2018-35-35.png?dl=0

@aloboa
Copy link
Author

aloboa commented Jun 11, 2021

This problem seems to be related to a proj version problem that I also experience with R:
rspatial/terra#248

In that link, a conflict between proj 7.2 and proj 7.1 is suggested. Nevertheless, in my case I only have proj 7.1

Instead, the conflict is caused by the OTB installation, which has its own proj
/home/alobo/OTB/OTB-7.3.0-Linux64/bin/proj
I realised this fact thanks to rgdal, which reports:
Path to PROJ shared files: /home/alobo/OTB/OTB-7.3.0-Linux64/share/proj

If I remove the OTB installation and restart, the problems are solved both in QGIS and in R, and I can successfully
install terra, and sf.
The rgdal installation, which always worked, reports another proj path:
Path to PROJ shared files: /home/alobo/.local/share/proj:/usr/share/proj

Unfortunately, If I install OTB even after having installed the R packages, I go back to problems in QGIS
and rgdal reports the OTB path again.

As I do need OTB, is there a way to specify which proj path should be used by QGIS?

@gioman
Copy link
Contributor

gioman commented Jun 11, 2021

As I do need OTB, is there a way to specify which proj path should be used by QGIS?

@aloboa ask in the developers mailing list, thanks! (but I guess as you are on linux you could compile QGIS code, specifying the paths to the libraries versions you need).

@aloboa
Copy link
Author

aloboa commented Jun 11, 2021

@gioman I am not a QGIS dev and not subscribed to that list. Could you just post this link?
Also, I doubt this is really a concern for developers, it is rather an installation issue.
Thanks

@gioman
Copy link
Contributor

gioman commented Jun 11, 2021

Also, I doubt this is really a concern for developers, it is rather an installation issue.

@aloboa if I understand correctly the issue is caused by OTB (that do not breaks only QGIS but also R), so I guess the ticket should be raised in OTB tracker. My suggestion was to write in the dev list to ask about how to compile choosing a specific path for a specific library, but probably is at the ccmake stage, see https://github.com/qgis/QGIS/blob/master/INSTALL.md#37-starting-the-compile

@aloboa
Copy link
Author

aloboa commented Jun 11, 2021

Seems that these issues have been solved by including both paths in otbenv.profile:
PROJ_LIB=/home/alobo/.local/share/proj:/usr/share/proj:/home/alobo/OTB/OTB-7.3.0-Linux64/share/proj
I will report back in case of further problems

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! Feedback Waiting on the submitter for answers
Projects
None yet
Development

No branches or pull requests

2 participants