Talk:Blue spruce
| This It is of interest to the following WikiProjects: | ||||||||||||||||||||||||
| ||||||||||||||||||||||||
Ellipse Reference
The reference to The Ellipse needs a source. I also failed to sign my last two edits, correcting the misspelling and fixing the formatting. Jo7hs2 (talk) 21:50, 13 December 2008 (UTC)
- Dealt with. Jo7hs2 (talk) 15:14, 1 May 2009 (UTC)
Requested move
- The following discussion is an archived discussion of the proposal. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.
The result of the proposal was moved. --BDD (talk) 18:22, 7 June 2013 (UTC)
Picea pungens → Blue spruce – WP:COMMONNAME Chrisrus (talk) 21:24, 30 May 2013 (UTC)
Oppose– the common name would not be capitalized. Revise the proposal and we can reconsider. Dicklyon (talk) 02:32, 31 May 2013 (UTC)- Support unabashedly a move to Blue spruce. Dicklyon, would you support that? Red Slash 04:49, 31 May 2013 (UTC)
- He was just concerned about the capitalization. It's fixed now, I'm sure he'll change to "support". Chrisrus (talk) 06:10, 31 May 2013 (UTC)
- Yes, support; it seems to me that this is such a well known species with well known common name that it should be titled with the common name. I've made a corresponding case fix multiple RM at Talk:Whitebark Pine, and so far have a little pushback with a preference for scientific name, which may be right for some of those. Dicklyon (talk) 06:29, 31 May 2013 (UTC)
- He was just concerned about the capitalization. It's fixed now, I'm sure he'll change to "support". Chrisrus (talk) 06:10, 31 May 2013 (UTC)
- Comment WP:COMMONNAME is not a policy that automatically favors "common names" over scientific names. The policy talks about "most commonly used" names (in reliable English-language sources). A simple link to WP:COMMONNAME is not a good argument for this move. What is the most commonly used name in reliable sources? "Blue spruce" beats "Picea pungens" in a simple Google test, but NGrams favors "Blue Spruce". Plantdrew (talk) 02:52, 1 June 2013 (UTC)
- Well said, absolutely! We can only support the vernacular name if it is indeed truly the common name. But I think in this particular case "Blue S/spruce" is the common name, in which case we can go with WP:MOSLIFE to guide us on capitalization. Which we should. Hence my support for exactly Blue spruce. Does that make sense? Red Slash 03:48, 1 June 2013 (UTC)
- Indeed, the original proposal was both wrong case and poorly explained rationale. Still, as RedSlash says, it moved us to the right answer. Compare n-grams. Dicklyon (talk) 03:53, 1 June 2013 (UTC)
- Oppose - the blue forms are the kind that are popular in the nursery trade, but the natural wild tree is green, and that type is known in the nursery trade as "Green Spruce". I could support "Colorado spruce" as a common name for this page, but not any of the capitalizations of "blue spruce". Sminthopsis84 (talk) 20:57, 2 June 2013 (UTC)
- n-grams suggest that blue spruce is much more common than any of those alternatives. Dicklyon (talk) 21:09, 2 June 2013 (UTC)
- Comment - the n-grams data would show that people are chatting about their gardens, but if the article is about Picea pungens then I'd want it to cover the wild form of the plant as well as the cultivated types. I'd prefer to see blue spruce and the other capitalizations and silver spruce redirect to a section of this page about the blue and silver cultivars. Sminthopsis84 (talk) 21:38, 2 June 2013 (UTC)
Does it matter at all to anyone if many readers want to read an article about the blue spruce, but not an article about Picea pungens? Chrisrus (talk) 22:43, 2 June 2013 (UTC)
- Sometimes when a plant has important uses, we have two pages. I can't think of an example, though, where there is just a single species involved. Banana refers to several species of Musa, Cinnamon comes from several species of Cinnamomum. There's Coffee, Coffee bean, and several species of Coffea. Perhaps there are closer examples to this situation, but if not, I think there could be an outcry about creating two pages. (I'd favour doing so, though). Sminthopsis84 (talk) 14:30, 3 June 2013 (UTC)
- Tea/Camellia sinensis is the best single species/common name for it's product split I'm aware of; both articles are well developed and have a pretty clearly defined scope. Carrot/Daucus carota is another, but the later article is also necessary for discussing the common weedy forms of the plant ("Queen Anne's lace"). There are several tropical fruits split from their species, but the articles are poorly developed, and scope is inconsistent (Carambola/Averrhoa carambola, Sugar-apple/Annona squamosa, Soursop//Annona muricata, Cherimoya/Annona cherimola). I can't imagine how to define the scope of separate articles for Blue spruce and Picea pungens. Plantdrew (talk) 18:32, 3 June 2013 (UTC)
- So redirecting to a section on this page about the coloured cultivars, blue and silver? Sminthopsis84 (talk) 10:35, 4 June 2013 (UTC)
- Tea/Camellia sinensis is the best single species/common name for it's product split I'm aware of; both articles are well developed and have a pretty clearly defined scope. Carrot/Daucus carota is another, but the later article is also necessary for discussing the common weedy forms of the plant ("Queen Anne's lace"). There are several tropical fruits split from their species, but the articles are poorly developed, and scope is inconsistent (Carambola/Averrhoa carambola, Sugar-apple/Annona squamosa, Soursop//Annona muricata, Cherimoya/Annona cherimola). I can't imagine how to define the scope of separate articles for Blue spruce and Picea pungens. Plantdrew (talk) 18:32, 3 June 2013 (UTC)
- Support. I don't think plants should be exempt from COMMONNAME at all, certainly not in this case. --B2C 06:49, 4 June 2013 (UTC)
- The above discussion is preserved as an archive of the proposal. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.
incorrect link for Blue Spruce for German (Deutsch)
the link for the Blue Spruce on the German wikipedia is incorrect but I don't know how to change it. The correct link would be <http://de.wikipedia.org/wiki/Blau-Tanne>
The Blau-Tanne belongs to the Edel-Tanne. Stech-Fichte, the current link is a slang name and not the correct botanical name. — Preceding unsigned comment added by 79.241.59.249 (talk) 10:03, 22 December 2013 (UTC)
Nobel winning Bob Dylan
Why is Bob Dylan's painting Blue Spruce entitled Blue Spruce? The tree is not in the painting.
https://www.facebook.com/photo/?fbid=693761162750522&set=oa.906063287282059 Htrowsle (talk) 14:36, 1 June 2023 (UTC)
Glaucous
Mention it is glaucous. Jidanni (talk) 14:07, 24 July 2023 (UTC)
Taxonomy
@MtBotany: nice work on the page! I'd be less emphatic though on saying "the closest living relative of the blue spruce is Picea mexicana"; 'may be' would be better than 'is'. Its position in Picea varies hugely depending on which study is used, and even within studies depending on what genetic markers are used. Ran et al. 2015 had P. pungens as sister to a whole bunch of mostly Eurasian spruces on cpDNA, but embedded within (!) P. chihuahuana on mtDNA; conversely Zou et al. 2015 had it as third-basal in the whole genus (after P. breweriana and P. sitchensis) on cpDNA, but sister to P. chihuahuana on mtDNA; and yet (very!) different again, Sullivan et al. 2017 had it on 'whole plastome' as sister to a clade of Pp. mariana, omorika, rubens, jezoensis and distant to their Pp. mexicana, engelmannii, glauca clade. Basically, Picea genetic studies are a complete mess (even worse than Pinus), every one of them different to the rest; until we know a lot more about what is going on with it, old traditional morphology – the sum of the whole genetic expression – is probably as good as anything. I'll be adding these (and some other) papers (with links) to the Picea page over the next day or two as time permits. - MPF (talk) 23:05, 7 November 2025 (UTC)
- Excellent. On reflection, I agree on softening the language since the studies are ongoing and even in Lockwood et al. they are open to different scenarios as to why the possible P. mexicana looks so much like P. engelmannii, though they favor morphological convergence it seems like they are open to the possibility of introgression during range expansion and contraction during the last glacial period. (p. 725) 🌿MtBotany (talk) 23:26, 7 November 2025 (UTC)
- @MtBotany Thanks! Missed out on seeing P. engelmannii subsp. mexicana on my Mexico trip, but the herbarium specimens and ones I've seen in cultivation are far more like P. engelmannii than P. pungens, as is its ecology. One more query, on the P. pungens 8-15 cm cone length: I've not seen Barnes & Wagner 1981 so don't know what it says, but I've not seen any reference giving that long, nor ever seen any myself over 9-10 cm long. Farjon gives 5-8 (-10) cm, Rushforth 7-12 cm, Earle (5-)6-11(-12) cm, and FNA similarly (5--)6--11(--12)cm (Earle probably copied this!). Do Barnes & Wagner actually give 15 cm? - MPF (talk) 22:42, 8 November 2025 (UTC)
- I just doubled checked Barnes & Wagner, they do give a range of 8 to 15 cm. It is possible they they got it wrong since they are an outlier and it is based on an older work from 1913 Charles Herbert Otis called Michigan Trees: A Handbook of the Native and Most Important Introduced Species. Possibly they copied information and did not do a field check on the measurements. I think FNA is the source to go with in this case. 🌿MtBotany (talk) 19:06, 10 November 2025 (UTC)
- @MtBotany Thanks! I wonder if Otis mistakenly measured cultivated Picea abies? Yes, agree with FNA as the best option; R J Taylor (who did Picea in FNA) is very good (unlike the hack they got in to do Pinus!) - MPF (talk) 21:30, 10 November 2025 (UTC)
- I just doubled checked Barnes & Wagner, they do give a range of 8 to 15 cm. It is possible they they got it wrong since they are an outlier and it is based on an older work from 1913 Charles Herbert Otis called Michigan Trees: A Handbook of the Native and Most Important Introduced Species. Possibly they copied information and did not do a field check on the measurements. I think FNA is the source to go with in this case. 🌿MtBotany (talk) 19:06, 10 November 2025 (UTC)
- @MtBotany Thanks! Missed out on seeing P. engelmannii subsp. mexicana on my Mexico trip, but the herbarium specimens and ones I've seen in cultivation are far more like P. engelmannii than P. pungens, as is its ecology. One more query, on the P. pungens 8-15 cm cone length: I've not seen Barnes & Wagner 1981 so don't know what it says, but I've not seen any reference giving that long, nor ever seen any myself over 9-10 cm long. Farjon gives 5-8 (-10) cm, Rushforth 7-12 cm, Earle (5-)6-11(-12) cm, and FNA similarly (5--)6--11(--12)cm (Earle probably copied this!). Do Barnes & Wagner actually give 15 cm? - MPF (talk) 22:42, 8 November 2025 (UTC)
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.
