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

20041207: McIDAS MAKEMAP command (cont.)



>From: Robert Mullenax <address@hidden>
>Organization: Impact Weather
>Keywords: 200412062121.iB6LL7lI007399 McIDAS MAKEMAP

re: GEMPAK ASCII map file not read by MAKEMAP
> Here is the file.  

I extracted the map file you sent (midamer.ssf) and had no problems turning
it into a McIDAS map file:

MAKEMAP midamer.ssf MULLENAX TYPE=GEM WEST=NEG DEV=CCC
MAKEMAP: Begin
MAKEMAP* input file pathname: /home/mcidas/workdata/midamer.ssf
MAKEMAP* output file name: MULLENAX
MAKEMAP* WEST POS/NEG: NEG
MAKEMAP* MAKEMAP: Read # of points in segment:  40
MAKEMAP* Read segment; #pts:  40
MAKEMAP* MAKEMAP: Read # of points in segment:  49
MAKEMAP* Read segment; #pts:  49
MAKEMAP* MAKEMAP: Read # of points in segment:  13
MAKEMAP* Read segment; #pts:  13
MAKEMAP* Read segment; #pts:  13
MAKEMAP: #segments written:  3
MAKEMAP: Done

To verify the integrity, I plotted the map segments on top of a
map of Iowa:

MAP IA
MAP: Completed frame 50
 
MAP X 4 FILE=MULLENAX
MAP: Completed frame 50

The map appears to be mostly Iowa, but has some portions that extend
beyond the Iowan borders.

Now, the question is why this did not work on your system(s)!?

Since I had no probem with the map creation, the output you sent along
previously:

  makemap.k midamer.ssf OUTMIDAM TYP=GEM West=NEG DEV=CCC
  MAKEMAP: Begin
  makemap.k* input file pathname: /usr/mcidas/workdata/midamer.ssf
  makemap.k* output file name: OUTMIDAM
  makemap.k* WEST POS/NEG: NEG
  makemap.k* Read segment; #pts:
  makemap.k: ERROR writing OUTMIDAM

make me think that the file /usr/mcidas/workdata/midamer.ssf was not
readable by the user running the 'makemap.k' command.  Could this
be the case?

>Thanks a bunch!

No worries.

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.

>From address@hidden  Tue Dec  7 15:26:40 2004

>No, I double checked.  It is readable and writable by the user.
>I am stumped.  What version of McIDAS are you using, also OS
>and compilers?   

>From address@hidden  Tue Dec  7 16:13:14 2004

>Sorry..but I figured it out.  I had the file in the pwd, instead
>of in the MCDATA path.  I saw you referenced the workdata directory
>and that rang a bell.  It works fine now.

>Thanks,
>Robert


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.