This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
> I tried Don's advice, subsetting the whole Data Source
> instead of each display during the Create Display step.
> I liked it at creation time, it worked great.
>
> Then I tried subsetting the Data Source to another longitude and it worked!
> The whole multi-layered display moved over to Africa.
> That was during the same session I think.
>
Brian,
It is not clear why your bundle not working. I created a simple bundle
and it worked. I did notice both bundles throw exception after the move. Can
you try to do a move after loading my bundle?
Yuan
> But now when I try to move the subset area using the saved bundle from that
> session, it fails.
>
> Yes I know about the "reload displays" checkbox in the Data Source Properties,
> and the "Reload Data" option under a right cluck of the Data Source, and
> Projections -->World to make plenty of room for any newly reloaded data to
> get displayed.
> But I keep getting Indonesia.
>
> I also tried pointing the bundle to use another model initialization time.
> (by checking "Change Data Sources" when opening the bundle and
> pointing it to a different datafile, from an initialization time 24h earlier).
> Again the functionality seems not to work, although it "should."
>
> Is it possible that some of the Properties of Data Sources are not being
> saved to bundles
> as they should be, specifically the Subset Area properties? Or perhaps each
> Display's Data Source
> and Subset Areas are being saved to the bundle, so that the Data Source
> Proerties
> (like its Subset Area) doesn't override these? Could it be fixed?
>
>
> 2. Reload Data Source doesn't seem to reliably force a reloading process. I
> get no response.
> Liklewise, the stop sign doesn't reliably force a stop to loading, I find.
> I get the feeling the GUI controls are like loose "suggestions" to IDV's
> processing engine,
> which simply ignores them sometimes. Is it like "fly by wire" in airplanes? I
> crave the
> feeling of a cable connecting my stick to the ailerons. Instead I push a
> button and hope
> something inside the system might respond. Am I wrong, are those linkages
> loose?
>
> Maybe some subprocess refuse to be interrupted, or refuse to start, and yet
> they don't
> actually return an error code? Is Java passive-aggressive?
>
> Is there a reason Don said "Theoretically, it should go get the data for the
> new region."?
> "Theoretically?"
>
> Thanks for any insights,
> Brian
> Here is the bundle I was working with.
>
>
>
> On Jan 5, 2013, at 6:02 PM, Don Murray wrote:
>
> So now I have nice multi-display bundles at one longitude,
> that I want to view at another longitude. (Asia <-> America).
> Or more generally for another spatial box.
> Keeping all the layers and color tables and etc. etc.
>
> Good luck. ;-)
>
> The best way to do this is to set the subset properties on the DataSource,
> not on each display. If you do that, then every display by default gets
> created using that spatial area. Right click on the DataSource in the Field
> Selector and then set the region you want.
>
> If you then want to view a different area, you can bring up the DataSource
> properties, change the region, make sure the reload displays checkbox is
> checked and click OK. Theoretically, it should go get the data for the new
> region. What it won't do is reproject the display to the new region.
>
> Brian Mapes
> address@hidden<mailto:address@hidden>
>
>
>
>
>
Ticket Details
===================
Ticket ID: LOC-679604
Department: Support IDV
Priority: Normal
Status: OpenAttachment:
test.xidv
Description: Binary data