User:PesachZ/SyncScratch View history

m (Copying text of wiki page for coparison with the "USA/Great Lakes/Meetups/2017" page)
m (Copying text of wiki page for coparison with the "Pennsylvania/Major roads/Main" page)
Line 1: Line 1:
== Planning Committee ==
<!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>
The Functional Classification chart shown below has been modified from the national chart to more closely reflect the roads in Pennsylvania.


* '''Regional Coordinators'''
=== {{Anchor|FC cross reference}}Functional Classification reference chart ===
** GizmoGuy411
** SkiDooGuy (Assistant)
* '''Committee Chair'''
** TerryPurdue
* '''Hotel Coordinator'''
** fbisurveillancevan21 (if Indy)
** ruggles76 (if Chicago)
* '''Raid Coordinators'''
** RoadTechie
** Enfcer74
** ehepner1977
* '''Presentation Coordinators'''
** Kartografer
** zohar760
* '''Social Coordinators'''
** solsmac
** OhioStMusicMan


== Planning Milestones ==
Use this chart to determine the road type for Pennsylvania roads based on the functional class.


''For details of the phases, see the [https://docs.google.com/document/d/1Ha91I9kRfNLHWHj2eqNbYpfCvXwwA5SrvE5H54ris8A Meetup Planning Recipe]'' (will need to request access from TerryPurdue)
First, find the functional class of the road from the [http://www.penndot.gov/ProjectAndPrograms/Planning/TrafficInformation/Pages/County-Functional-Class-Maps.aspx#.VwlWGJMrJE4 PennDOT Functional Classification county maps] and determine if it is a signed, numbered highway in a one of the highway systems.


[https://docs.google.com/spreadsheets/d/1eDv2SxikPQL5F6XstXJzzLgJFH0l_0nsohHrqHIA6qE Planning Milestones Google Sheet]
Follow the column for the road's highway system down to the row for the road's functional class to find the proper road type for that particular road.


== Possible Dates ==
The PennDOT color coding is cross-referenced in the first column of the table for your convenience.
# Aug 26
# Sep 9
# Oct 7
# Oct 14
# Oct 21
# Oct 28


=== Date Elimination ===


'''BIG unknown''': 2017 Global Champs Meetup in Israel. Waiting for word from Gizmo.
<div style="font-size:smaller">
{| border="1" style="border-collapse:collapse; text-align:center"
! scope="row" rowspan="2" colspan="2"|
! colspan="8"| <big>Highway Systems</big>
|-
! Interstate
! Interstate Business, Loop, Spur
! US Hwy (incl. some [[wikipedia:special routes|special routes]])
! US Hwy BUS, SPUR, LOOP
! State Route Shielded
! State Route Unshielded
! Locally Maintained
|-
|
| Examples
| I-80
| I-94 Business
| US-190
| US-460 Business
| SR-23 SR-309
| SR-2006
| Roberts St
|-
! scope="row" rowspan="8" style="width:28px"| <big>F<br>u<br>n<br>c<br>t<br>i<br>o<br>n<br>a<br>l<br> <br>C<br>l<br>a<br>s<br>s</big><!-- Temp placeholder -->
| '''Interstate'''<br>[[File:PA Blue.jpg]]||{{Freeway|Fw}}||n/a||n/a||n/a||n/a||n/a||n/a
|-
| '''Other Freeway'''{{ref label|a|a}}[[File:PA Darkred.jpg]]||n/a||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}
|-
| '''Other Expressway'''{{ref label|a|a}}[[File:PA Darkred.jpg]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}
|-
| '''Other Principal Arterial'''[[File:PA Red.jpg]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}
|-
| '''Minor Arterial'''[[File:PA Green.jpg]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}
|-
| '''Urban or Rural-Major Collector'''[[File:PA Purple.jpg]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}
|-
| '''Rural Minor Collector'''
[[File:PA Yellow.jpg]]
||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}{{ref label|b|b}}<br/>{{Street}}||{{Street}}
|-
| '''Local Roads or <br>Not Classified''' [[File:PA Orange.jpg]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}{{ref label|b|b}}<br/>{{Street}}||{{Street}}
|}
{{note|a|a}}Since Pennsylvania combines these two classes, use the criteria from the [[Road_types/USA#Freeway|USA Freeway page]] to determine if the road should typed as a freeway or major highway.


* May
{{note|b|b}} Some 4-digit State Routes are numbered for legacy or maintenance reasons, but they do not serve as primary thoroughfares for the area and should be classified as {{Street|Street}}.  
** 27 Indy 500
* June
** 3  Tentative Global Champs?
** 10 Tentative Global Champs?
** 17 Father's Day.
** 24 Church of Nazarene general assembly
* July
** 1. July 4. ***
** 8. Popcon ***
** 15. Black Expo. ***
** 22. Brickyard. ***
** 29. United Pentecostal youth conference ***
* Aug
** 5. TerryPurdue vacation ***
** 12. TerryPurdue vacation ***
** 19 Gencon. ***
** 26
* Sep
** 2. Labor Day. ***
** 9
** 16. Rosh Hashana. ***
** 23. Rosh Hashana. ***
** 30. Yom Kippur. ***
* Oct
** 7
** 14
** 21
** 28
* Nov
** 4. Tentative block for Indy marathon (was first weekend of November for 2016)
** 11. Tentative block for Thanksgiving.
** 18. Thanksgiving buffer. ***
** 25. Thanksgiving. ***


== 2016 Quotes ==
</div>


=== Submitted to Staff ===
===Naming===


==== Conrad ====
==== State routes with 2 or 3 digit route numbers ====
[[File:PA_SR_Shield.png|thumb]]
In Pennsylvania all State Routes should have any common name as displayed on street signs as the primary name in WME, and the route number in the alternate name field. The city name should be the same for both the common name and route number. ''SR-111'' is the current acceptable format. The use of '''State Hwy''' or '''PA-xxx''' and other variations '''{{Red|should not}}''' be used unless it is on the road signs that drivers would see.


* Hotel rooms
State Route naming should follow the following format:
** Rate: $189
** Subtotal: $189 * 45 = $8,505
** Tax (17%): $1,445
** Total: $9,950
* Conference space
** No charge
* Food/beverage
** Lunch choice: "Little Italy"
** $42 / person
** $42/person * estimated 45 people = $1,890
** Food minimum: $2,800
** The two coffee breaks won't get us to $2,800, so we'll be paying food minimum
** Service fee: 24% (minimum $672)
** Tax: 9% (minimum $252)
** Total: $2800 + $672 + $252 = $3,724
* Internet
** 100Mbps down/10 Mbps up
** $2400/day for two days ($4800)
** Service fee: 24% ($1,152)
** Total: $4800 + 1152 = $5,952
** Wi-fi is included "for free"


'''Grand total''': $19,626
*SR-28 S (divided one-way segments).
*SR-309 (undivided two-way segments).


==== Indy Downtown Marriott ====
'''{{Red|Note}}''': Some state routes have mixed signage, with route numbers at major intersections and road names at minor intersections. Until Waze gets state shields working completely, the best practice is to name the segments according the the signage that the motorist will see as he approaches the state route, with priority given to the major intersections.


* Hotel rooms
==== State routes with 4 digit route numbers ====
** Rate: $139
** Subtotal: $139 * 45 = $6,255
** Tax (17%): $1,063
** Total: $7,318
* Conference space
** Room rental: free
* Food/beverage
** Lunch choice: Southwestern
*** $45/person * 45 people = $2,025
** Coffee breaks
*** 3 gallons a day * 2 days * $74/gallon = $444
** Food minimum: $1,000 (we'll easily hit this)
** Price
*** Subtotal: $2,469
*** Service fee (24%): $592
*** Tax (9%): $222
*** Total: $3,283
* Internet
** 200Mbps total speed for convention space, unknown what percent we get
** Price
*** $75 per day per device
*** $75 * 45 * 2 = $6,750
*** Service fee: 24% ($1,620)
*** Sales tax (7%): $473
*** Total: $8,843


'''Grand total''': $19,444
State Routes with 4 digits (e.g. SR-3001) should not have the route number in the alternate field. SR-xxxx should be removed from the alt field, if you find it.


==== Alexander ====
==== County or township roads ====


* Hotel rooms
County (Co) and Township (T) roads need no special designation or road type. Road number info is not needed in the alternate name field.
** Rate: $159
** Subtotal: $159 * 45 = $7,155
** Tax (17%): $1,216
** Total: $8,372
* Conference space
** Room rental: free
* Food/beverage
** Lunch choice: I throw myself at men
*** $42/person * 45 people = $1,890
** Coffee breaks
*** "Nourishment hub": $18/person * 45 people = $810
*** 3 gallons of coffee/break * 2 breaks * $70/gallon = $420
** Price
** Subtotal: $3,120
** Service fee (24%): $750
** Tax (9%): $280
** Total: $4,150
* Internet
** 100Mbps up/down
** Price
*** No charge for internet itself, just for setup and cable rental
*** Wifi is included
*** $875 first day
*** $225 second day
*** Subtotal: $1,100
*** Service fee: 24% ($264)
*** Sales tax (7%): $77
*** Total: $1,442


'''Grand total''': $13,964
==== Ramps ====


=== Invoiced By Hotel (Final) ===
When naming a [[Road types/USA#Ramps|Ramp]] to a State Route, use the '''SR-111''' format. ''PA-111'' format '''{{Red|should not}}''' be used unless it matches exactly what is on the big green sign directing you to the ramp. It is best to reference Google Street View in WME, where available.


==== Hotel Rooms ====
Adhere to national standards for [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|Exit ramps and Entrance ramps (on-ramps)]]. Ramp names should use these formats:


* Per Room
Off-ramps:
** Room: $149.00/night
** 17% hotel + sales tax: $25.33
** Subtotal: $174.33


'''Total''': $6,275.88 (36 rooms)
*Numbered exit: (Exit 16: SR-15 / Scranton)
*Numbered exit with multiple Cities or Routes: (Exit 16: SR-15 N / SR-86 E / Wilkes / Scranton)
*Numbered exit with multiple exits: (Exit 16A-B: SR-15 N / SR-86 E / Scranton)
*Non-numbered exit: (to SR-15 / Scranton)


==== Catering ====
====Abbreviating Pennsylvania====
When naming roads or Ramps, use '''Penna.''' as the abbreviation for Pennsylvania. '''Penn''' causes text-to-speech conflicts with the numerous items named after William Penn. '''PA''' should not be used except as shown below.


* Saturday lunch buffet: $1,554.00 ($42.00/person * 37 people)
'''Penna. Tpk''' is the proper abbreviation for naming ramps, and for alternate names for the Turnpike.
* Sunday snacks: $666.00 ($18.00/person * 37 people)
* Coffee: $210 ($70/gallon * 3 gallons)
* Service charge: $24.00
* Sales Tax: $218.70


'''Total''': $3,231.90
==== Shortened state route names ====


==== Miscellaneous ====
The format '''SR-xxx''' (State Route) should be used when naming ramps (e.g., to SR-28 S / Pittsburgh). See also: [[#Ramps|Ramps]]. To maintain uniformity across the state, the PA-xxx format '''{{Red|should not}}''' be used unless it is on the road signs that drivers would see.


* Projector: $700.00
=== Locking Standard ===
* Podium: $0.00
* Wireless microphone: $150.00
* Power package: $250.00 (ensured one outlet per person)
* Projection screen: $0.00
* Service charge: $264.00
* Sales tax: $77.00


'''Total''': $1,441.00
{{Lock Standard State|PA}}


==== Grand Total ====
=== Speed Limits ===
* Hotel Rooms: $6,275.88
Pennsylvania follows the [[Speed_limits/USA|national guideline]] for speed limits, with a few exceptions listed below.
* Catering: $3,231.90
====Pennsylvania guidelines====
* Misc: $1,441.00
* When a speed limit changes at an intersection, the sign for the new speed zone can be found up to 200 feet after the intersection.<ref name="Title_67">[http://www.pacode.com/secure/data/067/chapter212/s212.108.html PA Title 67] PA Title 67, 212.108 (e) ''If the new speed limit begins at an intersection, the first sign should be installed within 200 feet beyond the intersection.''</ref> If the speed limit changes more than 200' from the intersection, add a junction at the sign and make the speed limit change there.
* Long term work zone speed limits may be mapped instead of the "ordinary time" speed limits.


'''Grand Total''' (hotel only, does not include airfare): $10,948.78
* Speed limit signs are supposed to be posted on every street, no further than 1/2 mile apart.<ref name="Title_75">[http://www.legis.state.pa.us/cfdocs/legis/LI/consCheck.cfm?txtType=HTM&ttl=75&div=0&chpt=33&sctn=62&subsctn=0 PA Title 75] The Pennsylvania Vehicle Code (Title 75), §3362 indicates that speed limit signing must be in accordance with Department regulations to include “…posting at the beginning and end of each speed zone and at intervals not greater than one-half mile”. In addition, the installation of speed limit signing will function as a constant reminder of the roadway’s speed limit. "</ref>. If you can verify that there are no posted signs, follow the PA guidelines:<ref name="Title_75_unposted">[http://www.legis.state.pa.us/cfdocs/legis/LI/consCheck.cfm?txtType=HTM&ttl=75&div=0&chpt=33&sctn=62&subsctn=0 PA Title 75]75.3362</ref>
**35 miles per hour in any urban district.
**25 miles per hour in a residence district (unless it is a numbered route classified as a local highway)
**55 miles per hour in other locations.


== 2016 Feedback ==
====Summary of National Guidelines====
<div style="float:right;">[[File:Speed_Limit_70.png|50px|thumb|Right|<span style="color:green;">Regulatory<br/>Yes</span>]]<br/>[[File:No Advisory Speed Plaque.png|50px|thumb|{{red|Advisory<br/>No}}]]</div>
*Only map speeds found on '''regulatory''' white rectangular signs with black lettering.
* Do not map '''advisory''' speed limits (generally an orange or amber rectangular sign with black lettering).
* Where there are variable speed limits, map only the speed limit which is in effect most of the time during daylight hours (most hours of the day, days of the week).
* Do not map special speed limits for special vehicles. Waze only supports speed limits for private passenger cars.
* Where the speed limit changes, make it change in the map. A new junction may need to be added. But '''do not add a new junction for a speed limit if it will be within 200 feet of an existing junction.'''


26 responses
====PA Speed Limit Resources====
*[//www.paturnpike.com/pdfs/travel/PATurnpikeSpeedLimits.pdf Pennsylvania Turnpike Speed Limit Map]
*[https://www.paturnpike.com/pdfs/travel/Speed_Limit_Map_Phase%201.pdf old Map]
*[http://www.pacode.com/secure/data/067/chapter212/s212.108.html PA Title 67]
*[http://www.legis.state.pa.us/cfdocs/legis/LI/consCheck.cfm?txtType=HTM&ttl=75&div=0&chpt=33&sctn=62&subsctn=0 PA Title 75]
=====Links to PA speed limit laws=====
{{reflist}}


=== Travel Arrangements ===
<!--


* 70% not applicable
See [[{{BasePage2}}/Major roads]] for guidance in {{RootPage2}} that may not be universal to all other states and territories.
* 23% 5/5 (excellent)
-->
* 8% 4/5
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
* 0% for 1/5, 2/5, and 3/5
-------------------------------------------------------------------------------------
 
---- This page is only transcluded into (displayed on) the main page for this state.
==== Comments ====
---- It directly follows the common guidelines applicable to all states. When this
 
---- page is present (even if blanked), it displaces any optional code that might be
* Amir did a great job with arrangements. Even checked into possibilities of red-eye flights at my request. Alas, none available so ended up sticking with my original request. Still was nice that he tried.
---- in that section.
* Travel agent contact did not take place until about a month after travel preferences were collected by Terry
---- If the original optional code from the main page for this section is still
* I guess I shouldn't complain about no driving reimbursement...even though I was getting edit area to improve Waze's data.
---- desired, it can be restored by adding the following code to the first line
* Wanted a private helicopter
---- between the "DO NOT MODIFY" lines on this page:
* the gentleman was great. asked directed question about what I wanted or needed and then booked accordingly.
----  {{:USA/CommonState/Major_roads|optional}}
* Given the large inconvenience flying to Indy - and Waze not paying for ground transportation - I suggest future GLR meetups be held at Hub Cities that would allow more people to fly. But that really just leaves Chicago as an option.
----
* Being an Indy local, travel arrangements were great!
-------------------------------------------------------------------------------------
* Travel agent was awesome! I gave him the flight numbers I wanted, and he was able to get me those fights!
---- If there will be a full page for this section, use code similar to the wording
* My 45 minute drive was quite nice :)
---- below to provide a hyperlink to that page. When creating the full page, use the
* My car was just excellent. Outstanding choice, including the custom plates. Would recommend using every day.
---- link on the talk page to ensure the preload data is provided to help with
* Process was simple, Amir did all I could have asked of a travel agent. Picked flights they were booked next day. Great job
---- formatting the page. Don't just use the red link from this section once it is
 
---- saved.
=== Hotel ===
----
 
See [[{{BasePage2}}/Major roads]] for guidance in {{RootPage2}} that may not be universal to all other states.
==== Parking ====
----
 
-------------------------------------------------------------------------------------
* 46% not applicable
---- This section has three possible purposes:
* 15% 5/5 (excellent)
---- 1. It is only providing a hyperlink to the full page for this section.
* 15% 4/4
---- 2. It is only providing some unique guidance for this state that differs from
* 15% 3/5
---- other states.
* 7.7% 1/5 (unacceptable)
---- 3. It is intentionally wiping out the general optional content for this section
 
---- for this state.
===== Comments =====
------------------------------------------------------------------------------------>
 
* Way too expensive
* Didn't park, but the valet was very good about arranging cab back to the airport. Overall, was VERY pleased with the service.
* Used the garage at the hotel with in and out service. It was a little pricy, but worth it overall to be able to come and go without worrying about finding something.
* Parking was very close to the hotel, the cash payment system was broken but it was kind of the help parking assistant to let me out for free.
* Didn't mind spending the money for the convenient parking.
* Parked my own and never needed it until I left.
* Free
* Rated 5 since I parked off site for a very reasonable downtown rate. Otherwise I'd rate parking a 1 since the hotel rate is usurious for Indy.
* I used the parking deck not the valet
* I was able to park my vehicle in my room. Can't get much more secure than that...
* Not a fan of paying for parking
* Yikes. The final cost of overnight parking in the parking garage was as much as the filet dinner.
* I thought the parking prices were absolutely ridiculous...now that said, it wasn't any more than other area hotels, however I would have hoped that for a decent group like we had, they could've lowered it a tiny bit. As for the time in bringing the car around, it was great! I absolutely loved the ability to text them when you were ready for your car - as I did that before I was leaving my room and it was there each time by the time I reached the street. They were very friendly too.
 
==== Check-in/-out ====
 
* 61% 5/5 (excellent)
* 19% 4/5
* 11.5% 3/5
* 3.8% 1/5 (needs improvement)
* 3.8% Not applicable
 
===== Comments =====
 
* No issues
* No issues
*Room was not available when I first got there, but to be fair was pretty early. Check-in is usually not until 3:00pm and they were very apologetic about not having room ready at 10:30 am 'ish. I wasn't worried about it as was more interested in getting to the meeting anyhow.
* Everything was fine
* Good
* Arrived early but did not have to wait long for room
* Front desk staff was not adequately trained in knowledge about the hotel. Got bad basic info about my room, and worse, it came from the staff person who was training someone else.
* I did have remind them that one night was covered by Waze
( Not a big deal, but the lack of automatic checkout was slightly annoying. I'm used to that with my business travel so I notice the inconvenience.
* The first room that we were assigned to was unacceptable because it was at the far end of the hall. With my wife's bad hip, it was to far to walk so they gave us another room that was just off the elevator.
* There was some confusion finding me during the check-in process, but thankfully it was cleared up quickly. I was accidentally booked for Sunday night.
* I checked in at 7:45am Saturday morning when I arrived back at the hotel, and the room was already ready!
( Very friendly staff. Although I have yet to see my credits back on my bill from the initial $50 charge for incidentals.
* I had the understanding the room would have been $159 for the extra night. The $20 dollars in taxes was a big surprise. Didn't make a big deal of it perhaps I misunderstood the arrangement. No biggie.
 
==== Room ====
 
* 69% 5/5 (excellent)
* 11.5% 4/5
* 11.5% 3/5
* 3.8% 1/5 (needs improvement)
* 3.8% Not applicable
 
===== Comments =====
 
* Amazing room
* Very nice accomodations. Only (very minor) complaint was the lack of readily available power plug at the desk for my laptop. There were various odd power strips in the desk, but none for std American power plug. Had to crawl behind desk to find available normal power outlet.
* Room was great, liked having a full size fridge for bringing my own drinks. Water pressure could use a boost. Everything was clean and comfortable.
* I thought it was a beautiful hotel. Better than I normally stay in on my dime.
* Good, no view
* Why the hell does it have a dedicated water heater if it ran out in 15 mins????
* only issue I had was housekeeping did not knock or announce herself. however the look on her face was priceless when she turned the corner and almost face planted with my fist because I was in the bathroom and did not know she was in there. my issue with this was I had the sign up NOT to come in, and it was not even checkout time, I had another 2 hours left on the clock.
* The room was exceptional.
* Using the lights was a learning experience, but it was nice nonetheless.
* Room was very, very nice!
* The modern art decor isn't really my thing but who can complain about a free hotel room for the wife and me and no kids?
* You already know about my room issues. And the fact that they upgraded me to the Pres suite - even though they were supposed to award that to one of our members anyway I thought was a bit "switch-aroo-esque"... Now the Pres suite was fantastic as you saw - minus the blood on the light switch! lol
* I never stayed in a classy hotel. So i cant compare to very much when it comes to this compared to red roof inns and days inns. The room was very nice. Lots of tv channels great picture. Clean remote. Bathroom clean, bed was comfy. Had an issue with the air condition not working properly upon returning from dinner the first night. it was fixed within an hour. Maint tech and desk staff were very apologetic. It did seem difficult to find a happy temp. It seemed to hot or to cold all night no middle. Snacks on the counter were a bit out of date. But that's to be expected who pays $9 for a handulful of popcorn.
 
=== Meetup ===
 
==== Communication ====
 
* 62% 5/5 (excellent)
* 27% 4/5
*  8% 3/5
*  4% 1/5 (needs improvement)
 
===== Comments =====
 
* Announcements were fine. Presentations were great. Honestly, was kinda glad that MR area was delayed as it forced some extra presentations. I was a little disappointed in myself for not making the rounds to meet everyone the first day, but that's on me. Setup was right, I just didn't take advantage of it. Sunday was really awesome. Despite several folx bailing early...got to meet and greet more.
* Hangouts are great, information distribution was great. Rarely had questions about what the schedule would be and when I did they were answered promptly.
* GHO was a well used tool for communication. A forum or place for important announcements without having too look through the GHO would have also been helpful
* I would have liked a more definite schedule. Maybe a one-page to print rather than recall all the various comments in the GHO. I took one wrong turn getting to the conference room first time. Maybe a sign at the top of the stairs to lead me down.
* Hey you're all volunteers, anything better than a "1" is to be commended.
* oh wow! what a wonderful group of people. everyone was more then happy to help.
* All good, except for that secretary person...
* I walked into a room of about 40 strangers and during the first day I only met or was introduced to about 4 people. I walked around to all of the tables but none of the attendees said anything to me. I spent most of the day sitting by myself. I only met and talked to about 10 people both days.
* It was great to interact and meet everyone.
* The GHO for the meetup was a very good resource. 1 suggestion would be to create a Google Doc with the loose itinerary for the event. I am a person who very much likes things planned ahead of time and likes to know said plans. Even if things aren't set in stone, having something that gives us a general idea of when things may happen is always better than nothing.
* The GHO was too chatty a venue for informing people of important information. No way I could leave it unmuted and so I feel like I missed a lot of stuff until right at the end. I'd recommend making a point of emailing all important information to participants and leave the GHO for smack-talking, general information and asking questions and such
* I seriously don't think there was anything that could have been done differently to make this part any better. It was very well hyped in the GHO and you as well as everyone who wanted to be able to be contacted were easily able to be through the GHO.
* The Google hangout, google sheet were a great idea. Pre meetup, during and post. Great idea. Everything seemed to work out well communication wise. Terry and all involved did a great job.
 
==== Conference Space ====
 
* 54% 5/5 (excellent)
* 39% 4/5
*  8% 1/5 (needs improvement)
 
===== Comments =====
 
* Not enough power connection
* Wireless speed was pretty impressive, actually. Plenty of power, but was kind of a pain digging under the tables for the power strips. Noticed that they had power strip plugged into power strip...no wonder they said we couldn't bring our own power strip.
* Round tables were actually better than rectangle, could see everyone, power strips in the floor led to a lot of crawling around though.
* Larger tables to get more people at each one might be a benefit to get more face to face discussion going.
* I would like Ethernet
* Wireless fine. Power adequate. Snacks wonderful. Maybe there should be enough tables to seat the number of raid groups with a # on each table. Or maybe that was a way to get people to wander around and bump into others.
* Perfect
* Not convinced that round tables are the best. However do see advantages for sub groupings.
* they ran out of diet pepsi, DIET PEPSI, I mean how dare they allow that to happen.was relieved to see shortly after bring it to their attention they doubled stacked it :D
* Wireless was good IMHO. Only negative was the power strip under the table setup. Most modern conference centers have tables set for power, usb, etc. It's not a big negative.
* When I arrived there did not appear to be any place to sit until they brought another table
* When the wifi worked, it worked well. Having an older laptop probably did not help me much.
* Even though we were told that we were limited to 1 outlet per person, a lot of us were able to expand that to 2.
* Quite impressed the wireless was able to handle that much load
* Nothing bad. Would have been nice to have better power distribution but only so many ways to do that. Mice on that table cloth was occasionally gnarly. A little more space to avoid drinks pressed against electronics would have been nice.
* The only reason I'm not rating it 5 was due to the power setup and the fact that another table wasn't set up from the start. The wireless speed, light, ambience, food setup etc.. was phenomenal.
* Room was nice. The wifi seemed plenty fast and convient. Room Seemed setup properly by the time we needed it. Staff was great setting up beverages and snacks.
 
==== Meeting Presentations ====
 
* 35% 5/5 (excellent)
* 31% 4/4
* 27% 3/5
*  4% 2/5
*  4% 1/5 (needs improvement)
 
===== Comments =====
 
* "Extra" presentations due to MR area delays were great. Breakout session on LAM project was particularly interesting to me. Highly recommend more breakout sessions next time.
* Presentations seemed like an afterthought. Good info from the NOLA meetup. Of course we would have liked to see more ;)
* I was only there for Sunday, I chose 5 for this answer
* The presentations given were good. Would like to have seen a few more topics presented though.
* Need staff there
* We shoulda done more
* Would have liked something from Waze staff, even remotely
* Make sure your presenters have an actual voice. Have 2nd mic to float room.
* I didn't have any specific expectations, nor did I have a comparison since this was my first meetup. It was nice to get some inside information.
* I was expecting formal discussions about various topics. There was very little presenter led discussion.
* I wanted to put a 0, because I missed the presentations. I'm sure they were awesome though!
* I enjoyed the presentations we had, but having staff there to give us some back-end presentations would have been nice. I know that they weren't able to come since they were in the states the weekend before, but maybe we could coordinate with their schedule next year to ensure we get someone.
* In my opinion we (and by we I especially mean Waze) could have benefited a lot more from the face-to-face time if there were more of an agenda. Map raids are great but to put it bluntly we can do map raids at home for a lot less (read: zero) expense to Waze/Google. I think there would be a lot more benefit to have organized 1 on 1 (or one on 2 or 3) mentoring, people lined up to give genuine presentations (whether in a small format of a single table or to the whole group) etc.
* Would have liked to have seen more of this. We can edit anywhere. If we had enough diversity at the meeting, SM only, SM/LAM, SM/LAM/AM breakouts might have been helpful. Particularly the SM to share 'management' ideas, etc. frustrations, ways different states may handle situations.
* I thought what was presented was done nicely. The only thing I would have liked to have seen is a few more targeted presentations regarding editing. During this time it would have been ideal for those who weren't interested to break out into smaller groups and work on things they wanted to address.
* I learned quite a bit. Don't really know what to expect this was my first time. I think most of the learning took place at the tables in groups. I will be more prepared nest meetup with questions and such. Some information was shared a few things discussed.
 
==== Meetup Raid ====
 
* 19% 5/5 (excellent)
* 39% 4/5
* 19% 3/5
* 15% 2/5
*  8% 1/5 (needs improvement)
 
===== Comments =====
 
* To be fair, no delusions here. I know the only point of the MR was so Waze/Google would pay for our trip...and I, personally, got a lot more out of the presentations and breakouts and just generally meeting my peers. That being said, I still don't know what the goals of the MR were. Also, would have helped to at least know the state if nothing else ahead of time in order to brush up on the relevant rules/policies. Would like to see a better distribution of senior to junior editors, but can only do what you can do with attendee's. I had originally envisioned groups of junior editors at tables with senior editors walking around, but seemed like we had more senior than junior at the meetup. :/
* Obvious answer about area. Typical map raids restrict the editor to the team area, possibly this was the result of the snafu in having the area ready.
* Raid seemed to be a side goal for the weekend, might have had to do with it being opened late. I don't think that is a negative since it was more important to get everyone together than gluing your face to a laptop when that kind of raid could be done at home.
* Delay in opening areas.Would have also liked to have started earlier than 10:00 AM (at least doing some optional work or breakouts before the rest of the attendees arrived)
* I wasn't registered but working with the other editors was nice and they all had a good size of area
* Not sure what the goals were beyond "clean it up". Area was OK...didn't run out of things to work on, but also didn't get close to done. Maybe if the area were announced ahead of time (with an "on your honor, no editing before meetup") would give us a chance to scope things out. Also would force you to get the area open for us in time.
* Besides the late start with the areas (Waze's issue, not ours), I don't think an actual goal was given. Just, here's your area, go fix stuff. Would have like to hear a more specific goal for the raid.
* More edits for me
* Not clear if we were working base maps, URs, speed limits, PURs, all the above?
* My bad....
* Would have been nice if Waze had actually had the areas set up!
* A. the raid was late in getting opened. B. even when it opened, it still took me another hour to get. C. no extension time after the raid. :(
* Obvious issue with the delay going live. There wasn't much coordination and we were left to ourselves - or we wander about to see what others were doing and listening in on problems and unique discussion. Aside from having active area, maybe we could identify some mentors with specific goals or problems to be solved.
* What I did at the "Meetup Raid" I could have done from home
* My muddy experience is probably due to my joining mid-way. I was happy with the team distributions and amount of area. The efficient/experienced had plenty of ground to cover, and the slower/less-experienced could focus on small patches (usually) without stepping on the bigger toes. Regarding clear goals, I only focused on updating county road naming conventions, as that was the goal stated to me. Nice and simple. If there were team goals, I was unaware of them. If there were overall raid goals, I was unaware of them. The mentorship was overwhelmingly beneficial, and was arguably the best part (to me) of the whole meetup.
* In all honesty, people were floating between regions. Personally, I went to different areas that had more to do since my area had very little to do.
* Was a raid complete with all the normal challenges.
* The only reason I didn't rate a 5 is due to the fact we weren't even sure if we were going to have the area until almost 2 in the afternoon (I think). I thought that could have been set up better. Now don't get me wrong, I know there was a SHIT ton being done behind the scenes to make it happen even when it did, but I'm not sure how many others knew that.
* Would have been nice to get the raid area on time. Don't know where the hold up was but the time allotted to raid wasn't very much. Perhaps there was a better more hands on raid Sunday but some had to leave earlier in the morning.
 
==== Meetup Lunch ====
 
* 78% 5/5 (excellent)
* 8% 4/5
* 8% 3/5
* 8% Not applicable
 
===== Comments =====
 
* Lunch was outstanding! Hotel did right by us on that one by far!
* Better than I expected given the available snootieness of the menu.
* Good selection of food options, snacks, coffee, soda, etc
* Exceeded expectations.
* The staff was excellent at helping me with my food allergies and their food was delicious!
* Plenty for lunch. Maybe more water for Sunday would have been nice.
* Actually preferred over NA 2016
* OMG! those little square cakes was so freaking good, 2-3 of us went head to head. good thing we shared like big kids. could have been gruesome. P.S the strawberry ones was the BOMB!
* We did not lack for food.
* I did not try anything but my wife told me it was excellent
* Missed out. Hope it was delicious!
* Lunch was fantastic
* Yogurt and granola next time? :)
* I thought lunch was great! It was truly the first time in my life that I felt extremely satiated after "Throwing Myself at Men!"
* Maybe a bacon salad next time.
* Lunch could have hung around longer. I myself wasn't aware there was going to be such a spread so early. Most had just finished with breakfast. There was more than enough food it just seems the staff was quick to collect the food back up.
 
=== Social ===
 
==== "Unscheduled" Socializing ====
 
* 35% 5/5 (excellent)
* 31% 4/5
* 12% 3/5
*  8% 1/5 (needs improvement)
* 15% Not applicable/no opinion
 
===== Comments =====
 
* Missed Friday due to work schedule. Unfortunately missed most of Saturday, but that's on me. Wasn't feeling too great so skipped Palominos and hit the sack early. From what I read (later) on the GHO, seems like most had a pretty good time and imho, unplanned events are best left unplanned.
* Not everyone is on the same budget, mandating an event where the attendee has to pay out of pocket is difficult. Allowing people to pick a venue and ask if anyone else is interested was good. A list of nearby recommended Places might have helped.
* The hotel bar was a good meeting place, open to everyone
* Probably OK...but didn't draw me in. Just wanted to go to my room and relax.
* I thought it was just fine. I joined in with some and not others. Since it wasn't 'scheduled' it didn't feel pressured to be there.
* this was good enough for me, but I did noticed some that did not attend but went to dinner with us. so maybe something that everyone can agree on would be best. but I like the whole meeting at a bar and seeing people fall off of the table they was sitting on,however they did not spill any. Kudos for them, very proud moment
* It would have been cool if there was a large group activity planned. Like a local baseball game, putt putt, bumper cars, etc. Logistics is hard with 50 people. Maybe more unstructured for Friday and something planned on Saturday?
* I don't usually go to a bar, but I was not invited either.
* I was grateful for the unscheduled socializing. I don't think I would have really met anyone otherwise.
* I personally prefer when things are pre-planned, so I know what to expect. I think having options availble but exact details not yet decided would be fine.
* Not big on hanging out in a hotel bar, but wasn't there Friday. Saturday,
* I think with our group it was definitely sufficient...however, that being said, I'm not sure * I would count on other groups to be near as social as we were. I think it would be a great idea to have something of this nature planned or to at least offer a few suggestions beforehand to make everyone aware of the possibilities.
* The system worked great! No problems here.
 
==== Saturday Night Dinner (Palomino's) ====
 
* 39% 5/5 (excellent)
* 23% 4/5
*  8% 3/5
*  4% 1/5 (needs improvement)
* 27% Not applicable
 
===== Comments =====
 
* Wasn't feeling so good so skipped Palomino's. Will definitely attend next time, though.
* 20th anniversary discount was a nice surprise. Food was good.
* Maybe a little more notice but I also understand if that location wasn't picked until Saturday.
* Timing was fine. Too bad about the extra long wait to get in because they screwed up the seating. Food was tastey, but service wasn't the best because of such a large group.
* Had some trouble getting back from the restaurant, but that has to do with poilicing, crime and the parking situation
* For getting 30 people seated and served, while prom attendees were there also. Nice job
* I did my own thing biiiiitch!
* Tough to do a dinner this size on a busy night in the city. Despite the reservation issues, though, the choice was good and everything worked. I'm not sure many restaurants could have done much better with the service under the circumstances.
* Nice place. And the post dinner entertainment was fun! Just glad nobody was shot.
* I chose not to attend because of the high carb menu.
* Again, hope it was delicious!
* The heads up was during that day, but it's not like I had anything else planned so it was fine for me. Honestly, I wasn't very happy with their dinner service. I understand that it was the same night as prom, but it took us longer to get in than it should have with a standing reservation, and I had to ask my server 4 times for a glass of water. Food was good, but our server was absolutely terrible.
* Great choice Terry!
* Pocket book hit... my own fault tho.
* No suggestions here..I thought it worked out very well.
* Possibly a dedicated room since we have enough attendees.
* Enjoyed the restaurant waitor was a dick. Again never ate at anything that fancy but I didn't have to attend if I didn't want to. :) all was well.
 
=== Overall ===
 
* 85% 5/5 (excellent)
* 12% 4/5
*  4% 3/5
 
==== Comments ====
 
* Actually might attend.
* Overall I would say it was an OUTSTANDING event. Great presentations and awesome people. Was great meeting everyone face to face. Particularly liked the breakout session for the ongoing LAM project. I'm just an interloper from neighbor region, but very pleased to have been included. Thank you all for this meetup.
* Overall I think it was a great experience. I hope to attend again next time.
* Some additional lecture topics, more editing time, on-time swag
* Having faces to names is very helpful. Having a meetup is very beneficial to the community and creates a better sense of community and creates memories.
* Obviously have the raid area ready at the start. But you know that. If presentations are known ahead of time, would be nice to have a list of presenters and topics. If topics are sensitive, just something like "Gizmo - Remarks". Have a sheet of "state-specific edit rules" that the SMs would like us to know that I can review and memorize before the meetup.
* Good
* Tell Waze to start raid area a day or 2 earlier. Then it will be on time. Like the break between speeches. Do 1 or 2, break to edit, then do another. Don't know how we can show everyone a solution to a question. There might have been something to learn at table 1, but table 7 didn't hear it. Maybe with a laptop connected to screen, someone can stand up and address the whole group?
* Presentations were off the cuff as raid area was not ready on time but still very good given that. That is about the only area needing work for next year. Loved the experience and getting to meet all from all over and all ranks.
* I only wish it had been longer
* I'm pretty
* I'd like to see 1-2 breakout sessions where more senior editors cover specific topics with less senior ones. As an R4 I could have both benefited from this on a few advanced topics, and helped out on some of the more basic ones. We did this informally with each other, but I think it could be formalized a little bit, at least as an option.
* place setting would have been good so each group would have been together. but, it was not a problem how the seating worked out.
* First one. Had a blast. Educational and entertaining. Next time I would plan to come earlier. Sounds like a lot of fun was had on Friday. Can't think of anything not already mentioned. I appreciate the work that went into organizing this.
* All attendees should be required to wear name tags at all times. Late on Sunday, one of my state managers was pointed out to me and I had to go introduce myself to him or I would not have met him because he didn't have his name tag on. 
* While I consider myself a pretty knowledgable editor, I was somewhat confused by some of the discussions and presentations. I'm sure that there were others in the room that were also mystified by the long strings of acronyms. The presenter should talk down to the least experienced person and not presume that everyone is as familiar with the subject as them. 
* I would like to see brief discussions, led by a presenter, that cover and clarify some of the editing issues that we see. An open discussion , with examples, would provide a learning experience 
* A schedule of events should be available so we would know in advance what to expect. Just sitting in a room for two days was not what I expected. 
* I have a bit of a hearing problem in a crowded noisy room. From where I was sitting, there were times when I couldn't hear. 
* Perhaps I missed it, but everyone should have been asked to introduce themselves. Even though I arrived late, I should have been asked to say something.
* Since this was my first time I'm hesitant to comment. I only have other conferences that I've taken to reference, but in those cases the itinerary was much more visible to everyone, and available at least a week or two before the event. Overall it was great, glad I did it, and look forward to next year.
* I enjoyed the venue, though I'm easy to appease and entertain. Though, someplace with easier/closer access via public transportation would be preferred. I'm also open to trying other cities/states, though (at this time) that would significantly decrease the likelihood of my participation.
* As my first meetup, I had an absolute blast! Overall in my mind, this was a huge success, thanks to our awesome planning committee!
* I think this was great for a first time event, nothing I've said previously should indicate dissatisfaction with anything as I certainly greatly enjoyed meeting everyone. All opinions expressed are from the perspective of giving greater value to Waze and to the attending editors in future meetups
* Parking...either lowered rate/comp'd, or closer to reasonably priced option. Power outlet availability - at least 2/person, hopefully 3. This was definitely the most fun I've had all year. It solidified relationships and really ingrained a camaraderie type feel within the editing community. I can't wait to do this again next year!
* Setting up the raid area ahead of time will be helpful. I think everyone did a great job from start to end. I can't wait until next year! Also we should request Waze swag today for next year. It would be so much easier to promote Waze with some cool swag!

Revision as of 01:48, 20 September 2016


The Functional Classification chart shown below has been modified from the national chart to more closely reflect the roads in Pennsylvania.

Functional Classification reference chart

Use this chart to determine the road type for Pennsylvania roads based on the functional class.

First, find the functional class of the road from the PennDOT Functional Classification county maps and determine if it is a signed, numbered highway in a one of the highway systems.

Follow the column for the road's highway system down to the row for the road's functional class to find the proper road type for that particular road.

The PennDOT color coding is cross-referenced in the first column of the table for your convenience.


Highway Systems
Interstate Interstate Business, Loop, Spur US Hwy (incl. some special routes) US Hwy BUS, SPUR, LOOP State Route Shielded State Route Unshielded Locally Maintained
Examples I-80 I-94 Business US-190 US-460 Business SR-23 SR-309 SR-2006 Roberts St
F
u
n
c
t
i
o
n
a
l

C
l
a
s
s
Interstate
 Fw  n/a n/a n/a n/a n/a n/a
Other Freeway[a] n/a  Fw   Fw   Fw   Fw   Fw   Fw 
Other Expressway[a] n/a  Major   Major   Major   Major   Major   Major 
Other Principal Arterial n/a  Major   Major   Major   Major   Major   Major 
Minor Arterial n/a  Major   Major   Minor   Minor   PS   PS 
Urban or Rural-Major Collector n/a  Major   Major   Minor   Minor   PS   PS 
Rural Minor Collector

n/a  Major   Major   Minor   Minor   PS [b]
 Street 
 Street 
Local Roads or
Not Classified
n/a  Major   Major   Minor   Minor   PS [b]
 Street 
 Street 

^a Since Pennsylvania combines these two classes, use the criteria from the USA Freeway page to determine if the road should typed as a freeway or major highway.

^b Some 4-digit State Routes are numbered for legacy or maintenance reasons, but they do not serve as primary thoroughfares for the area and should be classified as  Street .

Naming

State routes with 2 or 3 digit route numbers

In Pennsylvania all State Routes should have any common name as displayed on street signs as the primary name in WME, and the route number in the alternate name field. The city name should be the same for both the common name and route number. SR-111 is the current acceptable format. The use of State Hwy or PA-xxx and other variations should not be used unless it is on the road signs that drivers would see.

State Route naming should follow the following format:

  • SR-28 S (divided one-way segments).
  • SR-309 (undivided two-way segments).

Note: Some state routes have mixed signage, with route numbers at major intersections and road names at minor intersections. Until Waze gets state shields working completely, the best practice is to name the segments according the the signage that the motorist will see as he approaches the state route, with priority given to the major intersections.

State routes with 4 digit route numbers

State Routes with 4 digits (e.g. SR-3001) should not have the route number in the alternate field. SR-xxxx should be removed from the alt field, if you find it.

County or township roads

County (Co) and Township (T) roads need no special designation or road type. Road number info is not needed in the alternate name field.

Ramps

When naming a Ramp to a State Route, use the SR-111 format. PA-111 format should not be used unless it matches exactly what is on the big green sign directing you to the ramp. It is best to reference Google Street View in WME, where available.

Adhere to national standards for Exit ramps and Entrance ramps (on-ramps). Ramp names should use these formats:

Off-ramps:

  • Numbered exit: (Exit 16: SR-15 / Scranton)
  • Numbered exit with multiple Cities or Routes: (Exit 16: SR-15 N / SR-86 E / Wilkes / Scranton)
  • Numbered exit with multiple exits: (Exit 16A-B: SR-15 N / SR-86 E / Scranton)
  • Non-numbered exit: (to SR-15 / Scranton)

Abbreviating Pennsylvania

When naming roads or Ramps, use Penna. as the abbreviation for Pennsylvania. Penn causes text-to-speech conflicts with the numerous items named after William Penn. PA should not be used except as shown below.

Penna. Tpk is the proper abbreviation for naming ramps, and for alternate names for the Turnpike.

Shortened state route names

The format SR-xxx (State Route) should be used when naming ramps (e.g., to SR-28 S / Pittsburgh). See also: Ramps. To maintain uniformity across the state, the PA-xxx format should not be used unless it is on the road signs that drivers would see.

Locking Standard

In PesachZ we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked at least to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.

A great time to implement these locks is while bringing the road types of an area into compliance with the current US road type standards (FC and highway systems). Lock the roads based on type after they've been set to current US road type standards.

PesachZ Minimum Locking Rank Standard
Segment Type Statewide
 Freeway  5
 Ramp  Highest rank of connected segments
 Major Highway  3
 Minor Highway  3
 Primary Street  2
 Street  1 (Auto)
 Private Road  1 (Auto)
 • • • • Ferry • • • •   5
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2

Note: Do Not Mass Edit just to update locks to these standards, these can be adjusted as you find them while editing other aspects of the segments such as FC, speed limits, naming, etc.

Some segments still warrant higher locks and care should be taken when setting segment lock to these standards to look for and protect these special setups with higher locks. Some examples; segments which are part of BDP, U-turn prevention, or using micro-doglegs, or other complex intersection setups.

Speed Limits

Pennsylvania follows the national guideline for speed limits, with a few exceptions listed below.

Pennsylvania guidelines

  • When a speed limit changes at an intersection, the sign for the new speed zone can be found up to 200 feet after the intersection.[1] If the speed limit changes more than 200' from the intersection, add a junction at the sign and make the speed limit change there.
  • Long term work zone speed limits may be mapped instead of the "ordinary time" speed limits.
  • Speed limit signs are supposed to be posted on every street, no further than 1/2 mile apart.[2]. If you can verify that there are no posted signs, follow the PA guidelines:[3]
    • 35 miles per hour in any urban district.
    • 25 miles per hour in a residence district (unless it is a numbered route classified as a local highway)
    • 55 miles per hour in other locations.

Summary of National Guidelines

Regulatory
Yes

Advisory
No
  • Only map speeds found on regulatory white rectangular signs with black lettering.
  • Do not map advisory speed limits (generally an orange or amber rectangular sign with black lettering).
  • Where there are variable speed limits, map only the speed limit which is in effect most of the time during daylight hours (most hours of the day, days of the week).
  • Do not map special speed limits for special vehicles. Waze only supports speed limits for private passenger cars.
  • Where the speed limit changes, make it change in the map. A new junction may need to be added. But do not add a new junction for a speed limit if it will be within 200 feet of an existing junction.

PA Speed Limit Resources

Links to PA speed limit laws
  1. PA Title 67 PA Title 67, 212.108 (e) If the new speed limit begins at an intersection, the first sign should be installed within 200 feet beyond the intersection.
  2. PA Title 75 The Pennsylvania Vehicle Code (Title 75), §3362 indicates that speed limit signing must be in accordance with Department regulations to include “…posting at the beginning and end of each speed zone and at intervals not greater than one-half mile”. In addition, the installation of speed limit signing will function as a constant reminder of the roadway’s speed limit. "
  3. PA Title 7575.3362