Bounty/Flightgear Scenery Designer 2: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
m (Update forum links)
(Copy editing; +cat: Bounty)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
{{infobox Bounty
<!--{{infobox Bounty
|name = Flightgear Scenery Designer 2
|name = Flightgear Scenery Designer 2
|type = Additional software
|type = Additional software
Line 5: Line 5:
|money = US$25
|money = US$25
|status = open
|status = open
}}
}}-->


To claim this bounty, the developer must present a version of '''FlightGear Scenery Designer''' (FGSD), which includes all modifications described in the first FGSD bounty [[Flightgear Scenery Designer 1]] ''and'' additionally implements all features the original FGSD author had planned but not completed.


== Synopsis ==
== Synopsis ==
Implement "missing" features
Implement "missing" features


== Features ==
As of today (5 January 2012) the features the original FGSD author had planned are:
* Define arbitrary contour for maps
* Display map fragments according to their contour
* Import FG scenery by airport and radius
* Show altitude by colors
* Use curves to define land use contours and water bodies
* Use curves to define roads, railways and power lines
* Create photo-scenery
* Define taxiway network for FG AI Traffic
* Build airports
* Create building models according to templates and measures made on map
* Import OpenFlight models and export them to the FlightGear scenery format


== Description ==
The developer must present binary packages for current Windows and MAC OS versions as well as either present binary packages for the major Linux distributions (namely Ubuntu, OpenSuse and Debian) or present a sufficient documentation for compiling that enables an averagely experienced Linux user to compile the source him-/herself.
 
To claim this bounty, the developer must present a version of FGSD, which includes all modifications described in the first FGSD bounty [[Flightgear Scenery Designer 1]] and additionally implements all features the original FGSD author had planned but not completed. As of today (05JAN2012) these are:
<ul><li>Define arbitrary contour for maps</li>
<li>Display map fragments according to their contour</li>
<li>Import FGFS sceneries by airport and radius</li>
<li>Show altitude by colors</li>
<li>Use curves to define land use contours and water bodies</li>
<li>Use curves to define roads, railways and power lines</li>
<li>Create photo-sceneries</li>
<li>Define taxiway network for FGFS AI</li>
<li>Build airports</li>
<li>Create building models according to templates and measures made on map</li>
<li>Import OpenFlight models and export them to the FlightGear scenery format</li></ul>
 
The developer must present binary packages for current Windows and MAC OS versions as well as either present binary packages for the major Linux distributions (namely Ubuntu, Opensuse and Debian) or present a sufficient documentation for compiling that enables an averagely experienced Linux user to compile the source him-/herself.
 


== License ==
== License ==
The code must be released as Open Source under the GPL or a compatible license
The code must be released as Open Source under the GPL or a compatible license


== Claiming the bounty ==
== Claiming the bounty ==
To claim this bounty, the developer must contact the maintainer and announce the intention to work on this project. The developer then has 2 weeks time to present some progress. Then the task will be assigned to the developer and the assignment documented in the Wiki. When the developer is finished, he/she will contact the maintainer and present the results. The maintainer will together with the other contributors decide, if the result will be accepted and the bounty will be paid. Acceptance or non-acceptance will be documented in the Wiki as well.
To claim this bounty, the developer must contact the maintainer and announce the intention to work on this project. The developer then has 2 weeks time to present some progress. Then the task will be assigned to the developer and the assignment documented in the Wiki. When the developer is finished, he/she will contact the maintainer and present the results. The maintainer will together with the other contributors decide, if the result will be accepted and the bounty will be paid. Acceptance or non-acceptance will be documented in the Wiki as well.


== Contributors ==
== Contributors ==
sgofferj (maintainer) - US$25 - payable via PayPal - stefan DOT gofferje AT gmx DOT de
sgofferj (maintainer) - US$25 - payable via PayPal - stefan DOT gofferje AT gmx DOT de


== Status ==
== Status ==
Open
Open


== Related content ==
* {{forum link|t=14895|title=Bounty: Flightgear Scenery Designer}}
* [[Bounty/Flightgear Scenery Designer 1]]


== See also / related ==
[[Category:Bounty]]
 
*[http://forum.flightgear.org/viewtopic.php?f=18&t=14895 Forum thread about this bounty]
*[[Bounty/Flightgear Scenery Designer 1]]

Latest revision as of 04:52, 17 March 2020


To claim this bounty, the developer must present a version of FlightGear Scenery Designer (FGSD), which includes all modifications described in the first FGSD bounty Flightgear Scenery Designer 1 and additionally implements all features the original FGSD author had planned but not completed.

Synopsis

Implement "missing" features

Features

As of today (5 January 2012) the features the original FGSD author had planned are:

  • Define arbitrary contour for maps
  • Display map fragments according to their contour
  • Import FG scenery by airport and radius
  • Show altitude by colors
  • Use curves to define land use contours and water bodies
  • Use curves to define roads, railways and power lines
  • Create photo-scenery
  • Define taxiway network for FG AI Traffic
  • Build airports
  • Create building models according to templates and measures made on map
  • Import OpenFlight models and export them to the FlightGear scenery format

The developer must present binary packages for current Windows and MAC OS versions as well as either present binary packages for the major Linux distributions (namely Ubuntu, OpenSuse and Debian) or present a sufficient documentation for compiling that enables an averagely experienced Linux user to compile the source him-/herself.

License

The code must be released as Open Source under the GPL or a compatible license

Claiming the bounty

To claim this bounty, the developer must contact the maintainer and announce the intention to work on this project. The developer then has 2 weeks time to present some progress. Then the task will be assigned to the developer and the assignment documented in the Wiki. When the developer is finished, he/she will contact the maintainer and present the results. The maintainer will together with the other contributors decide, if the result will be accepted and the bounty will be paid. Acceptance or non-acceptance will be documented in the Wiki as well.

Contributors

sgofferj (maintainer) - US$25 - payable via PayPal - stefan DOT gofferje AT gmx DOT de

Status

Open

Related content