Enhancement request: Plots per row instead of per table or query
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- data-visualization
Research direction
Start by reading the linked datasette-enrichments-gmap-elevation implementation and the datasette-plot behavior it works around. Trace how plot data is currently accepted and rendered per table or query, then define the completed behavior as one chart being generated for each row from array or JSON data.
Written by the indexing model from the issue text.
Description
This came up while developing datasette-enrichments-gmap-elevation.
The enrichment enables the user to specify the latitude and longitude for two points (returned from a table) and returns the elevation profile between those points. The user can also specify the distance along the path between the two points that the elevation profile should cover and the number of points of elevation data the Google Maps API should return. It's currently used to look at the terrain around a ham radio station to determine how much the terrain affects the radio wave launch angle from the antenna. (Slope of the terrain is subtracted from the free-space launch angle of the antenna to give the actual launch angle. A lower launch angle equals a skip off the ionosphere further out and therefore high frequency radio contacts to locations further away.) People might also use the enrichment to visualize the hill they hiked down on their latest outing.
Ultimately, the enrichment returned rows that looked like:
Where each row contains a pair of points and each row contains a chart that profiles the elevation from the starting point on the left towards the endpoint of the path on the right, (restricted to the distance along the path the user requested.
If datasette-plot had a per row option that accepted either an array or json data, it would have saved the implementation here.
- Dominant language
- TypeScript
- Stars
- 28
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 datasette/datasette-plot
-
Installation errorOpen
Difficulty 3/5 1-2 days Newbie friendliness 35/100
datasette/datasette-plot#8 · 2 reactions ·
-
JS ErrorOpen
Difficulty 3/5 1-2 days Newbie friendliness 35/100
datasette/datasette-plot#7 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
datasette/datasette-plot#3 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
datasette/datasette-plot#2 · 3 comments ·
All issues in datasette/datasette-plot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rohitg00/agentmemory#1428 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
boxlite-ai/boxlite#1729 ·
Maintainers usually reply within 1 day
-
detectors enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
SM260845/readme-gen#1 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
angular/angularfire#3774 ·
Maintainers usually reply within 2 days