FlightGear wiki

Mapserver: Difference between revisions

Page Discussion

Mapserver (view source)

Revision as of 19:16, 25 August 2016

8,385 bytes added ,  25 August 2016
no edit summary
No edit summary
 
(20 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Stub}}
{{Stub}}


[[File:Mapserver.jpeg|thumb|mapserver screenshot]]


First announced in April 2016 <ref> {{cite web
First announced in April 2006 <ref> {{cite web
   | url    = http://sourceforge.net/p/flightgear/mailman/message/13175363/
   | url    = http://sourceforge.net/p/flightgear/mailman/message/13175363/
   | title  = <nowiki>[Flightgear-devel] Mapserver interface</nowiki>
   | title  = <nowiki>[Flightgear-devel] Mapserver interface</nowiki>
Line 10: Line 11:
   | script_version = 0.25
   | script_version = 0.25
   }}
   }}
</ref>, the Landcover DB (database) was a web service/server that used to provide {{Abbr|GIS| geographical information system}} data (mainly shapefiles and elevation data) via a PostgreSQL/PostGIS database behind the MapServer and Scenemodels websites <ref>{{cite web
</ref>, the '''Landcover DB''' (database) was a web service/server that used to provide {{Abbr|GIS| geographical information system}} data (mainly shapefiles and elevation data) via a PostgreSQL/PostGIS database behind the '''MapServer''' and '''Scenemodels''' websites <ref>{{cite web
   | url    = http://sourceforge.net/p/flightgear/mailman/message/28592333/
   | url    = http://sourceforge.net/p/flightgear/mailman/message/28592333/
   | title  = <nowiki>[Flightgear-devel] PostGIS update @ Landcover-DB</nowiki>
   | title  = <nowiki>[Flightgear-devel] PostGIS update @ Landcover-DB</nowiki>
Line 18: Line 19:
   | script_version = 0.25
   | script_version = 0.25
   }}
   }}
</ref> for use by FlightGear-related tools like [[TerraGear]] and [[TerraGear GUI]] to help create scenery tiles for FlightGear.  
</ref> for use by FlightGear-related tools like [[TerraGear]] and [[TerraGear GUI]] to help provide data for creating scenery tiles for FlightGear.  
 
The primary intention of the Scenemodels repository is and has ever been from it's initial start to have a common repository which is collaboratively filled with the best scenery models we have for the entire world and which are 'compatible' with the GPL. <ref> {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/28839631/
  | title  = <nowiki>Re: [Flightgear-devel] Re : Re : Scenery web and scene models</nowiki>
  | author = <nowiki>Martin Spott</nowiki>
  | date  = Feb 15th, 2012
  | added  = Feb 15th, 2012
  | script_version = 0.25
  }}
</ref>
 
Before Martin Spott started the "'''Landcover-DB'''"-project we were having an ongoing dispute about wether the underlying land cover data or some "tweaking the data"-techniques in the TerraGear toolchain had been responsible for certain "unexpected effects" in FlightGear's Scenery.
 
Finally, to resolve this issue, Martin stuffed all our land cover data into a PostGIS database, put a {{wikipedia|MapServer}} as a frontend so everyone could have a look at what's been the actual input to our Scenery processing
<ref> {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/24018550/
  | title  = <nowiki>Re: [Flightgear-devel] Cliffs</nowiki>
  | author = <nowiki>Martin Spott</nowiki>
  | date  = Nov 20th, 2009
  | added  = Nov 20th, 2009
  | script_version = 0.25
  }}
</ref>


For the time being, the service has been discontinued <ref>{{cite web
For the time being, the service has been discontinued <ref>{{cite web
Line 26: Line 50:
   | date  = Jul 3rd, 2007
   | date  = Jul 3rd, 2007
   | added  = Jul 3rd, 2007
   | added  = Jul 3rd, 2007
  | script_version = 0.25
  }} </ref> <ref>{{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/28880489/
  | title  = <nowiki>Re: [Flightgear-devel] Looking at a nice project from outside</nowiki>
  | author = <nowiki>Martin Spott</nowiki>
  | date  = Feb 23rd, 2012
  | added  = Feb 23rd, 2012
   | script_version = 0.25
   | script_version = 0.25
   }}
   }}
Line 40: Line 71:
   | title  = <nowiki>Re: Is the Scenery Workflow broken?</nowiki>
   | title  = <nowiki>Re: Is the Scenery Workflow broken?</nowiki>
   | author = <nowiki>psadro_gm</nowiki>
   | author = <nowiki>psadro_gm</nowiki>
  | date  = Mar 23rd, 2016
  | added  = Mar 23rd, 2016
  | script_version = 0.25
  }}
</ref> <ref>{{cite web
  | url    = http://forum.flightgear.org/viewtopic.php?p=263629#p263629
  | title  = <nowiki> and terrasync are going </nowiki>
  | author = <nowiki>Torsten</nowiki>
  | date  = Nov 9th, 2015
  | added  = Nov 9th, 2015
  | script_version = 0.25
  }}
</ref>, and the underlying data are unavailable <ref>{{cite web
  | url    = http://forum.flightgear.org/viewtopic.php?p=280237#p280237
  | title  = <nowiki>Re: Is the Scenery Workflow broken?</nowiki>
  | author = <nowiki>Torsten</nowiki>
   | date  = Mar 23rd, 2016
   | date  = Mar 23rd, 2016
   | added  = Mar 23rd, 2016
   | added  = Mar 23rd, 2016
Line 45: Line 92:
   }}
   }}
</ref>)
</ref>)
The data now missing represents man-months of research and tests in GIS land, building and testing tools, building and maintaining the database, shaping all the data into its current form and loading it into the DB, researching and testing how to build detailed airport layouts with TerraGear, the same with OSM roads, ensuring a certain quality level for the land cover data as well as for the Scenemodels repository <ref> {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/28882536/
  | title  = <nowiki>Re: [Flightgear-devel] Looking at a nice project from outside</nowiki>
  | author = <nowiki>Martin Spott</nowiki>
  | date  = Feb 24th, 2012
  | added  = Feb 24th, 2012
  | script_version = 0.25
  }}
</ref>


Various more or less complete attempts at re-creating this infrastructure have been discussed/attempted meanwhile <ref> {{cite web
Various more or less complete attempts at re-creating this infrastructure have been discussed/attempted meanwhile <ref> {{cite web
Line 66: Line 123:
</ref>
</ref>


== Datasets ==
FlightGear core developer Torsten has since begun exploring alternatives, i.e. starting over with a fresh landcover database <ref>{{cite web
  | url    = http://forum.flightgear.org/viewtopic.php?p=280232#p280232
  | title  = <nowiki>Re: Is the </nowiki>
  | author = <nowiki>Torsten</nowiki>
  | date  = Mar 23rd, 2016
  | added  = Mar 23rd, 2016
  | script_version = 0.25
  }}
</ref>, including a BOINC-based approach <ref>{{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34666765/
  | title  = <nowiki>[Flightgear-devel] Continous, Distributed Generation of Terrain</nowiki>
  | author = <nowiki>Torsten Dreyer</nowiki>
  | date  = Dec 3rd, 2015
  | added  = Dec 3rd, 2015
  | script_version = 0.25
  }}
</ref> (see also elgaton's ongoing status updates in the archives <ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35273151/
  |title  =  <nowiki> Re: [Flightgear-devel] Ready for the 2016.3.1 release? </nowiki>
  |author =  <nowiki> Alessandro Menti </nowiki>
  |date  =  Aug 11th, 2016
  |added  =  Aug 11th, 2016
  |script_version = 0.40
  }}</ref> <ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35135139/
  |title  =  <nowiki> Re: [Flightgear-devel] SIMGEAR build error </nowiki>
  |author =  <nowiki> Alessandro Menti </nowiki>
  |date  =  Jun 3rd, 2016
  |added  =  Jun 3rd, 2016
  |script_version = 0.40
  }}</ref> <ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35110565/
  |title  =  <nowiki> Re: [Flightgear-devel] SIMGEAR build error </nowiki>
  |author =  <nowiki> Alessandro Menti </nowiki>
  |date  =  May 24th, 2016
  |added  =  May 24th, 2016
  |script_version = 0.40
  }}</ref>)- as well as creating surrounding infrastructure/tools like [[TerraFS]] <ref>{{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34970123/
  | title  = <nowiki>[Flightgear-devel] TerraSync, the lazy way: terrafs</nowiki>
  | author = <nowiki>Torsten Dreyer</nowiki>
  | date  = Mar 27th, 2016
  | added  = Mar 27th, 2016
  | script_version = 0.25
  }}
</ref>.
 
<references/>
 
== Status ==
(last updated in 04/2016)
 
Because of Torsten's work, we will be able to keep up the current service of maintaining a scenemodels database and regular updates to the distributed scenery.
We will freeze the terrain at its current state to improve the way we handle it today.<ref> {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34627039/
  | title  = <nowiki>[Flightgear-devel] Some thoughts regarding scenemodels and
terrascenery</nowiki>
  | author = <nowiki>Torsten Dreyer</nowiki>
  | date  = Nov 17th, 2015
  | added  = Nov 17th, 2015
  | script_version = 0.25
  }}
</ref>
 
Currently almost all of our scenery is maintained in a database and the resulting files are automatically generated. We try hard to avoid incompatible chunks of scenery that don't match at their corners. Martin Spott has alway tried to encourage people to maintain data upstream and we would like follow this path.<ref>{{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34921577/
  | title  = <nowiki>Re: [Flightgear-devel] Barcelona Scenery Pack</nowiki>
  | author = <nowiki>Torsten Dreyer</nowiki>
  | date  = Mar 9th, 2016
  | added  = Mar 9th, 2016
  | script_version = 0.25
  }}
</ref>
 
The vision is having a solid tool chain generating a world scenery from a detailed and common database.
 
Lets avoid gaps, elevation steps, overlapping and incompatible scenery tiles and work together on a one-fits-all scenery.
 
Until we have that, the suggestion is this:
Somebody provides self-contained and tested chunks of Terrain to be merged into Terrasync. That "somebody" is responsible for the usability of that terrain chunk. By "provide" I mean:
* make it available by rsync, tarball or anything else to be fetched, unpacked into terrasync without human interaction.
* Work out a method to discover new or outdated chunks
* Work out a method how to tell scenemodels-db which objects need new elevations
* Somehow "sign" the chunk so we have somebody who gurantees GPL compatibility
* Work out a method how to avoid mutual exclusive changes (one person updating EDFE, another improving EDDF [both share a tile])
 
Not everything need to be ready in detail but I'd like at least have an idea how this should work.
 
What will not be accepted is:
Follow some dropbox / gg-drive links, unpack an archive, guess what it might be, remove all side effects, do some hours of test flying, resetting object elevations by guessing the area etc. etc.
 
'''And always remember - at one day we will have Martin's landcover db back and hopefully a working toolchain. Whenever that happens, we build a new "world scenery". What happens to all those manual updates? I fear they are lost.'''<ref> {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34924793/
  | title  = <nowiki>[Flightgear-devel] New Scenery: How? Was: Barcelona Scenery Pack</nowiki>
  | author = <nowiki>Torsten Dreyer</nowiki>
  | date  = Mar 10th, 2016
  | added  = Mar 10th, 2016
  | script_version = 0.25
  }}
</ref>
 
<references/>
 
== History ==


Originally, Martin Spott and Ralf Gerlich's work was concentrated on making more and different datasources accessible for scenery creation.  
Originally, Martin Spott and Ralf Gerlich's work was concentrated on making more and different datasources accessible for scenery creation.  
Line 97: Line 257:


<references/>
<references/>
{{TerraGear}}
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/96911...103597"