Sigh, it's true. I became aware of the OGR frontend just as the parser was
being completed :( Nothing like a good programming exercise to become
familiar with the code, though. Also, after playing with ogr2ogr, I have a
couple issues.
The first, is that the parser has a couple bugs. These can be fixed:
Here's an image showing some of the polys being closed with linear segments
instead of bezier.
http://dl.dropbox.com/u/29968727/Screenshot-Quantum%20GIS%201.7.0-Wroclaw.png
I had this exact same issue with my parser for a while, I'll look at the ogr
importer to see if I can submit a fix.
This image shows a different issue, which I have not seen with my parser.
http://dl.dropbox.com/u/29968727/Screenshot-Quantum%20GIS%201.7.0-Wroclaw-1.png
The poly holes should be circular, and it looks like there's an extra line
being added. Not sure if this is something similar to the above or not.
Another reason we may wish to stay with my parser is that it offers a bit
more flexibility. I plan on allowing options to set how many segments to
break curves into, (and possibly using more segments for curvier sections
than straighter sections) to try to optimize for the number of polys. I
didn't see any way to pass parameters to the ogr2ogr importer
I have some experience writing GRASS modules, and I noticed some were being
added to terragear-cs a few months ago. one of which looked like a skeleton
for a btg file exporter. Is anyone actively working on this? If not, I can
continue down that path.
I see qgis can only use grass modules "if QGIS was started from a GRASS
shell or if a GRASS mapset was opened from QGIS". Otherwise, we will need
both a grass module and a qgis plug-in. I imagine both will be able to
share most of the code.
I'd really like to be able to add something of use to the project, as I
really enjoy flightgear. In the past couple of years, there have been so
many new improvements to so many systems, yet the scenery / terrain still
seems to get the least attention (no fault on any of the developers, I just
think it's the most intimidating piece of the project) A one step at a time
approach is certainly necessary, and the 8.50 airport format looked like the
most achievable target.
Feel free to ping me on any item you feel is needed, but don't have time
for. I can generally dedicate ~8-10 hours a week (especially heading into
winter)
On Sun, Sep 4, 2011 at 6:20 PM, Martin Spott <[email protected]> wrote:
> HB-GRAL wrote:
>
> > To get XPlane gpl airport data into a postgres/postgis database as ESRI
> > shapes you can use the ogr2ogr gdal plugin written by Robin Peel [...]
>
> s/Robin Peel/Even Rouault/
>
> I know because we've been exchanging a couple of EMails over the past three
> years while chasing a few bugs in his implementation ;-)
>
> BTW, I'm really wondering why this forum user "Psadro" decided to invent
> his
> own v8.50 apt.dat-parser because, according to his explanations, he's doing
> exactly what's already implemented in the corresponding OGR-frontend.
>
> Cheers,
> Martin.
> --
> Unix _IS_ user friendly - it's just selective about who its friends are !
> --------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Flightgear-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
