Bug 281766

Summary:	Route maps in Marble should be exportable with a specific scale
Product:	[Applications] marble	Reporter:	Johannes Obermayr <johannesobermayr>
Component:	general	Assignee:	marble-bugs
Status:	CONFIRMED ---
Severity:	wishlist	CC:	f.esser, nienhueser, tobias.jakobs
Priority:	NOR
Version:	unspecified
Target Milestone:	some future version
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description Johannes Obermayr 2011-09-10 19:34:51 UTC

Version:           unspecified (using Devel) 
OS:                Linux

If you want to export a route map you can either choose to
1. export it in one general map (mostly with a bad resolution and without city/street names) or
2. zoom in, export to many detailed maps and put them with a graphic editor together (inconvenient and time intensive task).

So Marble should offer an option to export route maps with a specific scale (e. g. 1:1000, 1:10000, 1:100000, 1:1000000 or custom scale).

For this first the westernmost and easternmost longitude as well the most southernmost and northernmost latitude of the route map must be found.

I do not know how difficult/time intensive the implementation of such an feature is ...

Reproducible: Always



Expected Results:  
see above

Comment 1 Florian Eßer 2011-09-11 09:35:00 UTC

Yes, that would indeed be a nice feature to have in Marble.
(Maybe if I find some time, I could try to make a patch for that...)

However, if you need something similar right now, you might want to take
a look at the following quick&dirty PHP script I kludged for myself to
export a Marble-planned route to my Reading-A-Printed-Map (tm)
navigation system:
http://ente.baer.rwth-aachen.de/gpx/gpx-to-paper.php

It will generate a bunch of DIN-A4 pages containing the map around a
given gpx route. Just export your Marble route as *.gpx file and use it
with that script.
Specific scales are not supported however, it just uses a fixed OSM tile
zoom level. (15 by default)

Comment 2 Tobias 2014-10-29 13:58:02 UTC

I thing this is the same then Bug #200019.