SPIKE: Given the correct metadata, can CKAN display geospatial bounds correctly

[btylerburton]

User Story

In order to have an accurate understanding of what spatial data CKAN will support, datagovteam wants to test various datasets with spatial criteria in catalog-next.

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

• GIVEN a geospatial dataset is ingested by the Harvester 2.0
  AND it has output the spatial data correctly
  WHEN I visit the dataset's page in CKAN
  THEN I expect to see the bounding box rendered accurately

Background

[Any helpful contextual notes or links to artifacts/evidence, if needed]

Related to:

• Handle Spatial Data crossing meridian appropriately #5002
• Support spatial 'type':'envelope' in JSON harvest sources #5003

Security Considerations (required)

[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

Sketch

• Create some variations of a geospatial dataset with differing formats of geospatial data
  • Differing types: Point, Polygon, Envelope, Multi-Polygon, ...
  • ... (add more test cases here)
• Push them via CKAN API into catalog-next-web
• Determine if they display the metadata correctly

[btylerburton]

Determine all types of polygons that can be rendered based on dataset metadata.

Ex. below...

https://catalog.data.gov/dataset/2022-cartographic-boundary-file-shp-united-states-1-20000000