The Web Airport Generator doesnt work. The last step, downloading the file, fails with 404 error, unable to download the file
PS: It was the wrong file, the code dont accept 3d data, 2D worked fine
pb321 wrote in Fri Oct 26, 2018 4:34 am:I checked the coordinates of USMM and found we are placing things in the wrong folders. According to what I found tonight, USMM's coordinates are: N65°28.93' / E72°41.90' , so I think the subfolders should be, \e070n60\e073n65\. To be honest, I may not have the folders correct. Please check FG documentation to see how it works for your part of the world.
pb321 wrote in Sun Oct 28, 2018 3:03 am:So would it make sense to extract the apt.dat.gz found in FG/data/airports/ , then add the apt.dat info from World Editor for the two airports, then create a new apt.dat.gz? (...for local use only but would it allow positioning an aircraft at the airports from within FlightGear? Or would it create other problems? To get Metar data, could the airports be added to the metar.dat.gz in a similar manner?
pb321 wrote in Sun Oct 28, 2018 3:03 am:Would the "mix" of airport and terrain that you refer to, WoodSTokk, be the same or worse than what you would see when using the online Web Airport Generator with airports that are already in FlightGear's apt.dat.gz file?
Users browsing this forum: No registered users and 5 guests