reverse api for nominatim not working

[ghost]

by default -4 is going in api call for reverse.

in code why log is used to calculate scale

[pablocabto]

Any updates on this? According to the Nominatin API, 18 must be set in the zoom parameter to get building-level accuracy. However, the code uses a logarithmic operation and 18 becomes -4 in the actual request.

[simon04]

Please see the demo for the intended use of zoom/scale:

leaflet-control-geocoder/demo/index.html

Lines 62 to 79 in 0ace940

	map.on('click', function(e) {
	geocoder.reverse(e.latlng, map.options.crs.scale(map.getZoom()), function(results) {
	var r = results[0];
	if (r) {
	if (marker) {
	marker
	.setLatLng(r.center)
	.setPopupContent(r.html || r.name)
	.openPopup();
	} else {
	marker = L.marker(r.center)
	.bindPopup(r.name)
	.addTo(map)
	.openPopup();
	}
	}
	});
	});

This behaviour has been around forever, more specifically since 2014, 9a0e966.

[ciuliene]

This issue could be easily solved by setting the scale parameter as optional. Something like this:

reverse(location: L.LatLngLiteral, scale: number, cb: GeocodingCallback, context?: any) {
    const params = reverseParams(this.options, {
      lat: location.lat,
      lon: location.lng,
      zoom: scale < 0 ? undefined : Math.round(Math.log(scale / 256) / Math.log(2)),
      addressdetails: 1,
      format: 'json'
    });

See this