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

[Bug]: Address search returns shifted results #4751

Open
1 task done
RobiFag opened this issue Sep 16, 2024 · 6 comments
Open
1 task done

[Bug]: Address search returns shifted results #4751

RobiFag opened this issue Sep 16, 2024 · 6 comments

Comments

@RobiFag
Copy link
Contributor

RobiFag commented Sep 16, 2024

What is the bug? (in English)

I have a QGIS project with reference system EPSG:3003, using nominatim the address search returns shifted results. Changing the project reference system (we tried several EPSG 4326, 3857, 32632, 25832, 7791, ecc.) it works correctly.

Maybe something related to this issue #1624 ?

image

Steps to reproduce the issue

  1. Create a project with reference system EPSG:3003
  2. add some data
  3. activate the address search bar with nominatim from lizmap plugin
  4. search for an address using the web tool

Versions, safeguards, check summary etc

Versions :

  • Lizmap Web Client : 3.7.9
  • Lizmap plugin : 4.3.15
  • QGIS Desktop : 3.34.4
  • QGIS Server : 3.34.10
  • Py-QGIS-Server : not used
  • QGIS Server plugin atlasprint : 3.4.1
  • QGIS Server plugin lizmap_server : 2.9.4
  • QGIS Server plugin wfsOutputExtension : 1.8.0
List of safeguards :
  • Mode : normal
  • Allow parent folder : no
  • Prevent other drive : yes
  • Prevent PG service : no
  • Prevent PG Auth DB : yes
  • Force PG user&pass : yes
  • Prevent ECW : yes

Check Lizmap plugin

  • I have done the step just before in the Lizmap QGIS desktop plugin before opening this ticket. Otherwise, my ticket is not considered valid and might get closed.

Operating system

Ubuntu 20.04.6 LTS

Browsers

Firefox, Chrome, Microsoft Edge

Browsers version

Firefox Versione 130.0, Chrome Versione 128.0.6613.138, Microsoft Edge Versione 128.0.2739.79

Relevant log output

No response

@RobiFag RobiFag added the bug label Sep 16, 2024
@Gustry
Copy link
Member

Gustry commented Sep 16, 2024

Any chance you can try LWC 3.8.1 pre package ? Does it happen only with EPSG:3003 ?

BTW, your plugin is old, you should upgrade it.

@RobiFag
Copy link
Contributor Author

RobiFag commented Sep 16, 2024

I have just updated the lizmap plugin but nothing changed. At the moment EPSG:3003 and EPSG:3004 are the only ones we have encountered the problem with.

Regarding testing LWC 3.8.1, we need some time but I think we can make some tests.

@Gustry
Copy link
Member

Gustry commented Sep 16, 2024

I have just updated the lizmap plugin but nothing changed.

Yes, it wasn't related in this case, but always good to upgrade ;-)

@RobiFag
Copy link
Contributor Author

RobiFag commented Sep 18, 2024

Hi, I have already tested LWC 3.8.0 and the issue is still there, moreover the small yellow dot does not appear after searching.

Versions :

  • Lizmap Web Client : 3.8.0
  • Lizmap plugin : 4.3.24
  • QGIS Desktop : 3.34.4
  • QGIS Server : 3.34.9
  • Py-QGIS-Server : not used
  • QGIS Server plugin atlasprint : 3.4.1
  • QGIS Server plugin lizmap_server : 2.10.1
  • QGIS Server plugin wfsOutputExtension : 1.8.2
List of safeguards :
  • Mode : normal
  • Allow parent folder : no
  • Prevent other drive : yes
  • Prevent PG service : no
  • Prevent PG Auth DB : yes
  • Force PG user&pass : yes
  • Prevent ECW : yes

Copy link

This issue is missing some feedbacks. 👻
Please have a look to the discussion, thanks. 🦎

@github-actions github-actions bot added the stale This ticket might be closed soon label Oct 21, 2024
@Gustry
Copy link
Member

Gustry commented Oct 22, 2024

Yes, it looks linked to #1624

@3liz-bot 3liz-bot removed the stale This ticket might be closed soon label Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants