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

Home » Public Forums » archive » CGContour with and without cell_fill keyword
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: CGContour with and without cell_fill keyword [message #89926 is a reply to message #89925] Mon, 29 December 2014 09:32 Go to previous messageGo to previous message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
Jenny writes:

>
> Hi all, I'm using CGContour to make maps of vegetation index. I found my maps look quite different when I plot with or without the /cell_fill keyword as in the following lines:
>
> CGContour,lai,lon,lat,/cell_fill,c_colors=c_colors,Levels=us erLevels,max_value=dmax,min_value=dmin,C_CHARTHICK=2,/overpl ot, Color=black,missingvalue=nan
>
> CGContour, lai,lon,lat,c_colors=c_colors,Levels=userLevels,max_value=dm ax,$
> min_value=dmin,C_CHARTHICK=2,/overplot, Color=black,missingvalue=nan
>
> I know David suggests using cell_fill for projected maps or data with missing values, I thought that's just for making the map looks good, e.g. without holes etc., but not different maps.
>
> The map without the cell_fill keyword shows larger values (more realistic to me)than the map with the keyword. Does anybody knows why? Which map is correct?

The one with the CELL_FILL keyword is correct. The other is completely
wrong. :-)

http://www.idlcoyote.com/color_tips/fill_colors.html

Cheers,

David

--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: cgMap error!
Next Topic: _overloadMinus: what to do with invalid input?

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

Current Time: Fri Oct 10 08:57:54 PDT 2025

Total time taken to generate the page: 0.72086 seconds