Talk:List of Virginia Byways

Other possible byways

• 1967-04 p. 16: access to Gunston Hall (SR 242)
• 1967-05 p. 25: access to Mill Mountain Park (Mill Mountain Parkway)
• 1985-06 p. 67: access to Chickahominy Wildlife Management Area (SR 621 per project number)
• 1985-06 p. 68: access to Harry G. Daniel Park at Iron Bridge (SR 701 per project number)
• 1985-06 p. 69: access to Fisher Farm Park (SR 1040 per project number)
• 1985-06 p. 70: access to Liberty Lake Park
• 1985-07 p. 49: access to Beaumont Boat Landing (SR 669 per project number)
• 1985-07 p. 50: access to Portsmouth City Park
• 1985-09 p. 44: access to Three Lakes Park
• 1985-10 p. 29: access to Meadowlark Botanical Gardens (SR 7150 per project number)
• 1986-03 p. 39: access to Licking Run Park (SR 602 per project number)
• 1986-06 p. 139: access to Flowerdew Hundred Plantation (SR 639)
• 1986-06 p. 141: access to Gretna Town Park (SR 1340 per project number)
• 1986-06 p. 142: access to Belle Isle (Tredegar Street)
• 1986-06 p. 143: access to Great Neck Park
• 1986-11 p. 33: access to Council Park (SR 1030 per project number)

This is silly - could it be that these somehow weren't "real" Virginia Byways? --NE2 18:11, 23 August 2014 (UTC)

Missing byways

There are several byways that appear in the route index and VDOT byways map but for which I can't find their creation in the CTB minutes or state laws (they also don't appear to be signed):

• 1994-02 Accomack and Northampton Counties: SR 600, SR 180, SR 605, US 13 Bus., SR 126, SR 179 - this is the date SR 600 and SR 603 in Northampton County were added, but these weren't
• 1995-01 Prince Edward County: SR 696 (listed as a potential byway in the 1989 Virginia Outdoors Plan p. 250)

--NE2 23:33, 16 October 2014 (UTC)

The south half of SR 235 is signed as a byway, but doesn't seem to be defined as one anywhere. --NE2 23:51, 17 October 2014 (UTC)

Error: too many expensive function calls

Looking at the Parser profiling data seen in Show preview:

• The version of 07:58, 16 October 2014 was the last one that fit within the limit: Expensive parser function count 498/500
• The revision of 17:22, 16 October 2014 shows Warning: This page contains too many expensive parser function calls. It should have less than 500 calls, there are now 521 calls.,

and this article is now a member of Category:Pages with too many expensive parser function calls. I'll work on tracking down the source of the problem. Wbm1058 (talk) 16:52, 12 November 2014 (UTC)

I believe the problem is too many transclusions of Template:CTB minutes, the first line of which is:

{{#ifexist:Template:CTB minutes/{{{1}}}|{{cite report|title={{CTB minutes/{{{1}}}}}|publisher=Commonwealth of Virginia|page={{{page|}}}|pages={{{pages|}}}|quote={{{quote|}}}}}|

• #ifexist: is an expensive function. – Wbm1058 (talk) 17:05, 12 November 2014 (UTC)

Actually it's {{jct}}, and the problem may be fixed soon. Though it's simple enough to redo {{CTB minutes}} to get rid of that part, so I'll do that in the meantime. --NE2 17:09, 12 November 2014 (UTC)

OK, that did put it under. But you can see on list of state routes in Tennessee how {{jct}} is the real culprit. --NE2 17:29, 12 November 2014 (UTC)

OK. I saw that one was now coded as a Lua module, so wasn't sure about it. So both contribute to the total which is limited to 500. As you just mentioned while I was typing this, List of state routes in Tennessee is also showing the error: Warning: This page contains too many expensive parser function calls. It should have less than 500 calls, there are now 526 calls. – Wbm1058 (talk) 17:33, 12 November 2014 (UTC)

Yeah, that may be fixed. Anyway, for now {{jct}} fails pretty gracefully, with the shields simply not being shown at all. --NE2 17:41, 12 November 2014 (UTC)