effective central bin size in the Interfile header #1034
Description
found by @danieldeidda
We currently write an "effective central bin size" to the interfile header in all cases, but really only use it for the arc-corrected case (we write some warnings if it's not as expected, but that's the only thing we do with it). However, for a block/generic scanner, this concept makes no sense really. The central bin could be just next to a gap for instance. The keyword should really only be written (and read) for the arc-corrected case therefore.