You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/rosbags.md
+5-2
Original file line number
Diff line number
Diff line change
@@ -112,16 +112,17 @@ One very popular framework for storing scientific data is [HDF5](https://support
112
112
It basically has all the necessary requirements listed above such as random access, parallelism and compression.
113
113
It is further designed for highly complex data with an extensive amount of data.
114
114
HDF5 is open source and its source can be freely obtained from [bitbucket](https://bitbucket.hdfgroup.org/projects/HDFFV/repos/hdf5/browse) and is under a [permissive license](https://bitbucket.hdfgroup.org/projects/HDFFV/repos/hdf5/browse/COPYING) of the HDF group.
115
-
Multiple language wrapper or bindings are available, namely c/c++, python, fortran or java.
115
+
Multiple language wrapper or bindings are available, namely C/C++, python, fortran or java.
116
116
117
117
#### Pros
118
118
- Open Source and standard specification for file format
119
-
-Fullfils the requirements given
119
+
-Fulfills the requirements given
120
120
- Multi language support
121
121
- Large community of users
122
122
123
123
#### Cons
124
124
- Depending on a slowly developing standard
125
+
- The table dimensions of each chunk have to be of fixed size, known at startup.
125
126
126
127
There is a popular [blog post](http://cyrille.rossant.net/moving-away-hdf5/) by Cyrille Rossant, which gives a short introduction, but also discusses some controversy with HDF5.
127
128
@@ -145,5 +146,7 @@ It is also open source, [extensively tested](https://www.sqlite.org/testing.html
145
146
The Gazebo team created a nicely composed [comparison](https://osrfoundation.atlassian.net/wiki/spaces/GAZ/pages/99844178/SQLite3+Proposal) between SQLite and the existing rosbag format.
146
147
147
148
#### Pros
149
+
- Table dimensions do not have to be known at startup and can be flexibly extended.
150
+
- Ability to query the tables with classical relational SQL syntax.
0 commit comments