Filename sanitization sometimes breaks GCP files about nodeodm HOT 4 CLOSED

Wanted to reference OpenDroneMap/ODM#1074 here, since this may be the same issue.
The sanitizing in NodeODM seems unnecessary since the rest of ODM works without it. In addition to the above issue, I found it causes errors when using exif files sent from a master odm instance running with --sm-cluster, and any use of the feature and match data being transferred back will also have sanitized filenames that won't match filenames in the master node.

I would think this has been missed since the two most common use cases with WebODM and CloudODM both transfer data to NodeODM at the start of processing, ensuring all filenames are mangled from the start (except GCP entries)

from nodeodm.

Sorry for the late reply, mm, I think you're right, special characters should work OK in ODM (?) and I think this was implemented to originally fix the common issue of spaces in filenames, but since ODM handles those now, this is probably no longer needed.

from nodeodm.

Commit referencing sanitization: cbf5e40

from nodeodm.

Removed sanitization in latest master. This can be closed.

from nodeodm.