OpenEnergyPlatform / OpenEnergyPlatform/oemetadata
Bounding box should allow "null" types as value
Open
@Cpprentice is already working on this.
Since Jun 17, 2026.
part: backend 🧱
priority: high ⚡
status: active 🚧
type: bug 🐛
- Dominant language
- Python
- Stars
- 26
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Description of the issue
The Bounding Box property allows for numeric values. As we generally allow the user to leave fields empty, it should be okay to allow null values. This would also help with simplifying
Steps to Reproduce
- Create a table or navigate to a table you have permissions for on the OEP
- Edit the metadata and make sure the Bounding Box property is there in the Extend section of Spatial
- Leave it empty and attempt to submit the form
Ideas of solution
Add "null" to bounding box items type specification in the schema.json
https://github.com/OpenEnergyPlatform/oemetadata/blob/ed9a205dad73db27487d41ab2918c794830daf22/oemetadata/latest/schema.json#L550
Context and Environment
- Version used:
- Operating system:
- Environment setup and (python) version:
Workflow checklist
- I am aware of the workflow in CONTRIBUTING.md
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.