Problem with small area on projected map

classic Classic list List threaded Threaded
7 messages Options
Xtof Xtof
Reply | Threaded
Open this post in threaded view
|

Problem with small area on projected map

Hi all,

I'm using BIL file for elevations on a projected map.

If I'm defining a large area (using ProfileOptions) inside the boudaries of the BIL file, loading is fast and all is well displayed.


But if I'm defining a smallest area, buildings are loaded much slower and elevations don't seem to be taken into account anymore.


Any idea of the problem?

My configuration:
osgEarth 2.9.0RC1 / OSG 3.4.1 / GDAL 2.1.4 / Visual Studio 2010

Thanks,
Christophe
remoe remoe
Reply | Threaded
Open this post in threaded view
|

Re: Problem with small area on projected map

Hi

Do you have an earth file to reproduce this?

Cheers
Remo Eichenberger, Switzerland, @crocomer
ago ago
Reply | Threaded
Open this post in threaded view
|

Re: Problem with small area on projected map

In reply to this post by Xtof
Hi Xtof

  I've tested, More calculations may be required for irregular projections.eg UTM, which is slower, Mercator projection and geographic coordinates faster.

  For example, in the tests directory, boston_projected.earth is slower than boston_buildings.earth.
SXEarth,a free osgEarth GUI Editor and Flight Simulation.

Email: seegogo@126.com
SXEarth download: http://www.sxsim.com/en/

Xtof Xtof
Reply | Threaded
Open this post in threaded view
|

Re: Problem with small area on projected map

In reply to this post by Xtof
Hi,

In both cases, the same projected coordinate system is used, only the profile bounds differs.
And I was able to reproduce the problem with earth files:
Chicago_Projected_LargeArea.earth -> OK
Chicago_Projected_SmallArea.earth -> NOK

You could find earth files and data here:
Chicago_Projected

Thanks,
Christophe
Xtof Xtof
Reply | Threaded
Open this post in threaded view
|

Re: Problem with small area on projected map

In reply to this post by Xtof
After a bit more investigations, the problem appears when reducing the ymax value of the bounds:
osgEarth::Bounds(447000., 4637000., 450000., 4639650.); -> OK
osgEarth::Bounds(447000., 4637000., 450000., 4639600.); -> NOK
Reducing xmax value has no impact.
Xtof Xtof
Reply | Threaded
Open this post in threaded view
|

Re: Problem with small area on projected map

Any update on this topic?
Xtof Xtof
Reply | Threaded
Open this post in threaded view
|

Re: Problem with small area on projected map

Sorry to come again, but isn't there a fix for this problem?