Boundary for SpatialSeries

.github/PULL_REQUEST_TEMPLATE.md

@@ -6,6 +6,7 @@
 
 For all schema changes:
 - [ ] Add release notes for the PR to `docs/format/source/format_release_notes.rst`.
+- [ ] Have you included the relevant issue number using "Fix #XXX" notation where XXX is the issue number? By including "Fix #XXX" you allow GitHub to close issue #XXX when the PR is merged.
 
 If this is the first schema change after a schema release (i.e., the version string in `core/nwb.namespace.yaml` does not
 end in "-alpha"), then:

core/nwb.behavior.yaml

@@ -38,6 +38,10 @@ groups:
         is 'meters'. Actual stored values are not necessarily stored in these units.
         To access the data in these units, multiply 'data' by 'conversion' and add 'offset'.
       required: false
+    - name: bounds
+      dtype: float32
+      doc: The boundary range for the data. The units are the same as the units for the data.
+      required: false
   - name: reference_frame
     dtype: text
     doc: Description defining what exactly 'straight-ahead' means.

docs/format/source/format_release_notes.rst

@@ -12,6 +12,7 @@ Minor changes
 - Deprecated `ImagingRetinotopy` neurodata type. (#565)
 - Modified `OptogeneticSeries` to allow 2D data, primarily in extensions of `OptogeneticSeries`. (#564)
 - Added optional ``stimulus_template`` column to ``IntracellularStimuliTable`` as part of the ``IntracellularRecordingsTable``. (#545)
+- Added optional `bounds` attribute to `SpatialSeries.data`. (#567)
 
 2.6.0 (January 17, 2023)
 -----------------------