Template talk:Forecast/US

From Wikivoyage
Jump to navigation Jump to search

Text[edit]

Wow, schnazzy! Can I make one suggestion? The text as of now sounds like the data should be included in the box... can we change the line to read something like "Check the forecast for Seattle at NOAA" ? – (WT-en) cacahuate talk 14:42, 21 May 2007 (EDT)

Too obtrusive?[edit]

This seems like a useful template, but in the articles it's used on it generally looks out of place and a bit too noticeable - double border, two images, bold text, and it takes up a significant part of the width of the article text column. Can we make it a bit less obtrusive by removing one of the images and reducing the border? Something like:

CURRENT:

noframe

Check the weather forecast for {{{1}}} from NOAA.

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

PROPOSED:

noframe

Check the weather forecast for {{{1}}} from NOAA.

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

-- (WT-en) Ryan • (talk) • 00:10, 15 June 2007 (EDT)

Updated. I've added the old format above for reference. -- (WT-en) Ryan • (talk) • 03:29, 16 June 2007 (EDT)

Embed GEO template into Forecast template[edit]

See the page Graffiti wall/SubPage Test for example. That page is using a test version of Template:Forecast. The test template is Template:Graffiti_wall. It adds the geo template by embedding

{{geo|{{{2}}}|{{{3}}}}}

into a copy of Template:Forecast.

The result is adding a "map" link in the toolbox on the left.

This change immediately will add the map link to any page which already includes coordinates in the forecast template. If the page already includes both the geo and the forecast template, then the last one on the page is used for the map link. Since geo template is normally at the bottom of the page and forecast template is placed under climate, this means that the existing "geo" coordinates would continue to be used for the map, in case of conflict.

This should also work for the Template:ForecastNOAA. The Template:ClimateFahrenheit could also be modified, but would require placing the geo template inside the #if which checks for presence of coordinates. I have not tested either of these additional templates, but no reason not to work. I believe these are the only other two templates in actual use which include latitude/longitude coordinates.

This would automatically add the map link to pages which already have NOAA weather links but not the geo template. Pages such as Anchorage, Corpus Christi, Pittsburgh.

Note: The GEO template does not work in the wikivoyage namespace, so adding it to wikivoyage:Grafitti wall will not demonstrate the map link. That's why I used the subpage test page in MAIN:. --Bill in STL 20:38, 20 August 2010 (EDT)

Link Broken[edit]

The link created by this template does not work any longer. I checked on several pages, and none work. AHeneen (talk) 20:19, 29 January 2013 (UTC)[reply]

Swept in from the pub

Template:Forecast[edit]

Just bringing this up here, so it doesn't go unfixed. The link created by this template doesn't work. Someone needs to determine the right link for NOAA forecasts, and adjust the template accordingly. The link created by Template:ForecastNOAA does work. AHeneen (talk) 20:24, 29 January 2013 (UTC)[reply]

Yes Done. Thanks for the heads up. Fixed it. --Rogerhc (talk) 23:15, 29 January 2013 (UTC)[reply]