Search - Maps Query attribute refactoring
- Under review
Context & Scope
- Requested by both SubsurfaceIO and INT
- Search and Maps query attributes are conflated; look at separating these out into separate first-class services
R2 workaround is they clients run multiple queries and combine together.
When to revisit
Tradeoff Analysis - Input to decision
Alternatives and implications
Expose Elastic Query Functionality
- Allow client application to specify pass-through query
Provide an API that supports GEOJSON conversion for map specific queries
Provide a maps-specific consumption zone.