[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NMAP2, restore files, and streamlines.



Steve (and GEMPAK support),

I have been attempting to modify some of the NMAP2 restore files for use with 
streamlines; specifically, attempting to decrease the number of lines drawn.

This would be analogous, for instance, to using the STREAM keyword in gdstream 
- such that STREAM=0.5 or similar.

I've placed the STREAM keyword in my restore file, varying the value - with no 
effect.  I then have tried using the SKIP or CINT . . . nothing changes the 
output rendered.

So - how does one control the number of lines in a restore file for NMAP grid 
functions?
-- 
Stonie R. Cooper
Planetary Data, Incorporated
(402) 727-6599

From address@hidden  Wed Mar 17 09:06:04 2004
Return-Path: <address@hidden>
Received: from goose.inebraska.com (goose.inebraska.com [199.184.119.14])
        by unidata.ucar.edu (UCAR/Unidata) with ESMTP id i2HG64rV001719;
        Wed, 17 Mar 2004 09:06:04 -0700 (MST)
Keywords: 200403171606.i2HG64rV001719
Received: from [192.168.57.7] (oma-dsl-dynamic-206-222-202-066.inebraska.com 
[206.222.202.66])
        by goose.inebraska.com (8.12.10/8.12.10) with ESMTP id i2HG63wC029813;
        Wed, 17 Mar 2004 10:06:03 -0600 (CST)
From: Stonie Cooper <address@hidden>
Organization: Planetary Data, Incorporated
To: Steve Chiswell <address@hidden>
Subject: NMAP2, restore files, and streamlines - DISREGARD.
Date: Wed, 17 Mar 2004 16:05:36 +0000
User-Agent: KMail/1.6.1
Cc: GEMPAK support <address@hidden>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <address@hidden>
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on 
        laraine.unidata.ucar.edu
X-Spam-Level: 
X-Spam-Status: No, hits=-4.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
        version=2.63

Steve (and GEMPAK support),

Crap - STREAM was listed further down the restore file, clobbering my attempts 
at editing.  Disregard - I have it working now.
-- 
Stonie R. Cooper
Planetary Data, Incorporated
(402) 727-6599