User talk:Hike395

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)

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

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

Seven years

Precious

Seven years!

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

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

Edziza

Hi Hike395, do you have any interest in the Mount Edziza volcanic complex in BC? The reason I ask is because I know you've edited Mount Edziza in the past. I've been in the process of rewriting and expanding the Mount Edziza volcanic complex article in my sandbox for quite some time, having picked up in April after being relatively inactive since last October. Volcanoguy 00:14, 4 June 2023 (UTC)

I don't have any special expertise or interest in Mount Edziza -- I just made a few minor edits in the past. Your expanded version looks quite promising! — hike395 (talk) 03:49, 4 June 2023 (UTC)

Thanks, it's turning out to be the largest article I've ever wrote/expanded. Once I'm finished with it I plan on requesting a peer review and then eventually nominate it for FA. I can let you know when that time comes if you would like. Volcanoguy 05:23, 4 June 2023 (UTC)

Sure thing! — hike395 (talk) 15:28, 4 June 2023 (UTC)

More than four weeks in and just a single general support. Unless the nomination makes significant further progress towards a consensus to promote over the next two or three days I'm afraid that it is liable to be archived. Volcanoguy 23:35, 23 February 2024 (UTC)

Hi Hike, Volcanism of the Mount Edziza volcanic complex is at FAC if you're interested in participating. Volcanoguy 22:08, 16 September 2024 (UTC)

DYK for Red Sea mangroves

On 30 June 2024, Did you know was updated with a fact from the article Red Sea mangroves, which you recently created, substantially expanded, or brought to good article status. The fact was ... that despite a global decline in mangrove forests, Red Sea mangroves have expanded in area since 1972? The nomination discussion and review may be seen at Template:Did you know nominations/Red Sea mangroves. You are welcome to check how many pageviews the nominated article or articles got while on the front page (here's how, Red Sea mangroves), 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.

Z1720 (talk) 00:03, 30 June 2024 (UTC)

Category:Pages using Infobox boxer (amateur) with conflicting parameters has been nominated for deletion

Category:Pages using Infobox boxer (amateur) with conflicting parameters has been nominated for deletion. 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. Gonnym (talk) 16:47, 22 July 2024 (UTC)

Wildfire maps (.gif versions)

Hello!

I've noticed your substitution of the .png versions of the wildfire maps I've been adding—I wanted to say (1) thank you, and (2) I'm in the process of updating the map format for many of them. I've gone through many versions of data representation/symbology over the past 1.5 years and am finally beginning to standardize the earlier maps to match the later ones. I don't want you to have to duplicate your work, so it may be worth pausing for 1 to 3 weeks while I get caught up, after which the versions will be more static.

Best, Penitentes (talk) 18:54, 28 August 2024 (UTC)

Thanks for making such well-made maps! I'm not systematically converting them, just as I happen to come across them. I'll wait a couple of weeks before I convert any other ones. — hike395 (talk) 03:05, 29 August 2024 (UTC)

reverts in Commons

I notice you are engaged in mass reverts of my edits in Commons. Why are you doing this? I think, based on available facts, that my edits are correct. Thanks. Hmains (talk) 00:40, 2 October 2024 (UTC)

@Hmains: I'm not mass reverting your categorizations, which are largely good. Because I live in the area, I have a fair amount of local knowledge of the area. I can find miscategorizations that you may not realize that you are introducing. There may also be definitional issues. More specifically, none of the following images:

• 
• 
• 
• 
• 
• 
• 
• 

show the summit of Mount Morrison, Mono Jim Peak, nor Mini Morrison, but only the slopes of the Morrison massif rising from Convict Lake. The last two images are not even taken in the direction of Morrison, but instead show the opposite side of Convict Lake.

I also removed c:Category:Skelton Lake from File:Pyramid and Herlihy peaks.jpg because that isn't Skelton Lake (it's too far from the base of the mountains), and c:Category:Pyramid Peak (Mono County, California) doesn't exist. The latter category is unlikely to contain many pictures, so I would recommend not creating it. I cleaned up a number of categories (e.g., c:Category:Skelton Lake, c:Category:Mini Morrison, etc.) leaving images that illustrate the topic.

Hope this helps. — hike395 (talk) 03:25, 2 October 2024 (UTC)

Later -- Looking at the original image of File:Pyramid and Herlihy peaks.jpg here at flickr, I believe that is the east shore of Lake Mary. I took a picture facing the other way from the top of the red peak on the left, you can see that Lake Mary is quite a bit west of the ridge. I'll place it into the correct categorization — hike395 (talk) 03:32, 2 October 2024 (UTC)

Yes, it does help, of course. And thanks for your correction edits. Hmains (talk) 03:34, 2 October 2024 (UTC)

Nomination for deletion of Template:Infobox dim/core

Template:Infobox dim/core has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Gonnym (talk) 22:08, 14 October 2024 (UTC)

Re: Module:Infobox mapframe now supports all zoom dimensions

Hey there, thanks for the note!

Does that mean that we stop passing the |zoom= value calling {{map zoom}} with complex parameters, and instead simply pass all of these individual ones instead?

--Joy (talk) 06:27, 8 November 2024 (UTC)

Ah, sorry, I saw [1] after writing this message :)

On related note, I think the biggest actual issue I noticed with zooming so far was with the river infobox, where there was nothing to map because the input was free-form and we don't have a parser to guess from that. --Joy (talk) 06:30, 8 November 2024 (UTC)

@Joy: I modified {{Infobox river}} to default to the geohack "river" type, which should show a mapframe map that spans 20km in the infobox. I haven't seen any examples where this default is used, however. — hike395 (talk) 16:29, 8 November 2024 (UTC)

You can see e.g. Uba (river) where I had to force mapframe-zoom to a more useful value. If you edit the call to leave out the zoom setting, it's pretty crappy. --Joy (talk) 16:42, 8 November 2024 (UTC)

I modified Uba (river) to set |mapframe-length_km= to be the same value as |length=. You can see it looks pretty good.

The easiest thing may be to use AWB to go through and try to set |mapframe-length_km= or |mapframe-length_mi= to be an extracted value from |length=, when mapframe is present. A more complex solution is to create |length_km=, |length_mi=, and |length_ref= and then use AWB to feed both the length field and the mapframe. That will make neater infoboxes but will be a more fragile AWB run. I may attempt the first soon. What do you think? — hike395 (talk) 18:15, 8 November 2024 (UTC)

It seems to me that if we're going to undertake such a huge effort to parse existing length fields as input, we should use normal length_* as output, not the specific mapframe-*. --Joy (talk) 19:14, 8 November 2024 (UTC)

After some experimentation, I'm not confident that I can craft the regex required for these, so will not do either yet. — hike395 (talk) 01:35, 9 November 2024 (UTC)

@Joy: After more work, I've figured things out. I added parameters like |length_km= and |basin_size_mi2=, hooked those up to mapframe zoom, and am starting to (slowly) convert over with AWB. Do you have access to AWB? — hike395 (talk) 17:37, 9 November 2024 (UTC)

Aha, I see the edits from your contributions. I happen to have never used AWB myself, but the idea is pretty straightforward. I assume you wrote a bunch of regexes to convert the parameter values? Can I use them in JWB so I don't have to use the .NET program? --Joy (talk) 19:36, 9 November 2024 (UTC)

I don't know enough about WP:JWB, but I placed a specification of the task at User:Hike395/River. You may find it useful if you want to work on it, also. — hike395 (talk) 21:56, 9 November 2024 (UTC)

Later -- simplified it down to 4 regex, which will hopefully make it easier on you. — hike395 (talk) 22:09, 9 November 2024 (UTC)

Thanks, it seems to work quite well. I do wonder if we're both running the same script, aren't we going to cause each other to have to skip a lot? :) Maybe I could just move to some other part of the sorted list, like from letter N onwards or something. --Joy (talk) 23:08, 9 November 2024 (UTC)

Also, should we tune the regex handling of whitespace so we preserve the original indentation? I don't know if anyone will complain at the wholesale squashing of that. --Joy (talk) 23:11, 9 November 2024 (UTC)

I don't think we can easily preserve whitespace, since we're changing things around pretty drastically. I haven't seen people object to changing it, since it doesn't appear to readers. — hike395 (talk) 04:51, 10 November 2024 (UTC)

@Joy: I'm going on wikibreak for a few days, so feel free to run JWB. I (somewhat) fixed the spacing issue by adding a few spaces in the replacement (like you did, I think). — hike395 (talk) 14:51, 11 November 2024 (UTC)

Yeah I generally added the spaces because most river infoboxes seem to have them, so it fits somewhat better. I still have an occasional situation where I have to manually intervene to add a final enter, but it's generally infinitely quicker than doing it all manually. Thanks again. --Joy (talk) 15:20, 11 November 2024 (UTC)

BTW my regex updates are at User:Joy/JWB-settings.json, not sure if that's visible to all. --Joy (talk) 15:21, 11 November 2024 (UTC)

BTW, I realized that this could be done more effectively with this kind of PCRE:

::::::s/\b(\s*)?\|\s*(length|basin_size)(\s*)?=\s*{{(convert|cvt)\|([\d\.,]+)\|((?:km|mi)2?)[^}]*}}(\s*[^\|\n\s}][^\|\n}]*[^\|\n\s}])?(\s*[\|}\n])/$1| $2_$6$3= $5${7:+$1|$3$2_ref = $7:}$8/g ::::::

::::::s/\b(\s*)?\|\s*(length|basin_size)(\s*)?=\s*{{(convert|cvt)\|([\d\.,]+)\|(sqmi)[^}]*}}(\s*[^\|\n\s}][^\|\n}]*[^\|\n\s}])?(\s*[\|}\n])/$1| $2_mi2$3= $5${7:+$1|$3$2_ref = $7:}$8/g ::::::

But the regex engine used doesn't have the replacement feature, cf. User talk:Joeytje50/JWB#different regex engine support? --Joy (talk) 08:32, 13 November 2024 (UTC)

JFTR, I was able to fine-tune the JS regex so it mostly doesn't require intervention for the common cases, it's in the uploaded settings JSON file. --Joy (talk) 11:30, 25 November 2024 (UTC)

Whoops

I just reverted you by mistake [2] due to an edit conflict. I think it may be for the best, though, because the content by the IP seemed unsourced. Perception312 (talk) 15:05, 3 December 2024 (UTC)

No problem at all! I think your version is better. — hike395 (talk) 15:07, 3 December 2024 (UTC)

Changes to the whitelist and cite gnis2

This {{'cite gnis2','GNIS 0'},{'%a.*_USGS$'}} doesn't appear to be working correctly, see Mount Aldrich as an example, for CITEREFKoettlitz_Névé_USGS in Koettlitz Glacier. -- LCU ActivelyDisinterested «@» °∆t° 16:55, 5 December 2024 (UTC)

Also CITEREFBalsley_Peak_USGS in Alexandra Mountains. -- LCU ActivelyDisinterested «@» °∆t° 16:56, 5 December 2024 (UTC)

Thanks for letting me know, I will investigate. — hike395 (talk) 02:34, 6 December 2024 (UTC)

@ActivelyDisinterested: There was a typo in the whitelist ("cite gnis2" instead of "Cite gnis2"). Now fixed (along with other issues). — hike395 (talk) 05:14, 6 December 2024 (UTC)

Thanks for the fix. -- LCU ActivelyDisinterested «@» °∆t° 09:48, 6 December 2024 (UTC)

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)

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

Thank you for helping with Transactionalism!

I wanted to thank you for helping finish combining duplicate sources for the Transactionalism page! TheYearbookTeacher (talk) 11:50, 8 December 2024 (UTC)

Happy to help! — hike395 (talk) 14:53, 8 December 2024 (UTC)

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)

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)

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

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

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

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)

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)

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)

@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)

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)

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)

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)

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

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)

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

{{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)

@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)

@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)

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)

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)

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)

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)

@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)

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)