Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Critical Error Occurs apparently only on one key / value combination: landuse=grass #461

Open
JdPass opened this issue Apr 5, 2023 · 4 comments
Labels
bug An identified bug

Comments

@JdPass
Copy link

JdPass commented Apr 5, 2023

Critical Error Occurs apparently only on one key / value combination: landuse=grass

I have been using quickOSM successfully all day with many other key/val combinations but as soon as I try landuse=grass then I get a critical error. Log below:

2023-04-05T16:58:14     CRITICAL    A critical error occurred, this is the traceback:
2023-04-05T16:58:14     CRITICAL    
2023-04-05T16:58:14     CRITICAL    base_processing_panel.py
2023-04-05T16:58:14     CRITICAL    unknown
2023-04-05T16:58:14     CRITICAL     File "/Users/jdpass/Library/Application Support/QGIS/QGIS3/profiles/default/python/plugins/QuickOSM/ui/base_processing_panel.py", line 47, in run
              self._run()
             
              File "/Users/jdpass/Library/Application Support/QGIS/QGIS3/profiles/default/python/plugins/QuickOSM/ui/quick_query_panel.py", line 421, in _run
              num_layers = process_quick_query(
             
              File "/Users/jdpass/Library/Application Support/QGIS/QGIS3/profiles/default/python/plugins/QuickOSM/core/process.py", line 318, in process_quick_query
              return process_query(
             
              File "/Users/jdpass/Library/Application Support/QGIS/QGIS3/profiles/default/python/plugins/QuickOSM/core/process.py", line 257, in process_query
              return open_file(
             
              File "/Users/jdpass/Library/Application Support/QGIS/QGIS3/profiles/default/python/plugins/QuickOSM/core/process.py", line 106, in open_file
              layers = osm_parser.processing_parse()
             
              File "/Users/jdpass/Library/Application Support/QGIS/QGIS3/profiles/default/python/plugins/QuickOSM/core/parser/osm_parser.py", line 161, in processing_parse
              layers[layer]['vectorLayer'] = processing.run(
             
              File "/Applications/QGIS.app/Contents/MacOS/../Resources/python/plugins/processing/tools/general.py", line 108, in run
              return Processing.runAlgorithm(algOrName, parameters, onFinish, feedback, context)
             
              File "/Applications/QGIS.app/Contents/MacOS/../Resources/python/plugins/processing/core/Processing.py", line 179, in runAlgorithm
              ret, results = execute(alg, parameters, context, feedback, catch_exceptions=False)
             
              File "/Applications/QGIS.app/Contents/MacOS/../Resources/python/plugins/processing/gui/AlgorithmExecutor.py", line 72, in execute
              results, ok = alg.run(parameters, context, feedback, {}, False)

Environment

  • QuickOSM version: 2.2.1
  • QGIS version: 3.30.0-'s-Hertogenbosch
  • OS: MacOS 13.2.1
@JdPass JdPass added the bug An identified bug label Apr 5, 2023
@Gustry
Copy link
Member

Gustry commented Apr 5, 2023

I guess it's a duplicate of #422 and you should be able to fix it your self by following instructions. Let me know if it doesn't work and we can reopen.

@Gustry Gustry closed this as not planned Won't fix, can't repro, duplicate, stale Apr 5, 2023
@JdPass
Copy link
Author

JdPass commented Apr 5, 2023 via email

@Gustry
Copy link
Member

Gustry commented Apr 5, 2023

Ok, so the Processing plugin is installed and checked ?
Did you restart QGIS in the meantime ?

The processing plugin disabled is a very common issue unfortunetaly, and your logs does not help more :(

@Gustry Gustry reopened this Apr 5, 2023
@JdPass
Copy link
Author

JdPass commented Apr 5, 2023

Processing plug-in is installed and checked, I've restarted QGIS as well.

I was able to work around it by taking different extents and working around the area where there must be some landuse=grass polygon that is causing error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An identified bug
Projects
None yet
Development

No branches or pull requests

2 participants