Incorrect handling of Geospatial fields causes EDS-ingested records to not match schema and not have geospatial metadata indexed
When a record is ingested through EDS Fetch & Ingest process, the Spatial Point Wgs84 Coordinates fields are not transformed as expected to match the schema representation for spatial locations. This causes the records ingested through EDS Fetch & Ingest to not have their geospatial fields at the same JSON property path as regularly ingested records.
The issue is related to Search service flattening certain fields and EDS not undoing it when creating the manifests for ingestion.
See M22 testing writeup here: https://community.opengroup.org/osdu/platform/pre-shipping/-/blob/main/R3-M22/Test_plan_[…]22-EDS-testing-aws-spatial-fields-bfg.docx?ref_type=heads