osmWebWizard.py: wrong lengths in network when importing satellite images
downloading the network with satellite images switches to the Mercator Projection because the image tiles use this projection. However, this projection has a much larger spatial error compared to the default UTM projection. In an example project the distances in the network were exaggerated by a factor of 2 causing invalid route lengths and doubled travel times.
The user must be made aware of this. In satellite mode, it might even be desirable to build the network twice (once with UTM) and then apply the edge lengths from the UTM network as custom edge length values.
In the very least, the user must be made aware of the potential for invalid lengths.
maybe split into two options one for the images one for the projection change
The alternative to changing the network is changing the image (using gdalwarp as outlined in #6539).
Some useful code for stitching the tiles together can be found at https://github.com/jimutt/tiles-to-tiff.git
After building a single tif, it can be projected with gdalwarp -t_srs PROJ_STRING_FOR_UTM
Care must be taken due to #13904