"Curtis L. Olson" wrote:
> Martin Spott wrote:
>>I'm unable to dig into scenery building myself I have because I didn't
[...]
Oh man, so many mistakes in an EMail that short .... :-/
> Was my response a satisfactory answer for you then? I'm not sure I can
> parse your message here? You aren't building scenery yourself, but you
> are building a scenery building server??? I'm confused.
There's no reason to get into trouble :-))
What we've been talking about for a while is a PostGIS database where
the VMAP0 landcover data is being imported. After being done with this
we are enabled to export the whole stuff as shapefiles - one file for
each 'layer', each landcover type. This is why Ralf Gerlich started to
modify the shapefile decoder of TerraGear. Using shapefiles for this
type of data is convenient because the format is pretty common and
flexible enough for our needs.
In _my_ eyes - Ralf may comment on this if his goals are different, I
also invite Norman to share his thoughts - the first big step in the
process is to reach the state where Scenery can be built with landcover
data exported from the PostGIS database, featuring identical results as
building Scenery from stock VMAP0 files.
In a second step we're going to refine the landcover data by importing
work as Ralf and his friend already did for their area. We also might
think about importing the VMAP1 and/or TIGER data and whatever is
available under a license that meets our requirements. The whole
process gives us the ability to merge and refine landcover data from
many different sources - as we stick to a common interface by employing
a PostGIS database - while maintaining a stable interface to TerraGear.
The GSHHS shorelines for example are stored in the database as well.
This gives everyone the chance to adjust their favourite river mouth to
match the actual shoreline.
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
