Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Geocoder plugin: support other built-in providers #1852
Geocoder plugin: support other built-in providers #1852
Changes from 2 commits
f716052
5c7d7a0
31340d3
781cfe2
9375392
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: is 11 a good default? Or would None be a better default?
And another question: should we check or correct this value when
add_marker
is False?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
11 would preserve the current behavior so existing users would not be caught by surprise. The real gotcha would be the case when
add_marker
=True (when default handler in leaflet-control-geocoder will be usingfit_bounds
with no regard to current map zoom). What may not be obvious to normal folium users (with no knowledge of JS) is that both the default event handler formarkgeocode
as well as the one defined in_template
would be triggered.Not sure if there is a need to correct (beyond keeping the current default of 11). Can you explain more?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's good then. It was more a question for you. We can keep it like it is now then.