A few points questions to help formulate an opinion,
Do the PS connected jug handles usually have a BGS with names other than the street they connect to?
What would you do if there is a green sign for a jack handle connected to a street?
How would you treat a jug handle that connects to a short segment of street but it’s really supposed to lead you to an intersecting highway after that street. with or without a sign?
Sent using Tapatalk for Android 4.4.2
Are you able to find some examples in the form of screenshots or links?
Not in the very near future, sorry
Sent using Tapatalk for Android 4.4.2
Another question, would you apply these same rules to AGC off local highways which are after an intersection, as opposed to the Juvenal’s which comes before an intersection
Sent using Tapatalk for Android 4.4.2
Working on these right now.
Is this a good example?
https://www.waze.com/editor/?env=usa&lon=-74.41078&lat=40.64529&layers=1541&zoom=7
What’s a jack handle? Can’t find anything on it.
Kind of though in this case that short segment should probably just be upgraded to mH for continuity. Imagine this same setup but the other side of terril is also street not mH. That’s what I envisioned.
Sent using Tapatalk for Android 4.4.2
I see. I know I’m bound to run into one sooner or later.
I like this. In the Somerset/hunterdon area jug handles are primarily used for entering shopping/corporate complexes and at most only have a little green or blue sign.
Sent from my iPad using Tapatalk
In Fredo’s example, I would make that short Terrill Rd segment to the west (or north?) of Route 22 mH on grounds of continuity, keep that 1 cloverleaf jughandle that connects directly to it as ramp for the same reason, and make that ramp nameless since the GS only says Terrill Rd. All the other connectors on that side of Route 22 would be nameless streets.
This way at high speeds with auto zoom on, you still see the complete loop from Route 22 west to Terrill Rd south, but all those local streets, including the connectors that only serve those local streets, disappear, not leaving the map with the visual appearance of ramps to nowhere.
CORRECTION: It looks like you have to use the jughandle to get from Terrill Rd north to Route 22 west, so that path would also have to be mH (for the mainline segments of Terrill Rd along that path) and ramp (for the jughandle segments along that path, on grounds of continuity. Those ramp segments may or may not need to be named depending on what signage is present at its entrance.
Has anyone found a jughandle to a regular FC street where the GS has more than that directly-connected street’s name on it?
I haven’t had time to look, but if we’re making guidance we should think about all possibilities
Sent using Tapatalk for Android 4.4.2
That’s correct. I believe the only signage there is a regular highway sign for U-22 W pointing to the direction of the ramp with the words TO: above the highway sign. I don’t believe there’s a GS.
Sent from my iPad using Tapatalk
What I’m doing is looking for any jug handles as I pan very fast. I then see if they have match what was mentioned before as examples. However, if we are going to look at all the possibilities, then I’ll start looking at all jug handles for different configurations.
As far as duplicative text on the national cam page and the NJ page, there’s almost no cost to it. It is centrally maintained in a template now. Each of the two pages merely includes a template reference, which the magical Wiki software automatically pulls from the template into both pages every time the template is updated. The information is important to find in NJ for those looking to get the full NJ picture, and is important to find in the cam page for those wishing to get the full national cam picture. Templates provide an easy way to do both without having to do dual maintenance. If the section gets long, we may have to rethink whether we want a wall of text on this piece in both places.
The same applies to the locking chart. It is in a template now, and can be easily repeated across pages. If it it gets long, we can switch from transclusion (template inclusion) to simply linking. In the mean time, there’s no harm in transcluding it into all five pages (NE, PA, NY, NJ, DE).
Now for the philosophical discussion.
The purpose of templating was to provide for states where there was either a mess, no direction, or a lack of content where content was needed. That’s what I understood from Kent. It was never the intent to push states to adopt the national boilerplate. There’s also no policy that a state even adopt the templating system at all.
What the template system does it standardize structure, and provide starter content. Don’t like a section? Leave it out. Feel a need to address a section, but have no content of your own to fill it? You have the option of grabbing the standardized text.
Whatever sections you adopt will end up in a standardized order, and provide at least a minimum of reasonably edited content.
I’m fine with you disagreeing with me. I’m egalitarian. Perfectly happy to link arms with the worng-thinking among us. 
Seriously, though, we have a philosophical disagreement on this, which is OK. You want the national camera guidance to be part and parcel of NJ guidance, while I see the NJ camera guidance being primarily about the uniquely Joisey take on cams, with a convenient link to national cam information thrown in, without emphasis. The same concept will apply to some other sections: you may want to have NJ be a page of sections of national text with minor local tweaking, while I see more value in having sections of a local NJ page emphasize NJ text.
Think of it this way: If I am a reasonably experienced editor, and move to NJ, do I really need to see information that I already know that makes it harder to identify the information I do not already know?
This is not really a jughandle, it is a partial interchange, which happens to be used for an at-grade crossing. You have runt ramps interconnecting most of the crossing roads.
The “tentacle” visuals of ramp connectors don’t bother me, but I know there are differences in opinion about this. I actually like them, as they help the “important bits” stick out.
If we are worried about the tentacle visual, then PS’s suggestion is quite workable. I would break it down a little further, though:
No green sign at all: use type of target segment, no name
LGS only identifies the local road that the jug actually connects to: same as (1)
BGS that only identifies the local road jug connects to directly: open question. Do we always treat BGS the same as LGS? Or do we say BGS requires naming “to roadname”?
Green sign of any type that gives more than one name or names a segment that is not directly connected: type ramp, use content of LGS
Possible exception to #2: We currently allow adding an extra “locally used” name to a BGS list. If the sign says one thing but locals say another, it can also be treated the same way, which would require naming it and making it a ramp.
TL;DR Not a good example, tentacles is a personal judgement, the more simple and obvious the judhandle destination, the less need for naming and ramping it.
The flaw in your philosophical strand, is that the state template has three parts, the hard coded, the optional, and the unique. The hard coded “Boilerplate” text cannot be removed while still using the template. You would have to ditch the template entirely, and go with a standalone page. That would defeat all the work out into using this standard design. That’s not to say that you couldn’t do it. But it doesn’t seem to be the direction we are heading.
Add an experienced editor looking for info in a new location, you could shim the page focusing on the unique parts, which will always be below the boilerplate.
Sent using Tapatalk for Android 4.4.2
PZ,
It isn’t actually a flaw. It is the very reason Kent added two options, template and custom. You can always start with template, then migrate the text to custom.
Maybe I misunderstood kent, I was under the impression that the hard coded content for each section is designed not to be removable. The optional content is as it sounds optional, and can optionally be replaced with the unique content, and then there’s the unique subpage if you have a lot of unique content for a section.
Sent using Tapatalk for Android 4.4.2