Re: [Flightgear-devel] svg2ac

2006-03-02 Thread Julien Pierru
here is a screenshot of another airport (CYYZ - Toronto):http://flamebunny.homelinux.net/pics/CYYZ-1.jpgCurt do you think that svg2ac can be a good addition to Terragear. Maybe having svg2ac would make some features in svg2ac more performant, and it might make more sense to have it in there. What d

Re: [Flightgear-devel] svg2ac

2006-02-28 Thread Curtis L. Olson
Ampere K. Hardraade wrote: Curt, must TerrorGear be used if we want to make use those accurate taxiways from the airport diagrams? You can do what ever you like, however you like. I was just offering this up as one suggestion since it is a solvable problem and TerraGear includes one poss

Re: [Flightgear-devel] svg2ac

2006-02-27 Thread Ampere K. Hardraade
On Monday 27 February 2006 18:53, Curtis L. Olson wrote: > In TerraGear we avoid the polygon rendering problems you are seeing by > doing  a delauney triangulation ourselves and throwing away everything > outside the polygon boundary.  It would likely be a lot of effort on > your part to do the sam

Re: [Flightgear-devel] svg2ac

2006-02-27 Thread Curtis L. Olson
Julien Pierru wrote: Tiago and I have been working on a svg to ac converter to create airports from pdf files. Most of it is done, however we still have 2 problems, the first is that the code can't at the moment produce the accurate location of the origin (lat/long) and the second is that most

Re: [Flightgear-devel] svg2ac

2006-02-26 Thread Julien Pierru
Well we have an SVG parser that reads the input svg file and extract the polygons for the keywords buildings, runways & taxiways. The vertices are then stored and duplicated to create the "roof". The side polygons are computed by duplicating again 2 consecutive nodes that form an edge. The altitude

Re: [Flightgear-devel] svg2ac

2006-02-25 Thread Ampere K. Hardraade
On Friday 24 February 2006 01:59, Julien Pierru wrote: > Tiago and I have been working on a svg to ac converter to create airports > from pdf files. > Most of it is done, however we still have 2 problems, the first is that the > code can't at the moment produce the accurate location of the origin >