[Flightgear-devel] New fgfs-builder release; forking TerraGear
Hello! As there have been commits on TerraGear CVS I had to update the Custom Scenery patches, so therefore there is a new fgfs-builder release. This release is currently only available as a tar-ball from ftp://ftp.uni-duisburg.de/FlightGear/Misc_rag/fgfs-builder Note that this also includes several patches to TerraGear, some of which are build fixes, but also additions of tools such as ogrdecode and modifications to shape-decode. A tool for using DEM data in any GDAL-readable format called gdalchop is currently under development and will serve to allow using e.g. the CGIAR preprocessed SRTM data, which is delivered as GeoTIFF (with some unfortunate properties regarding the tiling). I had already submitted these patches to Curt, but it seems that within about 8 months there hasn't been a single slot of time in which he was able to review them. As I don't have access to TerraGear CVS and probably won't get any in the near future, I have switched to managing my additions locally with git, following the examples of others here on the list (Pigeon, John, Hans Fugal, ...). Keeping the patches up to date to CVS without having access to a proper VCS would become a PITA otherwise. Note that Custom Scenery also wants to go further on development and enhancement of TerraGear. We will synchronise with the official TerraGear CVS regularly and provided that acceptance of our patches is probable we will submit our changes back. However, given the past history of our submissions and the consistent refusal by Curt to give at least one of the team CVS write-access to make use of the VCS facilities (e.g. going out on a development branch), we now plan to actively fork TerraGear. This does not mean that additions and large changes may happen soon, but it just relieves us of an important management burden for bringing TerraGear forward and it should relieve Curt of our constant nagging. ;-) Just to clarify once more, in case it wasn't clear already: There is no bad mood behind this mail at all. We just want to move on. TerraGear is being criticized for its current state and to a large extent that criticism is justified. We would like to try enhancing it and making it more useable. A proper development environment is one requirement for the work that is ahead of us and while we would have liked to have done that within the already pretty sparsely used facilities, time has shown that it will not be possible so we're only creating a proper platform for our work. We are not breaking up with FlightGear, quite to the contrary. Cheers, Ralf - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New fgfs-builder release; forking TerraGear
Nice to hear! So the developement goes on? So it get's more userfriendly, and more independant of the platform? That's something we are really needing. I hope there is will be a healthy competeion between terragear and fgsd! Regards HHS --- Ralf Gerlich [EMAIL PROTECTED] schrieb: Hello! As there have been commits on TerraGear CVS I had to update the Custom Scenery patches, so therefore there is a new fgfs-builder release. This release is currently only available as a tar-ball from ftp://ftp.uni-duisburg.de/FlightGear/Misc_rag/fgfs-builder Note that this also includes several patches to TerraGear, some of which are build fixes, but also additions of tools such as ogrdecode and modifications to shape-decode. A tool for using DEM data in any GDAL-readable format called gdalchop is currently under development and will serve to allow using e.g. the CGIAR preprocessed SRTM data, which is delivered as GeoTIFF (with some unfortunate properties regarding the tiling). I had already submitted these patches to Curt, but it seems that within about 8 months there hasn't been a single slot of time in which he was able to review them. As I don't have access to TerraGear CVS and probably won't get any in the near future, I have switched to managing my additions locally with git, following the examples of others here on the list (Pigeon, John, Hans Fugal, ...). Keeping the patches up to date to CVS without having access to a proper VCS would become a PITA otherwise. Note that Custom Scenery also wants to go further on development and enhancement of TerraGear. We will synchronise with the official TerraGear CVS regularly and provided that acceptance of our patches is probable we will submit our changes back. However, given the past history of our submissions and the consistent refusal by Curt to give at least one of the team CVS write-access to make use of the VCS facilities (e.g. going out on a development branch), we now plan to actively fork TerraGear. This does not mean that additions and large changes may happen soon, but it just relieves us of an important management burden for bringing TerraGear forward and it should relieve Curt of our constant nagging. ;-) Just to clarify once more, in case it wasn't clear already: There is no bad mood behind this mail at all. We just want to move on. TerraGear is being criticized for its current state and to a large extent that criticism is justified. We would like to try enhancing it and making it more useable. A proper development environment is one requirement for the work that is ahead of us and while we would have liked to have done that within the already pretty sparsely used facilities, time has shown that it will not be possible so we're only creating a proper platform for our work. We are not breaking up with FlightGear, quite to the contrary. Cheers, Ralf - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Jetzt Mails schnell in einem Vorschaufenster überfliegen. Dies und viel mehr bietet das neue Yahoo! Mail - www.yahoo.de/mail - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New fgfs-builder release; forking TerraGear
Hi! Heiko Schulz wrote: Nice to hear! So the developement goes on? So it get's more userfriendly, and more independant of the platform? We don't have a development plan yet. There are some things we'd like to adress in the near future such as interfacing to GDAL and OGR, but there are some more things on our mind that we might start working on. Essentially the basic workflow of TerraGear will probably stay the same due to the possibility of parallelisation for automatic scenery building, but we'll probably need some more finetuned interface if we want to implement instantaneous and local scenery rebuilds from mapserver.flightgear.org on submission of new local data. I hope there is will be a healthy competeion between terragear and fgsd! As far as I view the relationship between fgsd they are more complementary than competitors. TerraGear is clearly better suited for automatic rebuilding as we will need it based on the scenery database, while fgsd is more suited for local work. So we will clearly not focus our work on competing with fgsd. I have to stress that there might not be big movement straight ahead, but currently I have some spare time to work on some TerraGear extensions, so it was the time to establish the work environment. Cheers, Ralf - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New fgfs-builder release; forking TerraGear
Nice to hear! So the developement goes on? So it get's more userfriendly, and more independant of the platform? That's something we are really needing. I hope there is will be a healthy competeion between terragear and fgsd! Regards HHS --- Ralf Gerlich [EMAIL PROTECTED] schrieb: Hello! As there have been commits on TerraGear CVS I had to update the Custom Scenery patches, so therefore there is a new fgfs-builder release. This release is currently only available as a tar-ball from ftp://ftp.uni-duisburg.de/FlightGear/Misc_rag/fgfs-builder Note that this also includes several patches to TerraGear, some of which are build fixes, but also additions of tools such as ogrdecode and modifications to shape-decode. A tool for using DEM data in any GDAL-readable format called gdalchop is currently under development and will serve to allow using e.g. the CGIAR preprocessed SRTM data, which is delivered as GeoTIFF (with some unfortunate properties regarding the tiling). I had already submitted these patches to Curt, but it seems that within about 8 months there hasn't been a single slot of time in which he was able to review them. As I don't have access to TerraGear CVS and probably won't get any in the near future, I have switched to managing my additions locally with git, following the examples of others here on the list (Pigeon, John, Hans Fugal, ...). Keeping the patches up to date to CVS without having access to a proper VCS would become a PITA otherwise. Note that Custom Scenery also wants to go further on development and enhancement of TerraGear. We will synchronise with the official TerraGear CVS regularly and provided that acceptance of our patches is probable we will submit our changes back. However, given the past history of our submissions and the consistent refusal by Curt to give at least one of the team CVS write-access to make use of the VCS facilities (e.g. going out on a development branch), we now plan to actively fork TerraGear. This does not mean that additions and large changes may happen soon, but it just relieves us of an important management burden for bringing TerraGear forward and it should relieve Curt of our constant nagging. ;-) Just to clarify once more, in case it wasn't clear already: There is no bad mood behind this mail at all. We just want to move on. TerraGear is being criticized for its current state and to a large extent that criticism is justified. We would like to try enhancing it and making it more useable. A proper development environment is one requirement for the work that is ahead of us and while we would have liked to have done that within the already pretty sparsely used facilities, time has shown that it will not be possible so we're only creating a proper platform for our work. We are not breaking up with FlightGear, quite to the contrary. Cheers, Ralf - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel __ Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern. www.yahoo.de/clever - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New fgfs-builder release; forking TerraGear
* Ralf Gerlich -- Friday 09 November 2007: I don't have access to TerraGear CVS and probably won't get any in the near future, I have switched to managing my additions locally with git, Maybe you don't want CVS access anymore, after you have dived into git, but I think you should have access to TerraGear, and maintain an alternative branch there. The main branch is a sensible area, and I understand why Curt is conservative here. It's not that you aren't trusted or deemed competent -- quite on the contrary --, but not all of your goals might be project goals yet. It looks like you aim for maximum quality and resolution, and I sure would like to have that too. But I tried your Bodensee tiles. Once or twice, and then never again. They made my machine crawl. If that became default fgfs scenery, then I'd have to leave the project (or ask people to donate a good machine). Of course, I understand that there's also a lot of room for improvements that don't force me to spend a few hundred Euro. :-) m. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New fgfs-builder release; forking TerraGear
Hi Melchior! Melchior FRANZ wrote: Maybe you don't want CVS access anymore, after you have dived into git, but I think you should have access to TerraGear, and maintain an alternative branch there. The main branch is a sensible area, and I understand why Curt is conservative here. I do understand Curt's point of view. It all started with the notion that git would be a good idea to use for managing my stuff outside CVS... It's not that you aren't trusted or deemed competent -- quite on the contrary --, but not all of your goals might be project goals yet. It looks like you aim for maximum quality and resolution, ...but then we realised exactly that we have possibly different aims. In principle this is a fork of course, but it also is a way to establish a good technical environment for our development. I have grown quite fond of git already. ;-) and I sure would like to have that too. But I tried your Bodensee tiles. Once or twice, and then never again. They made my machine crawl. If that became default fgfs scenery, then I'd have to leave the project (or ask people to donate a good machine). Oh, we know that problem and it's one of our many issues we are working on. But as you might know from 3D-modelling it's often easier to use more triangles than less. Most of that btw comes from the high additional triangles from the line data. Cheers, Ralf - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
