Re: nOOb questions

Drew Kirkpatrick wrote:

>We solely use imagery based scenery here, and have been needing to
>come up with our own database building process that's parallelized.
>Extending terragear could save us time, but the legalities get tricky
>since this is a government project, and I'm not sure if we'd be
>allowed to participate in an open source project. I'll have to scope
>that out, and prod the database guys to look at terragear. Thanks for
>the tips, and keep up the good work!
>  
>

I could point out that open-source refers to our suite of software 
tools.  We don't impose any licensing terms on the resulting scenery 
databases .   Our philosophy is that the licensing terms of the 
resulting scenery database need to be compatible with the terms of the 
source data.  The tools themselves don't add or remove any constraints.

That said, you won't find a lot of people willing to contribute their 
time for free with no hope of any return on that investment.

But if you could make some imagery (or imagery at some lower resolution) 
available under some sort of reasonable/workable licensing terms, that 
could be a very attractive return on our investment.  Thinking out loud 
here ... wouldn't it be cool to have something similar to google's map 
server imagery available, but available in the context of 
terragear/flightgear so we could interact and fly with the imagery using 
flightgear aircraft within the flightgear environment.  That doesn't 
necessarily mean give the imagery out for free to the world, just like 
google doesn't give out their imagery for free, it's use is solely 
limited to within the google map application.

Curt.

-- 
Curtis Olson        http://www.flightgear.org/~curt
HumanFIRST Program  http://www.humanfirst.umn.edu/
FlightGear Project  http://www.flightgear.org
Unique text:        2f585eeea02e2c79d7b1d8c4963bae2d


_______________________________________________
Terragear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/terragear-devel
2f585eeea02e2c79d7b1d8c4963bae2d