mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-13 15:51:00 +00:00
Maurice
51af575c9a
A right-click, click or drag on a repeated world copy reported the longitude it has on that copy (274.9 for -85.1). The place was saved there, the geocoder found nothing, and a route to a place on the real world ran across the whole map (#2976). Longitudes are now brought back onto [-180, 180] where the map hands them out (Leaflet and GL), where they are stored (places, booking endpoints, collection places, so REST, MCP, plugin RPC and importers alike) and before reverse geocoding. A migration moves the ones already stored. Leaflet draws a layer at its literal longitude only, so a trip from Los Angeles to Auckland had its pins at opposite ends of the world while the flight ran off the edge to the next copy (#2975). A trip that crosses the antimeridian is now drawn in one longitude frame, seamed in the widest stretch it leaves empty, so pins, routes, flights and every overlay lie on one copy and the map opens across the Pacific. Every other trip has no frame and draws exactly as before. The GL day fit also takes the short way. A new install now starts with Journey and Collections switched on, next to the trip addons (all but Road trip), Atlas, Vacay and the Naver import that already were. Existing installs keep their addons as they are. Closes #2975 Closes #2976
43 lines
1.5 KiB
TypeScript
43 lines
1.5 KiB
TypeScript
import { Polyline } from 'react-leaflet';
|
|
import { onRealWorld } from '../../utils/worldCopy';
|
|
|
|
/**
|
|
* P2A-03: an invisible band along a route segment on the Leaflet map, wider
|
|
* than the drawn line, that takes the click which reshapes the route, as the
|
|
* GL renderer's hit layer does: an 8 px line is too thin to aim at.
|
|
*/
|
|
export function RouteHitBand({
|
|
positions,
|
|
onRouteClick,
|
|
}: {
|
|
positions: [number, number][];
|
|
onRouteClick: (lat: number, lng: number) => void;
|
|
}) {
|
|
return (
|
|
<Polyline
|
|
positions={positions}
|
|
// Leaflet hands a path's click to the map as well unless the path says not to;
|
|
// stopping the DOM event does not reach that, and the map's click would add a
|
|
// point at the end of the tour under the shaping point (as TrackLines does).
|
|
bubblingMouseEvents={false}
|
|
pathOptions={{
|
|
color: 'transparent',
|
|
weight: 20,
|
|
opacity: 0,
|
|
lineCap: 'round',
|
|
lineJoin: 'round',
|
|
className: 'cursor-copy',
|
|
}}
|
|
eventHandlers={{
|
|
click: (e: { latlng: { lat: number; lng: number }; originalEvent: MouseEvent }) => {
|
|
// Stops the map's own click, which would otherwise open the add-place menu underneath the new via.
|
|
e.originalEvent.stopPropagation();
|
|
// The via is saved on the real world, whichever copy of it the route was clicked on (#2976).
|
|
const at = onRealWorld(e.latlng);
|
|
onRouteClick(at.lat, at.lng);
|
|
},
|
|
}}
|
|
/>
|
|
);
|
|
}
|