comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: GRIB data question
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: GRIB data question [message #78332 is a reply to message #78331] Thu, 10 November 2011 11:25 Go to previous messageGo to previous message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
David Fanning writes:

> Yeah, OK, I agree with this. But, how do you do it? How
> do you know what coordinate system the GRIB file creator
> had in mind when he or she created the file? How do you
> know what variables you have to change to get them into
> your right-handed coordinate system?

Incidentally, I think everyone agrees on a right-hand
coordinate system (maybe some of the planetary guys do
it differently on Mars or something). That's really not
the issue.

The issue is how do you start counting columns and rows.
The map projection people use a right-handed coordinate
system. It's just that they start counting from the
upper-left corner. Positive columns go to the right,
and positive rows go down (toward the origin of their
right-handed coordinate system, if you like).

My question is this: Is there a convention for how
and where one starts to count columns and rows for
a GRIB 2D array?

Cheers,

David



--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: changing the content of a NCDF file
Next Topic: Re: changing the content of a NCDF file

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu Oct 09 14:15:38 PDT 2025

Total time taken to generate the page: 2.63330 seconds