This user may have left Wikipedia. Chinissai has not edited Wikipedia since July 2017. As a result, any requests made here may not receive a response. If you are seeking assistance, you may need to approach someone else. |
Sorry about that I must have clicked the wrong button on my view. It was showing me that you were doing the opposite of what you were doing. I must have hit undo instead of diff. - Djsasso ( talk) 15:25, 16 May 2008 (UTC)
So much thanks for the help. Keep it up, we could (so could I) use a lot more of them! Mitch32( Wikipedia's worst Reform Luddite.) 04:28, 1 September 2013 (UTC)
Howdy. I appreciate the help reverting DJV11181988 on those senseless changes, just too many for me to handle. Anyway, when you get the chances, could you knock off the rest of NY's KMLs for decommissioned stuff and maps that you can do at least? Mitch32( Any fool can make a rule, And any fool will mind it.) 04:59, 9 June 2014 (UTC)
Hello, Chinissai, and welcome to Wikipedia! Thank you for your contributions. I hope you like this place and decide to stay. Here are some pages that you might find helpful:
Please
sign your name on talk pages using four tildes (~~~~); this will automatically produce your username and the date. If you need help, check out
Wikipedia:Questions, ask me on my talk page, or place {{helpme}}
on your talk page and ask your question there.
If you are interested, there is already a community of users who are roadfans or who edit articles about roads, just like you! Stop by any of these WikiProjects— WP:HWY (worldwide), WP:AURD (Australia), WP:CRWP (Canada), WP:INR (India), WP:UKRD (United Kingdom), or WP:USRD (United States)—and contribute. If your interest is in roads in the United States, there is an excellent new user's guide. There is a wealth of information and resources for creating a great article. If you have questions about any of these WikiProjects, you can ask on each project's talk page, or you can ask me!
If you like communicating through IRC, feel free to ask questions at #wikipedia-en-roads connect as well. Here, there are several editors who are willing to answer your questions. For more information, see WP:HWY/IRC.
Wow, you actually made a map for Interstate 26 in South Carolina. I didn't think anybody was going to do that. Thanks. --------- User:DanTD ( talk) 01:18, 2 September 2013 (UTC)
Hello! I'm enjoying seeing the new route maps you're putting up for state highways. (I'm looking in New Hampshire at the moment.) They will be a big help for readers of the articles. One question: would it be possible to display the maps in something other than straight lat/long? At the moment, it appears that the longitude values are given the same distances as the latitude values, which makes maps appear squashed in the north-south direction. A different projection (state plane or UTM, for example) would solve the problem. Anyway, I appreciate all the work you're putting into the maps! -- Ken Gallager ( talk) 13:12, 5 September 2013 (UTC)
I said it before on Commons, but holy crap your maps are awesome. If you run out of ideas, there is a category for the most-needed maps here. In addition, there is a USRD map request page. There is some crossover between the two. Thanks for your work! – Fredddie ™ 14:40, 21 September 2013 (UTC)
Christopher Thompson User talk:Christopher Thompson How do I make my own map to show it on pages — Preceding unsigned comment added by Christopher Thompson ( talk • contribs) 19:13, 19 October 2017 (UTC)
One of the best pieces of advice I ever received for alternative text was related to the infobox maps. Basically, it should give a brief description of where the highway is, not just say that it is a map of the highway. For example, "M-185 is a highway that runs around Mackinac Island in the Straits of Mackinac between Michigan's Upper and Lower peninsulas" while the caption says, "Map of the Straits of Mackinac with M-185 highlighted in red". (Past advice for alt text was to describe the image as if you were telling someone over the phone about it; the better advice is that the alt text should describe what the image is attempting to add to the article, or use a generic "photograph" or "map" if the caption does so already.) Imzadi 1979 → 22:53, 11 July 2014 (UTC)
|map_alt=
would give the condensed summary up front and fulfill the purpose of describing why we bothered to include a map in the first place.
Imzadi 1979
→ 00:50, 12 July 2014 (UTC)In lieu of not having Dispenser's project watchlist, I created a mega RC page at Special:RecentChangesLinked/User:Fredddie/Watchlist. – Fredddie ™ 22:42, 11 September 2014 (UTC)
What do you think of Special:Contributions/108.49.190.49? – Fredddie ™ 02:41, 9 October 2014 (UTC)
Thank you for the improved map of ABP. I believe it needs a slight tweak, as a section of Concord Avenue is highlighted in red, in contradiction to the statement in the article that "The southern terminus of the parkway is the westernmost of the two Fresh Pond rotaries" (emphasis added). Best wishes, Hertz1888 ( talk) 11:29, 30 July 2015 (UTC)
Do you think the article on I 87 is ready to be nominated for GA? Everything seems referenced. I did very little work on it so I would not be the one to nominate it. PointsofNoReturn ( talk) 02:13, 1 August 2015 (UTC)
The |needs-kml=
parameter has been superseded in normal usage. The banner now checks to see if a KML exists, and based on that, it will automatically display whether or not one is present. We only need to use the parameter to override that check for articles that do not, and will not, have a KML, something like
Michigan State Trunkline Highway System or
Michigan left. For talk pages of "regular articles" that have the parameter present, it's sufficient to remove |needs-kml=yes
and just save the page, or just purge the page.
Imzadi 1979
→ 02:44, 7 November 2015 (UTC)
The Original Barnstar | |
Thanks for the KMLs. Rs chen 7754 21:09, 7 November 2015 (UTC) |
Do you plan on taking out the rest of Colorado? If so, I'll just start on Florida. T C N7JM 18:21, 20 November 2015 (UTC)
Hi,
You appear to be eligible to vote in the current
Arbitration Committee election. The
Arbitration Committee is the panel of editors responsible for conducting the Wikipedia
arbitration process. It has the authority to enact binding solutions for disputes between editors, primarily related to serious behavioural issues that the community has been unable to resolve. This includes the ability to impose
site bans,
topic bans, editing restrictions, and other measures needed to maintain our editing environment. The
arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate, you are welcome to
review the candidates' statements and submit your choices on
the voting page. For the Election committee,
MediaWiki message delivery (
talk) 13:52, 24 November 2015 (UTC)
Unless the locations are contentious for some reason, we've traditionally left that column uncited. In fact, I don't think the location column is cited in any of the 25 featured articles on Michigan highways and roadways. We have cited the milepost column on the basis that statistics like mileages should be cited, and since the MPs are cited to a source that gives the location and the intersecting roadway, it's been a long-time practice that the other columns do not need to be explicitly cited, unless there's some controversy over the contents of that column. I fail to see where there's any controversy on I-91, so the reference is unnecessary. Imzadi 1979 → 23:08, 3 December 2015 (UTC)
WP:HWY/IRC has the details, but a bunch of us chat in a channel on IRC to facilitate editing. Of course, we take any big decisions to the appropriate talk page, but we've found that it helps to hammer through the initial thoughts about a new idea on IRC before taking a second draft on-wiki... Also, it's just faster some times when debugging stuff. Imzadi 1979 → 05:29, 18 April 2016 (UTC)
Since you're working on it, I have some questions:
I'm sure I'll have some more, but those are the things I'd like to see the most. – Fredddie ™ 21:36, 1 May 2016 (UTC)
@ Fredddie: Thanks for touching base.
1. Yes, the goal is to use shared road data modules as much as possible. We should do away with modules in Infobox road that are duplicate of those in Road data. In the browse section, the live version is already using Road data modules for shields and abbrs.
shieldmain
field should be used, to mimic the template name, with perhaps a fallback to shield
. We will need to figure out how to deal with banners. This will be easier if we don't need bannermain
.2. Added simple support for one nested infobox (see the testcases page). The skew seems to be Infobox's fault. We can definitely support a sequence of nested infoboxes and recursively nested infoboxes. Just curious, what's a use case for this?
I see you're working on length conversions now. Evad37 (or maybe it was Nbound) suggested a while back that when we imperialists convert one-half mile, it's preferable to convert to meters instead of kilometers. 1⁄2 mile (800 m) > 1⁄2 mile (0.80 km). Perhaps when the conversion is under 1 km, it should default to meters.
Thoughts? – Fredddie ™ 23:20, 6 May 2016 (UTC)
{{
routelist row/sandbox}}
, so we will need a parameter to request for unit change when invoked from {{
infobox road/sandbox}}
. In principle, it is doable, but not too trivial.
Chinissai (
talk) 23:36, 6 May 2016 (UTC)Would you be able to do something similar to Module:Jctint/USA for the Australian Jctint/core-based templates? {{ AUS-WAint}}, {{ ACTint}}, {{ NSWint}}, {{ NTint}}, {{ QLDint}}, {{ SAint}}, {{ TASint}}, and {{ VICint}} currently pass near-identical parameters through to {{ AUSintcore}}, which reassigns them through to {{ Jctint/core}}. (I was going to post this at the USRD thread, but decided it was a bit too offtopic for there) - Evad37 [ talk 02:21, 18 May 2016 (UTC)
@ Evad37: Can you help test Module:Jctint/AUS for me? You can replace state templates that call {{ AUSintcore}} with the following form of invocation, e.g., for ACT:
{{#invoke:Jctint/AUS|jctint |state=ACT |LGA={{{district|}}} |LGA_note={{{district_note|}}} }}
For other states, remove both LGA parameters above and change |state=
accordingly. Use WA for Western Australia.
I tried previewing {{ NSWint}} and {{ VICint}} with Newell Highway and it appeared okay to me. Note that the module uses Module:Jctint/core/sandbox, so you might not want to deploy this yet. (However, I doubt I will make any more significant changes to the sandbox in the near future, because it should now be general enough to handle junctions globally.) Chinissai ( talk) 14:45, 20 May 2016 (UTC)
Thanks! Looking pretty good so far, with the tests I've done. Having enumarated sub2 parameters (|location#=
) is cool, though there are a few issues with the current setup:
|LGA#=
for Australia), and be really cool (if its not too complicated) to be able to use enumerated versions of the formatting-shortcut parameters, e.g. |LGAC1=Foo
|LGAS2=Bar
|LGAT3=Baz
becomes [[City of Foo|Foo]]–[[Shire of Bar|Bar]]–[[Town of Baz|Baz]] tripoint
- Evad37 [ talk 03:11, 21 May 2016 (UTC)
|LGA1=Foo|sub1area1=pC|LGA2=Bar|sub1area2=pS|LGA3=Baz|sub3aread3=pT
. In this case, you will have to add "LGA" as an alias for |sub1=
in
Module:Road data/strings/AUS, but |LGA=
is already reserved for special text, so I couldn't reuse that. You can also customize |sub1area=
to something else, e.g., sub1area_param = "LGAarea"
.The Board of Trustees of the Wikimedia Foundation has appointed a committee to lead the search for the foundation’s next Executive Director. One of our first tasks is to write the job description of the executive director position, and we are asking for input from the Wikimedia community. Please take a few minutes and complete this survey to help us better understand community and staff expectations for the Wikimedia Foundation Executive Director.
Thank you, The Wikimedia Foundation Executive Director Search Steering Committee via MediaWiki message delivery ( talk) 21:49, 1 June 2016 (UTC)
I'm pretty sure
this edit, if it does what I think it does, just broke dozens of articles. It's completely redundant (and useless in my opinion) to require a |ctdab=
when |county=
is in the same template instance. –
Fredddie
™ 16:02, 11 June 2016 (UTC)
|county=
inserts a county column and should not have other functions. If you want to disambiguate a location, you need to use |ctdab=
. This is not redundant, as you specify two things that happen to be the same for two different outcomes. Otherwise, it is possible to have a template invocation that has |county=
, but the location (township, so far) that does not require disambiguation ends up getting disambiguated anyway. This is surely undesirable moving forward.
Chinissai (
talk) 16:14, 11 June 2016 (UTC)
|county=
in certain invocations, but |ctdab=
in others (in addition to the undesirable behavior above); they should be consistent among all.
Chinissai (
talk) 16:34, 11 June 2016 (UTC)
I understand that the signage has Amherst on it, however this is not how all the other exits are listed (they haven't all been scoped out on Google Maps for accuracy). The column titled "Destinations" actually has a citation listed for it [2], which lists EB/WB as "32, Palmer, Ware". Unless there is a plan that will ultimately fix this discrepancy for all the exits listed it should be reverted to the way MassDOT has it listed on their official website. Garchy ( talk) 20:26, 13 June 2016 (UTC)
I'm curious why you're changing |town=
to |location=
like in this edit
[3]. Towns in Wisconsin are the same thing as townships in other states and do not refer to a small city in the generic sense. I reviewed a few other edits you made last night/this morning that were on my watchlist and thought they were correct previously.–
Fredddie
™ 14:29, 1 October 2016 (UTC)
|town=
does not handle all of these cases (the latter two, in particular), and I am trying to make that work, ideally with
Module:Jctint/USA. The problem is that |town=
and |ctdab=
are overloaded to prevent the two case above, so we need a way to accommodate them. One way is like what I did, and like in New York articles: towns without a disambiguator are coded using |location=
and displayed as-is without Town of, towns with (town) disambiguator use |town=
, which I regard as sugar for |location=
with |area=town
, and towns with county disambiguator use |location=
and |ctdab=
and are displayed without Town of. This way, we can use both |area=
and |ctdab=
to handle the third case. If one needs the prefix Town of displayed (not entirely sure why, if the town is unique among incorporated places within a county), the fourth case has to be handled accordingly without using any kind of disambiguator to trigger the prefix. One way to do that is to dedicate |town=
for the prefix and use |area=
and |ctdab=
for the rest, but this just seems an overkill. Either way, I think we should make the usage for New York and Wisconsin consistent.
Chinissai (
talk) 15:13, 1 October 2016 (UTC)
{{{town}}}
and {{{ctdab}}}
do not handle this, and I am not willing to resort to |location_special=
, which suggests that there is a fundamental issue with how parameters are intended to work with all cases. If it's not our problem to fix town article names, it is our problem to fix how we handle them. And if we can't be consistent, we shouldn't try to.
Chinissai (
talk) 16:46, 1 October 2016 (UTC)|village=Bridgeport
(or |location=Bridgeport|area=village
if we don't have a village param) and redirect the
Village of Bridgeport redlink to the community disambiguator. The better solution is to use |town=Bridgeport
to get
Town of Bridgeport and move on. –
Fredddie
™ 17:07, 1 October 2016 (UTC)How about
Deerfield (town), Dane County, Wisconsin? (Again, no |location_special=
, as this naming convention is not uncommon.)
Speaking of convention, I had to look deeper into how these things are named (see Talk:List of towns in Wisconsin, Wikipedia talk:WikiProject Wisconsin/Archive 4#Naming convention for unincorporated communities, and Wikipedia talk:WikiProject Wisconsin/Archive 5#Yet another discussion about naming towns), and it turns out "inconsistent" is not the right word to use here. There are rules deciding how articles get named, but the resulting names can be ambiguous: Looking at Summit, Waukesha County, Wisconsin, it is usually impossible to tell whether Summit is a town or a village. So, in that respect, one could argue that, to be clear to readers, we should prefix Summit with Village of, which raises the same question I asked earlier: Why do we need to do this if we know there is only one Summit in Waukesha County, whether it be a village or a town? Well, it turns out, as you pointed out with Bridgeport, that the article covers both village and town, even if it says village in the infobox! This is illustrated by Interstate 94 in Wisconsin, which points to Summit (town), Waukesha County, Wisconsin, which redirects to the article in question.
So, I agree that a disambiguator is needed if the actual article talks about multiple entities, but this should be reflected in the link also, not just the displayed text. Otherwise, our template would permit incorrect coding like |town=Marshall|ctdab=Dane
to give
Town of Marshall, and it would be difficult to police. (Same issue with "New York," whether it is state or city. There is an ongoing operation to pipe [[New York (state)|New York]] even if the state article remains at "New York.") I suggest we do the same thing here. If we need Town of prefixed, use |town=
, but it will always add (town) disambiguator to the link. Create redirects as necessary. |ctdab=
works as in the general case. This way we can handle the Town of Deerfield properly. Otherwise, there is only one such named entity within the county, so no disambiguator is needed, hence no need to prefix with Town of.
You raised a good point about the equivalence with townships in other states, that Township is always displayed alongside the name, and suggested that we do the same with Wisconsin towns. I would note that it was trivial for townships, because every township article name has Township suffixed, so |township=
simply adds Township to both the link and displayed text. We could not do the same with towns by leaving the link alone without risking the possibility of incorrect coding above; some tradeoff needs to be made.
Chinissai (
talk) 19:20, 1 October 2016 (UTC)
I would be OK with adding (town) to every case of |town=
. Redirects are cheap. –
Fredddie
™ 21:45, 1 October 2016 (UTC)
Hello, Chinissai. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2016 election, please review the candidates' statements and submit your choices on the voting page. MediaWiki message delivery ( talk) 22:08, 21 November 2016 (UTC)
Hello, Chinissai. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2017 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery ( talk) 18:42, 3 December 2017 (UTC)
Template:Attached KML/Massachusetts Route 198 has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Gonnym ( talk) 08:17, 25 August 2023 (UTC)
Template:Attached KML/Massachusetts Route 96 has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Gonnym ( talk) 08:18, 25 August 2023 (UTC)
Template:Attached KML/Southern Artery has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Gonnym ( talk) 15:52, 20 September 2023 (UTC)
This user may have left Wikipedia. Chinissai has not edited Wikipedia since July 2017. As a result, any requests made here may not receive a response. If you are seeking assistance, you may need to approach someone else. |
Sorry about that I must have clicked the wrong button on my view. It was showing me that you were doing the opposite of what you were doing. I must have hit undo instead of diff. - Djsasso ( talk) 15:25, 16 May 2008 (UTC)
So much thanks for the help. Keep it up, we could (so could I) use a lot more of them! Mitch32( Wikipedia's worst Reform Luddite.) 04:28, 1 September 2013 (UTC)
Howdy. I appreciate the help reverting DJV11181988 on those senseless changes, just too many for me to handle. Anyway, when you get the chances, could you knock off the rest of NY's KMLs for decommissioned stuff and maps that you can do at least? Mitch32( Any fool can make a rule, And any fool will mind it.) 04:59, 9 June 2014 (UTC)
Hello, Chinissai, and welcome to Wikipedia! Thank you for your contributions. I hope you like this place and decide to stay. Here are some pages that you might find helpful:
Please
sign your name on talk pages using four tildes (~~~~); this will automatically produce your username and the date. If you need help, check out
Wikipedia:Questions, ask me on my talk page, or place {{helpme}}
on your talk page and ask your question there.
If you are interested, there is already a community of users who are roadfans or who edit articles about roads, just like you! Stop by any of these WikiProjects— WP:HWY (worldwide), WP:AURD (Australia), WP:CRWP (Canada), WP:INR (India), WP:UKRD (United Kingdom), or WP:USRD (United States)—and contribute. If your interest is in roads in the United States, there is an excellent new user's guide. There is a wealth of information and resources for creating a great article. If you have questions about any of these WikiProjects, you can ask on each project's talk page, or you can ask me!
If you like communicating through IRC, feel free to ask questions at #wikipedia-en-roads connect as well. Here, there are several editors who are willing to answer your questions. For more information, see WP:HWY/IRC.
Wow, you actually made a map for Interstate 26 in South Carolina. I didn't think anybody was going to do that. Thanks. --------- User:DanTD ( talk) 01:18, 2 September 2013 (UTC)
Hello! I'm enjoying seeing the new route maps you're putting up for state highways. (I'm looking in New Hampshire at the moment.) They will be a big help for readers of the articles. One question: would it be possible to display the maps in something other than straight lat/long? At the moment, it appears that the longitude values are given the same distances as the latitude values, which makes maps appear squashed in the north-south direction. A different projection (state plane or UTM, for example) would solve the problem. Anyway, I appreciate all the work you're putting into the maps! -- Ken Gallager ( talk) 13:12, 5 September 2013 (UTC)
I said it before on Commons, but holy crap your maps are awesome. If you run out of ideas, there is a category for the most-needed maps here. In addition, there is a USRD map request page. There is some crossover between the two. Thanks for your work! – Fredddie ™ 14:40, 21 September 2013 (UTC)
Christopher Thompson User talk:Christopher Thompson How do I make my own map to show it on pages — Preceding unsigned comment added by Christopher Thompson ( talk • contribs) 19:13, 19 October 2017 (UTC)
One of the best pieces of advice I ever received for alternative text was related to the infobox maps. Basically, it should give a brief description of where the highway is, not just say that it is a map of the highway. For example, "M-185 is a highway that runs around Mackinac Island in the Straits of Mackinac between Michigan's Upper and Lower peninsulas" while the caption says, "Map of the Straits of Mackinac with M-185 highlighted in red". (Past advice for alt text was to describe the image as if you were telling someone over the phone about it; the better advice is that the alt text should describe what the image is attempting to add to the article, or use a generic "photograph" or "map" if the caption does so already.) Imzadi 1979 → 22:53, 11 July 2014 (UTC)
|map_alt=
would give the condensed summary up front and fulfill the purpose of describing why we bothered to include a map in the first place.
Imzadi 1979
→ 00:50, 12 July 2014 (UTC)In lieu of not having Dispenser's project watchlist, I created a mega RC page at Special:RecentChangesLinked/User:Fredddie/Watchlist. – Fredddie ™ 22:42, 11 September 2014 (UTC)
What do you think of Special:Contributions/108.49.190.49? – Fredddie ™ 02:41, 9 October 2014 (UTC)
Thank you for the improved map of ABP. I believe it needs a slight tweak, as a section of Concord Avenue is highlighted in red, in contradiction to the statement in the article that "The southern terminus of the parkway is the westernmost of the two Fresh Pond rotaries" (emphasis added). Best wishes, Hertz1888 ( talk) 11:29, 30 July 2015 (UTC)
Do you think the article on I 87 is ready to be nominated for GA? Everything seems referenced. I did very little work on it so I would not be the one to nominate it. PointsofNoReturn ( talk) 02:13, 1 August 2015 (UTC)
The |needs-kml=
parameter has been superseded in normal usage. The banner now checks to see if a KML exists, and based on that, it will automatically display whether or not one is present. We only need to use the parameter to override that check for articles that do not, and will not, have a KML, something like
Michigan State Trunkline Highway System or
Michigan left. For talk pages of "regular articles" that have the parameter present, it's sufficient to remove |needs-kml=yes
and just save the page, or just purge the page.
Imzadi 1979
→ 02:44, 7 November 2015 (UTC)
The Original Barnstar | |
Thanks for the KMLs. Rs chen 7754 21:09, 7 November 2015 (UTC) |
Do you plan on taking out the rest of Colorado? If so, I'll just start on Florida. T C N7JM 18:21, 20 November 2015 (UTC)
Hi,
You appear to be eligible to vote in the current
Arbitration Committee election. The
Arbitration Committee is the panel of editors responsible for conducting the Wikipedia
arbitration process. It has the authority to enact binding solutions for disputes between editors, primarily related to serious behavioural issues that the community has been unable to resolve. This includes the ability to impose
site bans,
topic bans, editing restrictions, and other measures needed to maintain our editing environment. The
arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate, you are welcome to
review the candidates' statements and submit your choices on
the voting page. For the Election committee,
MediaWiki message delivery (
talk) 13:52, 24 November 2015 (UTC)
Unless the locations are contentious for some reason, we've traditionally left that column uncited. In fact, I don't think the location column is cited in any of the 25 featured articles on Michigan highways and roadways. We have cited the milepost column on the basis that statistics like mileages should be cited, and since the MPs are cited to a source that gives the location and the intersecting roadway, it's been a long-time practice that the other columns do not need to be explicitly cited, unless there's some controversy over the contents of that column. I fail to see where there's any controversy on I-91, so the reference is unnecessary. Imzadi 1979 → 23:08, 3 December 2015 (UTC)
WP:HWY/IRC has the details, but a bunch of us chat in a channel on IRC to facilitate editing. Of course, we take any big decisions to the appropriate talk page, but we've found that it helps to hammer through the initial thoughts about a new idea on IRC before taking a second draft on-wiki... Also, it's just faster some times when debugging stuff. Imzadi 1979 → 05:29, 18 April 2016 (UTC)
Since you're working on it, I have some questions:
I'm sure I'll have some more, but those are the things I'd like to see the most. – Fredddie ™ 21:36, 1 May 2016 (UTC)
@ Fredddie: Thanks for touching base.
1. Yes, the goal is to use shared road data modules as much as possible. We should do away with modules in Infobox road that are duplicate of those in Road data. In the browse section, the live version is already using Road data modules for shields and abbrs.
shieldmain
field should be used, to mimic the template name, with perhaps a fallback to shield
. We will need to figure out how to deal with banners. This will be easier if we don't need bannermain
.2. Added simple support for one nested infobox (see the testcases page). The skew seems to be Infobox's fault. We can definitely support a sequence of nested infoboxes and recursively nested infoboxes. Just curious, what's a use case for this?
I see you're working on length conversions now. Evad37 (or maybe it was Nbound) suggested a while back that when we imperialists convert one-half mile, it's preferable to convert to meters instead of kilometers. 1⁄2 mile (800 m) > 1⁄2 mile (0.80 km). Perhaps when the conversion is under 1 km, it should default to meters.
Thoughts? – Fredddie ™ 23:20, 6 May 2016 (UTC)
{{
routelist row/sandbox}}
, so we will need a parameter to request for unit change when invoked from {{
infobox road/sandbox}}
. In principle, it is doable, but not too trivial.
Chinissai (
talk) 23:36, 6 May 2016 (UTC)Would you be able to do something similar to Module:Jctint/USA for the Australian Jctint/core-based templates? {{ AUS-WAint}}, {{ ACTint}}, {{ NSWint}}, {{ NTint}}, {{ QLDint}}, {{ SAint}}, {{ TASint}}, and {{ VICint}} currently pass near-identical parameters through to {{ AUSintcore}}, which reassigns them through to {{ Jctint/core}}. (I was going to post this at the USRD thread, but decided it was a bit too offtopic for there) - Evad37 [ talk 02:21, 18 May 2016 (UTC)
@ Evad37: Can you help test Module:Jctint/AUS for me? You can replace state templates that call {{ AUSintcore}} with the following form of invocation, e.g., for ACT:
{{#invoke:Jctint/AUS|jctint |state=ACT |LGA={{{district|}}} |LGA_note={{{district_note|}}} }}
For other states, remove both LGA parameters above and change |state=
accordingly. Use WA for Western Australia.
I tried previewing {{ NSWint}} and {{ VICint}} with Newell Highway and it appeared okay to me. Note that the module uses Module:Jctint/core/sandbox, so you might not want to deploy this yet. (However, I doubt I will make any more significant changes to the sandbox in the near future, because it should now be general enough to handle junctions globally.) Chinissai ( talk) 14:45, 20 May 2016 (UTC)
Thanks! Looking pretty good so far, with the tests I've done. Having enumarated sub2 parameters (|location#=
) is cool, though there are a few issues with the current setup:
|LGA#=
for Australia), and be really cool (if its not too complicated) to be able to use enumerated versions of the formatting-shortcut parameters, e.g. |LGAC1=Foo
|LGAS2=Bar
|LGAT3=Baz
becomes [[City of Foo|Foo]]–[[Shire of Bar|Bar]]–[[Town of Baz|Baz]] tripoint
- Evad37 [ talk 03:11, 21 May 2016 (UTC)
|LGA1=Foo|sub1area1=pC|LGA2=Bar|sub1area2=pS|LGA3=Baz|sub3aread3=pT
. In this case, you will have to add "LGA" as an alias for |sub1=
in
Module:Road data/strings/AUS, but |LGA=
is already reserved for special text, so I couldn't reuse that. You can also customize |sub1area=
to something else, e.g., sub1area_param = "LGAarea"
.The Board of Trustees of the Wikimedia Foundation has appointed a committee to lead the search for the foundation’s next Executive Director. One of our first tasks is to write the job description of the executive director position, and we are asking for input from the Wikimedia community. Please take a few minutes and complete this survey to help us better understand community and staff expectations for the Wikimedia Foundation Executive Director.
Thank you, The Wikimedia Foundation Executive Director Search Steering Committee via MediaWiki message delivery ( talk) 21:49, 1 June 2016 (UTC)
I'm pretty sure
this edit, if it does what I think it does, just broke dozens of articles. It's completely redundant (and useless in my opinion) to require a |ctdab=
when |county=
is in the same template instance. –
Fredddie
™ 16:02, 11 June 2016 (UTC)
|county=
inserts a county column and should not have other functions. If you want to disambiguate a location, you need to use |ctdab=
. This is not redundant, as you specify two things that happen to be the same for two different outcomes. Otherwise, it is possible to have a template invocation that has |county=
, but the location (township, so far) that does not require disambiguation ends up getting disambiguated anyway. This is surely undesirable moving forward.
Chinissai (
talk) 16:14, 11 June 2016 (UTC)
|county=
in certain invocations, but |ctdab=
in others (in addition to the undesirable behavior above); they should be consistent among all.
Chinissai (
talk) 16:34, 11 June 2016 (UTC)
I understand that the signage has Amherst on it, however this is not how all the other exits are listed (they haven't all been scoped out on Google Maps for accuracy). The column titled "Destinations" actually has a citation listed for it [2], which lists EB/WB as "32, Palmer, Ware". Unless there is a plan that will ultimately fix this discrepancy for all the exits listed it should be reverted to the way MassDOT has it listed on their official website. Garchy ( talk) 20:26, 13 June 2016 (UTC)
I'm curious why you're changing |town=
to |location=
like in this edit
[3]. Towns in Wisconsin are the same thing as townships in other states and do not refer to a small city in the generic sense. I reviewed a few other edits you made last night/this morning that were on my watchlist and thought they were correct previously.–
Fredddie
™ 14:29, 1 October 2016 (UTC)
|town=
does not handle all of these cases (the latter two, in particular), and I am trying to make that work, ideally with
Module:Jctint/USA. The problem is that |town=
and |ctdab=
are overloaded to prevent the two case above, so we need a way to accommodate them. One way is like what I did, and like in New York articles: towns without a disambiguator are coded using |location=
and displayed as-is without Town of, towns with (town) disambiguator use |town=
, which I regard as sugar for |location=
with |area=town
, and towns with county disambiguator use |location=
and |ctdab=
and are displayed without Town of. This way, we can use both |area=
and |ctdab=
to handle the third case. If one needs the prefix Town of displayed (not entirely sure why, if the town is unique among incorporated places within a county), the fourth case has to be handled accordingly without using any kind of disambiguator to trigger the prefix. One way to do that is to dedicate |town=
for the prefix and use |area=
and |ctdab=
for the rest, but this just seems an overkill. Either way, I think we should make the usage for New York and Wisconsin consistent.
Chinissai (
talk) 15:13, 1 October 2016 (UTC)
{{{town}}}
and {{{ctdab}}}
do not handle this, and I am not willing to resort to |location_special=
, which suggests that there is a fundamental issue with how parameters are intended to work with all cases. If it's not our problem to fix town article names, it is our problem to fix how we handle them. And if we can't be consistent, we shouldn't try to.
Chinissai (
talk) 16:46, 1 October 2016 (UTC)|village=Bridgeport
(or |location=Bridgeport|area=village
if we don't have a village param) and redirect the
Village of Bridgeport redlink to the community disambiguator. The better solution is to use |town=Bridgeport
to get
Town of Bridgeport and move on. –
Fredddie
™ 17:07, 1 October 2016 (UTC)How about
Deerfield (town), Dane County, Wisconsin? (Again, no |location_special=
, as this naming convention is not uncommon.)
Speaking of convention, I had to look deeper into how these things are named (see Talk:List of towns in Wisconsin, Wikipedia talk:WikiProject Wisconsin/Archive 4#Naming convention for unincorporated communities, and Wikipedia talk:WikiProject Wisconsin/Archive 5#Yet another discussion about naming towns), and it turns out "inconsistent" is not the right word to use here. There are rules deciding how articles get named, but the resulting names can be ambiguous: Looking at Summit, Waukesha County, Wisconsin, it is usually impossible to tell whether Summit is a town or a village. So, in that respect, one could argue that, to be clear to readers, we should prefix Summit with Village of, which raises the same question I asked earlier: Why do we need to do this if we know there is only one Summit in Waukesha County, whether it be a village or a town? Well, it turns out, as you pointed out with Bridgeport, that the article covers both village and town, even if it says village in the infobox! This is illustrated by Interstate 94 in Wisconsin, which points to Summit (town), Waukesha County, Wisconsin, which redirects to the article in question.
So, I agree that a disambiguator is needed if the actual article talks about multiple entities, but this should be reflected in the link also, not just the displayed text. Otherwise, our template would permit incorrect coding like |town=Marshall|ctdab=Dane
to give
Town of Marshall, and it would be difficult to police. (Same issue with "New York," whether it is state or city. There is an ongoing operation to pipe [[New York (state)|New York]] even if the state article remains at "New York.") I suggest we do the same thing here. If we need Town of prefixed, use |town=
, but it will always add (town) disambiguator to the link. Create redirects as necessary. |ctdab=
works as in the general case. This way we can handle the Town of Deerfield properly. Otherwise, there is only one such named entity within the county, so no disambiguator is needed, hence no need to prefix with Town of.
You raised a good point about the equivalence with townships in other states, that Township is always displayed alongside the name, and suggested that we do the same with Wisconsin towns. I would note that it was trivial for townships, because every township article name has Township suffixed, so |township=
simply adds Township to both the link and displayed text. We could not do the same with towns by leaving the link alone without risking the possibility of incorrect coding above; some tradeoff needs to be made.
Chinissai (
talk) 19:20, 1 October 2016 (UTC)
I would be OK with adding (town) to every case of |town=
. Redirects are cheap. –
Fredddie
™ 21:45, 1 October 2016 (UTC)
Hello, Chinissai. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2016 election, please review the candidates' statements and submit your choices on the voting page. MediaWiki message delivery ( talk) 22:08, 21 November 2016 (UTC)
Hello, Chinissai. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2017 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery ( talk) 18:42, 3 December 2017 (UTC)
Template:Attached KML/Massachusetts Route 198 has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Gonnym ( talk) 08:17, 25 August 2023 (UTC)
Template:Attached KML/Massachusetts Route 96 has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Gonnym ( talk) 08:18, 25 August 2023 (UTC)
Template:Attached KML/Southern Artery has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Gonnym ( talk) 15:52, 20 September 2023 (UTC)