locationtech / locationtech/geomesa
Docs - Document use of visibilities in the converter library
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Docs - Document use of visibilities in the converter library
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2899
Key: GEOMESA-2899
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: James Hughes
Created: Tue, 18 Aug 2020 10:29:17 -0400
Updated: Fri, 16 Dec 2022 14:12:39 -0500
Affects Version(s): 3.0.0
Comments:
557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Thu, 8 Oct 2020 16:45:03 -0400):
it is mentioned already: https://github.com/locationtech/geomesa/blame/main/docs/user/convert/common.rst#L99
557058:48912df4-0004-4f90-9915-db26684ec006 (Wed, 14 Oct 2020 13:30:55 -0400):
Hmm…. I suppose I’m looking for a more concrete example. Since we are heading towards 3.1.0, I’m bumping this ticket.
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 in docs/user/convert/common.rst around the visibility discussion linked in the issue. Review what is already documented and add a concrete example of using visibilities in the converter library; the work is done when the intended usage is clear to converter users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100