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

Dashboard - GetFeatureInfo map issue #1759

Open
mbeneventi opened this issue May 15, 2024 · 2 comments
Open

Dashboard - GetFeatureInfo map issue #1759

mbeneventi opened this issue May 15, 2024 · 2 comments
Assignees
Labels

Comments

@mbeneventi
Copy link

mbeneventi commented May 15, 2024

##Expected Behavior
if the layer's getFeatureInfo has been disabled from geoserver (publishing --> Layer Settings --> Queryable) GeoNode does not allow query management.

Actual Behavior

the getFeatureInfo of the datasets does not seem to work properly in a dashboard that contain a map with layer for which the 'getFeatureInfo parameter' has been disabled on geoserver

Steps to Reproduce the Problem

  1. add a maps in a dashboard with almost a dataset configurated 'not queryable' in geoserver publishing section

Specifications

  • GeoNode version: 4.2.3
  • Installation type (geonode-project):
  • Installation method (docker):
  • Platform: ubuntu 22.04

allegato2 (1)

@giohappy
Copy link

giohappy commented May 15, 2024

@mbeneventi I will report here what have been already shared with you via other channels.

We have two problems here:

  1. There seems to be a bug in MapStore, where an error response from the GFI request for a layer breaks the visualization of other positive responses for other layers. The popup windows with the results is empty and keep spinning. An issue for this problem will be created for MapStore
  2. GeoNode doesn't manage the "queryable" information for layers, and it doesn't implement a way to inform the client about it. This is the limitation, I know, but it shouldn't affect the querying of other layers. When the query to the non-queryable layer fails the client just ignores it (as it happens in maps). The problem becomes visible in dashboards because of point 1.

This must be tested in the master version of GeoNode, since MapStore version has received a big upgrade that could already have fixed this.

I will move this issue to the client's repo, since the real bug (point 1) is related to the client and not the backend.

@giohappy giohappy transferred this issue from GeoNode/geonode May 15, 2024
@giohappy giohappy self-assigned this May 15, 2024
@giohappy
Copy link

I could reproduce the problem also with the master branch of GeoNode, which uses the latest released version of MS (2024.01.00).
The upstream issue has been created geosolutions-it/MapStore2#10326

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants