Closed martin-ueding closed 3 months ago
The distance string is not the problem. The issue is that I store the metadata before I check whether a time series exist. That used to be different, hence it is a bug now. I've fixed it in two ways: The metadata is saved only when a time series exists, that already rules out these activities. In the enrichment phase it will remove the intermediate metadata file if no matching time series is found. So it should cure the inconsistent state that you have and prevent it from happening again.
I was able to find one condition that crashes the import: Any activity that has no actual GPS data such as Pool Swimming. These activities have distance as a string (e.g. "2,000" for 2 km) and throw the following error message when importing:
Originally posted by @eifelkiwi in https://github.com/martin-ueding/geo-activity-playground/issues/112#issuecomment-2275988965