Hi Chase,
The DTEDLayer creates its own DTEDFrameCache and uses other DTED
components in the com.bbn.openmap.layer.dted package (DTEDFrame,
etc.). The DTEDFrameCacheLayer uses a
com.bbn.openmap.dataAccess.dted.DTEDFrameCache it finds in the
MapHandler as a centralized DTED repository, and uses the components
in the com.bbn.openmap.dataAccess.dted package
The components in the com.bbn.openmap.dataAccess.dted package are the
ones that are going to survive, since they have more flexibility to
handle DTED data that is stored with different naming conventions.
In the upcoming OpenMap 4.7 release, the DTEDFrameCacheLayer will be
renamed the DTEDLayer, and have the option of creating it's own
DTEDFrameCache or use the one it finds in the MapHandler. The other
DTED components in the com.bbn.openmap.layer.dted will be replaced by
the new package.
So, to answer you question, if you have other components that need
elevation data, use the
com.bbn.openmap.dataAccess.dted.DTEDFrameCache to get them that data,
and use the DTEDFrameCacheLayer to use that DTEDFrameCache instead of
creating a duplicate supply of data. If you just want one DTEDLayer
in your application, then using the old layer is fine.
- Don
On Dec 13, 2005, at 7:11 PM, Chase Barrett wrote:
> Hello all,
>
>
>
> I thought I had seen a posting that compared DTEDLayer and
> DTEDFrameCacheLayer, but after scanning the archives, I guess I’m
> just imagining things.
>
>
>
> In any case, what are the advantages/disadvantages of one layer
> over the other, and under what circumstances would you want to use
> each layer?
>
>
>
> Thanks,
>
> Chase
>
>
--
[To unsubscribe to this list send an email to "majdart_at_bbn.com"
with the following text in the BODY of the message "unsubscribe openmap-users"]
Received on Wed Dec 14 2005 - 08:54:10 EST