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

Fresh install uses legacy DXF/GPX/OSM importer, in contradiction to settings #1166

dg0yt opened this issue Oct 29, 2018 · 0 comments


Copy link

commented Oct 29, 2018

Steps to reproduce

  1. Do a Mapper installation on a pristine computer (or remove all configuration from the system's configurations storage).
  2. Create a new map.
  3. Open an OSM template.

Actual behaviour

  • Mapper asks whether to use the data georeferenced or not.
  • The template is displayed with areas not filled, and with some labels. This is the result of the legacy OSM importer.
  • However, in the settings dialog, OSM is checked for GDAL/OGR.

Expected behaviour

Mapper should use the GDAL/OGR based importer. (Areas should be filled, no labels.)


Uncheck the OSM checkbox in the settings for GDAL/OGR. Close the dialog. Open it again, check the OSM checkbox, and close it again.


Mapper Version: 0.8.3
Operating System: Windows, Linux

@dg0yt dg0yt self-assigned this Oct 29, 2018
@dg0yt dg0yt closed this in 0fa0851 Oct 29, 2018
@dg0yt dg0yt added this to the v0.8.4 milestone Oct 30, 2018
@dg0yt dg0yt changed the title Fresh install uses legacy OSM importer, in contradiction to settings Fresh install uses legacy DXF/GPX/OSM importer, in contradiction to settings Dec 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.