wsidicom is quite strict in accepting DICOM

[GeertLitjens]

DICOM files generated by, for example, https://github.com/GoogleCloudPlatform/wsi-to-dicom-converter are not accepted by wsidicom due to missing tags (e.g. OpticalPath-related), but can be opened by Orthanc. Maybe adding a flag --strict would be better? If you can read tags and the actual image data I think that should be enough to be acceptable.

[erikogabrielsson]

Thanks for the feedback @GeertLitjens. The OpticalPathSequence is currently checked to filter out non-standard files and is then parsed on two locations:

• To get the optical path identifier for an image-instance. If the OpticalPathSequence is missing the behavior should be changed to default the identifier to '0'.
• To be able to get optical path information. This will of coarse not be possible if there is not OpticalPathSequence, but the behavior should be changed so that no optical paths are parsed if there is not OpticalPathSequence.

There are other properties that should be set to default values if not set in the files.

[GeertLitjens]

Maybe good to know: the Orthanc converter by default does not add a FrameOfReferenceUID and no ImageType (all images are considered VOLUME by default). Might be worthwhile to consider supporting that still with a warning?