Talk:Hyperion (tree)

Hyperion's location

The longer Hyperion stays hidden, the better. Unfortunately, it will likely be found and mapped by someone who will publish the location, and from then on, say good by to Hyperion. The greatest disease Hyperion faces, is mankind. If you who are skeptical, can't believe in a 380-ft tree, Take a big gulp, because the Redwood has likely reached 400 in past ages. It is a statistical likelihood that taller trees than Hyperion have existed in the Redwoods, considering we only have 2 or 3 % of the original Old Growth left. --71.222.40.209 03:03, 23 October 2007 (UTC)

This is NOT a forum. Please make sure all information on this talk page pertains to improving the wikipedia page. Now, that said, I can't believe the mods aren't allowing the coordinates of the tree to be posted. Additionally, real photos of the tree exist and are available without copyright, yet the mods also will not allow a real photo of the tree. This is blatant censorship and am honestly a bit disappointed in wikipedia for doing this 2601:18E:101:BAAD:691C:7B4B:D431:4DC0 (talk) 20:22, 24 June 2019 (UTC)

Wrong wood volume

The tree is estimated to contain 502 m³ (18,600 cubic feet) of wood.

502 m³ is not equal to 18,600 cubic feet, but rather 17,728 cubic feet. If nobody can look up the citation and fix this, we'll need to remove it entirely. --Doradus (talk) 04:26, 27 June 2008 (UTC)

The wood volume figure estimate is drastically off. 379 foot height with 24 foot diameter at base is way higher than given estimates. If average diameter figure can be cited it's simple to calculate. Tmalo7310 (talk) 18:26, 1 July 2018 (UTC)

RfC - Coordinates for Hyperion

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I've placed this under geography, although it could go under biology as well. There appears to be a long-waged edit war on this page with regards to the coordinates for Hyperion. I've located a past discussion regarding the need to cite coordinates, as anybody can verify them by going to the location. IMO, this is equivalent to a photograph claiming to be of a certain location.

Other arguments raised in this particular topic are that the park services or discoverer don't want want the location made publicly available due to fears of vandalism (which is not backed by a source).

Should coordinates be included? Do they, and by extension all of the million or so coordinates on en.wiki, require citation? Do the opinions of the park services hold any weight? Most importantly, why do you take that stance? - Floydian ^τ _¢ 18:00, 14 May 2018 (UTC)

There isn't a biology RfC category - valid categories are listed at WP:RFC#Categories. But if you feel that something like Maths, science, and technology would apply, you can add |sci either before or after the existing |hist, but it must be before the |rfcid=28455FC otherwise Legobot won't pick it up. --Redrose64 🌹 (talk) 21:17, 14 May 2018 (UTC)

• Retain the coordinates. This is relevant and uncontroversial information, confirmed by what appears to be a RS. The views of the park authorities are unreferenced and maybe irrelevant. (I can see a case being made for removal on WP:BLPPRIVACY-like grounds – but no-one has made such a case.) Maproom (talk) 07:40, 17 May 2018 (UTC)
• Require a reliable source for the coordinates. I think this is different from the arguments about OR for coordinates because, well, the tree is hard to get to, so it's not like anyone can verify them by going there. And the tree isn't visible on Google Maps, so you can't check the information there either. If someone from Wikipedia had actually been there with a GPS and confirmed, I would be more happy with it being unreferenced (in the same way that if someone actually takes a picture, then we use their image description as a reliable source for what the picture is of). But if the coordinates are coming off of some random website that's not a reliable source, then that's not so good. By the way, here's a reliable source for the views of the park authorities, at least their views a decade ago: [1]. CapitalSasha ~ talk 05:06, 19 May 2018 (UTC)
• Omit the coordinates. I came here from the RfC notice, and it's a very interesting question. I see from looking over the edit history that the only source is a self-published one. It's possible that it might be wrong, and the source provided just above by CapitalSasha demonstrates that there could be harm resulting from our publishing the coordinates if they were accurate. The fact that we can provide some sourcing for something does not mean that we must report it. So the question for me comes down to how much it would be useful for our readers, and the only potential use I can think of would be to go looking for it, which is not a compelling one. I'd say that we should only include the coordinates if the park authorities were to make the coordinates public. --Tryptofish (talk) 17:54, 19 May 2018 (UTC)
• Omit coordinates. I agree with Tryptofish's assesment that this is an interesting question (which, I will add, raises a different layer of editorial duties from those we are used to considering in our content discussions). I also agree with how Trypto parses this difficult and close call. I don't believe its truly an abrogation of neutrality to not include every detail that is appropriately referenced, provided the omission is for reasonable and pragmatic cause. There are in fact many policies that allow or encourage editors to avoid including certain content even if verifiable; this one is simply a little different from those we typically see. At a bare minimum we would need a source that passes WP:RS at a gold standard level; otherwise we literally are sending people off into the forest with potentially erroneous information from which real harm could result. Even if we do get such a source which meets a high standard of verification, there remains an ethical check in place which I believe must be considered, given the conservation consequences. That is, at a minimum, a question which should be contemplated by the community. For the present article and time, I am siding with the precautionary principle and endorsing the omission of these coordinates. Snow ^{let's rap} 08:46, 20 May 2018 (UTC)
• Omit (Summoned by bot) per the Fish. ^{cinco de} L3X1 ◊distænt write◊ 11:58, 21 May 2018 (UTC)
• Omit yeah, I removed it as famousredwoods.com isn't RS, and also there appear to be concerns about revealing the location. In most cases coordinates are fine as it'll be relatively easy to verify by going to the location; but I think here, where there won't even be a marker so one can't exactly verify one has got the right tree, and so on, I think you'd need an RS. Galobtter (pingó mió) 06:19, 22 May 2018 (UTC)

Omit based on no weight in reliable sources. I however don't support this 'conservation' angle. It's the job of the park service or relevant forestry commission to protect the tree from visitors. If you visit General Sherman for instance, there are designated walkways in place to try to protect the roots. Infact by not revealing the location, visitors may damage the habitat of more, unprotected trees in search of Hyperion. Cesdeva ^(talk) 13:49, 26 May 2018 (UTC)

I think it comes to the same thing anyway. If the information were available in reliable sources then Wikipedia's inclusion would be unlikely to have a significant effect on the accessibility of the tree. CapitalSasha ~ talk 04:13, 27 May 2018 (UTC)

Good point Cesdeva ^(talk) 06:03, 27 May 2018 (UTC)

Omit Largely on same grounds as User:Cesdeva. For my part I cannot in good conscience add much; this talk page is too full of suspicious or bad-faith items for me to assess them. There is absolutely no point to including controversial items such as the coordinates until their reality and accuracy are beyond verifiable debate. If the details of the debate are to be included, then OK, but I don't see that as a practical prospect at the time of my writing this. JonRichfield (talk) 06:17, 27 May 2018 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Picture

Why do we not have a picture? Is this tree hiding or not existing? Pics or it did not happen! 2A02:8388:1641:8380:15C2:A3F1:9A28:71D9 (talk) 16:52, 11 November 2019 (UTC)

There are pictures of this tree, yes. Most, however, are in copyrighted materials.Ryoung122 06:30, 3 October 2023 (UTC)

Height of hyperion tree

Alexa says Hyperion is 115.8m tall. 82.9.135.72 (talk) 16:09, 14 June 2022 (UTC)

That's from the rounded imperial measurement of 380 feet (115.824m). - Floydian ^τ _¢ 22:37, 14 June 2022 (UTC)

Hyperion is still growing. It was 379 feet tall when discovered in 2006. It's now closer to 381 feet tall. The top is unbroken.

http://famousredwoods.com/hyperion/

Ryoung122 06:31, 3 October 2023 (UTC)

Coordinates from centroid of exclusion zone

Floydian removed the coordinates for the article, which were computed from the centroid of the exclusion zone. The following reasons were given in the edit summary, with my response to each:

• WP:SYNTH --- Centroid is a simple average of coordinates, covered by WP:CALC and is explicitly not original research
• RfC --- the RfC decided to omit the coordinates from famousredwoods.com, because famousredwoods.com is not a reliable source. The National Park Service writing about its own park resources appears to be a highly reliable source, so the RfC does not forbid coordinates from the NPS. There was no consensus for permanently removing the coordinates.
• NPS web page doesn't explicitly claim that the exclusion zone contains the tree --- That is true, but why would the NPS list a legal exclusion zone on a web page that discourages hiking to Hyperion, if it didn't contain it? I suppose it's possible that the NPS is trying to mislead the public by making an exclusion zone away from Hyperion. However, this possibility is excluded by a simple check of the coordinates from famousredwoods.com --- they lie within the exclusion zone.

The accuracy of the centroid is reflected in the precision of the coordinates: rounding to the nearest 0.1 minutes of arc (approximately 100m). Even though imprecise, it provides an approximate location of Hyperion. Other articles (such as those for mountain ranges) have imprecise coordinates that represent a region with a single point. One other possibility is to use {{maplink}} to show the exclusion polygon.

I'll restore the coordinates, but let's see if we can get consensus about what location data we should show. — hike395 (talk) 14:52, 27 May 2023 (UTC)

I mean the correct thing to do would be to leave the version without the coordinates, as it's a clear-cut case of synthesis (they provide an exclusion zone therefore the tree is within that). "why would the NPS list a legal exclusion zone on a web page that discourages hiking to Hyperion, if it didn't contain it?" - I think that question answers itself. Maybe to throw people off? The better question is still "Why would Wikipedia provide coordinates to (the centre of) a legal exclusion zone when the owner of the land discourages legally forbids hiking to it"? I'd also note that the NPS website was brought forward in the second reply to the RfC and didn't seem to sway any subsequent votes. Also perhaps the coordinates from famousredwoods.com was synthesized from the same coordinates, and is not an independent verification. - Floydian ^τ _¢ 18:12, 28 May 2023 (UTC)

Responding to Floydian's points:

• Why would Wikipedia provide coordinates to (the centre of) a legal exclusion zone when the owner of the land discourages legally forbids hiking to it"? -- because Wikipedia is not WP:CENSORED. Wikipedia has many coordinate links to places that the general public cannot legally access. For example, Area 51 (37°14′0″N 115°48′30″W), Camp Pendleton (33°12′53.1″N 117°23′15″W), and Onizuka Air Force Base(37°24′27.35″N 122°1′36.40″W, active until 2010). The current coordinates give the general location of the tree: entirely dropping the coordinates deprives our readers of information.
• NPS website was brought forward in the second reply to the RfC --- that is not possible. The RfC occurred in 2018. The Washington Post article on 1 Aug 2022 said that the exclusion zone was announced the week before (the week of 25 July 2022), with a link to the NPS website with the exclusion zone coordinates. The link text says "announced". To corroborate, the 15 July 2022 version of the NPS website does not have the exclusion zone, while the 31 July 2022 version of the NPS website does have the exclusion zone (dated 25 July at the bottom). The RfC could not consider or cover the NPS publication of the exclusion zone, since it happened 4 years previously.
• Also perhaps the coordinates from famousredwoods.com was synthesized from the same coordinates, and is not an independent verification. --- as above, the famousredwoods.com web site existed in 2018 and was discussed in the RfC. The current coordinates from famousredwoods.com are the same as the coordinates quoted in the 14 May 2018 version of the article. Those coordinates are in the exclusion zone, and were published at least 4 years before the NPS exclusion zone.

— hike395 (talk) 04:34, 29 May 2023 (UTC)

Fair enough about most of those points, not that those air force bases are subject to damage from the general public. My main point is that it's still synthesis. It would be fine to include something in the prose such as "The NPS has established an exclusion zone in the area of Hyperion, at (coordinates)," but to include them in the infobox/header as an absolute position is original research. (also I didn't realise how long ago that RfC was, feel like it was just a year ago not five haha) - Floydian ^τ _¢ 16:32, 29 May 2023 (UTC)

I see what you are saying. How about if we mark the coordinates in the infobox as the center of a closed area, rather than for the tree itself? That would be clearer. — hike395 (talk) 18:58, 29 May 2023 (UTC)

I noticed hike395's edit self-described as providing coordinates at center of a closed area, and went to the source provided (NPS's website with the exclusion zone coordinates). My reaction, without yet seeing the discussion here, was that such coordinates should not be provided, in part because I noted the source does not say that zone includes Hyperion and that it appeared to me to be presenting original research.

I think that Wikipedia readers and secondary users of Wikipedia information would assume the tree is inside the closed area, if coordinates are labeled "(center of closed area)" as they are now.

On a point of fact, I am not clear how big is that exclusion zone, so whether pointing to a "center" is giving away Hyperion's location within 100 yards or what distance, if Hyperion is in fact included in the area. I don't like going somewhat against the consensus of a formal-like discussion above, that coordinates of the tree should not be provided.

FWIW the radius of the area from its "center" is roughly 3,000 feet (910 m), by my estimation. Here are the 5 points NPS gives defining a closed area:

Map all coordinates using OpenStreetMap

Download coordinates as:

• KML
• GPX (all coordinates)
• GPX (primary coordinates)
• GPX (secondary coordinates)

41°12.689′N 124°1.343′W "NPS #1"

41°12.605′N 124°0.889′W "NPS #2"

41°12.407′N 124°0.492′W "NPS #3"

41°11.879′N 124°0.788′W "NPS #4"

41°11.783′N 124°1.302′W "NPS #5"

These points and all other coordinates on this Talk page can be seen in "Map of all coordinates using OpenStreetMap" at the right, here. In that OSM map display I see the point I suggested first (41.20880|-123.99534) does not exactly hit the parking lot in OSM and Bing... in general Google maps vs. Bing maps vs. OSM always display a little bit differently. Hmm, I tried a slightly different point that I find works well within all 3 map displays and suggest that instead. --Doncram 06:18, 25 June 2023

I have a different suggestion: provide 41.20880°N 123.99534°W / 41.20880; -123.99534 (Tall Trees Grove Trailhead Parking (first try)) 41.20809°N 123.99302°W / 41.20809; -123.99302 (Tall Trees Grove Trailhead Parking (better)) instead, which is a central point amidst the Redwoods park where people can park and go on walks to see tall redwoods. It is basically the location labelled "Tall Trees Grove Trailhead Parking" in Google maps, which shows it at the end of "Tall Trees Access Road" and shows hiking trails departing from it. It is, in rough terms, close to the coordinates that hike395 put in, and effectively the same place in large scale map display. Note I modified the infobox to include display of a California relief map, now with map caption "Approximate location in California", following example for the General Sherman tree given at template:infobox tree. An alternative would be to provide coordinates for a main entrance to the park, but AFAICT candidates for that would actually be outside the park and I think it would be difficult to compose an adequate succinct label.

I like how hike395's edit provided a custom label for the coordinates, and that the label is accurate for what it is (though I don't like the implication that it is pretty much the location of Hyperion). I suggest having a different accurate label in similar spirit, which could be:

1. "(central point in park for visitors to tall trees)", or
2. "(Tall Trees Grove Trailhead)", or
3. "(a central location in park)", or
4. "(a location of tall trees in park)".

Of these, I somewhat prefer the third. Readers who click on the coordinates and go to see it in Google maps will see/discover that it is the location of "Tall Trees Grove Trailhead Parking". Using Bing maps they will see/discover that it is the location of "Tall Trees Grove". Using OpenSourceMap there is no title for it but they will see it is a parking lot on Tall Trees Access Road and that various trails radiate away from it. With any of these labels in place I think this would be a perfectly acceptable result for readers to discover and they will not experience surprise or feel duped (in general I think that it is bad to cause readers to experience surprise or to feel duped when they follow any link). I think many/most readers who are interested in getting coordinates will understand that providing a specific point's coordinates is necessary for the approximate location in California to show on the relief map.

--Doncram (talk,contribs) 06:08, 25 June 2023 (UTC)

I'm confident that Hyperion is in the exclusion zone (see above). I have two issues with the parking lot coordinate idea:

• It's about 0.79 miles (1.27 km) away from the nearest point in the exclusion zone. In effect, we would be adding (at least) that much error to the coordinates, in order to protect the tree. This feels like "covering up" data to me, which contravenes WP:CENSORED.
• What source do we cite that says that this parking lot is somehow associated with Hyperion? If we're using the NPS exclusion zone webpage to find the parking lot, then why are we not using the NPS exclusion zone coordinates in the infobox? It seems (to me) that finding the nearest parking lot and presenting its coordinates is original research.

If other editors truly find using the centroid to be offensive, how about if we use one of the corners of the exclusion zone that is on an public Forest Service Road, e.g., 41°11.783′N 124°1.302′W? That is a location that people can travel to, and is supported by an NPS source. — hike395 (talk) 10:41, 25 June 2023 (UTC)

Those are exactly the same coordinates as point number 5, which display on OSM page as "NPS #5", despite Hike395 trying to have it display as "FS road". The OSM display apparently uses the name first-defined on this page .

Or, we can use this corner: 41°12.407′N 124°0.492′W, which is at the end of a 1.2-mile (1.9 km) hike from the same parking lot that Doncram suggested. — hike395 (talk) 10:47, 25 June 2023 (UTC)

That is the point displayed as "NPS #3". --Doncram (talk,contribs) 16:15, 27 June 2023 (UTC)