Improve spatial fields and bbox #276

[Ludee]

Summary of the discussion

Describe the findings of the discussion in the issue or meeting.

Type of change (CHANGELOG.md)

Changed

• Update spatial context keys (#321)

Workflow checklist

Automation

Closes #276

PR-Assignee

• 🐙 Follow the workflow in CONTRIBUTING.md
• 📝 Update the CHANGELOG.md
• 📙 Update the documentation
• 🐙 Assign a reviewer to the PR

Reviewer

• 🐙 Follow the Reviewer Guidelines
• 🐙 Provided feedback and show sufficient appreciation for the work done

[Ludee]

This is ready for review.

[Cpprentice]

The context update of spatial is weird as it seems to reintroduce the older version from before issue 318.

The other comment is just a small improvement.

[Cpprentice]

I did not see any use of EPSG in the context.json for now so I am not sure if it is needed.

I guess this was intended to be able to resolve the values in the crs field that is pattern constraint to an "EPSG:" prefix now.

But for that I believe it is mandatory to set "@type": "@id" instead of a string in line 299.

[Cpprentice]

I think I added a @nest for the spatial object in my context overhaul which would likely not cause a blank node with all that stuff inside but assign that directly to the parent object.
Also there was no nested @context before.

It seems to me that this just includes the old entries that have been in the context before. Please check and make sure we get a proper update in the end.