Allow for custom basemaps beyond the hard-coded choices offered in the combo box.

[reussinho]

Hi there,

we as a company are only working in Switzerland and therefore solely work with the coordinate system EPSG 2056 (LV95). It would be great if users could choose the coordinate system for the conversion instead of having WGS84 as default.

In addition, it would be really cool if you the use of WMS layers as basemap could be enabled (e.g. swisstopo), so that users are free to chose their own basemap.

Thanks in advance for your thoughts on these topics,
David

[nirvn]

@reussinho , I've renamed this PR to focus on the part that's not implemented (i.e. custom base map).

It will not be sitting super high in the list of priorities for now. I do feel like the converter should not try to achieve everything users could do by opening and tweaking the generated project further, inc. by adding custom WMS / XYZ / etc. basemaps :)

That said, thanks for the mention of project CRS parameter, that was a really good idea.

[reussinho]

@reussinho , I've renamed this PR to focus on the part that's not implemented (i.e. custom base map).

It will not be sitting super high in the list of priorities for now. I do feel like the converter should not try to achieve everything users could do by opening and tweaking the generated project further, inc. by adding custom WMS / XYZ / etc. basemaps :)

That said, thanks for the mention of project CRS parameter, that was a really good idea.

valid point. it would be a "nice to have" feature :) thanks anyway for implementing the CRS parameter!

[nirvn]

@reussinho , you're most welcome -- have you been using the plugin some more since you filed these enhancement requests? Working well?

[reussinho]

@reussinho , you're most welcome -- have you been using the plugin some more since you filed these enhancement requests? Working well?

I've been switching to a simple INTERLIS model for my use case, primarily because I'm more familiar with it. I've also had some issues with image types in QGIS 3.40.5, will open a separate issue for that soon.
I will surely be using XLSFormConverter in some form again in the future :)