#204 , diagnostic logging on the local-nDSM path
The previous code fell through silently to the public-provider chain at every failure mode of the local provider. The user only saw a missing LiDAR overlay with zero console hint about why. Three new one-shot console.warn entries make the failure visible:
- fetch threw: logs URL + underlying error (CORS / 404 / TLS visible instantly)
- fetch returned no band: logs URL + hint that the file must be reachable from the browser and serve a Float32 GeoTIFF / COG
- bbox does not cover home: logs the home lat/lon + the bbox numbers + a hint about the most common cause , a lat/lon swap in the four
lidar-local-ndsm-{min,max}-{lat,lon}keys
No behavioural change, the provider chain still falls back the same way it did before, only the user now has a diagnostic trail when the local file fails to load. Refs #204.