Yep. So right now the topic function accumulates the emitted features in a `features` array, and so you’d do the same thing for the header by stashing the value to the header event callback. Then you’d pass both the features and the header to the topic’s callback function so that you could verify both the expected features and header down below. You’d need to change the expected output files to contain both the features and the header object, of course (either as separate files or embedded within the JSON, but given that this JSON is generated by `shp2json` and is valid GeoJSON, I would use a separate file to store the expected header content).