-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Search Refactor #995
Search Refactor #995
Conversation
Seems like maybe the f-string usage in the geojson fields assertion check is causing the build failure. Testing normal string concatenation.
Reverted accidental vega_parse change.
Fixed docstring indentation.
Updating Tooltip docstring broke 120 char line limit.
Removed trailing white space.
Updating my fork to current Master.
…iLang.xml, ide.general.xml, Default.xml, project.default.xml, diff.xml, git.xml, other.xml, jdk.table.xml, Default.xml, code.style.schemes, find.xml, ui.lnf.xml, laf.xml, filetypes.xml, projectView.xml, vcs.xml, editor.codeinsight.xml, notifications.xml, keymap.xml, editor.xml, github_settings.xml, debugger.xml
…, IntelliLang.xml, ide.general.xml, Default.xml, project.default.xml, diff.xml, git.xml, other.xml, jdk.table.xml, Default.xml, code.style.schemes, find.xml, ui.lnf.xml, laf.xml, filetypes.xml, projectView.xml, vcs.xml, editor.codeinsight.xml, notifications.xml, keymap.xml, editor.xml, github_settings.xml, debugger.xml" This reverts commit 76c9622.
…ithub.com/jtbaker/folium to local" This reverts commit 84811a0.
Conflicts: vcs.xml
…, filetypes.xml, git.xml, keymap.xml, github_settings.xml, Default.xml, debugger.xml
Updated code for line length limitation, verbiage, and indentations.
exempt this line from the linter so we can traverse the data structure directly.
Hmm I seem to be missing some comments? Also the other notebook is back. And I thought you deleted the The plugin-Search notebook is still not working: Given the error message it seems there's an empty cell that's messing it up. |
@Conengmo sorry for the late response on this. My The notebook issue does seem to be for an empty cell. I'll see if I can get these issues updated and fixed. Thanks for your patience! |
@Conengmo do you think adding a |
Ok, I think I've got the issues addressed. Working notebook demo at nbviewer. Adds some functionality for usage on |
wow @jtbaker , this is huge in terms of impact. Thank you so much |
Let's do it separately. This PR is finished I think! |
Good work @jtbaker! |
@davidolmo no problem, it's fun to work on these and try to develop something that will be really straightforward and easy for a lot of people to develop these maps! to me, the real amazing work is the people writing the leaflet plugins and working in the DOM. we just have to figure out how to translate our python logic and data structures over to use them in the leaflet/plugin code. I'm glad you dig it! 😀 |
Hello, thank you for your work on the search plugin |
@rickantonais v0.8.0 was just released, including this PR: |
Thank you very much! It seems the conda install automatically install the 0.7.0 version though |
There is usually a little lag on when it hits the distribution channels I believe. If you have git on your machine you can install directly from the source here like this (make sure your conda environment is activated):
|
It works perfectly now thank you very much ! |
I reworked the Search plugin to reference a
folium.features.GeoJson
object via the .add_child()/.add_to() methods to combine these functionalities. Madesearch_zoom
optional, and added **kwargs to allow a variety of SVG style options on a match, likehighlight_function
in GeoJson.I think that this would have been cleaner to have an
object
keyword argument that we could pass afolium.features.GeoJson
object like this:But when I set up the logic that way, it inserted the Search object further up the
<script>
tag than the GeoJson - so when Search invoked the" {{ geo.get_name() }} "
method in the template when adding to the map, it didn't yet have a defined variable name to reference. Not sure if there is a way to get around this.With the
.add_child()
method, we're constrained to getting to the LeafletL.map()
object through the_parent
properties. We have to do this traversal twice withSearch
, sinceSearch
is a child offolium.GeoJson
, andfolium.GeoJson
is a child offolium.Map()
. I don't know if there are any edge cases such as FeatureGroups and SubGroups that further subclassGeoJson
fromMap
, and if they should try to account for those.Here's a sandbox I was working with for a Dataset I was already working on a tooltip issue for. I'll get a better example set up and committed after I've gotten some feedback on the design approach.
https://nbviewer.jupyter.org/gist/jtbaker/b347705fce2741eb5405874004a25079