Talk:Blue Hills (Washington)

Panoramic view
I've been experimenting with a full-width panaoramic view. (Using an available pic, anticipating a better view some time in the future.) I like the concept generally, but don't know how best to set it up. Taking out the previous lead image helps to consolidate the white-space. ~ J. Johnson (JJ) (talk) 22:50, 3 November 2014 (UTC)


 * Got a good panoramic view this morning from QA, will be uploading it "real soon now". ~ J. Johnson (JJ) (talk) 22:55, 12 November 2014 (UTC)


 * It's "now"! And new panoramic view is installed, with imagemap. Though there may be some adjustments needed. One particular point needs resolution: is the ridge in front of Gold Mountain Peak 1330, or Peak 1320? We should make a determination, then make it consistent across all articles. ~ J. Johnson (JJ) (talk) 21:50, 15 November 2014 (UTC)
 * Nice panorama. I included the peak viewfinder site in the caption. According to it, just out of frame would be South Mountain in the Satsop Hills over 60 miles away. Re 1320 vs 1330: (you mean in front of Green Mountain right?) there doesn't seem to be a "right" answer here as the maps are ambiguous as to the actual elevation. Google hits for each is about the same and very low. So: personal preference, peakbagger or Lists of John? I have a very weak preference for peakbagger as the "local" authority. — Brianhe (talk) 01:33, 18 November 2014 (UTC)
 * Stop press. Five-foot resolution Kitsap County GIS LiDAR data rendered as 3D map is online here: . It looks like there's actually a 1340-1345 ft. peak at x=1162912.15 ft y=213712.42 ft (47.56943°N, -122.76785°W). So ... Lists of John's 1330 feet is closest to the new "truth". — Brianhe (talk) 02:26, 18 November 2014 (UTC)


 * Yes, between Green Mtn. and the watershed. 1320/1330 could be the difference in mapping pre- and post-logging. Or even GPS readings. Or what various intrepid off-trail summiters thought was the summit. Just as I was going to shout "let's go for lidar!" you got there. (BTW, that's an Autocad file — perhaps you have Autocad?) So as we are in a position to make a determination of broad and lasting significance, how should we proceed: 1) Use a new label based on our best estimate? 2) Go with the best existing label?
 * Re De Ferranti 2005: I've seen that gif before, but it's not especially useful. Certainly wasn't used here, so I am going to remove it. If the sources for identifying the peaks need be cited it would be peakfinder.org (which is excellent), and various maps. I'm not fully inclined to citing the maps, but I may mention peakfinder for the readers' edification. ~ J. Johnson (JJ) (talk) 00:17, 21 November 2014 (UTC)
 * I think it would be confusing to start using a name we just made up, also not sure but this might violate WP:OR. It makes more sense to use the existing label closest to the new measurement, i.e. Peak 1330, and make a notation about the differences.
 * De Ferranti would be a good EL for the article if you don't mind. — Brianhe (talk) 19:22, 21 November 2014 (UTC)
 * I'm fine with 1330, for the reasons you cited. I'm somewhat set against De Ferranti, even as an external link, as I just don't see that is useful or adds anything not to be had from Peak Finder. I see the direction parameter for PF doesn't work; I may write to them if about that if I get some time. ~ J. Johnson (JJ) (talk) 04:20, 22 November 2014 (UTC)

Hey, check this: I've managed (an epic effort) to grab and massage some elevation data, so I can do 3-d views, from any pov. Some aspects are much clearer than could be ascertained from the contours or shaded-relief. E.g., the Peak 1320/1330 question could be simple matter of which "peak": it's definitely a ridge, with as many as four peakish points. (I think that ridge needs a definite name.) And it looks like the imagemaps need some adjustment. ~ J. Johnson (JJ) (talk) 21:27, 18 December 2014 (UTC)

P.S. Even better, I managed to get some contours on that ridge, and determined that of the five peaks the highest is the next to last one on the north end, at a tad over 405 m. This with 5-meter contours. ~ J. Johnson (JJ) (talk) 23:44, 19 December 2014 (UTC)

Misc.
I think you're trying over-hard to work in "Chehalis Gap". I was reminded of this this past weekend on seeing a book on PNW weather, and it did not mention this. This term seems to be restricted mainly to some of the local weather blogs, and thus lacks adequate notability. For this article I think it would be sufficient to say that storms proceeding down the coast tend to send a lot of moisture around the south end of the Olympics, which the Blue Hills intercept. Also, I don't know that Spada and Chester Morse need to be mentioned; that other localities have access to mountain reservoirs doesn't seem relevant to anything here. ~ J. Johnson (JJ) (talk) 22:21, 24 November 2014 (UTC)
 * Maybe true on the first point. More research would bear this out; however it was prevalent in several outdoors guides indexed by Google Books. However, I think it is very valuable to put Bremerton's water supply in context. It is unique as a medium-large city in the state that draws the majority of its supply from a reservoir not fed by snowpack. Without this context there is little to inform the reader why the reservoir is worth talking about. The city with its population and industrial base have a fascinating relationship to the very topography we're describing in the article that few of them are probably even aware of. The interaction of the Blue Hills and Chehalis Gap are arguably why the Kitsap Peninsula is not a low-population area more akin to the San Juan Islands. The comparison to Cascades reservoirs (or Lake Cushman) tells part of the story why. – Brianhe (talk) 05:53, 28 November 2014 (UTC)
 * Maybe this source can help drive the point, contrasting Bremerton to most other Western U.S. cities: "In the western United States, most water arrives in winter storms, which swoop in from the Pacific and dump snow atop the region’s mountain ranges. Mountain snowpack serves as the West’s water tower, and over the past century Westerners have built hundreds of dams to catch and store snowmelt as it fills the region’s rivers in spring." from National Geographic — Brianhe (talk) 06:24, 28 November 2014 (UTC)


 * I think the Navy is why central Kitsap Peninsula is not a low-population area, and particularly the Yard; the availability of water being an enabler, not a cause. I agree it is a fascinating situation, which warrants some explanaton. But in regards of the source of the wet air I think you don't need to go beyond the storms blowing in "thorugh the gap between the Olympic Mountains and the Willapa Hils (called the Chehalis Gap) ...", leaving any further explanation of that to the other article.
 * Likewise, mentioning the mountain reservoirs of Everett, Seattle, Tacoma, and even Port Townsend certainly establishes that some cities rely on mountain reservoirs, but not that most (?) localities in the region do, which is rather tangential itself. The main point is that the Peninsula does not have such access, which is sort of "blue skyish".
 * Took a look this morning, but the scattering of snow didn't really change the view. I have gotten interested in extracting some elevation data to create a manipulable image, but there's a bit of a "learning hill" to ascend. By the way, I suspect you have Autocad; can it read ArcGIS shapefiles? ~ J. Johnson (JJ) (talk) 22:44, 29 November 2014 (UTC)
 * No time for a full reply right now. Got the free DWG viewer here: . Brianhe (talk) 23:49, 29 November 2014 (UTC)
 * No good: Autocad is Windooze only. I suspect it doesn't handle shapefiles anyway. ~ J. Johnson (JJ) (talk) 00:17, 30 November 2014 (UTC)

J.: 1) Concerning the significance of the Chehalis Gap. It's mentioned quite a bit in serious writing about meteorology. "Local weather blogs" is kind of downplaying the importance of Cliff Mass, Jeff Renner, and Steve Pool isn't it? Each one a published author per citations at Chehalis Gap. Not sure what their (inter)national impact is but they also have a Puget Sound audience in the millions via TV and radio. 2) Won't fight you on the issue of what drives Kitsap population, it's kind of a Gedankenexperiment at any rate. One does wonder what the Navy would do if they didn't acquire water from the municipal gov't, and had to fight for groundwater rights. Maybe a desalinization plant... Anyhow what can I do to get the article ready to publish? If you think it's critical, I can move the stuff about other city reservoirs somewhere else. — Brianhe (talk) 22:29, 2 December 2014 (UTC)


 * Let me go through and change all the Peak 1320 references to Peak 1330 per the discussion above (any minute now), and I'd say it's close enough to roll. I'm not at all against citing our local weather experts, though we should tread carefully in regard to the use of blogs. Regarding mention of the other reservoirs: it just seems to me to be irrelevant detail. ~ J. Johnson (JJ) (talk) 19:44, 3 December 2014 (UTC)
 * I generally prefer to use books as sources, then journals, then newspapers, then websites, then blogs last. But AFAIK this is just a personal prejudice. Blogs are considered reliable sources if they are created by established experts who have published elsewhere, per WP:SPS. -- Brianhe (talk) 20:36, 3 December 2014 (UTC)
 * The key thing is to "exercise caution". When using a blog there is a greater need to show that the author is reliable.
 * I worked on the 1320 labeling, including a note why we are going with 1330. But it's not properly cited, particularly for the lidar datum. I tried to use the National Elevation Database, but that didn't work. Tried some other places, with no luck. Tried to check the PeakFinder url, and this updated browser I'm using keeps insisting on going to South Peak -- Alaska!
 * I also looked for how to put the panoramic view into something like wide image so it will fill the page. But that doesn't seem to integrate with the imagemap. I'm frustrated enough to lower the bar. Let's say "good enough" and promote. ~ J. Johnson (JJ) (talk) 23:05, 3 December 2014 (UTC)
 * Done! There's no time limit on making it "even better", as they say. — Brianhe (talk) 23:35, 3 December 2014 (UTC)
 * Yup. Could use more attention on the references, but likely better than the average 'pedia article as it stands. I am still puzzling out exactly what we are looking at in the view. I have figured out how to get 3-D images from a DEM map, which could be a great exploration tool, and possible future graphic. And my photographer friend found the article interesting enough to consider visiting the place, so perhaps next spring we can a better "recreation" image. ~ J. Johnson (JJ) (talk) 22:05, 4 December 2014 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 1 one external link on Blue Hills (Washington). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20140613082750/http://www.nass.usda.gov:80/Statistics_by_State/Washington/County_Profiles/kitsap.asp to http://www.nass.usda.gov/Statistics_by_State/Washington/County_Profiles/kitsap.asp
 * Added tag to http://www.keypennews.com/index.php/rss-feed/item/114-the-chehalis-gap-the-coriolis-effect-and-the-aleutian-low

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

Cheers.— InternetArchiveBot  (Report bug) 13:06, 4 November 2016 (UTC)

Article Class
I have rated this article as C-class. With some improvements to style, I think this will be a B-class article soon. Citations are also a bit clunky and could use review.Carmelator (talk) 03:07, 31 January 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 6 external links on Blue Hills (Washington). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20131020144830/http://epa.gov/climatechange/impacts-adaptation/northwest.html to http://www.epa.gov/climatechange/impacts-adaptation/northwest.html
 * Added archive https://web.archive.org/web/20121111001219/http://www.cityofbremerton.com/content/dw_bremertonwaterhistory.html to http://www.cityofbremerton.com/content/dw_bremertonwaterhistory.html
 * Added archive https://web.archive.org/web/20140822043910/http://www.ci.bremerton.wa.us/display.php?id=867 to http://www.ci.bremerton.wa.us/display.php?id=867
 * Added archive https://web.archive.org/web/20141105133338/http://www.kitsapgov.com/parks/parks/pages/gift_catalog/dream.htm to http://www.kitsapgov.com/parks/parks/pages/gift_catalog/dream.htm
 * Added archive https://web.archive.org/web/20130219043655/http://geopubs.wr.usgs.gov/open-file/of00-356/of00-356.pdf to http://geopubs.wr.usgs.gov/open-file/of00-356/of00-356.pdf
 * Corrected formatting/usage for http://www.nass.usda.gov/Statistics_by_State/Washington/County_Profiles/kitsap.asp

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 05:03, 22 July 2017 (UTC)