Hello,
Martin Spott schrieb:
[SNIP]
Actually, I _do_ agree that having preprocessed scenery
_is_ an advantage. But it does have disadvantages as well:
1.) At the current state it appears (to me) nearly impossible to inject
user-contributed additions into the scenery,
2.) I don't manage to build the necessary tools on my server ;-))
Share your problems with us, perhaps we can help ;-)
Maybe the way to go might be to make it easier for everyone to build
the tools (and to simplify the process of scenery generation) and to
add his personal scenery improvements using common open GIS file
formats but keep the preprocessed scenery as we are already used to it.
I'm currently working on some more detailed scenery data for the region
around Lake of Constance, Southern Germany, and I still have to check on
some legal issues, but I'd love to share my experience on that with you
as soon as I get some more time (been quite busy in the last few months).
I'm using GRASS (http://grass.itc.it) for digitising and the preliminary
results are quite interesting regarding better orientation - at least
for a local ;-)
I had to write an additional tool to get linedata imported from GRASS to
TerraGear, but actually with all the support libraries available this is
far from complex :-)
Most of the exporting and scenery generation tasks is automated using
scripts and a single configuration file.
When the legal issues are resolved, I might be able to share the
digitised data with the community and perhaps we could start a
discussion on how the integration of such data into the standard scenery
data can be organised and automated - for Curt's convenience ;-)
Oh, and not to forget: FlightGear is an astonishing piece of software!
In the meantime it has totally replaced my commercial flight simulation
software (don't make me say names ;-), making it possible for me to
actually drop Windoze :-) Thank you to all who contributed!
Regards,
Ralf
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
