User talk:Hike395

If I have left you a message: please answer on your talk page, linking to me ({{Ping|Hike395}}), so that I will be notified. If you leave me a message: I will answer on my talk page, linking to your username, so that you will be notified. Please click here to leave me a new message.

Archives

1, 2, 3, 4, 5, 6, 7, 8, 9, 10 11, 12, 13, 14, 15, 16, 17, 18, 19, 20 21, 22, 23

This page has archives. Sections older than 270 days may be auto-archived by Lowercase sigmabot III if there are more than 12.

Precious

hiking mountains

Thank you for quality articles around the Geology of the Rocky Mountains and Lake Sammamish State Park, for improving and fixing templates, for welcoming and advising users, for your contributions from 2003 saying "the best part of editing WP is when several editors cooperate to make a high-quality article", such as The Three Sisters, - you are an awesome Wikipedian!

--Gerda Arendt (talk) 08:39, 6 January 2018 (UTC)[reply]

Thank you, Gerda! —hike395 (talk) 14:07, 6 January 2018 (UTC)[reply]

Two years ago, you were recipient no. 1818 of Precious, a prize of QAI! --Gerda Arendt (talk) 07:29, 6 January 2020 (UTC)[reply]

Seven years

Precious

Seven years!

--Gerda Arendt (talk) 08:18, 6 January 2025 (UTC)[reply]

Thanks again, Gerda! — hike395 (talk) 08:22, 6 January 2025 (UTC)[reply]

In appreciation

		The Good Article Rescue Barnstar
		This is presented to you by the GAR process in recognition of your sterling work in helping Ben Nevis retain its Good Article status. Please feel free to display the GA icon on your userpage. Keep up the good work! ~~ AirshipJungleman29 (talk) 23:29, 5 December 2024 (UTC)[reply]

Thanks, Jungleman! It is always nice to rescue articles. — hike395 (talk) 05:47, 6 December 2024 (UTC)[reply]

cite simbad

Your edit at {{cite simbad}} appears to have borked the template. See Category:CS1 errors: invalid parameter value

—Trappist the monk (talk) 15:29, 25 December 2024 (UTC)[reply]

The articles in Category:CS1 errors: invalid parameter value have malformed {{cite simbad}} – positional parameters are not supported. Because Module:Citation mode uses Module:Arguments, when |mode= is not present in the template, args[1] gets the value of the first positional parameter in the template and assigns that value to |mode= in the wrapped {{cite web}}. |mode= only accepts cs1 or cs2; anything else causes an error message:

{{Cite simbad|HD+984|title=HD 984}}

"HD 984". SIMBAD. Centre de données astronomiques de Strasbourg.

Perhaps line 19 should be rewritten to ignore parent frame parameters:

local args = getArgs(frame, {frameOnly = true})

I have to wonder if Module:Arguments is really needed in this application...

Of course, as is, the current code does serve as a way to detect malformed templates but the error messages emitted are sufficiently obscure that non-technical editors will be at a loss to know how to repair a malformed template.

—Trappist the monk (talk) 16:32, 25 December 2024 (UTC)[reply]

Thanks for catching this. Will fix according to your suggestion. — hike395 (talk) 17:06, 25 December 2024 (UTC)[reply]

Umm, disclaimer: none of what I wrote has been tested...

—Trappist the monk (talk) 17:13, 25 December 2024 (UTC)[reply]

Don't worry -- per your hint (above), I just ripped out Module:Arguments. You're correct, we don't need to trim arguments in Module:Citation mode: we can let the downstream template handle it. I tested in my sandbox. — hike395 (talk) 17:31, 25 December 2024 (UTC)[reply]

For completeness, I figured out a (somewhat ugly) way to test the module both with and without {{CS1 config}}, documented at Module:Citation mode/doc. — hike395 (talk) 18:00, 25 December 2024 (UTC)[reply]

Template:A Short Biographical Dictionary of English Literature

Hi Hike395, your recent edits to this template seem to have caused a CS1 error for pages using the |inline= parameter. See John Abercrombie (physician)#cite_note-SBDEL-4 for an example. I'm not really sure how the whole Module:Template wrapper thing works, so I don't want to break anything by trying to fix it myself. Thanks! Jay8g [V•T•E] 05:51, 28 December 2024 (UTC)[reply]

@Jay8g: Thanks for alerting me. By default, Module:Template wrapper passes along all arguments given to the template that calls it. In this case, I hadn't filtered out |inline=, which was being passed to {{cite web}}. It's super easy to filter it (added it to the _exclude line). Now fixed. — hike395 (talk) 07:31, 28 December 2024 (UTC)[reply]

Category:Recreation has been nominated for merging

Category:Recreation has been nominated for merging. A discussion is taking place to decide whether it complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. Marcocapelle (talk) 05:05, 30 January 2025 (UTC)[reply]

Yosemite Decimal System

Given you responded to this topic years ago, you might be interested in the current discussion on the Yosemite Decimal System talk page. Over a year ago the Yosemite Decimal System article was replaced with a redirect page that now points to Grade (climbing)#American YDS grade. This article focuses on 5.x climbs and provides no information on YDS class 1, 2, 3, and 4 climbs. As a result, hundreds of wikilinks for class 1-4 climbs are now effectively useless. Most of these referring articles are for mountains and many use the YDS template in the info box. Given your many contributions to mountain-related articles, your input on this issue would be valuable. We need a solution that will work for all YDS classes. Thank you. Zapus (talk) 22:01, 8 February 2025 (UTC)[reply]

Mountain Infobox Rock type

I was just informed that you recently removed a series of parameter names displayed in the "Rock type" field and only left "geology". Are there plans to redirect rock type to the geology parameter? Because right now all the thousands of rock type are not displaying in the mountain infobox and so are lost. — Preceding unsigned comment added by Ron Clausen (talk • contribs) 23:00, 11 February 2025 (UTC)[reply]

@Ron Clausen: That was an error: I restored |rock=. — hike395 (talk) 02:35, 12 February 2025 (UTC)[reply]

jfyi, according to the template parameter usage report, |rock= is unused in article space, so no readers were affected. It appears that a bot that ran back in 2021 copied all uses of |rock= to |geology=. I'll leave |rock= functional, however. — hike395 (talk) 02:48, 12 February 2025 (UTC)[reply]

Thank goodness for bots and AI... we have nothing to fear. Ron Clausen (talk) 03:12, 12 February 2025 (UTC)[reply]

{{OSM Himalaya}}

let me know once you have finished your update as I have noted work in progress in correcting scaling changes as shrinking created lots of labelling issues as you discovered ChaseKiwi (talk) 15:24, 13 April 2025 (UTC)[reply]

@ChaseKiwi: Thanks for putting this template together! I'm done tweaking the template (for now), and have to add parameters to just a few more articles.

What kind of labelling issues are you thinking of? I can think of a few, but curious if there are more:

• Many of the peaks are very close together, so if the zoom level is too low, then they lie on top of each other. The only way I know how to solve that is to make the markers be zoom-level dependent (i.e., only show the major markers when zoom <= 6).
• The country+flag labels are a little fragile: I've gone through each map individually and made sure that they aren't particularly ugly. I shrank the size of the country label and flag markers. They probably could be made to be closer together (is that what you're thinking of?)

— hike395 (talk) 15:35, 13 April 2025 (UTC)[reply]

@ChaseKiwi: I was just thinking: if we rewrote this in Lua, then we could make a truly adaptive map: i.e., we could take the center lat/long, the zoom level, and the height/width and compute exactly which peaks would be visible. Of course, this is what the OpenStreetMap app does, itself, but I don't know an easy way of transcluding a live OSM map onto a WP page (instead of the WikiMap framework) — hike395 (talk) 15:44, 13 April 2025 (UTC)[reply]

Yes, that is why I did not try to scale any smaller. Almost all the numeric labels are now out of alignment as well as the more obvious flags. There was already some individual scale logic and also individual logic in positioning of the flags. It will take quite a bit of manual fiddling and correcting any logic for individual maps that use the template such as Zemu Gap Peak and List of Himalayan peaks and passes. Frankly this was one of impacting templates we checked with the recent upgrade of {{OSM Location map}} to Lua and the changes after upgrade (and a few logic corrections by user:RobinLeicester) were minimal but in due course non urgently would have justified code improvement. The problem is that you have to x,y position each numeric label for any scale change and Robin has also introduced some better parametrisation to do this that I was non urgently going to have to get my head around. Likely no problem once you tell me you have stopped editing for a as I had just completed my planned improved page of the week and the numeric labels need to get out of overlying each other and flags can be again fine tuned. The main problem is with logic switching code that corrections are difficult to test in sandbox and I do not want to create the obvious server editing churn so did not want you trying to correct at same time as me. ChaseKiwi (talk) 16:04, 13 April 2025 (UTC)[reply]

Scale smaller = higher zoom level = zoom in?

All of the manual effort is why I think we need Lua helper code. It's relatively easy to convert lat/long to/from pixel coordinates on a map (using orthographic projection, which is not precisely what OSM is using). Given that code, we could:

• Trim down the legend to contain only those points that would show up in the map at a specified zoom level
• Automatically position labels for countries (assuming you specified a lat/long rectangle for where you'd like the labels to be)
• Automatically position labels for markers in terms of pixel offsets, rather than lat/long

Now it's not a trivial amount of code to do all three, but I wonder if it's worth it to save future labor? Especially if other editors want to make templates similar to what you've done here. — hike395 (talk) 16:23, 13 April 2025 (UTC)[reply]

Not worthwhile doing as we are overlying OSM map and you would need AI to sort out all the conflicts in border shape I found with flag and country markers and how marker best positioned depending on underlying features. {{OSM Location map}} has better and more stable functionality now than it had when I went around improving others historic work ChaseKiwi (talk) 02:21, 14 April 2025 (UTC)[reply]

Ah, Having had a look at the code you removed no wonder every thing is mucked up. You removed the ability to centre map on individual pages, based on page name which allowed change in coordinates on that page, individualised labelling moving by pixels and control the zoom level. Perhaps the template now needs optional parameters to meet good programming practice as you summarise as "template coordinates should be adjustable by article edits, not by central edits. refactoring". I apologise for the hack but it seemed an elegant solution given I was adapting someone's other code and I did not decide one map would do on all the pages affected. I note that the quickest option if allowed, so as to have good maps with clear labelling is just reversion of all but one edit to the logic that you made, as far as I can see, and then when time and knowledge allows creating a template with option parameters which is probably where you are coming from with comments on Lua helper code. I am not an experienced Lua or Template programmer but do like maps that look good, which some of these do not at the moment. ChaseKiwi (talk) 09:30, 14 April 2025 (UTC)[reply]

@ChaseKiwi: I've changed multiple things over the last day, let's separate to make sure we edit the right things:

Software change

• I moved the height, width, zoom, central point, and float values from being constants in {{OSM Himalaya}} to being parameters, whose values are specified in the calling article. This does not change functionality at all, it simply changes where the values are specified. In theory, we can exactly reconstruct the previous version of the maps under this change. This is simply good practice: if you are going to have a template whose formatting parameters vary by article, you should let editors of that article easily change it (subject to consensus, of course). I would strongly prefer that we keep this change.

Formatting changes --- happy to discuss and change these and see if we can come to some compromise/consensus on what makes the nicest maps.

• Reduced the size of the country labels and flags by 25%, because they seemed to "shout" at me (compared to the marker sizes)
• Put the legend into a {{collapsible list}} because it was making the infoboxes too long. (Turns out that {{OSM location map}} has an auto-caption feature --- maybe we should use that?)
• Use hlist to separate the legend entries
• Changed the default size of the map to be 320x200px, again to prevent the infoboxes from getting too long. Turns out the Himalaya run east-west, so I don't think we lost anything here.
• At every infobox, I centered the map at the lat/long feature of interest.
• At every infobox, I chose a zoom that made the map look the best. It's a pity that we can only choose integer zoom values (which changes the map zoom by 2x).
• I dramatically shrank the map image at List of Himalayan peaks and passes, because the previous size (1000x550) was crowding the actual list off the first page. Previously, the map strongly violated the WP:IMGSIZELEAD policy (which specified a maximum image size of upright=1.35 or 300px. The map still violates the policy (at 480x300), but it's not as bad.

Most importantly: It would be great to understand what exactly you think is ugly about the current maps, and which maps you think are ugly, so that I can help fix it and we can come to some mutual agreement. As I said above, all of the formatting changes can be altered and improved upon. Please let me know. We can also move this discussion to Template talk:OSM Himalaya, if you prefer. — hike395 (talk) 14:58, 14 April 2025 (UTC)[reply]

I can live with this as it will aid future maintenance. I did not like the size of image I inherited for the reasons you outline but gave up when tried reduced scaling. The master image should display the whole of the Himalayan range in my view and `I think this was a constraint. The large flags are a function of the initial image size and the border disputes seemingly more important to many users than the mountains. The main hate point is the overlapping of number labels and drift of some flags and their labels outside the respective countries which is poor presentation and I will see if I can do anything useful in a sandbox with your plan when time. ChaseKiwi (talk) 17:02, 14 April 2025 (UTC)[reply]

"On Earth"

Thanks. Great. 2601:196:180:DC0:86F:23B3:85AA:DDF4 (talk) 22:27, 28 April 2025 (UTC)[reply]

Thank you!

		The Template Barnstar
		Dear Colleague, Thank you so much for fixing so promptly the red error message caused by {{Cite DGRG}}. Your technical expertise is very much appreciated; thank you once again! With kind regards; Patrick. ツ Pdebee.^(talk)^(become old-fashioned!) 10:17, 12 May 2025 (UTC)[reply]

@Pdebee: You're welcome! — hike395 (talk) 12:39, 12 May 2025 (UTC)[reply]

Mount Morrison - incorrect edit?

Hello Hike395, i fear that your edits to Mount Morrison on May 31 may be incorrect. The introductory sentence on that page says: "According to USGS GNIS", but it appears "Mount Morrison" is an *unofficial* name for the mountain in Idaho. I have been unable to find the mountain under that name in the GNIS database, and you did not provide a link to GNIS for that mountain either. I think either the introductory sentence needs to be modified or "Mount Morrison (Idaho)" must be placed outside the table. Thanks in advance for having another look, Schwarze (talk) 02:40, 31 May 2025 (UTC)[reply]

 Fixed You are correct. — hike395 (talk) 03:55, 31 May 2025 (UTC)[reply]

The World Destubathon

Hello. You're invited to participate in The World Destubathon. We're aiming to destub a lot of articles and also improve longer stale articles. It will be held from Monday June 16 - Sunday July 13. There is $3338 going into it, with $500 the top prize and $500 into geography and populated place articles. If you are interested in winning something to save you money in buying books for future content, or just see it as a good editathon opportunity to see a lot of articles improved for articles which interest you, sign up on the page in the participants section if interested.♦ Dr. Blofeld 17:14, 4 June 2025 (UTC)[reply]

DYK for Carlo Rinaldini

On 19 June 2025, Did you know was updated with a fact from the article Carlo Rinaldini, which you recently created, substantially expanded, or brought to good article status. The fact was ... that 17th-century mathematician Carlo Rinaldini studied gall-inducing insects, air convection, and the design of thermometers? The nomination discussion and review may be seen at Template:Did you know nominations/Carlo Rinaldini. You are welcome to check how many pageviews the nominated article or articles got while on the front page (here's how, Carlo Rinaldini), and the hook may be added to the statistics page after its run on the Main Page has completed. Finally, if you know of an interesting fact from another recently created article, then please feel free to suggest it on the Did you know talk page.

SL93 (talk) 00:03, 19 June 2025 (UTC)[reply]

Hetch Hetchy power generation

The source cited for Hetch Hetchy power generation loss with restoration doesn't line up with the phrasing you've included. Saying it would "make up for only a fraction" doesn't quite give an accurate picture. According to SFPUC filings, the annual power generation is 1,547 GWh and the source has the power generation reduction at 339 GWh. That's 22% drop in production. In this context, the "only a fraction" phrasing appears inaccurate and I have phrased this to better reflect the source and reality. 45thingitis (talk) 13:19, 11 July 2025 (UTC)[reply]

I rephrase to highlight the fraction you've pointed out. — hike395 (talk) 16:33, 11 July 2025 (UTC)[reply]

In appreciation

		The Good Article Rescue Barnstar
		This is presented to you by the GAR process in recognition of your sterling work in helping Mount Adams (Washington) retain its Good Article status. Please feel free to display the GA icon on your userpage. Keep up the good work! ~~ AirshipJungleman29 (talk) 17:02, 11 July 2025 (UTC)[reply]

Thanks, AJ! I love rescuing Good Articles that have strayed off the path. — hike395 (talk) 06:13, 13 July 2025 (UTC)[reply]

Request

Hello, Hike395.

Could you please rename Waipio Valley to the correct spelling Waipiʻo Valley? In Hawaii, as well as in official U.S. documents, Hawaiian spelling is always used for Hawaiian place names.

Yours sincerely, Oratas (talk) 14:45, 19 July 2025 (UTC)[reply]

Re: Talk:Robin Williams...

Am wondering about your decision to keep year-old threads and to also increase the number of threads-left/threads-to-archive on this talk page. - Shearonink (talk) 15:55, 24 August 2025 (UTC)[reply]

@Shearonink: Thanks for asking! WP:TALKSIZE states that

Large talk pages are difficult to read and load slowly over slow connections. As a rule of thumb, archive closed discussions when a talk page has numerous resolved or stale discussions

Discussion on Talk:Robin Williams has died down: there have only been 5 threads over the last year. I believe that 5 threads are not difficult to read, and the current talk page is only 6K, smaller than most image thumbnails, so will load quickly over slow connections. The default autoarchiving is minthreads=5/minthreadstoarchive=2, so I set the archiving to that. Given the lack of discussion, 12 months seems like a reasonable expiration date --- many Talk pages with little discussion have expiration of 12 months.

Hope this helps! — hike395 (talk) 16:29, 24 August 2025 (UTC)[reply]

It seems excessive to me to retain threads that have no replies for over a year but ok. - Shearonink (talk) 16:42, 24 August 2025 (UTC)[reply]

Infobox settlement

Hi @Hike395, I've just been thinking back to a conversation we had at Template talk:Infobox settlement/Archive 33 in June last year. I wondered if there were any plans in place yet to port convinfobox over to Lua please? I know you said it was a big job though. Many thanks Dgp4004 (talk) 15:10, 20 September 2025 (UTC)[reply]