FSDS - Configure geometry encoding in attribute descriptors instead of globally
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
The issue body names no files, tests, or entry points. Start by locating the FSDS geometry-encoding configuration and attribute-descriptor code, then determine how the current global setting is applied. Done means geometry encoding is configured through attribute descriptors rather than a global setting, with relevant tests updated.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
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 locationtech/geomesa
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
locationtech/geomesa#10761 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
locationtech/geomesa#10324 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
locationtech/geomesa#10111 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
locationtech/geomesa#10052 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
locationtech/geomesa#9998 ·
All issues in locationtech/geomesa
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
requires-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/datafusion-comet#6060 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
lichess-org/lila#21756 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
salesforce/evalon#10 ·