SPC Outlook Plot Line Width?

[sudokoko]

Hello,

I'm experimenting with the SPC Outlook example code, and I was able to customize the US States/Counties line width, but cannot seem to figure out how to change the line width/style of the outlook lines itself. Any way to do this?

Here's my code for the PlotGeometry/MapPanel portion of the program:

# Initialize geometry plotting
otlk = PlotGeometry()
otlk.geometry = day1_outlook['geometry']
otlk.fill = day1_outlook['fill']
otlk.stroke = day1_outlook['stroke']
otlk.labels = day1_outlook['LABEL']
otlk.label_fontsize = 'large'

...

us_counties = MetPyMapFeature('us_counties', '20m', linewidth=0.2, facecolor='None', edgecolor='gray')
us_states = MetPyMapFeature('us_states', '20m', linewidth=1.5, facecolor='None', edgecolor='black')
panel = MapPanel()
panel.title = 'SPC Day 1 Categorical Convective Outlook (Valid ' + time_issued + 'Z - ' + time_expire + 'Z)\nData Processed In: ' + generatetime + 's — Graphic Generated: ' + now + ''
panel.plots = [otlk]
panel.area = [-120, -75, 25, 50]
panel.projection = 'lcc'
panel.layers = [us_counties, 'ocean', 'lakes', 'land', us_states, 'coastline', 'borders']

Any guidance/assistance is much appreciated!

[dopplershift]

The options on PlotGeometry for controlling the appearance of the geometry (not the labels) are:

• stroke - edgecolor for polygons, line color for lines
• marker - What symbol is used for points
• fill - fill color for points/polygons

It doesn't appear we have any option for the stroke/line width. I can see adding it as stroke_width, but I do hesitate a bit because I don't want to add attributes for every matplotlib option. On the other hand, we probably should add it since, as you noted, we do have the option for the map features.

I think given that last sentence, I lean to adding it. @dcamron @kgoebber any thoughts?

[sudokoko]

Quick sub-question, is there any specific way to add a custom text box to a specific location? For example, like what is done below:

[kgoebber]

I think adding a stroke_width would be appropriate and inline with still keeping the options limited, but bring the most useful options through to the declarative syntax.

[dcamron]

I'm on board. There are some considerations in the geojson-specific space given that we could encounter a few different specs of stroke-width if users expect to drop that in the same way they can with these other properties. As long as we document it well, I think it's fine to start with just "this is just a pathway to mpl linewidth" and worth including. I'll open an issue from this discussion, thanks y'all!