Attaches a polyline to the given plot.
load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_code.ncl" function gsn_add_polyline ( wks  : graphic, plot  : graphic, x [*] : numeric, y [*] : numeric, res  : logical ) return_val [*] : graphic
One-dimensional arrays of the same length containing the X and Y coordinates of the polyline, and must be in the range of the X/Y coordinates of the data in plot. If you are adding the line to a map, then X should correspond to longitude values, and Y to latitude values.res
A variable containing an optional list of polyline resources, attached as attributes. Set to True if you want the attached attributes to be applied, and False if you either don't have any resources to set, or you don't want the resources applied.
An array or scalar representing the ids of each polyline attached will be returned. If you call any of the gsn_add_polygon, gsn_add_polyline, or gsn_add_polymarker functions in the same NCL script, you must assign each of their return values to a unique variable name. There's more information on this below in the examples section.
This function creates and attaches polylines to the given plot. If you have no missing values in your data, then only one polyline is attached. If missing values are encountered in the middle of the x and/or y arrays, then the points are ignored and the polyline will be disconnected at this pair. This causes multiple line segments to be created. This function will return a scalar or an array of type "graphic" depending on how many line segements are created.
This function only attaches the polyline(s) to the plot. Hence, you can only see the polylines when you call draw on the plot you attached them to.
If you are attaching a polyline to a plot and not seeing it on the plot, then you may want to check the draw order of the various elements of your plot. For example, if you are attaching the polyline to a map and you have mpFillDrawOrder set to "PostDraw", then this may cause your line to be hidden behind the map fill. You can also try specifying the draw order of the line itself, relative to elements of the plot you're attaching it to. The resource for this is tfPolyDrawOrder, and it can be set to one of "PreDraw", "Draw", or "PostDraw" (the default is "PostDraw"). See example 4 below.
The value(s) returned from this function must be assigned to a unique variable. This is necessary so that the polyline(s) "live" for the duration of the NCL script. This is especially imperative if the call to gsn_add_polyline is inside a function or procedure. Please see the examples section below for more information.
There are many line dash patterns available, and you can use the gsLineDashPattern resource to change the dash pattern. The default is a solid line. You can also create your own dash pattern using the NhlNewDashPattern function.
Previously, drawing a polyline around the equator, for example, could be specified using 2-element arrays. For example:
lnid = gsn_add_polyline(wks,map,(/0,360/),(/0,0/),lnres)Now, however, in order to eliminate a number of ambiguous situations and to make user code simpler in most cases, a new behavior has been introduced: the line between two points on the globe always follows the shortest path. In the example above, the behavior in NCL V6.2.0 leads to a 0-length line. The recommended approach now for drawing a line around the equator is to use four points, such that the distance from one to the next is always less than 180 degrees. For example:
lnid = gsn_add_polyline(wks,map,(/0,120,240,360/),(/0,0,0,0/),lnres)
gsn_polygon, gsn_polymarker, gsn_polyline, gsn_polygon_ndc, gsn_polymarker_ndc, gsn_polyline_ndc, gsn_add_polygon, gsn_add_polymarker, gsn_add_polyline, gsn_text, gsn_text_ndc, gsn_add_text, gsn_add_shapefile_polylines, gsn_add_shapefile_polymarkers, gsn_add_shapefile_polygons, NhlNewMarker, NhlNewDashPattern
This example shows how to add several lines to a plot, and how to make sure every call to gsn_add_polyline is returned to a unique variable using an array.
Note that this won't work if you add the lines from within an NCL function or procedure. In this case, you have to make sure the variables "live" outside the function or procedure by attaching them to a return value of a function, or to an input variable. This is demonstrated in example 2.
load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_code.ncl" begin ; ; Create workstation. ; wks = gsn_open_wks("x11","addlines") ; ; Create some dummy data. ; npts = 500 x = fspan(0,npts-1,npts) y = 500.+ 0.9 * x * sin(0.031415926535898*x) xyres = True xyres@gsnDraw = False xyres@gsnFrame = False xyres@gsnMaximize = True xy = gsn_y(wks,y,xyres) ; ; Initialize some data for adding several polylines to plot. ; plx = (/min(x),max(x)/) ply = (/300,300/) yvalues = (/ 300, 450, 510, 670, 720, 910/) colors = (/"orange","purple","red","blue","brown","green"/) nvalues = dimsizes(yvalues) plres = True ; ; When adding the polylines, Make sure each variable name is unique. ; You can do this via an array of type "graphic". ; dum = new(nvalues,graphic) do i=0,nvalues-1 plres@gsLineColor = colors(i) ply = (/yvalues(i),yvalues(i)/) dum(i) = gsn_add_polyline(wks, xy, plx, ply, plres) end do draw(xy) ; Drawing the XY plot will also draw the lines we just added. frame(wks) endExample 2
This example is identical to example 1 except the polylines are being added from within a procedure. This is not the most efficient way to do things, but this example is merely to show how to make sure the polylines "live" outside a function or procedure. If you don't do this, then you will get several warning messages of the form:
warning:TransformPostDraw: tfPolyDrawList element 0 is invalid warning:TransformPostDraw: tfPolyDrawList element 1 is invalidand you wouldn't see any polylines.
load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_code.ncl" ; ; This procedure adds a line to a plot, making sure that it is returned ; to a unique variable name, and that this variable is retained even ; outside this procedure call. ; procedure add_line(wks,plot,x,yval,line_color) local plres, str, y begin plres = True plres@gsLineColor = line_color ; Set the line color. y = (/yval,yval/) str = unique_string("polyline") ; "unique_string" will return a unique ; string every time it is called from ; within a single NCL session. ; ; You can then use this unique string as an attribute variable name ; that gets attached to the plot variable. This ensures that this ; value will live for the duration of the script. ; plot@$str$ = gsn_add_polyline(wks, plot, x, y, plres) end begin ; ; Create workstation. ; wks = gsn_open_wks("x11","addlines") ; ; Create some dummy data. ; npts = 500 x = fspan(0,npts-1,npts) y = 500.+ 0.9 * x * sin(0.031415926535898*x) xyres = True xyres@gsnDraw = False xyres@gsnFrame = False xyres@gsnMaximize = True xy = gsn_y(wks,y,xyres) ; ; Create X and Y values for polylines. Also set up color array. ; xvalues = (/min(x),max(x)/) yvalues = (/ 300, 450, 510, 670, 720, 910/) colors = (/"orange","purple","red","blue","brown","green"/) nvalues = dimsizes(yvalues) do i=0,nvalues-1 add_line(wks,xy,xvalues,yvalues(i),colors(i)) end do draw(xy) ; Drawing the XY plot will also draw the lines we just added. frame(wks) endExample 3
load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_code.ncl" begin ; ; Open X11 window ; wks = gsn_open_wks("x11","add_primitive") ; ; Create some dummy data. ; npts = 500 x = fspan(0,npts-1,npts) y = 500.+ 0.9 * x * sin(0.031415926535898*x) xyres = True xyres@gsnMaximize = True xy = gsn_y(wks,y,xyres) ; ; Create data for primitives. ; plx = x ply = 500. + 0.5 * x * sin(0.031415926535898*x) pgx = (/ 100., 200., 200., 100., 100. /) pgy = (/ 200., 200., 300., 300., 200. /) pmx = (/ 200., 150., 200., 250. /) pmy = (/ 900., 800., 700., 800. /) ; ; Set up three separate resource lists, although we could have ; used the same one here. ; pmres = True plres = True pgres = True plres@gsLineColor = "orange" plres@gsLineThicknessF = 2.0 pgres@gsFillColor = "Navy" pmres@gsMarkerIndex = 12 pmres@gsMarkerSizeF = 0.02 pmres@gsMarkerColor = "yellow" ; ; Make sure each variable name is unique. ; dum1 = gsn_add_polyline (wks, xy, plx, ply, plres) dum2 = gsn_add_polygon (wks, xy, pgx, pgy, pgres) dum3 = gsn_add_polymarker(wks, xy, pmx, pmy, pmres) draw(xy) frame(wks) ; ; Resize the plot and draw in the middle of the frame, and ; see how the primitives automatically get adjusted as well. ; setvalues xy "vpXF" : 0.3 "vpYF" : 0.7 "vpWidthF" : 0.4 "vpHeightF" : 0.4 end setvalues draw(xy) frame(wks) end
Example 4[This example will only work for any version of NCL later than V5.1.1.]
Try uncommenting the setting of the tfPolyDrawOrder resource below, and watch how this changes the order of when the yellow box is drawn with respect to the map outlines, map fill, and contour lines. You can also play with the cnLineDrawOrder and mpOutlineDrawOrder resources to further control the draw order of individual plot elements.
load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_code.ncl" load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_csm.ncl" begin ; ; Open a netCDF file and read some data. ; a = addfile("$NCARG_ROOT/lib/ncarg/data/cdf/meccatemp.cdf","r") t = a->t(0,:,:) ; Read first time step wks = gsn_open_wks("x11","draw_order") res = True res@gsnDraw = False res@gsnFrame = False res@gsnMaximize = True res@gsnAddCyclic = False ; Don't add longitude cyclic pt. res@mpOutlineOn = True ; res@cnLineDrawOrder = "Draw" ; These resources can be one of ; res@cnFillDrawOrder = "Draw" ; "PreDraw", "Draw" or "PostDraw". ; res@mpOutlineDrawOrder = "Draw" ; res@mpFillDrawOrder = "PreDraw" plot = gsn_csm_contour_map(wks,t,res) gres = True gres@gsFillColor = "yellow" ; gres@tfPolyDrawOrder = "Draw" ; this can be used for polylines, polymarkers, or polygons lat = (/-25, 35, 35, -25, -25/) lon = (/-45, -45, 5, 5, -45/) dum = gsn_add_polygon(wks,plot,lon,lat,gres) draw(plot) frame(wks) end