Bug report #18518

QGIS Server 3 GetFeatureInfo doesn't resolve value relations anymore

Added by Tudor Bărăscu about 6 years ago. Updated almost 6 years ago.

Status:Closed
Priority:Normal
Assignee:Alessandro Pasotti
Category:QGIS Server
Affected QGIS version:3.1(master) Regression?:Yes
Operating System:Debian Buster Easy fix?:No
Pull Request or Patch supplied:Yes Resolution:
Crashes QGIS or corrupts data:No Copied to github as #:26406

Description

QGIS Server should should return the "solved" values when doing GetFeatureInfo on value relation and not the id's/keys.

Associated revisions

Revision eb0be331
Added by Alessandro Pasotti almost 6 years ago

[bugfix][server] Respect relations in getfeatureinfo

Fixes #18518

QGIS Server 3 GetFeatureInfo doesn't resolve value relations anymore

History

#1 Updated by Kim Frankcombe about 6 years ago

Tudor, I thought the same thing but found it off the side of my screen. Are you sure you are not seeing the same issue with the Identify Results window opening with the Features column maximised and the Value off screen, right? Try dragging the Results window left and see if the values appear.

#2 Updated by Tudor Bărăscu about 6 years ago

I'mo doing the request manually from terminal, so there's no client issue here. On a QGIS 2.18 server it works as it should.

I actually don't understand what are you suggesting to do.

E.g. For an integer column, let's say we have the column value 3 that when mapped to a table using value relation has the value "Functional". In GetFeatureInfo I get 3 instead of "Functional" --> I get the key and not the value.
I am not saying that I don't get any Return Value in order to search it in the side of the screen like you're suggesting, I'm saying that I don't get the expected output.

Thanks for the info!

#3 Updated by Alessandro Pasotti almost 6 years ago

  • Assignee set to Alessandro Pasotti

#4 Updated by Alessandro Pasotti almost 6 years ago

  • Status changed from Open to In Progress
  • Pull Request or Patch supplied changed from No to Yes

#5 Updated by Anonymous almost 6 years ago

  • % Done changed from 0 to 100
  • Status changed from In Progress to Closed

Also available in: Atom PDF