I was thinking of the more general situation and packagin having had to deal with it, but I'll take a simpler solution anytime. Thanks for pointing out how it can apply in this case...
| Chris Pelkie <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 07/08/2004 07:23 AM
|
To: [email protected] cc: Subject: Re: [opendx-users] stiching together DEMs |
Lloyd gave a correct and useful solution, but I think it's more complex
than needed in this case.
Karl, you have .dx files already, of 'same structure", thus suitable for
MultiGrid. So, try this first. Just make a text file with the following
contents. This assumes your DEM files are called "DEM_00.dx", "DEM_01.dx",
"DEM_10.dx", and "DEM_11.dx". The names of course don't matter, nor does
the implied tiling.
# clip here ---------------
# multigrid declaration
object "DEM_group" class multigrid
member 0 file DEM_00.dx # note: no quotes around filename
member 1 file DEM_01.dx
member 2 file DEM_10.dx
member 3 file DEM_11.dx
# clip here ---------------
That's it! Save the file as "DEM_group.dx", for simplicity, in the same
path as the member files. Import that file, and everything you've done so
far should continue to work, except now you'd see 4 patches, located
wherever their positions put them (tiled, overlapped completely, partially,
whatever).
At 08:23 PM 07/07/04 -0400, you wrote:
>You need to have an individual Import for each DEM. You then pass all of
>them to CollectMultiGrid to "stitch" them together, assuming that the DEMs
>represent individual tiles, which is common. If there is overlap, then
>you'll need to mark which cells are to be used in those areas. If you want
>to make this more elegant, you can put the Import into a For loop,
>appending to CollectMultiGrid with each iteration, and then make a macro
>out of it. The input to the macro would indicate the number of DEMs, path
>and file name information, etc.
>
>
>
>|---------+---------------------------------------->
>| | Karl Pohlmann <[EMAIL PROTECTED]> |
>| | Sent by: |
>| | [EMAIL PROTECTED]|
>| | son.ibm.com |
>| | |
>| | |
>| | 07/07/2004 07:02 PM |
>| | Please respond to |
>| | opendx-users |
>| | |
>|---------+---------------------------------------->
>
> >---------------------------------------------------------------------------------------------------------------------------------------------|
> |
> |
> | To: [email protected]
> |
> | cc:
> |
> | Subject: [opendx-users] stiching together
> DEMs
> |
> |
> |
>
> >---------------------------------------------------------------------------------------------------------------------------------------------|
>
>
>
>
>Hello again,
>
>First of all, I appreciate all the help that I have received on this
>forum over the past several weeks. I've been able to get up and running
>with OpenDX very quickly as a result.
>
>My question is simple: Is there a way to load multiple, same structure
>data sets without having to set up an input module for each one? In
>this case I am importing digital elevation data (converted from DEM to
>DX format using dxconvert). Each dataset covers a subset of the final
>area in the visualization, and my understanding of the dataflow model
>suggests that each successive DEM that I import will replace the last
>one in the final image. To get around this, my DX program includes an
>import module for each one of the six or eight DEMs that I need. This
>gets rather messy so I'm wondering if there is a more elegant solution?
>
>Thanks in advance,
>
>Karl Pohlmann
>
>
>--
>Karl Pohlmann
>Associate Research Hydrogeologist
>Division of Hydrologic Sciences
>Desert Research Institute
>755 East Flamingo Road, Las Vegas, NV 89119
>Phone: 702-862-5485 Fax: 702-862-5427
>E-mail: [EMAIL PROTECTED]
>http://www.dri.edu/People/karl/
> - - - __o
> - - - - _`\<,_
> - - - - - (_)/ (_)
Chris Pelkie
Scientific Visualization Producer
618 Rhodes Hall, Cornell Theory Center
607-254-8794
