Suggestion: add cross reference to styling geospatial data in Form Styling
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 58/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Open the Form Styling documentation and compare its coverage with the choice-properties section in Form Question Types. Add the requested Geospatial Data cross-reference and summary, then verify that the Sphinx documentation build renders the section and link correctly.
Written by the indexing model from the issue text.
Description
It would perhaps be helpful to add a section in 'Form Styling' that has a summary of the fact you can manage the colour of points and lines plus the marker symbol and include a link back to the choice-properties section?
I would suggest Geospatial Data as the heading (for consistency) e.g. https://docs.getodk.org/form-styling/#geospatialdata
REASON: I was trying to remind myself of different ways of styling data on maps in the Docs and went to Form Styling... Then I used a search 'marker-color' and the results gave me https://docs.getodk.org/form-question-types/ So I had to find in the page and found it:
https://docs.getodk.org/form-question-types/#choice-properties
So that's logical, in that I am using it in a select question, but I was coming at it from a styling perspective (perhaps illogical) so looked there...
Oh, and github doesn't let me use SeeWhy :-)
- Dominant language
- Python
- Stars
- 58
- Forks
- 161
- Avg merge
- 20h 51m
- Merged PRs (30d)
- 2
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 getodk/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Central Collect
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Make it explicit that an S3 bucket configured for use with Central must accept abitrary connectionsOpenCentral
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
area:cli area:security enhancement priority:medium size:small
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
RonaldHensbergen/composable-data-stack#1338 ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
almanac-data/climate-almanac#139 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 comment ·
Maintainers usually reply within 1 day