I ran the script against 2019 and 2020 data and the coordinate pairs in the output (SQL/WKN) ended up lat,lon instead of the expected lon,lat. The script returned lon,lat for 10 years, as far as I can trace the git history, the input projection didn't change (*.prj file), the hardcoded projection config in the script didn't change either. And I ran the script myself against 2019,2018 data and still had the output files, can't reproduce it.
Maybe in the past the scripts ran under Python2 and now Python3 (or rather updated Python libraries) changed.
I wish I had a good explanation.
I ran the script against 2019 and 2020 data and the coordinate pairs in the output (SQL/WKN) ended up lat,lon instead of the expected lon,lat. The script returned lon,lat for 10 years, as far as I can trace the git history, the input projection didn't change (*.prj file), the hardcoded projection config in the script didn't change either. And I ran the script myself against 2019,2018 data and still had the output files, can't reproduce it.
Maybe in the past the scripts ran under Python2 and now Python3 (or rather updated Python libraries) changed.