Re: [Flightgear-devel] Terrasync for WS3.0

[merspieler <mer...@al...>]

Thanks for the words of caution.

On 1/8/24 17:25, Torsten Dreyer wrote:
>   * create and allow updates of the scenery sometimes

Someone just sends me a new 10x10 degrees area and I update it

>   * do this even if the original creator has left the project

It all just depends on me so I can update anything, and if I'm gone then 
this WS3.0 terrasync will be gone as well

>   * incorporate changes into existing scenery (doing this manually gets
>     boring over time)

What changes other than point 1 do you mean?

>   * work in coexistance with existing processes, think of the scenery
>     database e.g.

I wouldn't touch any of that, just distribute WS3.0 related directories:
* vpb
* NavData (for updated matching apt.dat file)
* Terrain (only containing ICAO.btg and matching .stg files for updated 
airports)
* little maybe (only for a small area, no contributions from others 
(unless they somehow donate more disk space)) Orthophotos

>   * manage expectations from our users

Goal is to test terrasync and provide an easy way to get started with 
WS3.0. I DO NOT intend to become the defacto central place for WS3.0 
when WS3.0 is ready and to be released, it is meant for "development" only.

> None of these should hold you back collecting and hosting the data in 
> the way you mentioned.
> You can start right away with your server, add the .dirindex files and 
> make people use your T/S
> mirror by setting the correct property on startup.
> 
> But please think carefully about the above mentioned items (and maybe 
> some more) before
> going large scale.

I'm not planing on doing another world build. I should be able to handle 
the load of some more static hosting.