Creating new drivers

classic Classic list List threaded Threaded
5 messages Options
Adam Adam
Reply | Threaded
Open this post in threaded view
|

Creating new drivers

So now that I'm more familiar with osgEarth, I was looking into writing a custom driver to test some obscure data.  Is it really as simple as say, copying the google plugin, modifying it, and building it?  Or is there some hidden section of code that I need to modify as well to allow the plugin to work with osgEarth?

Thanks,
Adam
gwaldron gwaldron
Reply | Threaded
Open this post in threaded view
|

Re: Creating new drivers

Adam,

Yes, using one of the built-in drivers as a template is a good idea. How obscure is your data? The GDAL driver can read a lot of formats.

Glenn
Glenn Waldron / Pelican Mapping
Adam Adam
Reply | Threaded
Open this post in threaded view
|

Re: Creating new drivers

One is VMAP0 that I can't get to load.  I can convert it to shp with OGDI and then use osggis to create the adapted model, but I can't get gdal to open it directly (currently trying noamer/bnd/polbndl.lft)

The other is a proprietary heightfield definition we have in house.

Thanks,
Adam
Adam Adam
Reply | Threaded
Open this post in threaded view
|

Re: Creating new drivers

Also, trying:

<![CDATA[
gltp:/vrf/home/adam/current_issues/osg_lib/vmap0/v0noa_5/vmaplv0/noamer 'polbndl@bnd(*)_line'
]]>


Like OGDI does, causes osgEarth to prefix the path infront of gltp.  
gwaldron gwaldron
Reply | Threaded
Open this post in threaded view
|

Re: Creating new drivers

In reply to this post by Adam
Gotcha. VMAP0 (and shape) are vector formats; osgEarth only supports raster/dem formats (today anyway). You will need a way to rasterize the data. Mapnik or Mapscript/C++ are two possibilities.

Glenn
Glenn Waldron / Pelican Mapping