getting off the ground - mapping packages [message #12986] |
Tue, 29 September 1998 00:00  |
John Gash
Messages: 1 Registered: September 1998
|
Junior Member |
|
|
All,
I was wondering if anyone would have a pointer to IDL sources
(free or commercial) for various map importers/readers (DLG, TIGER,
VPF, AVHRR, ADRG, DOQ, DTED, DEM,...), projection conversion
packages, and datum conversion packages.
I'm currently evaluating RSI's ENVI and would like to get a feel for
alternate IDL solutions that are not such a black box as ENVI is.
Idealistically, the solution would be to have a set of modules that
can be integrated into an application. Also, I would like to hear from
others that have customized or integrated ENVI into there environment.
Second, I would like to be able to access some CORBA services I've
written.
This superficially seems obtainable through IDL's external call. The
drawback however is, I would like to be able to retain the client
object handle for subsequent calls. I don't know enough about how
a C/C++ object file is treated within an IDL application. Are
dynamically
allocated memory from an external C++ object still available from
call to call? If so then I would think, I can use a static attribute
to retain the CORBA object? Has anyone done this? Thoughts?
Thanks
John
--
John D. Gash, jgash3@llnl.gov,
Voice/925.422.0708, Fax/925.423.8274, B/170, R/1125
Recycles: LLNL PO Box 808 MS L-103, Livermore CA, 94550
|
|
|
Re: getting off the ground - mapping packages [message #13073 is a reply to message #12986] |
Thu, 01 October 1998 00:00  |
rivers
Messages: 228 Registered: March 1991
|
Senior Member |
|
|
In article <36117330.B60BDF9A@llnl.gov>, John Gash <gash1@llnl.gov> writes:
> All,
>
> Second, I would like to be able to access some CORBA services I've
> written.
> This superficially seems obtainable through IDL's external call. The
> drawback however is, I would like to be able to retain the client
> object handle for subsequent calls. I don't know enough about how
> a C/C++ object file is treated within an IDL application. Are
> dynamically
> allocated memory from an external C++ object still available from
> call to call? If so then I would think, I can use a static attribute
> to retain the CORBA object? Has anyone done this? Thoughts?
I know that dynamically allocated memory in C code is still available from
call to call when using call_external. I am not sure about C++
____________________________________________________________
Mark Rivers (773) 702-2279 (office)
Argonne National Laboratory (630) 252-0422 (office)
Building 434A (630) 252-0405 (lab)
9700 South Cass Avenue (630) 252-1713 (beamline)
Argonne, IL 60439 (630) 252-0443 (FAX)
|
|
|