Answer:
It depends on how many World Tiles (submodules) you want to initialize/manage, and which Tiles are those.
terraGIT is a git repository with submodules, consisting of one super-repository - terraGIT, and submodules containing either the Terrain or the Objects for any particular World Tile (10x10 degrees) as seen in this scenery map:
http://ns334561.ip-5-196-65.eu/~fgscenery/WS2.0/scenery-2.0.1.html
The super-repository (terraGIT itself) is about 600MB complete. The superrepository includes the install/deinstall scripts, all the configuration files of the Airports folder, and every shared model. This is the minimum clone size, but with terraGIT alone you wouldn't have much any scenery at all!
It's the required management basis.
The terraGIT submodules are repositories within the super-repository. Each Tile has 2 important branches:
The Terrain branch, gets stored in
Code: Select all
terraGIT/Terrain/
Contains the FligthgGear terrain for the respective quad.
The Objects branch, gets stored in
Code: Select all
terraGIT/Objects/
it contatins the Static objects and the locations (stg lines) of any object (SHARED and STATIC) of such tile.
Completely initializing a tile will give you the terraGIT version of those 10x10 degrees. You can indicate flightgear to use terraGIT as an scenery patch,
Code: Select all
--fg-scenery=/path/to/terraGIT
and allow terrasync to fetch any other place in the World, except those tiles you have fetched.
Therefore, you don't need to terraGIT the whole planet to get terraGIT going.
A tile is fully downloaded using the install/tile script. example
Code: Select all
install/tile w130n30
Installs the original tile containing KSFO and KHAF (where KHAF is also not underwater anymore).
This script manages the initialization of both Terrain and Objects of the corresponding tile, so it is an abbreviated way of doing
Code: Select all
git submodule init Objects/w130n30
git submodule init Terrain/w130n30
git submodule update Objects/w130n30
git submodule update Terrain/w130n30
You can use wildcards (like *) to manage large patches of scenery. Example you can download the whole tiles on the latitude n30 by doing
Code: Select all
git submodule init Objects/*n30
git submodule init Terrain/*n30
git submodule update Objects/*n30
git submodule init Terrain/*n30
Since * means any character(S) you could even be more efficient and do
Code: Select all
git submodule init */*n30
git submodule update */*n30
Intriguingly you can even update and init in the same line with, per example, getting the e020 longitude tiles
Code: Select all
git submodule update */e020* --init
Back to terraGIT download sizes.
With this in mind, the download size of each tile is very variable. In flat and simple areas of the world (poles), or places of the earth with few elevation and shapefiles changes a whole tile does not exceed a few MB in size. Other places of the earth where terrain is more convoluted, or there is use of extensive landclasses, then the size of a tile can grow to be a few GB. Top size is the central Europe tile where Paris is (not surprising) with about 2.7 GB of total size.
So, if you initialize that tile, your local terraGIT will grow to be 4GB (600 MB original plus 2.7 GB of your downloaded tile).
So, in reality, how big terraGIT will occupy in your hard-drive depends ultimately of how much of the World you are planning to fetch and update with it, not on terraGIT itself.
How Much Hard-drive do I need to spare if I want to download the whole world?
You are looking for a total of about 250GB for the whole collection. So make sure you've got plenty of hard-drive space reserved, and enjoy the World on your hands.
There are different ways to get the whole world, the first one is using the install/World script
Code: Select all
git pull
install/World
That script does initialize (if needed) and update the World to the latest revision. The first time will take you somewhere between 12 hrs to a week to get (totallly depending on your ISP speed).
You can do it manually with the submodule command
Code: Select all
git pull
git submodule init
git submodule update
the comands init and update without additional information means (ALL)
Or if you feel you want to come by blocks, you can set yourself to download by patches, and work your way up/or down, example :
By latitudes, north bound
Code: Select all
git submodule init */s90
git submodule update #wait
git submodule init */s80 #go up 10 deg
git submodule update #wait
git submodule init */s70 #go up 10 deg. walk your way up to latitude n80
git submodule update #wait
In summary, terraGIT is a very flexible way to obtain (download), update , and share your scenery (we accept scenery patches, new configuration files, new models (shared and static) high resolution textures, texture tiling, and texture reusing on multiple models, among many more improvements -- your imagination is the limit).
The size of the terraGIT in your computer (locally) depends on how much scenery you are fetching, and where it is.
It can be as small as less that 1GB or as large as 250GB (full world)
This size is the size of your local repository, and not the size of any particular repository hosted in Github.
Feel free to ask for clarification below,
IH-COL
