Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • I Indexer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 16
    • Merge requests 16
  • 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
  • Indexer
  • Issues
  • #20
Closed
Open
Issue created May 29, 2021 by Debasis Chatterjee@debasiscOwner

Frame of Reference - Handle creating WGS84 values when indexing Master Data Well (AsIngested -> WGS84)

See enclosed example JSON file from here.

https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/schema/-/blob/master/Examples/master-data/Well.1.0.0.json

Well.1.0.0.json

For SpatialLocation, we see AsIngestedCoordinates and also Wgs84Coordinates.

Can Indexer's Normalizer handle this situation and fill Wgs84Coordinates by applying suitable CRS Conversion from AsIngestedCoordinates?

Thus avoid any human error and also ease the effort of creating json/payload manifests.

Assignee
Assign to
Time tracking