![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 20 | Archive 21 | Archive 22 | Archive 23 | Archive 24 | Archive 25 | → | Archive 30 |
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please increase the number of leaders to six or more.
Askeuhd ( talk) 09:11, 3 December 2012 (UTC)
Can we add <center>...</center> around image_sky? John of Cromer in China ( talk) mytime= Mon 17:45, wikitime= 09:45, 3 December 2012 (UTC)
These two temporary maintenance categories have been around for 3+ years and are placed in all articles by this template with subdivision_name = United States (50,000 articles). Category:Infobox Settlement US maintenance appears for transclusions that provide latd, Category:Infobox US maintenance appears for those that don't.
The category descriptions link to a brief discussion with unclear guidance. The category text "{{ Infobox Settlement}} used on US cities." and the ubiquitous maintenance categories imply that US cities shouldn't be using {{ Infobox settlement}} or shouldn't be using the term "United States" (try alternatives such as "USA") – seemingly not the intended message!
What is the maintenance advice for editors? Thanks. — Mrwojo ( talk) 19:18, 2 December 2012 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
See above – two old maintenance categories are included on all U.S. settlement articles with no known maintenance required. See Averill, Vermont and Mesa, Washington as examples of the two categories being transcluded.
There's some unrelated testing going on in the template sandbox so I've dropped the template's code with edits into my own sandbox: Edited version.
The following code should be removed from the template:
{{#ifeq:{{NAMESPACE}}||{{#ifeq:{{{subdivision_name}}}|United States|{{#if:{{{latd|}}}|[[Category:Infobox Settlement US maintenance]]|[[Category:Infobox US maintenance ]]}}|}}{{#ifeq:{{{subdivision_name}}}|[[United States]]|{{#if:{{{latd|}}}|[[Category:Infobox Settlement US maintenance]]|[[Category:Infobox US maintenance]]}}|}}}}
Thanks. — Mrwojo ( talk) 16:53, 11 December 2012 (UTC)
Request withdrawn
I'd like to have the option like:
| coord = {{coord|8|54|54|N|79|35|58|W|display=inline,title|name=)}}
- DePiep ( talk) 22:02, 17 December 2012 (UTC)
OK, this is my example:
{{ Infobox organization}} has option
| coords = {{coord|31|15|25|N|32|18|30|E}}
(used in this article)
And not by individual numbers. I resurrect my request. - DePiep ( talk) 19:33, 23 December 2012 (UTC)
coord
parameter doesn't mean that it's a good idea. If you really need to embed a {{
Coord}} in this infobox, you could put it in one of the blank fields. —
Stepheng3 (
talk) 19:48, 23 December 2012 (UTC)
latd=
and longd=
. This approach is preferable mainly because it makes the coordinates available for the infobox's {{
Location map}}. Additionally, in most cases, the infobox provides the correct type and region code for the coordinates, and changes to the population_total=
parameter will be reflected in the Geohack link. —
Stepheng3 (
talk) 00:19, 24 December 2012 (UTC)
|coordinates_region=
; if that is blank or absent, it's determined by pushing |subdivision_name=
and |subdivision_name1=
through {{
CountryAbbr}}
; but note that both of those methods are defeated if |coordinates_type=
is non-blank. --
Redrose64 (
talk) 16:28, 24 December 2012 (UTC)|name=
should not be used inside an infobox.
Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits 10:37, 24 December 2012 (UTC)
|name=
should not be used inside an infobox" is explained in the coordinates template's documentation.
Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits 12:56, 26 December 2012 (UTC)We should add an |etymology=
parameter, for settlements where we have a cited explanation of the derivation or meaning of the name.
Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits 20:27, 29 December 2012 (UTC)
I propose that we add a pronunciation parameter, to take a copy of the IPA pronunciation of a place's name; for example "rɛdɪŋ" for Reading). This will make them machine readable, so that others can import and reuse them. A use case for such a facility is in this blog post about sat-nav devices mispronouncing names. As noted above, the generic "spare" parameters are not suitable for this. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:07, 10 January 2013 (UTC)
I'd like a new parameter, airport, where we could add a suitable airport (or two) for people wanting to travel to the settlement. Maybe we could add railway station also. Of course, in areas where people can't or avoid travelling by train, the railway station field can be omitted. -- BIL ( talk) 21:37, 28 December 2012 (UTC)
airport
to the template, because no one has objected its addition, only objecting using blank1_info_sec1
etc for this. However, the template is protected. If an admin includes the field airport
, I will update the documentation, and start adding this info to settlement articles. --
BIL (
talk) 17:34, 13 January 2013 (UTC)Really screws up trying to organize a page because the infobox bleeds too far down the page. Can we make it collapsible? Maybe provide a smaller version of it? -- ColonelHenry ( talk) 18:47, 21 January 2013 (UTC)
{{
Stack}}
template, which will allow an image or table to be placed right of the text and left of the infobox. I updated the article for
Stillwater Township, New Jersey to move the history section to the top (where it should be anyway) and used {{
Stack}}
to keep the gristmill image to the right of the history. That moved the remaining sections down away from the infobox and therefore the climate table and population table are to the right of the appropriate sections. --
Zyxw (
talk) 05:14, 29 January 2013 (UTC)
Infobox settlement | |
---|---|
Area | |
• City | 10,000 sq mi (30,000 km2) |
• Land | 1,000 sq mi (3,000 km2) |
• Water | 100 sq mi (300 km2) |
• Urban | 10 sq mi (30 km2) |
• Rural | 1 sq mi (3 km2) |
• Metro | 0.1 sq mi (0.3 km2) |
• blank1 | 0.01 sq mi (0.03 km2) |
• blank2 | 0.001 sq mi (0.003 km2) |
While updating the documentation for the supporting templates of Infobox settlement, I noticed the infobox is over-rounding the conversion of square miles to square kilometres, such that an area of 10,000 sq mi displays 0 km2 as the conversion (see examples to the right). The template which needs to be corrected is Template:Infobox settlement/areadisp. I have an edit request with more details at Template talk:Infobox settlement/areadisp#Edit request: Fix over-rounding in conversion of square miles to km2. Posting this here for those who don't watch the sub-template talk pages. -- Zyxw ( talk) 02:02, 5 February 2013 (UTC)
I've been thinking that there should be an incorporated-from parameter in the template, which would be filled in with whatever municipality the settlement is incorporated from. Any thoughts? King Jakob C2 23:10, 14 February 2013 (UTC)
|established_title = Incorporated
(the word "from" is obviously redundant). See for example
Brockville. --
P 1 9 9
✉ 13:18, 15 February 2013 (UTC)
Is there a parameter to indicate which seat the place falls under in a legislature? It doesn't quite fit "subdivision_typeX". – H T D 16:26, 13 February 2013 (UTC)
Currently the infobox supports five leader_nameN and leader_titleN parameters. In certain parts of California, these parameters are used to present the legislators associated with populated places. When the place is an incorporated municipality, editors can run out of parameters, as has happened for instance in Livermore, California. It would be helpful to have additional fields — at least seven, maybe as many as ten. — Stepheng3 ( talk) 22:45, 17 March 2013 (UTC) Another example is Ione, California.— Stepheng3 ( talk) 18:39, 18 March 2013 (UTC)
We can add the info to the Footnotes, but it looks bad. Needs a separate field in the formatting. — LlywelynII 15:30, 14 March 2013 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
I suggest adding Demonym(s) and Language(s) to the Infobox list of features. These two items might be inserted immediately before or after or between Nickname(s) and Motto. Many thanks.
Laird of abbeyhill ( talk) 19:24, 25 March 2013 (UTC)
|population_demonym=
.
Frietjes (
talk) 19:36, 25 March 2013 (UTC)Per this discussion, can anyone suggest a fix (for the technically challenged). Thanks in advance. RashersTierney ( talk) 18:29, 27 March 2013 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
A long time ago we discussed about the problem regarding long countries like Chile and how could be displayed a two-columns-table instead of every-image-down-under-the-previous-image in order to make the infobox more compact and shorter. We reach an agreement to merge the new {{
infobox settlement Chile}}
-features in the general infobox.
As far as I know, until now no one proposal has been made to merge both boxs.
I worked out a solution for the merge. Simply we add four new parameters (for four images) and build up a two-column-table with this images. The code is in {{
Infobox settlement/sandbox}}
version of 14:52, 9 February 2013 (current version today), and the results are shown in
Template:Infobox settlement/testcases (please use the (current) version 15:09, 9 February 2013). The example is the infobox for the City of Linares in Chile.
I had elaborated also a solution with only one new parameter but I decided to propose the 4-new-params solution.
I think the solution with 4 new parameters is better than a solution with only one new parameter, because the new code for 4 new params doesn't interfere in the logic of the "old" template or at least interfere less than the code with only one new parameter.
I ask you to inspect the new code in sandbox and, if you find it good, to support the merge. --Best regards, Keysanger ( what?) 13:54, 15 February 2013 (UTC)
Are there other editors interested in this issue?. If not, I would like to proceed to improve {{
infobox settlement Chile}}
and leave {{
infobox settlement}}
to its own destiny. --Best regards,
Keysanger (
what?) 12:09, 20 February 2013 (UTC)
{{
Infobox settlement/sandbox}}
version of 14:52, 9 February 2013 (current version today, again), and the results are shown in
Template:Infobox settlement/testcases (please use the (current) version 15:09, 9 February 2013). The example is the infobox for the City of Linares in Chile, that is case 0. There are some other people testing the population density. (I reverted their changes today, sorry).|pushpin_map_cl=
would trigger the code fork to go the the pushpin-on-the-side? this way we could re-use the image_flag (rather than needing image_flag_cl) and image_shield (rather than needing image_shield_cl). although, I think we probably want to keep image_map_cl, since we are significantly resizing the default map. also, is there a reason for having the map between the shield and the flag? and, why _cl and not _right or _side or _narrow? otherwise, no objections here.
Frietjes (
talk) 22:35, 1 March 2013 (UTC)
|pushpin_map_cl=
. The code is in the sandbox version of "21:21, 11 December 2012" and the testcase version of "21:29, 11 December 2012". But I would prefer the 4-new-params solution because it doesn't interfere with the old-code. the 4-p solution is a new block of code, full separated from the old params. It is easier for the maintenance.There seems to be something going wrong with automatic density calculation: it produces "Formatting error: invalid input when rounding". You can see this on, for example, Acapulco. I suspect it may have something to do with the most recent edit on {{ Rnd}}, but I don't have the template coding skills to figure it out myself. - htonl ( talk) 22:47, 22 February 2013 (UTC)
I'm going to go ahead and suggest that what you probably want is something for precision like:
{{#expr: {{ min| {{#expr: {{precision|{{{pop}}}}} + {{order of magnitude|{{{pop}}}}} }} | {{#expr: {{precision|{{{area}}}}} + {{order of magnitude|{{{area}}}}} }} }} - {{order of magnitude|{{#expr: {{{pop}}}/{{{area}}} }} }} }}
With appropriate formatnum and scale factors added in for converting area into the right units, etc.
For example, area = 654.2, pop = 123456, gives density = 188.7
Or, area = 650, pop = 123000, density = 190.
Dragons flight ( talk) 02:49, 23 February 2013 (UTC)
For the record, I added error trapping and converted back to the Lua version of {{ rnd}}. This will allow existing pages to render in much the same way they did before. Rather than displaying a visible error (which may be disruptive to readers), now bad pages will be added to the hidden category Category:Pages with bad rounding precision and display a number rounded to 1 - {{ order of magnitude}}, which approximates the prior behavior. It is still a good idea to fix Template:Infobox settlement/densdisp and other templates that are sending bad precision values, but now we should be able to do that without being too distracting. Dragons flight ( talk) 18:13, 23 February 2013 (UTC)
![]() | This
edit request to
Template:Infobox settlement/densdisp has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
By using a second "/sandbox2" (as Template:Infobox settlement/densdisp/sandbox2), I have corrected the typos in the 5 population-density formulas to get the complex calculations to work, by inserting the 2 missing right parentheses brackets ") )" into each {rnd} where the decimal-digit count (expected "2") was causing an expression error instead. Compare results:
You missed my point. Yes, the template sets the precision, but a correct version of that template really ought to give appropriate precision for both numbers. Sticking in some extra parens makes the expression syntactically valid, thus eliminating the error message, but I'm not sure that the output is actually correct. Consider:
Your sandbox2 seems to leave the /km^2 and /sq mi numbers with significantly different precision in most cases. In addition, in the low precision cases at the end your version seems to be giving rather more precision than is warranted. I know we can "fix" the math by adding in a few parentheses, but frankly I am inclined to think that the computation needs a more serious overall so that the results it generates are actually sensible and not just syntactically complete. It would be rather nice if someone actually familiar with this infobox would chime in with what they actually want to see as output. Dragons flight ( talk) 20:50, 27 February 2013 (UTC)
Abhishek191288 tells me that the prohibition at WP:INDICSCRIPT should apply not only to the lead sentence but also to infoboxes. I disagree. There is a place in the settlement infobox for native names, and it seems appropriate to place the native script there. See edits and reversions by Abhishek191288 at Munirabad, Chikkaballapur, Chikmagalur, Bellary and Belgaum. Comments pro or con? -- Bejnar ( talk) 07:31, 11 April 2013 (UTC)
If you look in the Tampa Bay Area article there is a typo in the Population Section. The Urban section puts a comma in the year. For example "2,783,243 (19th as of 2,008)". This comma should not exist. Chotchki ( talk) 20:06, 19 April 2013 (UTC)
Per
this thread, I have added functionality to allow the pushpin map to appear to the right of the flag, shield, emblem, logo, and one map. To enable this feature, you just need to use |pushpin_map_narrow=yes
or any non-blank value. The changes should have no visible appearance on existing transclusions. This will now enable {{Infobox settlement Chile}}
to be merged with this template per the outcome of the associated TfD. Please let me know if anything goes haywire. Thanks!
Plastikspork
―Œ(talk) 22:32, 11 May 2013 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
The 2010 census population citation is outside the parentheses, but any estimation population citations (2011 or 2012) are inside of the parentheses. Example here. T C N7JM 06:48, 28 May 2013 (UTC)
|pop_est_as_of=
may or may not include a reference, as in |pop_est_as_of=2010<ref>the source for that</ref>
or |pop_est_as_of=2010
This value has parentheses wrapped around it by the template before being displayed; and because of that, the closing parenthesis is necessarily after the </ref>
should the latter be present. To move the closing parenthesis between the year and the <ref>
would require either of two things to happen:
|pop_est_as_of=(2010)<ref>the source for that</ref>
|pop_est_note=
and display that immediately after the closing parenthesis. Editors will then need to split existing instances of |pop_est_as_of=2010<ref>the source for that</ref>
into |pop_est_as_of=2010
|pop_est_note=<ref>the source for that</ref>
{{
edit protected}}
should be open, so I've deactivated it. --
Redrose64 (
talk) 19:21, 30 May 2013 (UTC)
![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 20 | Archive 21 | Archive 22 | Archive 23 | Archive 24 | Archive 25 | → | Archive 30 |
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please increase the number of leaders to six or more.
Askeuhd ( talk) 09:11, 3 December 2012 (UTC)
Can we add <center>...</center> around image_sky? John of Cromer in China ( talk) mytime= Mon 17:45, wikitime= 09:45, 3 December 2012 (UTC)
These two temporary maintenance categories have been around for 3+ years and are placed in all articles by this template with subdivision_name = United States (50,000 articles). Category:Infobox Settlement US maintenance appears for transclusions that provide latd, Category:Infobox US maintenance appears for those that don't.
The category descriptions link to a brief discussion with unclear guidance. The category text "{{ Infobox Settlement}} used on US cities." and the ubiquitous maintenance categories imply that US cities shouldn't be using {{ Infobox settlement}} or shouldn't be using the term "United States" (try alternatives such as "USA") – seemingly not the intended message!
What is the maintenance advice for editors? Thanks. — Mrwojo ( talk) 19:18, 2 December 2012 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
See above – two old maintenance categories are included on all U.S. settlement articles with no known maintenance required. See Averill, Vermont and Mesa, Washington as examples of the two categories being transcluded.
There's some unrelated testing going on in the template sandbox so I've dropped the template's code with edits into my own sandbox: Edited version.
The following code should be removed from the template:
{{#ifeq:{{NAMESPACE}}||{{#ifeq:{{{subdivision_name}}}|United States|{{#if:{{{latd|}}}|[[Category:Infobox Settlement US maintenance]]|[[Category:Infobox US maintenance ]]}}|}}{{#ifeq:{{{subdivision_name}}}|[[United States]]|{{#if:{{{latd|}}}|[[Category:Infobox Settlement US maintenance]]|[[Category:Infobox US maintenance]]}}|}}}}
Thanks. — Mrwojo ( talk) 16:53, 11 December 2012 (UTC)
Request withdrawn
I'd like to have the option like:
| coord = {{coord|8|54|54|N|79|35|58|W|display=inline,title|name=)}}
- DePiep ( talk) 22:02, 17 December 2012 (UTC)
OK, this is my example:
{{ Infobox organization}} has option
| coords = {{coord|31|15|25|N|32|18|30|E}}
(used in this article)
And not by individual numbers. I resurrect my request. - DePiep ( talk) 19:33, 23 December 2012 (UTC)
coord
parameter doesn't mean that it's a good idea. If you really need to embed a {{
Coord}} in this infobox, you could put it in one of the blank fields. —
Stepheng3 (
talk) 19:48, 23 December 2012 (UTC)
latd=
and longd=
. This approach is preferable mainly because it makes the coordinates available for the infobox's {{
Location map}}. Additionally, in most cases, the infobox provides the correct type and region code for the coordinates, and changes to the population_total=
parameter will be reflected in the Geohack link. —
Stepheng3 (
talk) 00:19, 24 December 2012 (UTC)
|coordinates_region=
; if that is blank or absent, it's determined by pushing |subdivision_name=
and |subdivision_name1=
through {{
CountryAbbr}}
; but note that both of those methods are defeated if |coordinates_type=
is non-blank. --
Redrose64 (
talk) 16:28, 24 December 2012 (UTC)|name=
should not be used inside an infobox.
Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits 10:37, 24 December 2012 (UTC)
|name=
should not be used inside an infobox" is explained in the coordinates template's documentation.
Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits 12:56, 26 December 2012 (UTC)We should add an |etymology=
parameter, for settlements where we have a cited explanation of the derivation or meaning of the name.
Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits 20:27, 29 December 2012 (UTC)
I propose that we add a pronunciation parameter, to take a copy of the IPA pronunciation of a place's name; for example "rɛdɪŋ" for Reading). This will make them machine readable, so that others can import and reuse them. A use case for such a facility is in this blog post about sat-nav devices mispronouncing names. As noted above, the generic "spare" parameters are not suitable for this. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:07, 10 January 2013 (UTC)
I'd like a new parameter, airport, where we could add a suitable airport (or two) for people wanting to travel to the settlement. Maybe we could add railway station also. Of course, in areas where people can't or avoid travelling by train, the railway station field can be omitted. -- BIL ( talk) 21:37, 28 December 2012 (UTC)
airport
to the template, because no one has objected its addition, only objecting using blank1_info_sec1
etc for this. However, the template is protected. If an admin includes the field airport
, I will update the documentation, and start adding this info to settlement articles. --
BIL (
talk) 17:34, 13 January 2013 (UTC)Really screws up trying to organize a page because the infobox bleeds too far down the page. Can we make it collapsible? Maybe provide a smaller version of it? -- ColonelHenry ( talk) 18:47, 21 January 2013 (UTC)
{{
Stack}}
template, which will allow an image or table to be placed right of the text and left of the infobox. I updated the article for
Stillwater Township, New Jersey to move the history section to the top (where it should be anyway) and used {{
Stack}}
to keep the gristmill image to the right of the history. That moved the remaining sections down away from the infobox and therefore the climate table and population table are to the right of the appropriate sections. --
Zyxw (
talk) 05:14, 29 January 2013 (UTC)
Infobox settlement | |
---|---|
Area | |
• City | 10,000 sq mi (30,000 km2) |
• Land | 1,000 sq mi (3,000 km2) |
• Water | 100 sq mi (300 km2) |
• Urban | 10 sq mi (30 km2) |
• Rural | 1 sq mi (3 km2) |
• Metro | 0.1 sq mi (0.3 km2) |
• blank1 | 0.01 sq mi (0.03 km2) |
• blank2 | 0.001 sq mi (0.003 km2) |
While updating the documentation for the supporting templates of Infobox settlement, I noticed the infobox is over-rounding the conversion of square miles to square kilometres, such that an area of 10,000 sq mi displays 0 km2 as the conversion (see examples to the right). The template which needs to be corrected is Template:Infobox settlement/areadisp. I have an edit request with more details at Template talk:Infobox settlement/areadisp#Edit request: Fix over-rounding in conversion of square miles to km2. Posting this here for those who don't watch the sub-template talk pages. -- Zyxw ( talk) 02:02, 5 February 2013 (UTC)
I've been thinking that there should be an incorporated-from parameter in the template, which would be filled in with whatever municipality the settlement is incorporated from. Any thoughts? King Jakob C2 23:10, 14 February 2013 (UTC)
|established_title = Incorporated
(the word "from" is obviously redundant). See for example
Brockville. --
P 1 9 9
✉ 13:18, 15 February 2013 (UTC)
Is there a parameter to indicate which seat the place falls under in a legislature? It doesn't quite fit "subdivision_typeX". – H T D 16:26, 13 February 2013 (UTC)
Currently the infobox supports five leader_nameN and leader_titleN parameters. In certain parts of California, these parameters are used to present the legislators associated with populated places. When the place is an incorporated municipality, editors can run out of parameters, as has happened for instance in Livermore, California. It would be helpful to have additional fields — at least seven, maybe as many as ten. — Stepheng3 ( talk) 22:45, 17 March 2013 (UTC) Another example is Ione, California.— Stepheng3 ( talk) 18:39, 18 March 2013 (UTC)
We can add the info to the Footnotes, but it looks bad. Needs a separate field in the formatting. — LlywelynII 15:30, 14 March 2013 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
I suggest adding Demonym(s) and Language(s) to the Infobox list of features. These two items might be inserted immediately before or after or between Nickname(s) and Motto. Many thanks.
Laird of abbeyhill ( talk) 19:24, 25 March 2013 (UTC)
|population_demonym=
.
Frietjes (
talk) 19:36, 25 March 2013 (UTC)Per this discussion, can anyone suggest a fix (for the technically challenged). Thanks in advance. RashersTierney ( talk) 18:29, 27 March 2013 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
A long time ago we discussed about the problem regarding long countries like Chile and how could be displayed a two-columns-table instead of every-image-down-under-the-previous-image in order to make the infobox more compact and shorter. We reach an agreement to merge the new {{
infobox settlement Chile}}
-features in the general infobox.
As far as I know, until now no one proposal has been made to merge both boxs.
I worked out a solution for the merge. Simply we add four new parameters (for four images) and build up a two-column-table with this images. The code is in {{
Infobox settlement/sandbox}}
version of 14:52, 9 February 2013 (current version today), and the results are shown in
Template:Infobox settlement/testcases (please use the (current) version 15:09, 9 February 2013). The example is the infobox for the City of Linares in Chile.
I had elaborated also a solution with only one new parameter but I decided to propose the 4-new-params solution.
I think the solution with 4 new parameters is better than a solution with only one new parameter, because the new code for 4 new params doesn't interfere in the logic of the "old" template or at least interfere less than the code with only one new parameter.
I ask you to inspect the new code in sandbox and, if you find it good, to support the merge. --Best regards, Keysanger ( what?) 13:54, 15 February 2013 (UTC)
Are there other editors interested in this issue?. If not, I would like to proceed to improve {{
infobox settlement Chile}}
and leave {{
infobox settlement}}
to its own destiny. --Best regards,
Keysanger (
what?) 12:09, 20 February 2013 (UTC)
{{
Infobox settlement/sandbox}}
version of 14:52, 9 February 2013 (current version today, again), and the results are shown in
Template:Infobox settlement/testcases (please use the (current) version 15:09, 9 February 2013). The example is the infobox for the City of Linares in Chile, that is case 0. There are some other people testing the population density. (I reverted their changes today, sorry).|pushpin_map_cl=
would trigger the code fork to go the the pushpin-on-the-side? this way we could re-use the image_flag (rather than needing image_flag_cl) and image_shield (rather than needing image_shield_cl). although, I think we probably want to keep image_map_cl, since we are significantly resizing the default map. also, is there a reason for having the map between the shield and the flag? and, why _cl and not _right or _side or _narrow? otherwise, no objections here.
Frietjes (
talk) 22:35, 1 March 2013 (UTC)
|pushpin_map_cl=
. The code is in the sandbox version of "21:21, 11 December 2012" and the testcase version of "21:29, 11 December 2012". But I would prefer the 4-new-params solution because it doesn't interfere with the old-code. the 4-p solution is a new block of code, full separated from the old params. It is easier for the maintenance.There seems to be something going wrong with automatic density calculation: it produces "Formatting error: invalid input when rounding". You can see this on, for example, Acapulco. I suspect it may have something to do with the most recent edit on {{ Rnd}}, but I don't have the template coding skills to figure it out myself. - htonl ( talk) 22:47, 22 February 2013 (UTC)
I'm going to go ahead and suggest that what you probably want is something for precision like:
{{#expr: {{ min| {{#expr: {{precision|{{{pop}}}}} + {{order of magnitude|{{{pop}}}}} }} | {{#expr: {{precision|{{{area}}}}} + {{order of magnitude|{{{area}}}}} }} }} - {{order of magnitude|{{#expr: {{{pop}}}/{{{area}}} }} }} }}
With appropriate formatnum and scale factors added in for converting area into the right units, etc.
For example, area = 654.2, pop = 123456, gives density = 188.7
Or, area = 650, pop = 123000, density = 190.
Dragons flight ( talk) 02:49, 23 February 2013 (UTC)
For the record, I added error trapping and converted back to the Lua version of {{ rnd}}. This will allow existing pages to render in much the same way they did before. Rather than displaying a visible error (which may be disruptive to readers), now bad pages will be added to the hidden category Category:Pages with bad rounding precision and display a number rounded to 1 - {{ order of magnitude}}, which approximates the prior behavior. It is still a good idea to fix Template:Infobox settlement/densdisp and other templates that are sending bad precision values, but now we should be able to do that without being too distracting. Dragons flight ( talk) 18:13, 23 February 2013 (UTC)
![]() | This
edit request to
Template:Infobox settlement/densdisp has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
By using a second "/sandbox2" (as Template:Infobox settlement/densdisp/sandbox2), I have corrected the typos in the 5 population-density formulas to get the complex calculations to work, by inserting the 2 missing right parentheses brackets ") )" into each {rnd} where the decimal-digit count (expected "2") was causing an expression error instead. Compare results:
You missed my point. Yes, the template sets the precision, but a correct version of that template really ought to give appropriate precision for both numbers. Sticking in some extra parens makes the expression syntactically valid, thus eliminating the error message, but I'm not sure that the output is actually correct. Consider:
Your sandbox2 seems to leave the /km^2 and /sq mi numbers with significantly different precision in most cases. In addition, in the low precision cases at the end your version seems to be giving rather more precision than is warranted. I know we can "fix" the math by adding in a few parentheses, but frankly I am inclined to think that the computation needs a more serious overall so that the results it generates are actually sensible and not just syntactically complete. It would be rather nice if someone actually familiar with this infobox would chime in with what they actually want to see as output. Dragons flight ( talk) 20:50, 27 February 2013 (UTC)
Abhishek191288 tells me that the prohibition at WP:INDICSCRIPT should apply not only to the lead sentence but also to infoboxes. I disagree. There is a place in the settlement infobox for native names, and it seems appropriate to place the native script there. See edits and reversions by Abhishek191288 at Munirabad, Chikkaballapur, Chikmagalur, Bellary and Belgaum. Comments pro or con? -- Bejnar ( talk) 07:31, 11 April 2013 (UTC)
If you look in the Tampa Bay Area article there is a typo in the Population Section. The Urban section puts a comma in the year. For example "2,783,243 (19th as of 2,008)". This comma should not exist. Chotchki ( talk) 20:06, 19 April 2013 (UTC)
Per
this thread, I have added functionality to allow the pushpin map to appear to the right of the flag, shield, emblem, logo, and one map. To enable this feature, you just need to use |pushpin_map_narrow=yes
or any non-blank value. The changes should have no visible appearance on existing transclusions. This will now enable {{Infobox settlement Chile}}
to be merged with this template per the outcome of the associated TfD. Please let me know if anything goes haywire. Thanks!
Plastikspork
―Œ(talk) 22:32, 11 May 2013 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
The 2010 census population citation is outside the parentheses, but any estimation population citations (2011 or 2012) are inside of the parentheses. Example here. T C N7JM 06:48, 28 May 2013 (UTC)
|pop_est_as_of=
may or may not include a reference, as in |pop_est_as_of=2010<ref>the source for that</ref>
or |pop_est_as_of=2010
This value has parentheses wrapped around it by the template before being displayed; and because of that, the closing parenthesis is necessarily after the </ref>
should the latter be present. To move the closing parenthesis between the year and the <ref>
would require either of two things to happen:
|pop_est_as_of=(2010)<ref>the source for that</ref>
|pop_est_note=
and display that immediately after the closing parenthesis. Editors will then need to split existing instances of |pop_est_as_of=2010<ref>the source for that</ref>
into |pop_est_as_of=2010
|pop_est_note=<ref>the source for that</ref>
{{
edit protected}}
should be open, so I've deactivated it. --
Redrose64 (
talk) 19:21, 30 May 2013 (UTC)