Failure due to space in filename

[ajanett]

The GeoPackage specification has no limitations on characters in filenames and does not state that spaces are not allowed. The only requirement is 'A GeoPackage SHALL have the file extension name ".gpkg".'. In the case that a geopackage has the .gpkg extension, but a space in the name, the ETS fails with an immediate Fatal Error in calling an extension function which eventually tells us there is an "illegal character in path'. Removal of the space from the file name corrects the issue. However, the problem here is that the test code should not HARD fail on such an item. If spaces are a problem and not to be allowed, the test code should report this as an issue; and the specification should also include the requirements to support this if necessary.

[jyutzler]

Now that the TC is behind me, I'm looking at a sprint on the ETS. I will take a look at this and other ETS issues.

[jyutzler]

This must be a TEAM engine problem. PR #65 does not duplicate the issue. I am unassigning myself.

[dstenger]

@keshav-nangare Can you please do further investigation and create a TEAM Engine issue in case it is related to it?

[keshavnangare]

Fixed with this commit: 11c912d [PR: #64]

[dstenger]

Fix did not work and merged branch was reverted: #66 (comment)

[keshavnangare]

Fixed this issue with commit: ed41f4c

Tested the fix with following data:

1. emp ty.gpkg

2. bluemarble.gpkg