Hi Curt! Curtis Olson wrote: > The decision was made to go with vmap0 entirely. We gave up accuracy > around the coast lines, but we gained a much more consistent picture of > the world ... with no major missing bits and no overlapping sections.
Thanks for jumping in with that explanation. Anybody interested in details is invited to look at the data available on mapserver.flightgear.org. The database includes both the VMAP0 data and the GSHHS data. You may notice that at some points VMAP0 waterways supposed to flow into the ocean or a lake do not reach the shore as defined by GSHHS. I can imagine the disappointed comments coming up with if we used that set with the next scenery build... ;-) The database gives us the possibility to adjust these points, but it will be a whole lot of work and we first want to get the most current version of GSHHS into the database. Currently there is no shapefile version of GSHHS 1.5, which was available for 1.3, so we need to get some tool to import the custom binary format of GSHHS into the database, including the handling of shorelines crossing the dateline, etc (e.g. Eurasia continent definition). Yes, this is on my TODO-list, and no, it's not on top. To make the long story short: Don't expect GSHHS shorelines consistent with the rest of our data with the next scenery release. Cheers, Ralf ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
