[osg-users] FW: Image border duplicated
Riepl, David M
> All,
>
> I have created a terrain database using osgdem with DTED .dt1 and 5m
> imagery. I have osgdem reproject my source data from geographic to
> transverse mercator projection using --cs and proj4 parameters. Here
> is what I am using:
> "C:\locationof\osgdem" -d D\DTEDtest\mosaic\dtedmosaic.tif -t
> D:\SourceData\Imagery\OTW-5m --cs "+proj=tmerc +lat_0=42.5
> +lon_0=-115.75 +k=0.9996 +x_0=0 +y_0=0 +datum=WGS84" -o
> output_3dmap.ive -l 99
>
> There are 100 individual pieces of imagery used as the input source.
> But I did not mosaic the imagery as that is impractical when
> attempting to reach 5m output resolution for an area as large as mine.
> Problem is, when looking at the point where the edges of 2 images meet
> there is duplication where the images overlap. I have attached a
> screenshot. So for example, there is a road at the top of the
> image...you can plainly see that the section of road is repeated.
> Same with the river below it.
> <<Overlap-duplicated.jpg>>
> I see this duplication on ALL the east/west edges of all the
> images...I haven't seen this behavior on the north/south edges. The
> source images do overlap. But if I check them in a viewer they
> overlap perfectly, with no weird offset or anything...and they are the
> same projection. So I don't see how that could be the issue.
>
> Thoughts? Advice? Help?
>
> David Riepl
> Visualization IG/DB Team
> Training Systems & Services
> The Boeing Company
> 314-777-4741
>
Robert Osfield
I have seen this problem with osgdem before. Which version of
osgdem/VPB are you using?
Robert.
> _______________________________________________
> osg-users mailing list
> osg-...@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>
_______________________________________________
osg-users mailing list
osg-...@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Robert Osfield
> Hi David,
>
> I have seen this problem with osgdem before. Which version of
> osgdem/VPB are you using?
Sorry typo, I *haven't* seen this problem with osgdem before.
Robert.
Riepl, David M
I am using osgdem associated with osg 1.2 because that is the version
the target Image Generator software is using.
David Riepl
Visualization IG/DB Team
Training Systems & Services
The Boeing Company
314-777-4741
Robert Osfield
On Feb 19, 2008 7:51 PM, Riepl, David M <david....@boeing.com> wrote:
> I am using osgdem associated with osg 1.2 because that is the version
> the target Image Generator software is using.
A lot has changed to osgdem since OSG-1.2, its now part of separate
project VirtualPlanetBuilder and this is my focus, as well as the
OSG-2.x series.
I don't have your data, nor OSG-1.2 installed so can't test the
directly for the type of problem you have. Since you have the data
that reproduces the problem I'd suggest trying VPB-0.9.5 + OSG-2.3.4
or SVN of both out to see if it fixes the problem when using this
data.
If this does fix the problem then you could create the database as
.osg and associated imagery to retain compatibility with OSG-1.2 (.osg
files are pretty resilient w.r.t forward/backwards compatibility which
.ive are very sensitive to version). .osg aren't appropriate for
paging, so with OSG-1.2 you could then batch convert the .osg files to
.ive files. A bit long winded, but should hopefully be workable.
The other route would be to upgrade the IG to OSG-2.x, this needn't be
that complicated as the bulk of original the OSG API remains the same,
libs like osgProducer while not in the core anymore are still
available as a separate project. Also porting to osgViewer needn't be
that complicated for many apps - it all depends on how much Producer
vs osgProducer code you used in the app.