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

Markers on map are not placed at the right place #6599

Closed
lndrtrbn opened this issue Apr 5, 2024 · 1 comment · Fixed by #6639
Closed

Markers on map are not placed at the right place #6599

lndrtrbn opened this issue Apr 5, 2024 · 1 comment · Fixed by #6639
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@lndrtrbn
Copy link
Member

lndrtrbn commented Apr 5, 2024

Description

In the cartographic map we have markers for some entities, for examples cities.
Depending of the zoom level, the markers are not placed at the corresponding latitude longitude.

image

image

And the more you zoom out the worst it is.

Environment

  1. OS (where OpenCTI server runs): Edge
  2. OpenCTI version: 6.0
  3. OpenCTI client: frontend
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create a city with lat lng (Example: Chantepie 48.08885, -1.61524)
  2. Zoom in and out on the map

Expected Output

Marker always placed where it should be

Actual Output

Wrong place when zooming out

@lndrtrbn lndrtrbn added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Apr 5, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.10 milestone Apr 6, 2024
@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Apr 8, 2024
@nino-filigran
Copy link

Reproduced on demo

@SamuelHassine SamuelHassine modified the milestones: Release 6.0.10, Release 6.1.0 Apr 8, 2024
@frapuks frapuks self-assigned this Apr 10, 2024
@frapuks frapuks linked a pull request Apr 10, 2024 that will close this issue
5 tasks
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants