Blue Lines when using TimestampedGeoJson in Folium
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, python
- Domain
- data-visualization, frontend
Research direction
Start with the attached animated_train_bug.txt, save it as HTML, and inspect the generated TimestampedGeoJson code around line 118. Reproduce the blue lines in Chrome at 08:50:54 and 08:28:50, then trace the animation and styling behavior. Done means the unintended lines no longer appear and the reported hardware strain is reduced.
Written by the indexing model from the issue text.
Description
Describtion
During the animation with the TimestampedGeoJson plugin in Folium, blue lines briefly appear along the route of the objects, causing undesired strain on the hardware.
To Reproduce
You can use the txt file and safe it as HTML and open it in your browser. At the timespamps 08:50:54 and 08:28:50 you can see the blue lines.
Expected behavior
The blue lines should not appear during the animation and the hardware should not be strained.
Environment:
- Browser: chrome
- Python version: 3.10.13
- folium version: 0.15.1
Additional context
To hide the lines, I replaced the following code in the HTML file (line 118):
style: function (feature) {
return feature.properties.style;
}
with the code:
style: function (feature) {
return {
opacity: 0.0
};
}
However, this does not reduce the hardware strain.
You can find an example Folium map animated_train_bug.txt (you can safe it as html and open it with chrome) and a video illustrating the issue attached (timestamp bug: 08:50:54 and 08:28:50).
Can you help making a fix for this issue please?
Uploading animation_rando_blue_lines.mp4…
- Dominant language
- Python
- Stars
- 7.4k
- Forks
- 2.3k
- Avg merge
- 17h 22m
- Merged PRs (30d)
- 11
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python-visualization/folium
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
python-visualization/folium#2092 · 5 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 67/100
python-visualization/folium#2278 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
python-visualization/folium#2259 ·
-
Map output from OSM returns blocked tiles, due to defective request or not following referer-policy Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
python-visualization/folium#2236 · 5 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
python-visualization/folium#2219 · 2 comments ·
All issues in python-visualization/folium
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·