This page is currently being updated as of 5 Apr 2025. Please reach out to the local community with any questions.
The Northeast Region (NOR) includes:
Delaware / New Jersey / New York / Pennsylvania
Each of the pages linked above has additional state-specific map guidance recommendations that differ from the others in this region and other regions, so be sure to also review the specific editing guidelines from those pages before editing in Northeast.
The current primary Regional Coordinator for NOR is orbitc 
. The region also has the following Assistant Regional Coordinators: PhantomSoul and RussPA
Editing Community
Communication
The Northeast Region (NOR) community uses Discord as its primary communication platform. Please join us in the Waze NOR Editors server and let us know where in the region you plan to edit so the appropriate roles and channels can be assigned. You can learn more about Discord here.
If you prefer to not use Discord, you may reach out to your local state’s Waze Community in their respective forums using your Waze account or reach out to a State Manager on the tables at the bottom of this page: Delaware / New Jersey / New York / Pennsylvania
Update Requests 
Any editor can research and reply to an Update Request. Rank 1 editors will need to work with a more senior editor to review and close a UR.
The main objective is to resolve legitimate map issues – not just to close URs. Be sure to take time to understand the issue, and ensure that the reporter has time to respond. URs may be left open longer if needed to properly resolve the issue.
Many URs require more information from the reporter to find a solution. This is understandable, since it usually isn’t possible (or desirable) for the reporter to leave a full explanation while driving. To improve the chances of getting a response while the incident is still fresh in the reporter’s mind, it is best to send an inquiry as soon as you see a UR that hasn’t yet been addressed by another editor.
To improve your chances of getting helpful replies to your UR comments, use specific, personalized comments such as “Hello! Volunteer map editor responding - Last Tuesday at 5PM you submitted a map issue regarding wrong driving directions. Waze instructed you to turn right on W 40th Street, but you continued straight on 8th Avenue. What was wrong?”. Be very cautious of any scripts which have options to automate your comments - do not allow them to automatically fill and send an entire comment. If you use automatically generated responses like “You reported turn not allowed”, be sure to add the specific details most likely to solicit the answers you need.
Some Wazers see a response to their UR via the email address associated with their Waze account, and not in the Waze app itself. For this reason, it helps to let the reporter know they need to reply using the Waze app inbox, that email responses will not reach us. This can be kept brief, for example “Note: e-mail replies won’t reach us, please use the Waze app inbox to respond.” at the end of the message to the reporter.
The Northeast Region (NOR) largely follows national guidance with these exceptions:
- No editor “owns” a UR, we work as a team to investigate and resolve issues. However, if it is clear an editor is actively working on an issue with the reporter, etiquette dictates that you contact them before stepping in and resolving it.
- A reminder should be sent to the UR reporter if no response is received after the initial inquiry. The timeline of correspondence and closure follows.
Timeline
The following timeline starts on “Day 0,” which is the day you find a UR that has not yet been addressed by another editor:
| Example | Workflow / Response | |
|---|---|---|
| Jan 20 | The day the first message is sent to the reporter: Use aerial view, street view, and the information in the UR to try to solve the UR. If you can fix the problem, do so, and thank the reporter for their help. If not enough information is available and you cannot identify the problem, respond to the UR asking for more information. |
|
| Jan 24 | 4 days after the initial message: After 4 days if you haven’t received a response from the reporter and you still cannot identify the problem send a reminder message for more information. |
|
| Jan 28 | 4 days after the last reminder was sent: If you still haven’t received a reply from the report, and you still cannot identify the problem, you may close the UR as not identified, leaving a message indicating that we did not have enough information to identify the problem. In this final message you may include the state’s email address for any follow up information (where available): New Jersey - WazeNewJersey@gmail.com New York - WazeNewYork@gmail.com Pennsylvania - WazePennsylvania@gmail.com Northeast Region - WazeNortheast@gmail.com |
When leaving the e-mail address, request that the reporter put your editor username in the subject line so emails can be auto forwarded to you.You are not required to use this email address if you don’t wish to. However if you do use it, it is strongly recommended you register here: Waze NOR Email Subscription
Closing a UR as Not Identified
- If there is a cluster of URs and you can not figure out the root of the problem, consider leaving the URs open a little longer to see if another UR comes along to provide more information. This may allow you to solve them all or leave a map comment to track.
- Fix another issue in the area. While you may not have solved this issue, make sure we are always improving the map. A good practice is to make at least one improvement in the area (fix/add info to a place, update house numbers, add missing speed limits, etc) when marking a UR as Not Identified - this will help future proof the area.
- Special consideration should be given to URs that have comments, a problem identified, or reasonable Waze routes and/or user traces. In these cases, clusters can potentially form with similar information and the issue can be solved using deductive reasoning. In these cases it’s always wise to consult with a state manger for guidance on closing the UR.
- Last but certainly not least, when in doubt, ask for a second opinion. A second set of eyes may help you identify an issue you missed.
Roads (Segments)
Segment Details
Highway Naming
Use the following designations when naming numbered highways in the region:
| Delaware | New Jersey | New York | Pennsylvania | |
|---|---|---|---|---|
| Interstates | I-## | I-## | I-## | I-## |
| US Highway | US-## | US-## | US-## | US-## |
| State Highway | SR-## | SR-## | NY-## | SR-## 1 |
| County Road/Route | N/A | CR-## | CR-## | N/A |
1 PA-## may be occasionally used to match signage. See the Pennsylvania page for more information.
Often when US Hwys, State Roads, and County Roads pass through municipalities, they have a local name (e.g., “Main St”). Please see Road Names for instructions on how to name these segments. The region is currently experimenting with dual naming on these roads (e.g., US-1 • Main St). Check the local state Wazeopedia pages for further guidance.
Road Shields
Except for shared national shields (i.e., Interstate, US Highway, and County Road/Route, where applicable), road shields standards are set on a per-state basis. See the individual state pages for state-specific field information.
Road Type (Functional Classification)
Under Construction
Locking Standard
NOR has set a 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 of special situations (areas with long-term construction, recurring mistakes, segments which are part of BDP, other complex mapping/routing situations, etc.), but should not be locked lower. Road types not listed below (Passageway, Off-Road/Not Maintained, Runway) are used on a case-by-base basis and their creation and locking should be discussed with your local state editing community.
Note that due to the complexities of routing in New York City, the locking standards within the city’s five boroughs are elevated compared to the rest of the region.
| Segment Type | Northeast Region | NYC Only |
|---|---|---|
| Freeway | 5 | 5 |
| Ramp | Highest Connected Type | Highest Connected Type |
| Major Highway | 3 | 5 |
| Minor Highway | 3 | 4 |
| Primary Street | 2 | 3 |
| Street | 1 (Auto) | 1 (Auto) |
| Private Road | 1 (Auto) | 1 (Auto) |
| Parking Lot Road | 1 (Auto) | 1 (Auto) |
| Ferry | 5 | 5 |
| Railroad | 2 | 2 |
| Pedestrian Path | 3 | 4 |
Elevation
The Northeast Region uses the “True Elevation” method for setting the road elevation attribute of segments. In general, most segments (driveable or non-driveable) should have an elevation of Ground unless they pass either:
- over another segment or large waterway on a bridge (i.e., elevated above ground level by means of a man-made structure - this does not include segments which are elevated above surrounding ground level solely by earthen construction), or
- are underground (negative elevations) as a tunnel (i.e., segments which pass under ground level segments via the use of a tunnel, large culvert or similar structure - this typically does not include segments which are below surrounding ground level but in an open cut).
In some cases, wide bridges or earthen structures may cause GPS issues with the underlying segment, acting more as a tunnel over the segment than an overpass. In these cases, it may be more appropriate to use a negative elevation and the tunnel checkbox - please consult with a state manager before making such an edit.
Segments should be cut to the extent of the bridge deck to the best estimate possible. This may include creating junction nodes at the expansion joints, abutments of the bridge, or other feature visible in imagery. Tunnels should be cut at least 50 feet from the tunnel portal to allow for GPS data to be collected at both ends of the tunnel (be sure to set the tunnel checkbox). Segments should not be cut where they are within 200 feet of an existing junction node - the elevation should extend extra distance in these cases to allow for better speed data collection.
At this time, true elevation only affects the look of the map in the LiveMap. However, it is anticipated the Waze app will render elevated segments at some point in the future.
Special Roads
Dirt Roads
The unpaved checkbox should be used for any gravel or dirt road that is periodically maintained or “improved” (i.e., the road is graded and leveled from time to time). Any drivable road which is not paved with asphalt or concrete should have the unpaved box checked.
In areas where a vehicle cannot maintain a steady speed of 10mph or more, or otherwise requires high clearance, it should be set as Off-road / Not Maintained type with the unpaved attribute checked. The need to map these types of roads within the region is rare and should be done in consultation with the local Waze community.
Driveways
NOR follows national guidance for Driveways. The following is regional guidance:
- Driveways are to be mapped with Private Road (PR) segments.
- Of note, for exceptionally long driveways, WME may prevent saving when a Residential Point Place (RPP) is too far from the roadway. In such cases, an editor should place the RPP at the furthest possible point and use an Entry Point to reach the final stop.
Alleys
This region has unique guidelines for mapping alleys:
- Alleys should always be mapped if they have a name.
- Alleys should always be mapped if they are the sole access to a home or business.
- Alleys should always be set to Private (PR) road type
- Alleys are normally mapped if they are acknowledged by the municipality (e.g., signed, present in GIS, etc.)
If an alley does not meet the above criteria, mapping is optional. Leave the name field blank.
Cemetery Roads
Roads within cemeteries with historical significance or useful as navigation aid can be mapped. Internal roads should be mapped using the Parking Lot Road (PLR) type if mapping the roads is warranted.
Non-Drivable Roads
Under Construction
Road Closures
Under Construction
Places
Place Names
Under Construction
Chain Harmonization Sheet
The name spellings in the following sheet have been standardized for chains or franchises so that Wazers will receive consistent results when searching in the client. Please use them when you edit one of these chain or franchise businesses. Websites and descriptions have also been included for many of them. If you have any thoughts on a effective and short description for a location please let us know.
Missing Chains
If you don’t find the business you’re looking for, please use this form to submit the missing information and send a chat to ehcool68.
View this list full-screen in Google Sheets
Locking Standards
Once you have correctly filled in as as much information as is available, and preferably harmonized (see next section), Places should be locked to a minimum of Level 2. The region has decided several place categories are more sensitive or important to routing and should be locked higher. Special consideration is also given to places that are considered sensitive, complex or intricate that may raise their lock level on a case-by-case basis.
Please reach out to your local community if you need assistance in locking a place with one of these categories higher.
| Lock Level | Place Categories |
|---|---|
| Level 3 | College / University Courthouse Ferry Pier (passenger ferries) Government Jail / Prison / Correctional Facility Parking Lot Train Station |
| Level 4 | EV Charging Station Fire Department Gas Station Hospital / Urgent Care Park Police Station |
| Level 5 | Airport Ferry Pier (vehicle ferries) Military (except recruiting offices) Rest Area |
| Highest lock of underlying roads |
Bridge Tunnel |
Permanent Hazards
Cameras
The legality of enforcement cameras varies by state. If you get a request for a camera type that is illegal in the state you are editing (or you find an already approved one), please remove it. Cameras types that area available in the Waze Map Editor but that are not listed here are either 1) illegal in all of the region’s states or 2) otherwise not mapped because they cannot be used for traffic enforcement (e.g., Dummy Cameras). Please reach out to your local state community if you need help identifying a camera’s type.
| Delaware | New Jersey | New York | Pennsylvania | |
|---|---|---|---|---|
| Speed Camera | Illegal | Illegal | Legal 1, 2 | Legal 2 |
| Red Light Camera | Legal 3 | Illegal | Legal 3 | Legal 3 |
| Noise Camera | Illegal | Illegal | Legal 4 | Illegal |
| Bus Lane Camera | Illegal | Illegal | Legal 4 | Illegal |
1 Limited to school zones in specific municipalities. See individual state page for details.
2 Limited to specific active work zones. See individual state pages for details.
3 Limited to specific municipalities. See individual state pages for details.
4 New York City only. See individual state page for details.
School Zones
Under Construction
Key Regional Editors
The following tables contain the key Waze Editing Community leadership for the region and its states. Please reach out to your local leaders through their Discuss profiles or in Discord if you are interested in editing or have any questions. Area Managers and active editors working towards the Area Manager role are listed on their individual state pages.
Regional Coordinators
| Username (Rank) | National Role | Regional Role |
|---|---|---|
| orbitc (6) |
Global Champ | Regional Coordinator (RC) |
| PhantomSoul (6) |
Global Champ | Assistant Regional Coordinator (ARC) |
| RussPA (6) |
Global Champ | Assistant Regional Coordinator (ARC) |
USA Champs & Country Managers based in NOR
| Username (Rank) | National Role | State/Regional Role |
|---|---|---|
| Doctorblah (6) |
Local Champ | PA State Manager |
| PesachZ (6) |
Global Champ | |
| Rfrsw101 (6) |
Local Champ | NY State Manager |
| whoaitspete (6) |
Local Champ | NY State Manager |
Joyriding (5)  |
Country Manager | NY State Manager |
| phuz (5) |
Country Manager | PA, DE State Manager |
| sikemever (5) |
Country Manager | NOR Multi-State Manager |
| snhroc (5) |
Country Manager | NY State Manager |
State Managers
| Username (Rank) | State/Regional Role | State |
|---|---|---|
| Be8el0ve (5) |
State Manager | New Jersey |
| dhschneider (5) |
NOR Multi-State Manager | New Jersey |
| Drummin4JC (5) |
State Manager | Pennsylvania |
| ehcool68 (5) |
NOR Multi-State Manager | Pennsylvania |
| G_W1Z (5) |
State Manager | Pennsylvania |
| Jdelosa (5) |
NOR Multi-State Manager | New York |
| krzycholub (5) |
State Manager | New Jersey |
| MGODLEW (5) |
State Manager | Pennsylvania |
| MRSmith66 (6) |
NOR Multi-State Manager | New Jersey |
| NJMedic2535 (5) |
State Manager | New Jersey |
| Poncewattle (5) |
State Manager | Delaware |
jushag (4)  |
State Manager | New York |