World Scenery V2.3

[laserman]

WAAA has the old layout.
new layout Date Approved: 19 Sept 2016

I admit I like to teleport globally with the ufo.

Code: Select all

:PgICAO

[IAHM-COL]

airports approved after Sept 1st 2016 do not exist in apt.dat10.50.
They will become apt11.00

So. yeah. WAAA has too late approval for the inclusion in Marvin2.3 by default.
In principle --havent fully tested,-- Marvin2.3 offers the advantage of seamless patching if I reconstruct an airport with my terragear flavor, but due to issues with zero elevation terrain in several areas I think next is moving to Marvin2.5 include fixing those elevation issues, the water sources in Europe, and going apt.dat 11.0 by default.

I want to test if elgaton's terragear ws2.0 patch works with mine first, and then see how to start addressing these.

I communicated briefly with Wllbragg, and maybe he is willing to cooperate with NLCD landclasses for USA. That'll be mind-buggling great, but sometimes I don't know if he is up to participate with FGMEMBERS branded material.

[laserman]

my terragear flavour

?

I know that you love free software and the GPL,
but on the other hand I get the impression that you also like to keep some secrets & mystery

terraGIT/Objects is terrasync objects(date?) + project3000(version 11/2015)

terraGIT/Terrain is very nice, I like it a lot. I'm sure it was long hard work to make it.
But I like to point out that it's currently a binary only version of terrain.
The user currently has not the 4 freedoms of free software with it.

The situation with scenery 2.0 is similar. Martin Spott told me, that it was not build from shapefiles because the filesize would be too large to handle. terragear did read the landclass polygons directly from the postgress database.

Maybe, if you describe you workflow and you input data, or jwocky gives me ssh access to Marvin so that I can look for myself, then I can help with finding and fixing bugs.

how about a mumble meeting to talk about scenery?

HerbyW was asking if/ how often the Objects path will be updated.

[SHM]

terraGIT/Objects is terrasync objects(date?) + project3000(version 11/2015)

HerbyW was asking if/ how often the Objects path will be updated.

terraGit is updated with the new objects in terrasync every month.

But I like to point out that it's currently a binary only version of terrain.
The user currently has not the 4 freedoms of free software with it.

All the shapefiles used for the generation comes from CORINE, V0, or OSM (all these are freely available on the internet) and the custom shapefiles used are already there in the terragit github organisation. (https://github.com/FGMEMBERS-TERRAGIT?u ... &language=)

The elevation data comes from viewfinderpanorama.
The apt.dat files comes from xplane gateway.

So, all the sources are already there and not hid from others

By terragear flavour I think Israel means that if the patching is done by Marvin only, the ugly seams won't be there.

[IAHM-COL]

@D-LASER


As SHM says above.

All sources of terraGIT (elevation, landclasses) are listed in each repository readme and are available under GPL license. Therefore, we comply with GPL requirement of making sources available.

https://github.com/FGMEMBERS-TERRAGIT/e ... /README.md

Maybe, if you describe you workflow and you input data, or jwocky gives me ssh access to Marvin so that I can look for myself, then I can help with finding and fixing bugs.

Unable.

how about a mumble meeting to talk about scenery?

Sure. No problem... I'll join a bit later after breakfast.
hopefully we meet.

HerbyW was asking if/ how often the Objects path will be updated.

We dont work by schedule.
we can add objects to the scenery coming from any source at any time. the sources include your P3000, OSM2City buildings and projects, Terrasync, the FG custom Scenery packages, etc

In fact, it is very simple to fork any tile, add new objects (with ac files, xmls, textures, nasals etc) and then send a pull request.
Normally I'd accept such pull request without any concern if the GPL material is not available elsewhere.

So in reality, new objects can show up to the terraGIT scenery at any time.

[IAHM-COL]

terraGIT/Objects is terrasync objects(date?) + project3000(version 11/2015)

No. That's not how it works.

terraGIT/Objects contains multiple sources of files

see the readme:

https://github.com/FGMEMBERS-TERRAGIT/e ... /README.md

the objects can be
1) Project3000 --now last version you gave me in tgz as here:
https://github.com/FGMEMBERS-SCENERY/Project3000
2) terrasync objects -- currently updated to Dec 08/2016
3) Objects from customs Scenery packages in FGMEMBERS-SCENERY
(not all imported yet, but working on doing them one at a time)
In general several of these packages have already been imported to terraGIT, and do not have similar content in terrasync
this includes both static objects as well as shared objects worldwide
4) JMaverick AirBase Shared objects and its locations worlwide
5) Objects that I build and I add directly to terraGIT. I don't bother anymore to beg the terrasync gatekeepers to accept my contributions.
6) Objects other build and send pull requests to terraGIT for inclusion. I dont' care if these are not distributed anywhere else. More importantly contribute objects individually and massively to terraGIT is much easier than filling the terrasync form and our requirements for inclusion are no way near that stringent either. Example: we allow shared textures, baking maps, larger textures, multiples objects per ac file (like multiple buildings in a larger ac) etc.
(if it works for FG it works for terraGIT)

Not related to Object path
7) The "Airports" directory has a few dozen changes of mine, and thousands of changes of P3000 now as well)
8) The Terrain directory is now a complete new rebuild
9) I am finishing details to include a NavData/apt.dat configuration to perfectly matches the available airport layouts build
10) I am working on terrain v2.5 to get rid of the nasty bugs that v2.3 has

That, I think sums it up

So basically everyone thinking that the objects or terraGIT are only those in terrasync + Project 3000 is heavily confused.

[laserman]

I suggest you add a readme file to

https://github.com/FGMEMBERS-TERRAGIT/terraGIT

that explains how to use terraGIT and/or links to this forum.

[IAHM-COL]

yes. Great suggestion!

[IAHM-COL]

I suggest you add a readme file to

https://github.com/FGMEMBERS-TERRAGIT/terraGIT

that explains how to use terraGIT and/or links to this forum.

Hi D-LASER

I added a README.md

Not the much entertaining instructive in the web, but it will help people to set up their systems

Feel free to improve it


https://github.com/FGMEMBERS-TERRAGIT/terraGIT


IH-COL

[laserman]

EDDS: taxiways & apron missing

I opened it in WED: same result
I did contact Jan, the author of that layout.

Scenery ID 13957 (WEDbot) is still good.