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.
Hi Adam- This is Don. > The text track data looks good. Thanks Jeff. I haven't tried the PS > issue but I assume that Don will contact me when this is fixed. I've been looking into this and don't have a solution. There are just too many lines in the maps. Even loading them in spikes my memory. I am doing some efficiencies in the fix I made last week, but those don't seem to matter on the capture. The PDF creates an XML object in memory with all the line commands in it and then turns it into a PDF. Apparently, the document is too big to hold in memory. Possible work arounds: - use other, lower resolution maps. ;-) - capture an image of the maps and then load it back in as a geolocated image to IDV. That way, it will get captured as an image. However, that will reduce the line quality. I'll keep looking into it. Don Murray > At 05:34 PM 11/29/2009, you wrote: > > > Here's the text point data file. > > > > > > >Hi Adam, > >Your text track data should work OK the latest nightly build. > > > >Sorry for any inconvenience. > > > >-Jeff > > > > > > > > > >Ticket Details > >=================== > >Ticket ID: LBC-866411 > >Department: Support IDV > >Priority: Normal > >Status: Open > > Ticket Details =================== Ticket ID: LBC-866411 Department: Support IDV Priority: Normal Status: Open