support "geospatial" in theme as spatial document

[rshewitt]

User Story

In order to offer backwards compatibility of spatial datasets, datagov wants to label open search docs as spatial when "geospatial" is in the theme array.

Acceptance Criteria

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

• GIVEN we used to consider datasets with "geospatial" in the theme array
  WHEN syncing with opensearch happens
  THEN datasets with "geospatial" in the theme area will be considered spatial
  [AND optionally another verifiable outcome]

Background

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

Security Considerations (required)

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

Sketch

[Notes or a checklist reflecting our understanding of the selected approach]

[SueValente]

if theme = geospatial, then show as part of geospatial datasets
Would require a re-harvest of entire dataset.

also need to update geospatial filter.. should consider filters and what not

[chris-macdermaid]

Adding some GeoPlatform operational context here.

We’ve received a few questions from agencies about changes in GeoPlatform harvesting behavior related to the current geospatial filtering logic. Specifically:

• records that previously were not harvested into GeoPlatform are now appearing, and
• some expectations around what qualifies as “geospatial” no longer align with prior behavior/documentation that referenced the theme field.

From our understanding, the current behavior now considers records geospatial when they contain a spatial field, rather than relying on theme=geospatial as was historically expected by some users.

That change has operational impacts for GeoPlatform because we consume the spatial_filter=geospatial results directly from Data.gov harvesting workflows. We are already seeing questions from agencies and data stewards around unexpected records appearing in GeoPlatform and how this affects NGDA/GDA-related tracking and reporting.

Is there any existing documentation explaining the behavior change that we can point agencies to when responding to these questions? Even a short clarification of the intended geospatial filtering behavior would be helpful.

[FuhuXia]

@chris-macdermaid
The behavior change is not intentional. Your understanding is right, the spatial filter on the new catalog is more like datasets-with-spatial-value and datasets-without-spatial-value, which is different from old catalog where we rely on theme=geospatial. From developer point of view, it makes sense to implement it that way.

I am trying to understand from the user point of view, why user wants dataset claiming to be geospatial but contains no (valid) spatial value?