X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 11 Mar 2017 06:53 AM by  anon
Can't standardize COLORBAR across multiple VECTOR maps
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:2
New Member


--
11 Mar 2017 06:53 AM
    I'm creating wind maps using the MAP, VECTOR, and COLORBAR and LEGEND functions, and I'm using them to build wind animations. THE PROBLEM: I cannot standardize the color bar and sample vector length across multiple wind maps. EXAMPLE-MAP-1 EXAMPLE-MAP-2 I'm using the TARGET option with COLORBAR to set the range: cbar = COLORBAR(TARGET=wind_vectors, blah) ... so, I cannot use the RANGE=[min,max] option with COLORBAR. Also, the LEGEND sample vector change size from map to map. I'm using: sample_vector= LEGEND(SAMPLE_MAGNITUDE=50, blah) I have also tried using a 'fake, fixed' maximum wind speed. My winds have a maximum allowable wind speed, so I added a 'dummy' data value that is larger than any of my winds. This means I will have a known MIN and MAX (say, 0 and 100 m/s) in my wind speed data. This approach has worked for me before, but it does not work when I use the TARGET option with COLORBAR. So, how do I standardize the COLORBAR range and the LEGEND sample vector across multiple wind maps when the wind speeds may have different min/max from one map to the next? I appreciate any advice. PD

    Deleted User



    Basic Member


    Posts:143
    Basic Member


    --
    12 Apr 2017 04:47 PM
    Are you using the AUTO_RANGE keyword when calling VECTOR. I think you should be able to limit the magnitudes for each of your maps to the same ranges and thus the colorbar should be consistent between them. -David

    Deleted User



    New Member


    Posts:2
    New Member


    --
    13 Apr 2017 10:07 AM
    Hi David, Yes, that works. To be honest, I kept overlooking that keyword since the phrase AUTO_RANGE implied (to me) that the data-->color scale would be AUTOmatically inferred from the input data. In fact, since it gives us control, that keyword should be named MANUAL_RANGE or something like that. Anyway - it works. Thanks for the feedback- PD
    You are not authorized to post a reply.