Kai Pastor

The above code probably doesn't take properly into account the case that a dash symbol might be defined (`!= NULL`) but invisible: If I modify one of the **506 Footpath**...

You may now test the unstable build if it solves the problem with unwanted dash points for 709.2 and other line symbols. There are no dangerous changes since 0.6.1 in...

Class `Georeferencing` applies `roundDeclination()` to the arguments given to the setters for declination/grivation, and OCD import must go through these setters. https://github.com/OpenOrienteering/mapper/blob/9e874fe7d9d1b19e7560a2ed63be9a5da5cd0908/src/core/georeferencing.cpp#L841-L853

IIUC, potrace (which is underlying CoVe) is much more a tool for areas than for lines? The implementation of the "Fill bounded areas" tool is quite similar to the desired...

GDAL's polygonize algorithm seems to have users not only in QGIS: https://www.dropbox.com/s/3vxnj0eurr6y9hp/polygonize.zip?dl=0&file_subpath=%2Fpolygonize.txt

> As a result, this feature could not be installed, right? Someone needs to do the work.

Well, we are prepared to handle DXF data in paper coordinates or projected coordinates, but not in geographic coordinates. DXF's origin is CAD, it is an abbreviation for "drawing interchange...

> It's worth a mention that although it's rare and impractical, it is not an invalid DXF file. Sure. That's why I wanted to point out what we do handle,...

> I believe that Mapper should not reimplement the DXF driver for this reason and the geodata information handling should be upgraded on the GDAL side. Sure! If anyting at...

> Should we throw in an issue over there? Yes. However, I would insist that we do that as well prepared as possible: - with a minimal DXF test file...