Continues #5473 by fixing the rendering.

When anything is added to the map, its longitude could be as well (the original 
longitude) + n * 360. n is an integer and usually it's 0 but that 
doesn't work when looking at the map near the antimeridian. Here I'm 
picking such n for each changeset bbox that it's going to be at the closest 
location to the map view center.

![image](https://github.com/user-attachments/assets/6607ac59-e348-4ae8-a817-aebf07465639)

You can view, comment on, or merge this pull request online at:

  https://github.com/openstreetmap/openstreetmap-website/pull/5903

-- Commit Summary --

  * Support unwrapped bbox values in changeset history queries
  * Add history changesets layer module
  * Rename changesets layer constant
  * Rename map listeners on history page
  * Render changesets at locations closest to map view center

-- File Changes --

    A app/assets/javascripts/index/history-changesets-layer.js (76)
    M app/assets/javascripts/index/history.js (86)
    M app/controllers/changesets_controller.rb (32)
    M test/controllers/changesets_controller_test.rb (104)
    M test/system/history_test.rb (28)

-- Patch Links --

https://github.com/openstreetmap/openstreetmap-website/pull/5903.patch
https://github.com/openstreetmap/openstreetmap-website/pull/5903.diff

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/5903
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/pull/5...@github.com>
_______________________________________________
rails-dev mailing list
rails-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/rails-dev

Reply via email to