[http://members.aon.at/mfranz/flightgear/mapsync]
* darko -- Friday 08 April 2005 12:33:
> Melchior FRANZ wrote:
> >You may want to replace the "austria()" function by "italy()".

> Should I have to replace 9,19 and 46,50 values with coords of Italy to 
> have my Land instead of Yours?

Sure. If you want to use this feature at all. Just define a lat/lon
bounding box for your country. I use(d) this

(1) to only generate selected areas at the first run, because I was too
    impatient to wait for them (KSFO/bay area & Austria). That's commented
    out now; it's this part:

        if ! austria && ! ksfo; then continue; fi

(2) to choose higher map resolution for some regions of interest (ROI).
    (commented out in the version that I put on the HP; active in my personal
    version)



> $lon and $lat are set automatically reading the name of the scenery directory,
> if I've well read... isn'it? 

Yes. The script uses a set environment variable FG_ROOT or the default 
installation
path (/usr/local/share/FlightGear/) and seeks the scenery there 
(./Scenery[/Terrain]/)
or in the last path of FG_SCENERY (if defined), or the only command line 
argument.
It goes through all installed scenery tiles/chunks and generates the map image 
in
$FG_ROOT/Atlas/ and a smaller image in $FG_ROOT/Atlas/lowres/ *if* the image is
missing or there's at least one *.btg.gz file newer than the respective map 
image.

I've got the whole world installed (from which most scenery is quite old).
Generating maps for all takes a few hours, while the mapsync script takes "only"
15 minutes. Occasionally I update regions via terrasync, after which I run
mapsync to get the newest maps.

m.

_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to