Hallo! I wanted to thank you for this plugin, which is really useful. Also, I wanted to say that due to the fact that I am not a native English speaker, and that I don't have much technical knowledge, this request was written by an AI. I am sorry if any part of it doesn't sound appropriate.
I'm using Map View v6.1.4 on Obsidian to trace a multi-stop itinerary that crosses the antimeridian. My route goes eastward: Madrid → New York → Tokyo.
The first segment (Madrid → New York) is drawn correctly, heading east across the Atlantic. However, the second segment (New York → Tokyo) does not continue eastward across the Pacific. Instead, the polyline reverses direction and heads west, crossing Europe and Asia to reach Tokyo — effectively wrapping the wrong way around the globe.
This suggests that Map View does not handle the antimeridian crossing for polylines. When two consecutive points have longitudes that differ by more than 180° (e.g., New York at -74° and Tokyo at +139°), the plugin appears to draw the shortest line in longitude space — going west from -74° to +139° — rather than continuing eastward across the Pacific.
Steps to reproduce:
- Create notes with geolocations for at least three points spanning the antimeridian, e.g.: Madrid (40.4168, -3.7038) → New York (40.7128, -74.0060) → Tokyo (35.6762, 139.6503).
- Connect them with a path/route in Map View.
- Observe that the New York → Tokyo segment is drawn westward across Europe instead of eastward across the Pacific.
Expected behaviour: The polyline should continue eastward from New York across the Pacific to Tokyo, respecting the intended itinerary order.
Actual behaviour: The polyline wraps westward, crossing back through Europe, which does not represent the real travel route.
Additional notes:
- I tried adding intermediate waypoints in the Pacific (e.g., longitude -170° and +170°), but the route still wraps incorrectly.
- I tried changing the map's initial center coordinates to the Pacific; the issue persists.
- I checked the display rule's
pathOptions, but there is no exposed setting (such as noClip, wrapLng, or an antimeridian toggle) that would allow the user to control this behaviour.
It would be very helpful if Map View could either:
- Automatically detect antimeridian crossings and split polylines accordingly, or
- Expose a user-facing setting (e.g., "Wrap world" / "Allow antimeridian crossing") in the path display rules or plugin settings.
Thank you for your work!
Hallo! I wanted to thank you for this plugin, which is really useful. Also, I wanted to say that due to the fact that I am not a native English speaker, and that I don't have much technical knowledge, this request was written by an AI. I am sorry if any part of it doesn't sound appropriate.
I'm using Map View v6.1.4 on Obsidian to trace a multi-stop itinerary that crosses the antimeridian. My route goes eastward: Madrid → New York → Tokyo.
The first segment (Madrid → New York) is drawn correctly, heading east across the Atlantic. However, the second segment (New York → Tokyo) does not continue eastward across the Pacific. Instead, the polyline reverses direction and heads west, crossing Europe and Asia to reach Tokyo — effectively wrapping the wrong way around the globe.
This suggests that Map View does not handle the antimeridian crossing for polylines. When two consecutive points have longitudes that differ by more than 180° (e.g., New York at -74° and Tokyo at +139°), the plugin appears to draw the shortest line in longitude space — going west from -74° to +139° — rather than continuing eastward across the Pacific.
Steps to reproduce:
Expected behaviour: The polyline should continue eastward from New York across the Pacific to Tokyo, respecting the intended itinerary order.
Actual behaviour: The polyline wraps westward, crossing back through Europe, which does not represent the real travel route.
Additional notes:
pathOptions, but there is no exposed setting (such asnoClip,wrapLng, or an antimeridian toggle) that would allow the user to control this behaviour.It would be very helpful if Map View could either:
Thank you for your work!