fix: preserve exact coordinates entered in waypoint input fields

[DennisOSRM]

Problem

When a user types raw GPS coordinates (e.g. 34.129382,-118.141254) into a waypoint input field, Nominatim forward-geocodes the string and snaps the result to the nearest named address — sometimes more than a block away from the entered point.

Entering the same coordinates directly in the URL (?loc=34.129382,-118.141254) works correctly because that path bypasses geocoding.

Root Cause

LRM's autocomplete fires a suggest call as the user types. The suggest results (from Nominatim forward-geocode) appear in a dropdown and get auto-selected. When Enter is pressed, LRM uses that pre-selected suggest result — with Nominatim's snapped center — instead of the exact coordinates.

Fix

Introduces a coordinate-preserving geocoder wrapper (geocoder.coordPreserving()) that detects coordinate strings in both the geocode and suggest paths:

• Coordinate input: Nominatim reverse-geocodes the point for a human-readable display name, but the result's center is overridden with the exact typed lat/lon.
• Address input: Nominatim forward-geocode is used as before (no change in behavior).
• The wrapper also bridges leaflet-control-geocoder's Promise-based API to the callback-based API that leaflet-routing-machine's autocomplete expects.

Files Changed

• src/geocoder.js — Added coordPreserving() factory with coordinate detection and Nominatim reverse-geocode
• src/index.js — Use coordPreserving() geocoder; restore leaflet-control-geocoder side-effect import
• bundle.js, bundle.js.map, bundle.raw.js — Rebuilt

Fixes #154

[Copilot]

Pull request overview

Adds a coordinate-preserving geocoding path for waypoint input fields so that raw lat/lon inputs keep the exact typed coordinates (while still showing a reverse-geocoded display name), aligning typed-input behavior with the existing ?loc=lat,lon URL path.

Changes:

• Introduced coordPreserving() geocoder wrapper that detects coordinate strings and reverse-geocodes for display while overriding the result center to the exact input.
• Switched the routing plan’s geocoder to createGeocoder.coordPreserving() and adjusted the leaflet-control-geocoder import to be side-effect only.
• Rebuilt distributable bundles (bundle.js, bundle.js.map, bundle.raw.js).

Reviewed changes

Copilot reviewed 2 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/geocoder.js	Adds coordinate parsing + a wrapper geocoder that preserves exact centers and bridges Promise results to LRM’s callback autocomplete API.
src/index.js	Uses the new coordinate-preserving geocoder for waypoint inputs; restores geocoder side-effect import.
bundle.js	Rebuilt compiled bundle reflecting the new geocoder behavior.
bundle.js.map	Updated sourcemap for rebuilt bundle.
bundle.raw.js	Rebuilt raw bundle including updated sources/dependencies.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

67108864 is a scale constant corresponding to zoom 18 (256 * 2^18). Adding an inline comment (or deriving it from L.CRS.EPSG3857.scale(18)) would make the intent clearer and avoid this looking like an arbitrary magic number.

Suggested change

	return nominatim.reverse(latlng, 67108864).then(function(results) {
	// Use scale corresponding to zoom level 18 (was hard-coded as 256 * 2^18 = 67108864)
	return nominatim.reverse(latlng, L.CRS.EPSG3857.scale(18)).then(function(results) {