Feature type or srid for ... could not be determined or was not requested.

[qgib]

Author Name: Sandro Santilli (@strk)
Original Redmine Issue: 7889
Affected QGIS version: master
Redmine category:data_provider/postgis

---

I can't load PostGIS columns of type "geometry" because QGIS mandates to specify a SRID, and if I fake one it complains about "could not be determined or was not requested". A column of type "geometry" has a SRID of 0. This is being a problem with 83445af

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Sandro is this a regression since 1.8 or previous master revisions?

---

• status_id was changed from Open to Feedback

[qgib]

Author Name: Sandro Santilli (@strk)

---

I'm not building very often (scared by instability), but it's likely not older than one month, as a regression.

PS: I can only see Feedback and Closed as ticket statuses

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Sandro Santilli wrote:

I'm not building very often (scared by instability), but it's likely not older than one month, as a regression.

but still a regression, right? if not please lower the priority.

PS: I can only see Feedback and Closed as ticket statuses

Let me see if I can do something in redmine administration.

---

• priority_id was changed from Normal to Severe/Regression
• fixed_version_id was configured as Version 2.0.0

[qgib]

Author Name: Sandro Santilli (@strk)

---

Still happening. Seems to only happen with tables with geometries having a SRID=0 (ie: unkown srid).
Is this a documented new requirement ?

[qgib]

Author Name: Sandro Santilli (@strk)

---

And yes, it is a regression. I used to be able to use geometries with NO srid just fine. I didn't even have to manually enter one (but this is a separate topic, maybe)

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Sandro Santilli wrote:

And yes, it is a regression. I used to be able to use geometries with NO srid just fine. I didn't even have to manually enter one (but this is a separate topic, maybe)

fixed by f990886?

[qgib]

Author Name: Sandro Santilli (@strk)

---

"almost". The error message isn't shown anymore now, BUT I just cannot select the table with SRID=0.
Here's a screenshot: http://strk.keybit.net/tmp/cannot_select_geom.png
Clicking on the line the cursor is on (identified has containing Point with SRID 0) does not highlight it, so you can't click on "Add"

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Sandro Santilli wrote:

"almost". The error message isn't shown anymore now, BUT I just cannot select the table with SRID=0.
Here's a screenshot: http://strk.keybit.net/tmp/cannot_select_geom.png
Clicking on the line the cursor is on (identified has containing Point with SRID 0) does not highlight it, so you can't click on "Add"

better add this comment also in the commit page

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

Fixed in changeset "925d3179e17bf3e4516ac2037a0ee7d10fc16b66".

---

• status_id was changed from Feedback to Closed

[qgib]

Author Name: Sandro Santilli (@strk)

---

Thanks a lot, fix confirmed !

[qgib]

Author Name: Sandro Santilli (@strk)

---

Hey Jef, I tested with postgis 1.5 and it still fails there. SRID=-1 is the unknown in there. If -1 has special meaning in qgis (does it?) it'd be better to convert it to 0 when it comes from the database

---

• status_id was changed from Closed to Reopened

[qgib]

Author Name: Sandro Santilli (@strk)

---

THe recommended way is to convert any SRID < 0 coming from the database to 0. This si what PostGIS 2.0 does when data gets in the db (either from old dumps or old applications)

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

Fixed in changeset "10a91b7fb964b1a36ca0693187e165713c4b3127".

---

• status_id was changed from Reopened to Closed

[qgib]

Author Name: Sandro Santilli (@strk)

---

Works for me with both 1.5 and 2.0 -- thanks again !