3liz/QuickOSM

Python exception : cannot convert float infinity to integer

EazyArt opened this issue · 3 comments

2023-03-08T13:29:11     CRITICAL    Произошла критическая ошибка, вот отчет:
2023-03-08T13:29:11     CRITICAL    
2023-03-08T13:29:11     CRITICAL    base_processing_panel.py
2023-03-08T13:29:11     CRITICAL    cannot convert float infinity to integer
2023-03-08T13:29:11     CRITICAL     File "C:\Users/kotar/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\QuickOSM\ui\base_processing_panel.py", line 47, in run
              self._run()
             
              File "C:\Users/kotar/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\QuickOSM\ui\quick_query_panel.py", line 421, in _run
              num_layers = process_quick_query(
             
              File "C:\Users/kotar/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\QuickOSM\core\process.py", line 318, in process_quick_query
              return process_query(
             
              File "C:\Users/kotar/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\QuickOSM\core\process.py", line 251, in process_query
              final_query = query.prepare_query()
             
              File "C:\Users/kotar/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\QuickOSM\core\query_preparation.py", line 312, in prepare_query
              self.replace_bbox()
             
              File "C:\Users/kotar/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\QuickOSM\core\query_preparation.py", line 172, in replace_bbox
              self._format_decimals_wgs84(y_min),
             
              File "C:\Users/kotar/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\QuickOSM\core\query_preparation.py", line 193, in _format_decimals_wgs84
              number = str(int(coordinate * multiplier) / multiplier)

Can you copy/paste your Logs from the QuickOSM tab ? (the small comic-strip bubble bottom right corner of QGIS to open the message log panel)
From when you press the run button.

This is obviously a temporary solution.
The bug is still somewhere, ready to occur at some point :)

Thanks for the feedback.