locationtech / locationtech/geomesa
Remove global axis order hint from MetadataBackedDataStore
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Remove global axis order hint from MetadataBackedDataStore
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2360
Key: GEOMESA-2360
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Assignee: James Hughes
Reporter: James Hughes
Created: Thu, 2 Aug 2018 18:22:06 -0400
Updated: Fri, 28 Dec 2018 11:03:32 -0500
Affects Version(s): 2.1.0
Comments:
557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Wed, 8 Aug 2018 09:40:52 -0400):
We probably need to verify how the hint is interacting with the geometry factories we use during serialization. We have the CRS_EPSG_4326 constant which is now set to longitude first on creation, but we don't actually use that in most places.
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 MetadataBackedDataStore and tracing how its global axis order hint is applied during serialization. Check how CRS_EPSG_4326 is created and compare the geometry factories used in serialization. Done means removing the global hint without breaking the intended longitude-first CRS behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100