I will simply add that a “Why” should be included - Why is the downlock being requested? My standard format in requesting a downlock: “L5>L3 please - fix ramp geometry, name, centering: <PL>”
Dave
You might also, at least optionally, include the approximate location.
Some editors have the necessary rank to do it, but don’t have the location in their edit area. It would save them checking and finding they couldn’t do the down/up lock.
Thanks for bringing this up, Mark, and thanks to everyone else for the inputs. Good ideas, all of them. Seems like we have a pretty good format nailed down. Now…where should we put it? I’m thinking under the Community Section we could put a short blurb about the Hangout and some of the better uses (i.e. downlocks, closures, peer to peer mentoring <– my personal favorite)…along with this advice on downlock request format (and maybe similar for closure requests).
Anyone familiar enough with editing the state templates care to take a stab at it?
Looks pretty good, Mark. A couple of notes on the formatting section…
#1 only works if the editor is running Toolbox (and therefor fancylinks which is built in).
The problem in #2 can/will/should be fixed by the KeepMyLayers script. KML also solves the layers issue in #1 on the receiving end of PL.
PL works for places, too, but instead of (or in addition to) segments=#########& you’ll get a venues=##########,#######& Not necessarily important for the wiki, but seemed worth mentioning here at least.