FlightGear Newsletter December 2015: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
mNo edit summary
Line 36: Line 36:
|date  = Nov 9th, 2015
|date  = Nov 9th, 2015
}}''
}}''
{{FGCquote
|1= I download the latest planet and run osm2pgsql - here are a few numbers:
The complete planet dump file is approx. 30GB. download yours here (pick the pbf).
The import into a postgresql database takes something between one day (hexacore, 64GB RAM, 4 disks RAID10 7200RPM 4TB Array) to one week (average quad core, 8GB, single consumer market HD) and explodes to several hundret GB for the database (depends a lot on filesystem params).
I would not recommend this procedure for the average user.
For the brave, the excellent howto is here: https://switch2osm.org/serving-tiles/manually-building-a-tile-server-14-04/
|2= {{cite web
  | url    = http://forum.flightgear.org/viewtopic.php?p=267920#p267920
  | title  = <nowiki>Re: OSM, the death of scene models?</nowiki>
  | author = <nowiki>Torsten</nowiki>
  | date  = Dec 9th, 2015
  | added  = Dec 9th, 2015
  | script_version = 0.23
  }}
}}


== In the hangar ==
== In the hangar ==

Revision as of 14:15, 10 December 2015

This newsletter is a draft.

Please feel free to add content you think will be of interest to the FlightGear community. You can read the latest newsletter at FlightGear Newsletter November 2015.


Magagazine.png
Enjoy reading the latest edition!
Please help us write the coming edition!
December 2015

Development news
New scenemodels and TerraSync hosting needed
In the hangar

Scenery Corner
Project Venezuela
Community News

Contributing
Translators required
FlightGear logos
Screenshots

Development news

New scenemodels and TerraSync hosting needed

By the end of this year (2015), the FlightGear Project's hosting for the scenemodels database and website and the TerraSync repository will no longer be available. As a result, the FlightGear Project is searching for a replacement, even just a temporary one. The technical requirements are roughly these:

  • A PostgreSQL database (with the PostGIS extension) of approximately 40 GB, with capacity to expand (this is for the scenemodels database).
  • An Apache webserver, PHP, access to the database and the usual toolkit for hosting the scenemodels website
  • An SVN server with 140+ GB for the TerraSync repository.
  • Enough bandwith to serve the data.
  • One or more reverse proxies serving TerraSync requests (not much storage required, just bandwidth).

If you can provide the above, are able to provide help, or have any serious ideas for a replacement, please get in touch via the forum topic or the mailing list topic

Torsten (Nov 9th, 2015). Scenemodels and terrasync are going down.

Cquote1.png I download the latest planet and run osm2pgsql - here are a few numbers:

The complete planet dump file is approx. 30GB. download yours here (pick the pbf). The import into a postgresql database takes something between one day (hexacore, 64GB RAM, 4 disks RAID10 7200RPM 4TB Array) to one week (average quad core, 8GB, single consumer market HD) and explodes to several hundret GB for the database (depends a lot on filesystem params).

I would not recommend this procedure for the average user.

For the brave, the excellent howto is here: https://switch2osm.org/serving-tiles/manually-building-a-tile-server-14-04/
— Torsten (Dec 9th, 2015). Re: OSM, the death of scene models?.
(powered by Instant-Cquotes)
Cquote2.png

In the hangar

Scenery corner

Project Venezuela

Legoboyvdlp has been working wih WED to create several new airports for Project Venezuela. Unfortunately, due to problems with the MapServer, these new airports will not be generated.

Maiquetia now features animated jetways for most gates.

SVCS now has shared models. They are also in TerraSync

Community news

FlightGear is now on Steam Greenlight. If this game gets through Greenlight, updates will be able to be pushed out through Steam, along with scenery data etc.

Contributing

Translators required

En.gif The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, start at Help:Translate.
Fr.gif Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire Help:Traduire.
De.gif Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit Help:Übersetzen an.
Nl.gif De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij Help:Vertalen.
Es.gif La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en Help:Traducir.
Cat.gif La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a Help:Traduir.
Pt.gif A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em Help: Traduzir.

FlightGear logos

If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit FlightGear logos for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

Screenshots

The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings (anti-aliasing, texture sharpening, etc.). More info at Howto:Make nice screenshots.