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 "New York/Closures/Major" page)
 
(635 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Planning Committee ==
<!-- ========================
    ↓  EDITS TO THIS TABLE ARE MADE BELOW THE INSTRUCTIONS    ↓
==============================
This page is only viewed directly in the Major Events table on the Closures subpage.--><noinclude>[[Category:{{RootPage2}}]]
[{{fullurl:{{BasePage2}}/Closures|action{{=}}purge}} {{u|Click here to return to the {{RootPage2}}/Closures Subpage}}]<br/>


* '''Regional Coordinators'''
These rows fill the major Event table, and are modified using the template {{tl|Event/Item}}. If you are working on a Major Event in {{RootPage2}}, please add add that event to this table. If the event is already listed, please add your username to the row, preceded by a pipe (|), and change the date to today's date in the <code>updated=</code> parameter.
** 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 ==


''For details of the phases, see the [https://docs.google.com/document/d/1Ha91I9kRfNLHWHj2eqNbYpfCvXwwA5SrvE5H54ris8A Meetup Planning Recipe]'' (will need to request access from TerryPurdue)
This template accepts many parameters which must be separated from each other using pipe characters (|), but can be placed in any order and will automatically  the correct parts of the table. To use a parameter you must keep the name of parameter (the part before the equals sign (=) identical to this list, and only modify what goes after the equals sign (=).


[https://docs.google.com/spreadsheets/d/1eDv2SxikPQL5F6XstXJzzLgJFH0l_0nsohHrqHIA6qE Planning Milestones Google Sheet]
==Accepted parameters:==


== 2016 Feedback ==
*<code>name=</code> The name of the event.
*<code>area=</code> The county or are the event takes place in.
*<code>date=</code> The estimated date(s) this event happens on.
*<code>road=</code> The main road(s) affected by this event.
*<code>pl=</code> A [[permalink]] to the affected road(s), or a link to documenting listing all the affected roads (usually a Waze event closure document).
*<code>source=</code> A link to an official information source for this event, a government website, the hosting organizations webpage, etc.
*<code>status=</code> Whether this event has been submitted to Waze yet for this season. It accepts the following options spelled only exactly as listed here in order to correctly change the color of the row, filled with anything else will display with a white background
**<code>not submitted</code> produces a red background
**<code>submitted</code> produces a light green background
**<code>in progress</code> produces an orange background.
*Up to six editors can be listed in the table for any event. These can be the editors who are working to get it submitted, maintain the segments, or just have special knowledge of the event/area. They are entered as unnamed parameters. Meaning they are to be entered between two pipe (|) characters of the adjacent parameters. Each editors name (without any spaces) should be separated with a pipe (|).
*<code>updated=</code> the date this event was last updated in this table. This is used to keep the table current, and identify stale entries.


26 responses


=== Travel Arrangements ===
The updated parameter (<code>|updated=YY/MM(/DD)|</code>) should be updated any time you update a row. Put the date you are modifying the row after the equals sign (=).


* 70% not applicable
* 23% 5/5 (excellent)
* 8% 4/5
* 0% for 1/5, 2/5, and 3/5


==== Comments ====
The <code>|date=|</code>, and <code>|updated=|</code> parameters should use the format YY/MM/DD. The day of the month is optional. Using this format will make it easier to sort the list by updated date. This will help ensure the information on the list is current, and make it easy to find stale rows which may need to be adopted by other editors.


* 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.
* Travel agent contact did not take place until about a month after travel preferences were collected by Terry
* I guess I shouldn't complain about no driving reimbursement...even though I was getting edit area to improve Waze's data.
* Wanted a private helicopter
* the gentleman was great. asked directed question about what I wanted or needed and then booked accordingly.
* 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!
* My 45 minute drive was quite nice :)
* My car was just excellent. Outstanding choice, including the custom plates. Would recommend using every day.
* Process was simple, Amir did all I could have asked of a travel agent. Picked flights they were booked next day. Great job


=== Hotel ===
For example an Event row should look like this;


==== Parking ====
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}


* 46% not applicable
* 15% 5/5 (excellent)
* 15% 4/4
* 15% 3/5
* 7.7% 1/5 (unacceptable)


===== Comments =====
If there are multiple editors it should look like this


* Way too expensive
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username1|username2|updated{{=}}14/08}}
* 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 =====
'''Whenever you edit this table, please be sure to include the name of the event you are editing in the summary field under the edit box.'''
————————————————————————————————————


* 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)
''The actual contents of this page '''will only be visible''' in the [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''
* 11.5% 4/5
* 11.5% 3/5
* 3.8% 1/5 (needs improvement)
* 3.8% Not applicable


===== Comments =====
==TO EDIT THIS TABLE CLICK HERE >> ==
</noinclude><includeonly><!--
------ DO NOT MODIFY ABOVE THIS LINE -----
======                               ======
======                              ======
======                              ======
====== DO NOT MODIFY ABOVE THIS LINE ====-->
{{Event/Item|name=New Years Celebration|area=NYC|road=Times Sq/Coney Island|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1716991474|date=12/31-01/01 annual|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/08}}


* Amazing room
{{Event/Item|name=NYC 1/2 Marathon & St. Patricks' Day Parade|date=03 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=339510355|area=NYC|road=5 Boroughs|status=submitted|updated=2017/02/09|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
* 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.
{{Event/Item|name=July 4th Celebration|area=NYC|status=submitted|updated=2017/02/12|Rfrsw101|jdelosa|johnsninja58|PesachZ|road=FDR Dr|date=07/04 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1864894199|source=http://www.nyc.gov/html/dot/html/motorist/wkndtraf.shtml}}
* I thought it was a beautiful hotel. Better than I normally stay in on my dime.
 
* Good, no view
{{Event/Item|name=Summer Streets|road=Park Ave|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1984749524|source=http://www.nyc.gov/html/dot/summerstreets/html/home/home.shtml|date=08 First 3 Sundays|area=NYC|status=submitted|updated=2017/02/10|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
* 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.
{{Event/Item|name=West Indian Day Parade|date=09 Labor Day annual|area=Kings|road=Eastern Pkwy, Classon-Rochester St Johns-Empire|source=http://maps.nyc.gov/streetclosure/|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1605830763|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/10}}
* The room was exceptional.
 
* Using the lights was a learning experience, but it was nice nonetheless.
{{Event/Item|name=TD 5 Boro Bike Tour|area=NYC|date=05 First Sunday annual|road=5 Boroughs|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=790135118|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/08}}
* 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?
{{Event/Item|name=NYC TCS Marathon|area=NYC|date=11 First Weekend annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=0|road=5 Boroughs|source=http://www.tcsnycmarathon.org/race-day/course|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/07}}
* 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.
{{Event/Item|name=UN General Assembly|area=NYC|road=East Midtown|date=09 Last Two Weeks Annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1895099030|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/08}}
 
{{Event/Item|name=Macy's Thanksgiving Day Parade|area=NYC|road=Herald Square|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1774745119|date=11 Last Thursday Annual|source=http://social.macys.com/parade/#route|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/08}}
 
{{Event/Item|name=Chinese New Year Parades|date=01 or 02 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1190958434|area=NYC|road=Chinatown/8th Avenue/Flushing|status=submitted|updated=2017/02/08|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
<!--- DO NOT MODIFY BELOW THIS LINE ------=====                                =====
=====                                =====
=====                                =====
----- DO NOT MODIFY BELOW THIS LINE ----->
</includeonly>

Latest revision as of 05:15, 19 February 2017

Click here to return to the PesachZ/Closures Subpage

These rows fill the major Event table, and are modified using the template {{Event/Item}}. If you are working on a Major Event in PesachZ, please add add that event to this table. If the event is already listed, please add your username to the row, preceded by a pipe (|), and change the date to today's date in the updated= parameter.


This template accepts many parameters which must be separated from each other using pipe characters (|), but can be placed in any order and will automatically the correct parts of the table. To use a parameter you must keep the name of parameter (the part before the equals sign (=) identical to this list, and only modify what goes after the equals sign (=).

Accepted parameters:

  • name= The name of the event.
  • area= The county or are the event takes place in.
  • date= The estimated date(s) this event happens on.
  • road= The main road(s) affected by this event.
  • pl= A permalink to the affected road(s), or a link to documenting listing all the affected roads (usually a Waze event closure document).
  • source= A link to an official information source for this event, a government website, the hosting organizations webpage, etc.
  • status= Whether this event has been submitted to Waze yet for this season. It accepts the following options spelled only exactly as listed here in order to correctly change the color of the row, filled with anything else will display with a white background
    • not submitted produces a red background
    • submitted produces a light green background
    • in progress produces an orange background.
  • Up to six editors can be listed in the table for any event. These can be the editors who are working to get it submitted, maintain the segments, or just have special knowledge of the event/area. They are entered as unnamed parameters. Meaning they are to be entered between two pipe (|) characters of the adjacent parameters. Each editors name (without any spaces) should be separated with a pipe (|).
  • updated= the date this event was last updated in this table. This is used to keep the table current, and identify stale entries.


The updated parameter (|updated=YY/MM(/DD)|) should be updated any time you update a row. Put the date you are modifying the row after the equals sign (=).


The |date=|, and |updated=| parameters should use the format YY/MM/DD. The day of the month is optional. Using this format will make it easier to sort the list by updated date. This will help ensure the information on the list is current, and make it easy to find stale rows which may need to be adopted by other editors.


For example an Event row should look like this;

{{Event/Item|date=14/10|in progress|username|updated=14/08}}


If there are multiple editors it should look like this

{{Event/Item|date=14/10|in progress|username1|username2|updated=14/08}}


Whenever you edit this table, please be sure to include the name of the event you are editing in the summary field under the edit box. ————————————————————————————————————


The actual contents of this page will only be visible in the Major Events table, or when editing this page.

TO EDIT THIS TABLE CLICK HERE >>