locationtech / locationtech/geomesa
Improve distribution and documentation of Leaflet support
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Improve distribution and documentation of Leaflet support
- Rename geomesa-jupyter-* to geomesa-notebook-*, since they can be used in both Jupyter and Zeppelin
- Figure out best practice to distribute/obtain JS and shapefiles needed to run Leaflet module
- Write up docs for using Leaflet in Jupyter and Zeppelin
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-1760
Key: GEOMESA-1760
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Assignee: Matt Zimmerman
Reporter: Matt Zimmerman
Created: Wed, 5 Apr 2017 11:14:24 -0400
Updated: Wed, 16 May 2018 16:25:20 -0400
Parent: GEOMESA-1562
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.
Research direction
Start by locating the geomesa-jupyter-* modules and the Leaflet module, then review how their JavaScript and shapefiles are currently distributed. Document the supported Leaflet workflow for both Jupyter and Zeppelin, and confirm that the renamed geomesa-notebook-* modules and acquisition steps are clear in both environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, jupyter
- Domain
- data-visualization, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100