geocoding

When a buggy house number is entered in OSM, its import creates an entry in the word table. Even when the house number is later corrected, the entry remains. That often leads to odd search errors because house numbers are optional parts of the query and can practically change the search into a partial one.

We should have a task to clean out house numbers from the word table that no longer appea

Hi,

There is a DeprecationWarning using Node.js 16 (Nuxt.js project).

 ERROR  (node:10619) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /{my-local-path}/node_modules/leaflet-geosearch/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show w

We have, for a very long time, had a little bit of logic for managing one small aspect of localization (the order of housenumber and street name in labels) in a file in pelias/api: middleware/localNamingConventions.js.

Since that file was created, we've created an entire package, [pelias/labels](https://github.com