Search - Map aggregate functionality (R3)
Redesign for generic case rather than putting in code
Status
-
Proposed -
Trialing -
Under review -
Approved -
Retired
Context & Scope
- Displays wells on map to ensure return result is as soon as possible; restricts # of fields and wells. Allows returning wells based on searches of child data.
- If query is geographic boundary and otherwise minimal, return all wells within that boundary: three fields (well name, unique id, …?)
- This functionality is a popular request, but implemented as special case in the data platform; not clear whether it can be generalized - Alan
Decision
Rationale
Supports ISVs required functionality in a way that's not over-fitted for INT and SSIO
Consequences
When to revisit
Tradeoff Analysis - Input to decision
Alternatives and implications
- Retain R2 injection of Elastic spatial filter
- Redesign for generic case rather than putting in code