Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion: Additional providers #11

Open
rbrundritt opened this issue Sep 21, 2021 · 2 comments
Open

Discussion: Additional providers #11

rbrundritt opened this issue Sep 21, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@rbrundritt
Copy link

Is there any concerns with adding support for additional geocoding providers? Default would stay as it is, but we could wrap other services and give users an option to specify which provider/service they want to use, and the associated credentials to access that service.

A couple of examples:

https://github.com/smeijer/leaflet-geosearch
https://github.com/perliedman/leaflet-control-geocoder

@thaddmt
Copy link
Collaborator

thaddmt commented Oct 12, 2021

There shouldn't be any concerns and is something we're planning to add going forward. For example with AWS Amplify we added some external geocoder providers using amazon location service - https://github.com/aws-amplify/maplibre-gl-js-amplify/blob/main/src/AmplifyMapLibreGeocoder.ts#L6

@HarelM
Copy link
Collaborator

HarelM commented Aug 26, 2024

This can be done either with docs or exporting utility method to configure the relevant geocoder.
Feel free to submit a PR.
This library is now up to date with latest technologies.

@HarelM HarelM added the enhancement New feature or request label Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants