Talk:BSicon/Icon geometry and SVG code neatness

From Wikimedia Commons, the free media repository
Jump to: navigation, search
See also: Talk:BSicon/Icon geometry and SVG code neatness/Formations

ZOLL[edit]

Separated from Talk:BSicon/Renaming#GRENZE vs ZOLL

To be honest, I wanted to raise this issue for quite a long time, but always postponed it. So,
My impression – don't know where I got that from, correct me if I'm wrong – was that the present design of   (ZOLL) was intended to make it different from   (GRENZE) and thus prevent it from being deleted as a duplicate. With that threat gone (hopefully), I think we might reconsider the geometry and the colours. I understand that Tuválkin as the author of that change might think different, but... To my eyes, the older one looks better. There are two issues:

  1. The ring in   (ZOLL) is both thicker and smaller in outer radius, so the inner space is much smaller and the icon looks really blurred and cluttered. Similarly, the distance between the ring and the black bar is reduced, so there is no space visible between them at 20px as in   (GRENZE), which was better – again, IMHO.
  2. The colour of the ring is too bright. Not as much as some were originally, but still. I does stand out in an RDT.   (GRENZE) uses #CC0000, which doesn't differ much from #BE2D2C, but... is that bad?

A minor issue is that the white outer ring, if kept at all, should be confined to the area where there's a track (like here). All in all, I could live with the older design... But I would really like you all to tell me that I'm a fool and that the newer design is much much better!! YLSS (talk) 22:22, 13 January 2015 (UTC)

Take a look at en:Comparison of European road signs#Checkpoints. (I'm sorry I did.) Useddenim (talk) 01:49, 14 January 2015 (UTC)
GRENZE GRZq+ZOLL ZOLL
GRENZE GRZq+ZOLL ZOLL


Tested a new design at   (GRZq+ZOLL). Can be seen at the bottom of fr:Schéma de la ligne de Creil à Jeumont. Opinions? YLSS (talk) 16:18, 14 March 2015 (UTC)

I like that new design, and it seems to work well at 20px — which was my concern when I created the alternative design for the ZOLL family. -- Tuválkin 22:36, 2 June 2016 (UTC)
@Tuvalkin: Maybe it might be better with a mask instead of the grey separator? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
07:32, 4 April 2017 (UTC)
I agree that the separation element should be all around, as a disc, to enable clean overlaying. (I’m not calling it a mask, but yeah.) -- Tuválkin 10:53, 4 April 2017 (UTC)
@Tuvalkin: I meant using an SVG <mask>…</mask> for the non-overlay icons; sorry for the ambiguity. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
10:55, 4 April 2017 (UTC)

Elevated wyes[edit]

(Pinging: Useddenim, Tuvalkin, YLSS, Newfraferz87, Sameboat) Was wondering: why   (ABZgl+l),   (uABZl+l),   (uABZgl+l) and   (uABZl+l) (all regular 100px stroke) but   (uhABZgl+l) (60px stroke for curves)? Jc86035 (talkcontributionsuploads) 13:37, 2 June 2016 (UTC)

There was concern that 100px width is too thick for 90 degree turn by 250px radius. At one point new icons of similar gl+l or gr+r composition cease this practice. -- Sameboat - 同舟 (talk · contri.) 13:59, 2 June 2016 (UTC)
Yes, and in my opinion things like   (uhABZgl+l) should be standartized to use 100px thick lines. -- Tuválkin 22:36, 2 June 2016 (UTC)
I wasn't too sure how much visual problems would changing icons such as   (uhABZgl+l) bring about, so I didn't touch them. Unless more objections are raised, it seems that's not much of a problem now, so I'm fine with them being standardized. However, I did note the differences between   (uKRZlr+lr) and   (uABZlr+lr) and how it's absolutely necessary for the former to have narrow turning curves (otherwise it will end up as   (uJUNC) ).   ~ Newfitz Yo! 09:46, 5 June 2016 (UTC)
  (ABZgr+r green) is an example of an icon with narrow (75px) stokes for both the curves and the through line. IMHO it shows the triangle more clearly without excessively thinning the strokes. Useddenim (talk) 03:38, 6 June 2016 (UTC)
@Useddenim: 75px (all tracks), imho, seems to look a bit nicer than 100px (all tracks). Not sure if it's better than 100px–60px though. Jc86035 (talkcontributionsuploads) 05:48, 7 June 2016 (UTC)
And   (uhKRZl+lr) is an example with 70px lines. My point is that there are configurations where narrower lines are needed, and using all narrowed lines looks much better than a combination of thick and thin. Useddenim (talk) 10:26, 7 June 2016 (UTC)
@Useddenim: That particular one does look a little wonky though (the straight lines are a bit off), maybe you could fix that for a better demonstration? Jc86035 (talkcontributionsuploads) 11:09, 7 June 2016 (UTC)
That's because the icon itself is asymmetrical (unless you consider the top left–bottom right axis...) Useddenim (talk) 15:11, 7 June 2016 (UTC)
  (uhKRZl+lr) is more visible given the space between the lines/curves, but I would still argue that it is not symmetric and less aesthetically pleasing than   (uKRZl+lr). Would it be possible to reach a happy medium?   ~ Newfitz Yo! 15:43, 14 June 2016 (UTC)
Yes, if you don't mind a slight kink in the straight-through lines. Useddenim (talk) 16:58, 14 June 2016 (UTC)

Number size[edit]

num1m num1r num2r num3l num5m num7r num0m num11m
20px
num1m num1r num2r num3l num5m num7r num0m num11m
30px
num2a sameboat002
20px
num2a sameboat002
40px
BSr + num2r
BSicon BSr.svg
20px, platforms
BSr + num2r
BSicon BSr.svg
40px platforms

What's the standard code of a number icon? Several of them seem to be differently sized (or squashed), but only at 20px. Jc86035 (talkcontributionsuploads) 14:08, 15 June 2016 (UTC)

or is it just librsvg being weird? Jc86035 (talkcontributionsuploads) 14:11, 15 June 2016 (UTC)

It's something to do with the way fonts are rendered by the svg engine. Tuvalkin might know more about it. Useddenim (talk) 03:27, 16 June 2016 (UTC)
I started this series (and am responsible for the bad root letter case). Now I think we better use <path> to outline the numeric glyphs instead of using <text> and existent font for best result. I opt for the pixel by pixel style for simple and neat edge and the icon should be done in 20x20px natively to ensure that they look crisp in the RDT. -- Sameboat - 同舟 (talk · contri.) 07:00, 16 June 2016 (UTC)
@Sameboat: Would making the edges slightly curved work? It's clear to read but it's also not particularly aesthetically pleasing. Jc86035 (talkcontributionsuploads) 09:16, 16 June 2016 (UTC)
I think you want curved corners? Anything not horizontal or vertical will cause blurred edge after scaling due to interpolation which is something I want to avoid in small size rasterized icon. -- Sameboat - 同舟 (talk · contri.) 09:34, 16 June 2016 (UTC)
Revised my temp BSicon for numeric 0~9 (0 is hidden). All path are originally centered at (0,0) and moved to position via transform-translate for easier derivation. -- Sameboat - 同舟 (talk · contri.) 11:08, 16 June 2016 (UTC)
Should the numbers be aligned closer to the icon edge, similarly to the currently-used icons? Jc86035 (talkcontributionsuploads) 11:52, 16 June 2016 (UTC)
They are 1 to 2 px away from the 20x20px canvas edge. I don't think it's a good idea to align the object on the edge if it isn't meant to connect to the adjacent icon like STR/BHF icons do. Arguably you can move 1,4,7 leftward (x: 4->3), 3,6,9 rightward (x: 16->17), 7,8,9 downward (y: 16->17) all by 1px. -- Sameboat - 同舟 (talk · contri.) 12:04, 16 June 2016 (UTC)
One problem is that the current icons are thin enough to fit on the 125px-wide platforms (see w:en:Template:Mile End–Bow Road tube station). With a margin on both sides the numbers would have to be 3px (or, normally, 75px) wide…? Jc86035 (talkcontributionsuploads) 12:34, 16 June 2016 (UTC)
Moved the numeric closer to edges and thinner glyph width, but I can see another issue when overlapping on platform icons is the terrible low contrast, even though this can be fixed by using white numeric. -- Sameboat - 同舟 (talk · contri.) 12:50, 16 June 2016 (UTC)

Continuation icons[edit]

exlGRZx + hCONT+f
BSicon exlGRZx.svg
CONTge uvCONTge-
uvCONTfge BSicon .svg uvCONTge-
CONTf + exlGRZx
BSicon CONTf.svg
BSicon .svg
exlGRZx + CONTge
BSicon exlGRZx.svg

Which one of the three lengths for opposite-direction CONT arrows – 275px (  (uCONT+fq), +gq and the elevated ones), 325px (  (CONTfa), ge, most others) or 350px (  (uvCONTge-) and all other parallel icons except these two) – is correct? Jc86035 (talkcontributionsuploads) 12:10, 21 August 2016 (UTC)

I'm probably guilty of drawing my icons inconsistently, but I would say that   (uvCONTge-) is too long whereas the other two are correct. However, I just realized where the extra length came from: Note the second line of the example: the tail was extended to match the head of the opposite direction. The stand-alone tail should be shortened to the standard length. Useddenim (talk) 14:23, 28 January 2017 (UTC)
@Useddenim: so 325px would be best for all of them? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
14:35, 28 January 2017 (UTC)
No. As stated above, they are all correct except for the single parallel line tail (which should be shortened to 325px). The line on elevated CONTinuation starts (  (hCONT+f), for example) was shortened to compensate for the extra length of the formation, resulting in an overall-balanced icon. Note the positions of the line ends relative to the centre of the icon. Useddenim (talk) 16:16, 28 January 2017 (UTC)
@Useddenim: The issue I was originally concerned with, I think, was that the formations could look inconsistent when they were overlaid differently to form parallel tracks. There isn't a need for this anymore, since Epicgenius's track diagram style mostly uses fades instead of continuation arrows, but it might still help to standardize them (especially in the case of parallel elevated continuation icons, which could be created but don't exist yet). Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
04:28, 29 January 2017 (UTC)

Parallel curves[edit]

v-STRlf uvSTR+rf- uv-STR+lf vSTRrf-

@Useddenim, Sameboat: Some of these and these (many of the icons without elliptical curves) seem to have lines which are 5px off from 125/375, but I'm not sure if this is a problem in the subcategories as well. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
08:37, 20 December 2016 (UTC)

┌───┘
Fixed earlier this week. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
09:49, 28 January 2017 (UTC)

Tunnels under water[edit]

@Useddenim, Sameboat: Should tunnels be drawn above water   (WTUNNEL1) or below water   (tWSTR)? I'm inclined to put them above water, because we already have   (WTUNNEL) and it wouldn't make any sense for tunnels crossing   (WDOCKSm). Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
09:58, 28 January 2017 (UTC)

  • I normally put tunnels under water because that's where they are IRL; but, I have no objection to the reverse if it's needed for clarity. Useddenim (talk) 14:15, 28 January 2017 (UTC)
  • I think the dashed design of tunnel lines is meant to enable their placement on top of (=over) other elements in order to keep them visible — and the “solid” water is a good example —, regardless of the “background” (which is actaually a foreground). This was probably not thought originally so for earlier tunnel BSicons, but merely lifted from existing mapping conventions elsewhere, but originally done thusly for that reason, I believe. -- Tuválkin 02:19, 29 January 2017 (UTC)

BHFCC[edit]

BHFCC sky BHFCC BHFCCe BHFCCa
80px
BSicon .svgBSicon .svgBSicon .svgBSicon .svgBSicon .svgBSicon .svgBSicon .svgBSicon .svgBSicon .svgBSicon .svgBSicon .svgBSicon .svg
BHFCC sky BHFCC BHFCCe BHFCCa
20px

@Useddenim, Tuvalkin: I've tried adjusting the tunnel portals very slightly for   (BHFCC sky) so the BHF circle doesn't overlap with the portals as much, matching the   (hBHFCCe) portals. (Currently the portals are a bit inconsistent.) Is it working? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
10:00, 17 February 2017 (UTC)

✓OK Looks good. Useddenim (talk) 11:14, 17 February 2017 (UTC)

INTACCs[edit]

@Useddenim, Tuvalkin, Lost on Belmont: I reuploaded several vINTACC icons assuming that they would use the same station circles as vINT icons, but for some reason they don't (50px black line instead of 60px). Is this deliberate, and should   (INTACC-M) use 50px as well (since it has to match with 60px INT icons)? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
11:02, 19 February 2017 (UTC)

There was a lengthy debate about this a few years ago. (Line thickness, circle radius.) Unfortunately, I don’t remember what the consensus was. Try digging through the archives… Useddenim (talk) 13:36, 19 February 2017 (UTC)
@Useddenim: According to archive 2, YLSS simply went with 50px rings (maybe he didn't anticipate that the interchange icons were expected to line up perfectly). I haven't found anything else yet. A few icons still have 53px rings. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
13:53, 19 February 2017 (UTC)
  • Hmm, new idea (in line with whats’s being discussed elsewhere): What if INTACCs were black with a white wheelchair symbol, period? -- Tuválkin 14:48, 19 February 2017 (UTC)
    • @Tuvalkin: That would probably result in more problems for distinguishing set black icons, so it doesn't sound like the best idea. The blue looks nice, though, and I don't think it's necessary for us to change the wheelchair's colour. Jc86035 (talk) Use {{re|Jc86035}}
      to reply to me
      14:53, 19 February 2017 (UTC)
    •   (lINTACC-L) would also end up being almost 100% black with a little white wheelchair on the edge, and it would be hard to recognize it as a sort of INT. Jc86035 (talk) Use {{re|Jc86035}}
      to reply to me
      14:55, 19 February 2017 (UTC)

Shifts in tunnel[edit]

@Useddenim, Tuvalkin: Should three-quarter and four-quarter tunnel shifts have separate corner icons? Looking at en:Template:BMT Fourth Avenue Line, they don't match up perfectly. (In addition, Useddenim's   (tSHI4c1) is different to YLSS's   (utSHI4c1).) Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
09:14, 26 February 2017 (UTC)

  • If they don’t match, then separate icons should exist. (But don’t ask me about tunnels, I may tell my opinion at last! Face-grin.svg) -- Tuválkin 13:56, 1 March 2017 (UTC)

Parallel stations[edit]

@Useddenim, Tuvalkin: Is the slight difference in geometry between (e.g.)   (v-BHF-L) and   (lv-BHF-L) intentional? (The legende icon's station is slightly smaller, with the circle's centre being 25px to the right so that the left edge is exactly in the middle.) Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
11:32, 1 March 2017 (UTC)

  • All of a sudden, I’d say that any difference is unintentional. If thre’s a good reason for it, I don’t remember and may never read about it. -- Tuválkin 13:51, 1 March 2017 (UTC)

┌───┘

@Tuvalkin: I suppose it might be to do with having parallel passing tracks, but the difference (while noticeable) is probably negligible. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
14:57, 1 March 2017 (UTC)

I think I put the edge at 250px to allow it to be used with d icons and to reduce the chance of overlapping other features. Useddenim (talk) 02:40, 2 March 2017 (UTC)
@Useddenim: Should we keep them as they are? The slightly wider gap could be marginally better (see also w:en:Template:Metra Electric Line, which uses the 300px station circles instead of the 250px ones). Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
07:06, 2 March 2017 (UTC)
The Metra diagram was a bit of a kludge because there is no elevated version of   (vBHF-STR). I don't think it looks bad, but it may look better with 250px∅ stations. Useddenim (talk) 11:22, 2 March 2017 (UTC)
@Useddenim: Updated the diagram with   (hvBHF-STR) and its ACC version (used with   (hdBHF+R)). Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
13:17, 2 March 2017 (UTC)
Awww, you took away all the bumps. (Actually, the diagram now looks much neater.) Useddenim (talk) 00:58, 3 March 2017 (UTC)

Crossovers[edit]

@Useddenim, Tuvalkin, Axpde: Is   (FOWl) semantically the same as   (FOWl+BRÜCKE)? Why does the former not need a bridge? (Also, why does   (ÜWBl) also exist, and should the mask be removed?) Should two of them (plus -r, ex- variants) be deleted/redirected? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
13:28, 11 March 2017 (UTC)

I created to versions of "FOW" (Fahrordnungswechsel = change of side of travel), one with bridges and one without, because some users demanded different versions. The "ÜWBL" has a grey masking, don't know whether there is a need for it ... a×pdeHello! 14:59, 11 March 2017 (UTC)
@Axpde: I don't think it's really necessary to have two/three different versions, since FOWl is almost never used and there's obviously a bridge in real life. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
02:02, 13 March 2017 (UTC)
It wash the wish of a user on dewiki to have a version without the bridges.
And as I said before there's a problem with "ÜWBL" because it has a grey masking! a×pdeHello! 06:57, 13 March 2017 (UTC)
@Axpde: I've trialled a version of   (ÜWBl)/r without the mask, using a more exact rotation for the bridge. Should   (FOWl+BRÜCKE)/r be deleted/redirected as duplicates? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
11:38, 13 March 2017 (UTC)
"FOW" is the correct root for this icon, furthermore the bridge icons in my version are correct, in your version it seems as if the tracks don't hit each other ... a×pdeHello! 17:09, 13 March 2017 (UTC)
@Axpde: Do you mean the line crossing under doesn't seem to align with itself? Is there that much difference with a 3.2° rotation of the formations? I think having +BRÜCKE in an icon name is a lot more cumbersome than just using a different root; furthermore using ÜWB matches with the parallel icons of the same root such as   (vÜWBl). @Useddenim, Tuvalkin: any second opinions? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
00:28, 14 March 2017 (UTC)
  1. The option without bridges may be used for level crossings or perhaps if it's not sure whether it's bridged or not. Regardless, it was the explicit wish of another user.
  2. It's nowhere written that bridges have always to be right-angled crossing other tracks.
  3. FOW is for a two track railroad changing the side of travel direction, ÜWB is for two parallel railroads crossing each other.
Greets a×pdeHello! 02:29, 14 March 2017 (UTC)
@Axpde: What do you mean by "it seems as if the tracks don't hit each other"?
  1. Okay. No objection to keeping them.
  2. Waiting for a second opinion; if you're referring to my modification of the bridge shape I just thought it was more aesthetically pleasing.
  3.   (vÜWBl) is basically the track diagram version of   (ÜWBl). I don't think there's anything wrong with those icons' naming.
Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
04:38, 14 March 2017 (UTC)
I was pinged in this discussion, but what I have to say about this icon is not constructive to the details of the discussion. But here it goes (and it was expressed before): Kill it with fire! The only way to properly depict this kind of arrangement is with something like   (vÜWBl). A diagram using   (STR) instead of   (vSTR) to show a double track has no business illustrating the swapping of their expected directions: Just add a "🔀" or a "⤨" in the text if really needed. -- Tuválkin 12:36, 15 March 2017 (UTC)
@Tuvalkin: I don't think there's a problem with splitting the line, as we could treat it as a   (nSTR) crossover which happens to merge at both ends. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
15:51, 15 March 2017 (UTC)
Well, in my opinion   (nSTR) is the root of all (that) evil… -- Tuválkin 17:32, 16 March 2017 (UTC)

k curves[edit]

@Useddenim, Tuvalkin: Are k curves better as quadratics or arcs? I might reupload a bunch of them as arcs at some point (modifying the current code definition slightly to d="M 982.84,-250 A 732.84 732.84 0 0 0 250,482.84 V 500" to prevent the curves touching the corners), but the quadratic curve could end up being better if slightly adjusted. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
07:04, 12 March 2017 (UTC)

  • I started changing the compound curve icons from Beziers and quadratics to arcs to simplify the creation of elevated h icons. Useddenim (talk) 17:48, 12 March 2017 (UTC)
  • Looks good so far. -- Tuválkin 12:36, 15 March 2017 (UTC)
    • @Useddenim, Tuvalkin: Mostly ✓ done, although there are some 3-way junctions and forks remaining. Also, for the LSTR icons, should r=750 (perfect circle) be used instead of 732.84, since the dots don't actually need to avoid the corner? (It could pose some minor symmetry problems, though.) Jc86035 (talk) Use {{re|Jc86035}}
      to reply to me
      13:44, 4 April 2017 (UTC)

Quarter-width icons[edit]

@Useddenim, Tuvalkin, Axpde, Lost on Belmont: There are several quarter-width icons where the feature doesn't quite fit in the image (e.g.   (ckSTRc1),   (cCONTfq)). Should we do away with them, considering they can usually be replaced by half-width icons? The difference in rendering is somewhat noticeable (especially for the CONT icons), even at 20px. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
11:27, 4 April 2017 (UTC)

  • Symbol keep vote.svg Agree -- Tuválkin 11:34, 4 April 2017 (UTC)
  • Symbol keep vote.svg Keep in dewiki without overlay we need those micro icons + they can't be replaced by icons of different width! a×pdeHello! 11:58, 4 April 2017 (UTC)
    • @Axpde: Doesn't matter, none of them are in the Bilderkatalog and therefore shouldn't be used there anyway. In addition, it would only take some copying-and-pasting to port over overlay capability or {{Routemap}} (incidentally, documentation has already been translated into German on dewikivoyage). Jc86035 (talk) Use {{re|Jc86035}}
      to reply to me
      13:20, 4 April 2017 (UTC)
      • It's just ridiculous, User:Jc86035 worries about our dewiki Bilderkatalog. Hear ye, hear ye!
        And as long you don't manage to convince some dewiki hardliners, we have no overlay hence in need of those icons! a×pdeHello! 13:32, 4 April 2017 (UTC)
        • @Axpde: In practice, do dewiki users use non-Bilderkatalog BSicons despite the guidelines? I just assumed that most diagrams would only use its icons given the complete lack of KRWs and the like. Jc86035 (talk) Use {{re|Jc86035}}
          to reply to me
          13:36, 4 April 2017 (UTC)
          •  Note that even though KRW icons are not included in der Bilderkatalog, they appear to be fairly frequently used. Useddenim (talk) 01:21, 5 April 2017 (UTC)
          • User:Jc86035, why do you wrack your brain about topics which are not of your concern? Is there not enough work to do for you outside dewiki? a×pdeHello! 13:45, 4 April 2017 (UTC)
            • @Axpde: Regarding the Bilderkatalog, because it affects this discussion and the BSicon WikiProject, mostly. I wouldn't really care except the icons are in use there as well so we all have to take that into account (otherwise the BS2 root would have been eliminated before I even started uploading these). Jc86035 (talk) Use {{re|Jc86035}}
              to reply to me
              13:49, 4 April 2017 (UTC)
  • Question are these icons actually used (outside of de.wiki)? Lost on  Belmont 3200N1000W  (talk) 00:06, 5 April 2017 (UTC)
    • I use them often enough, particularly the cSTRc icons. Useddenim (talk) 01:24, 5 April 2017 (UTC)
      • @Useddenim: The cSTRc icons are fine; it's the ckSTRc icons which have display issues. Jc86035 (talk) Use {{re|Jc86035}}
        to reply to me
        03:23, 5 April 2017 (UTC)

500x[edit]

I've tried adjusting the curve for   (5001) to M -166.7,333.3 35.4,131.2 A 106.52,106.52 0 0 1 110.7,100 c 64.3,0 64.3,25 139.3,25 l 250,0, but it doesn't really work that well. Is there a better way? (Just a single arc with the current parallel lines geometry reduces the inside of the curve to an angle, since the radius is only 21.17.) Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
05:51, 11 April 2017 (UTC)

More things[edit]

@Useddenim, Tuvalkin, Lost on Belmont: Pings here so I don't do them twice on this page. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
18:10, 12 April 2017 (UTC)

LLSTR icons for compound junctions[edit]

Should there be separate LSTR and LLSTR icons for KRWs (and other shifts, if necessary), 3-column curves and k curves? Many of the lücke icons in those groups (especially the 3-column curves) currently have somewhat-awkward positioning so that they can kinda-sorta connect with both the next interrupted line and a normal track. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
18:10, 12 April 2017 (UTC)

Deliberately drawn that way. They may look a little awkward at full size, but are fine at 20px. Useddenim (talk) 00:50, 20 April 2017 (UTC)
@Useddenim: The LLSTR distinction might still be better, especially for elevated lines (e.g. at w:en:Template:Seremban Line). Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
16:23, 24 May 2017 (UTC)

Platforms[edit]

Should platforms be moved slightly closer to their adjacent tracks so that they're perfectly in line with elevated formations? (This isn't really a major thing, but it seems odd to have the platforms further away than the viaduct edges.) This could also require renaming, to differentiate between a platform with an edge adjacent to a track and a legende platform with 125/250px width (e.g.   (STR+BSlr)PSTR-LR;   (vSTR-BS)vPSTR-L or vPSTR-L-PLT;   (BSlr) (no geometry change)PLT-LR).

In addition, should elevated platforms have formations (e.g.   (6001),   (hKRZ+BSel)), or do we just ignore that? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
18:10, 12 April 2017 (UTC)

Parallel curves[edit]

Should   (hSTR+r-) and   (uh-STRr) be reuploaded with the usual parallel curves geometry, or should they just be renamed to hSTR+rg and uhSTRrf once the latter filename is eventually freed up? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
18:27, 12 April 2017 (UTC)

Only renamed. Circular curves look better than elliptical ones. Useddenim (talk) 10:26, 19 April 2017 (UTC)
@Useddenim: hSTR+rg or hSTR+r-STR, or something else? (The latter could have some problems with which-part-does-the-prefix-apply-to but it should be fine I guess.) Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
12:12, 19 April 2017 (UTC)

Black INTs and DSTs[edit]

@Useddenim, Tuvalkin: I accidentally uploaded about 20 INT/DST duplicates in set black, not realizing that they have exactly the same geometry. Would it be better to do something to separate them (add masking/white outline like   (ZOLL), change the set black colour to something less saturated, decrease the INT circle stroke width…) or just leave them as they are? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
05:07, 19 April 2017 (UTC)

  • I vote for changing the color of all icons of set black to  RGB:333333  or some such. Back then I suggested this very change for this exact reason:  Black  is one of the special colors of BSicons, along with platform grey, light grey (“ex-black”), formations’ greyish green, white (inside DSTs etc.), and (sorta) water blue. Using it as the line color not only makes INTs and DSTs look identical but also clashes with things like   (TRAJEKT),   (GIP), and, of course,   (ENDEa). I can take care of the recolorings and their uploads: would have it done in 2 weeks, tops. -- Tuválkin 09:59, 19 April 2017 (UTC)
    • @Tuvalkin: Is there enough contrast?     #333333        #000000     Maybe 383838 or 404040 might be better, but not sure. I could probably reupload everything in the category automatically with pywikibot (I don't think it contravenes the bot policy since it's uploads and it's actually quite slow at 4/minute), although it might be a while since I probably won't be editing for some time. Jc86035 (talk) Use {{re|Jc86035}}
      to reply to me
      10:13, 19 April 2017 (UTC)
  • Dark grey 38 or 40 look okay. -- Tuválkin 11:05, 19 April 2017 (UTC)
  • Jc86035, concerning the upload, it can be done with Vicuña, I think. -- Tuválkin 08:33, 5 August 2017 (UTC)
    • @Tuvalkin: The problem with Vicuña is that it generates a confirmation dialog if the file already exists, for every file, and it seems impossible to turn it off, so even if the script is slower (the maximum seems to be 10/minute per Terminal window) it's not as cumbersome. Jc86035 (talk) Use {{re|Jc86035}}
      to reply to me
      08:46, 5 August 2017 (UTC)
  • Weak vote for changing colour, then adding white lining if necessary. Useddenim (talk) 10:28, 19 April 2017 (UTC)
  • The idea behind changing line black to  RGB:404040  is exactly to enrure that there’s enough contrast with feature black, so no white lining is necessary. -- Tuválkin 08:33, 5 August 2017 (UTC)
  • Ouch. This whole situation doth sucketh. Seems that a color change is the only reasonable option. (I'd very much welcome alternatives though.) Lost on  Belmont 3200N1000W  (talk) 01:30, 21 April 2017 (UTC)
  • Ah yes, that issue. (It would be good to move here from that discussion about set olive the part that is about set black…) Well, here’s the thing: The problem ehere is not the shapes and sized of DSTs and INTs, the problem here is that line black is (even when recolored) nominally and visually the same color as feature black, and we’re facing a basic design issue: If we chose to include in our diagrams special colors for fixed features to be used along with varying line colors, then we CANNOT have lines that use those colors. That’s a problem quite simple to avoid when creating iconography for a given system, but while trying to document and stylize the graphical options chose by the creators of thousands of such diagrams worldwide, we were bound to bump into this problem. I’m not sure what to do now, but to me the idea of creating a special set of INTs or DSTs for one line color is inherently abhorrent, as it goes against the very basic philosophy of BSicons: Line colors change, the rest does not.
Maybe what we should do is simply go ahead and allow that INTs or DSTs of black lines are almost indistinguishable, which is expactable when one accepts that black is also used for some features, and let the BSicon users (which we are, too) come to the conclusion that detailed diagrams, which make use of (black) line side features, are not compatible with multi colored line diagrams, more suitable for simpler uses.
-- Tuválkin 09:55, 5 August 2017 (UTC)
@Tuvalkin: An existing issue with the INTs and INTACCs, in any case, is that non-circular INTACCs are sometimes 50px, but sometimes 60px to match   (lvINT-L) and others (I think at least one of these was chosen arbitrarily after lack of participation in discussion). Regardless of the line colour, changing the INT stroke width to 50px would (technically) solve both problems. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
10:00, 5 August 2017 (UTC)
  • I’m not against that, at all. (Provided the change is done across all sets, not only for set black, yes?) -- Tuválkin 10:18, 5 August 2017 (UTC)
    • @Tuvalkin: Of course; only changing set black would be counterintuitive. Is a stroke width of 50px enough to distinguish DST and INT, or do you think a narrower stroke would be needed (i.e.   (PETERWHY-INT))? Using something different would necessitate reuploading all of the INTACCs as well, but there are only 156 of them, which is not that many in comparison to the 4,750 INTs. Jc86035 (talk) Use {{re|Jc86035}}
      to reply to me
      11:47, 5 August 2017 (UTC)
    • pinging Useddenim Jc86035 (talk) Use {{re|Jc86035}}
      to reply to me
      12:23, 5 August 2017 (UTC)

kLSTR[edit]

BSicon uhkLSTR.svg

moved from en:Template talk:Pink Line (CTA)

@Useddenim: The kLSTR icons don't line up properly. Did you use the right geometry? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
12:39, 10 July 2017 (UTC)

@Jc86035: They look correct on my computer. Rendering error? Useddenim (talk) 16:10, 10 July 2017 (UTC)
@Useddenim: It's hard to see on a display with regular pixel density, but   (kLSTR3) and   (kLSTRr+1) (and blue versions) have different geometry. The latter uses a geometry which has a dot exactly in the middle of the icon border, whereas the former matches the corner icon in its stroke-dasharray and thus aligns with the corner icon correctly. I didn't update the LSTRs when reuploading most of the k curves, although it might make sense to first rename the originals to use the LLSTR root since in order for them to match all three pieces of the curve have to be LUECKEn. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
16:16, 10 July 2017 (UTC)
@Jc86035: I created the ukLSTR (and uhkLSTR) icons from the figure above, and then just moved the viewBox in 500px steps, so I don’t know how the geometry would have changed. Useddenim (talk) 21:32, 10 July 2017 (UTC)
@Useddenim: I don't really know either, since you uploaded all of them in one batch but still used a different stroke-dasharray for the r+1 and l+4 icons. I'll reupload them. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
03:53, 11 July 2017 (UTC)

evACC[edit]

@Useddenim: What would elvACC look like? Would there be one wheelchair or two? (This might need to be used for Church Avenue in the F and G NYCS diagrams.) Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
09:18, 3 August 2017 (UTC)

It wouldn't look like anything. Because l (legend) icons only have single features, they can have either have no prefix (in use) or the ex prefix (completely out-of-use). Being partially out-of-use (e secondary feature, or x main feature) doesn't make sense. Useddenim (talk) 13:16, 3 August 2017 (UTC)
@Useddenim: Like   (uxmlvBHF), I meant. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
13:39, 3 August 2017 (UTC)
I sill don't get it, unless you mean station open, no longer any wheelchair access? That scenario has been discussed at en:WT:London Transport (I think), and the consensus was, IIRC, use the regular station symbol and leave the specifics to the actual station page. Useddenim (talk) 17:11, 3 August 2017 (UTC)
@Useddenim: No, as in, part of the station open but all of it has or would have wheelchair access. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
14:44, 4 August 2017 (UTC)
This would probably occur so infrequently (and even then, only be a temporary situation) that it would be best handled as a text note (or with overlays if you absolutely insist on illustrating it). Useddenim (talk) 17:04, 4 August 2017 (UTC)

Three-quarter shifts[edit]

@Tuvalkin, Useddenim, Lost on Belmont: Is there any advantage to having the odd shape of the SHI3 curves, just to match corner icons? Neither tunnel nor elevated corners match the SHI4 corners (the current at-grade corners don't match perfectly either), and I'm reuploading most of them for some reason, so the shape could be switched from M 250,0 C 250,198 625,302 625,500 to M 250,0 C 250,250 625,500 625,500. On the other hand, this would make it slightly harder to draw junctions between a SHI3 and a KRW, although those are probably quite rare. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
16:19, 4 August 2017 (UTC)

@Jc86035: IIRC, the SHI3 icons were drawn precisely that way in order to use the SHI4 corners and to align correctly with KRWs; but as you noted, that is a rare construct. So go ahead and make the needed changes. Useddenim (talk) 17:16, 4 August 2017 (UTC)
✓ Done; categories are yet to be sorted correctly. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
08:26, 8 August 2017 (UTC)

18[edit]

@Useddenim, Tuvalkin: Should a prefix be reserved for 18-width icons? These can't currently be rendered properly due to their width of 2.5px (which would be rounded up to 3 by MediaWiki), but they could be handled in Routemap since the module generates table cells for c, d and so on, instead of loading the images. This would be useful for w:en:Template:5 (New York City Subway service), since due to the use of quarter-width icons the maximum width is 65px and the collapsible sections currently need to be either 60px or 70px wide to be aligned correctly. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
08:25, 8 August 2017 (UTC)

  • I think so. Although too close for parallel stretches, it can be useful for tight spots, and this disrance can be obtained with the old templates (see f.i. what I did at depósito Ribeira in pt:Template:Elétricos de Sintra (diagrama)). Also, remember those old bub icons? They had 3 parallel lines on a single icon.
The matter of half pixels is separate from the nomenclature of BSicons: After all, if we redrew all BSicons at 400px instead of 500px, that matter would not arise.
Are we running out of letters, though? Maybe o, following Latin "octavus" and its derivatives?
-- Tuválkin 09:37, 8 August 2017 (UTC)
✓ Agree. Useddenim (talk) 12:24, 8 August 2017 (UTC)
@Useddenim, Tuvalkin: ✓ Done in Module:Routemap on English Wikipedia. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
14:38, 8 August 2017 (UTC)

Parallel 3/4 shifts[edit]

vSHI3
equal space between
UNequal space between

@Jc86035: Please compare the original icons with your new uploads. Useddenim (talk) 18:29, 13 August 2017 (UTC)

@Useddenim: This is deliberate. The double tracks I uploaded and re-uploaded are different to the single tracks like the   (vKRW) icons and use M 125,0 C 125,250 500,350 500,500 M 375,0 C 375,150 750,250 750,500. If necessary,   (utvSHI3+lr-SHI3+l) can be renamed to utvSHI3+l-Rr-SHI3+l-L to distinguish it from the icons with regular geometry (and the vKRWs can be renamed to vSHI4l, vSHI4l-L etc.). Jc86035 (talk) 03:27, 14 August 2017 (UTC)
I have modified the diagram to show a 12 gap instead of a 34 gap in the second row. Jc86035 (talk) 03:31, 14 August 2017 (UTC)
If we follow the pattern for the 4/4 shifts, then we need a different root (KR3?) to differentiate between 3/4 shifts with two lines vs a single-line SHI3. Useddenim (talk) 03:48, 14 August 2017 (UTC)
@Useddenim: I don't think so – it should be possible to distinguish double   (vSTR2-L) and single   (v-STR2) geometries without changing the root. There aren't even any   (vSHI4l) icons at the moment; it's impractical to make another root for this. Jc86035 (talk) 03:50, 14 August 2017 (UTC)
✓OK Useddenim (talk) 03:55, 14 August 2017 (UTC)

exdSHI1+r[edit]

exdSHI1+r

Should   (exdSHI1+r) be 250×500 size. Rowan03 (talk) 17:15, 15 August 2017 (UTC)

Yes. Useddenim (talk) 23:45, 15 August 2017 (UTC)

Diagonal roads[edit]

Diagonal roads

Should   (RP43+1) and   (RP42+4) to match corners. Rowan03 (talk) 00:29, 21 August 2017 (UTC)

@Rowan03: Yes. I can't fix it right now since I'm already working on some other things, so you could try aligning the dashes to the corner icons in Inkscape (requires XQuartz on Macs), opening the Inspector (Shift+Ctrl+X) and manually changing the stroke-dasharray if necessary, and then copying the code back from the Inspector into a text editor (e.g. Notepad++, BBEdit, TextEdit). (Don't drag objects with the cursor, change values manually. Lengths of 45° diagonals are height (y-axis) × √2 rounded to 2 decimal places. Import the corner icons using the Import button in the top left and then move them 500px.) Jc86035 (talk) 05:24, 21 August 2017 (UTC)