locationtech / locationtech/geomesa
Look into using TransformFeatureStore for relational projection handling
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Look into using TransformFeatureStore for relational projection handling
From a discussion with GeoTools/GeoServer devs, it was suggested that TransformFeatureStore/FeatureCollection is the new hotness, and that TransformProcess is the old and busted.
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2321
Key: GEOMESA-2321
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Tue, 17 Jul 2018 08:35:25 -0400
Updated: Tue, 17 Jul 2018 08:35:25 -0400
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 reviewing the GeoTools/GeoServer discussion around TransformFeatureStore, FeatureCollection, and TransformProcess, then trace how GeoMesa currently handles relational projections. Done means establishing whether TransformFeatureStore is suitable and implementing or documenting an agreed direction; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100