Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • S Storage
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 20
    • Merge requests 20
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • System
  • Storage
  • Issues
  • #82
Closed
Open
Issue created Jul 19, 2021 by Sanjeev-SLB@spellikodukuMaintainer

OSDU R3 SpatialLocation Support WGS84

The Search service needs to be able to accept incoming bounding box and bounding polygons defined in WGS84 and compose queries with those against R3 Storage Records containing AbstractSpatialLocation-compliant GeoJSON blocks. The types of GeoJSON that need to be handled break down into two types: FeatureCollections and AnyCRSFeatureCollections. The former will always be in WGS84 per the OSDU schema spec, and the latter may have a CRS definition attached that can be in any CRS supported by the CRS service. The WGS84 bounding shape against WGS84 feature collections.

Note: All incoming bounding boxes and polygons are in WGS84 points.

Scen. 1 WGS84 bounding box against WGS84 feature collection GIVEN an incoming bounding box of 4 lat/lon points AND one or more storage records that has a R3 SpatialLocation GeoJSON WGS84 feature collection AND a Search query using the bounding box as a constraint AND the feature collection has features contained in the bounding box WHEN the search request is issued THEN the Search query will return records where the feature collection contains items in the bounding box

Scen. 2 WGS84 bounding polygon against WGS84 feature collection GIVEN an incoming bounding polygon of N lat/lon points AND one or more storage records that has a R3 SpatialLocation GeoJSON WGS84 feature collection AND a Search query using the bounding polygon as a constraint AND the feature collection has features contained in the bounding box WHEN the search request is issued THEN the Search query will return records where the feature collection contains items in the bounding polygon

Assignee
Assign to
Time tracking