Changes

From Wazeopedia

Real time closures

1,083 bytes added, 4 years ago
Understanding closures with an end date circa 1970: Now shows NOT SET
===== Understanding closures with an end date circa 1970 =====
Note: Waze has recently changed the user interface, so you should not see these anymore. You will instead see the closure marked as end date "Not set" (see [[#Closure date NOT SET|next section]]). It is possible that there are some existing closures that use the old format described in this section, or that not all servers have been updated to use the new interface described in the next section.
When a mobile user [[#Report closure feature in the Waze app|submits a Closure Report through the app report menu]], Waze puts it on the map as a closure, similar to a manually-entered closure. Unlike WME-entered reports, the app supports submitting closures without indicating an end date/time. These are recorded with a "null" date time, which in Unix, by convention (as described below), is midnight of 1 January 1970. Because Waze uses the [[UTC]] time zone, this may be ±1 up to 13 hours for you.  In the [http://en.wikipedia.org/wiki/Unix Unix operating systems] a time is encoded as the number of seconds passed since January 1st, 1970. A "null" date will be zero seconds passed and show a date time of 1970-01-01T00:00 UTC. Adjusted for time zones, and you could have a date-time anywhere from 1969-12-31T12:00, to 1970-01-01T12:00, or one hour more when adjusted for Daylight Saving (Summer) Time.  {{Anchor|Closure date NOT SET}}===== Closures with end date "Not set" ===== You may occasionally see an RTC in WME with end date of "Not set" (or set in 1969-1970 in the older style [[#Understanding closures with an end date set as circa 1970-01-01 00:00 ±1 day|described above]]).
*These may not be actively affecting routing in Livemap or the Waze app.
*They may be submitted by any rank user, even if the user is below the rank to have [[#closure feature permissions|RTC permission]].
''These are [[#Report closure feature in the Waze app|Closures reported from within the Waze app]]'''.
A Closure reported from the Waze app does not include an end date in it. These closures are therefore reported to WME with no assigned end date. The end date field is essentially blank - it is "null". In the [http://en.wikipedia.org/wiki/Unix Unix operating systems] a time is encoded as the number of seconds passed since January 1st, 1970. A "null" date will be zero seconds passed and show a date time of 1970-01-01T00:00 UTC. Adjusted for time zones, and you could have a date-time anywhere from 1969-12-31T12:00, to 1970-01-01T12:00.
This explains the anomalies listed above;
* There needs to be multiple reports to activate them.
* It is possible to have more than one report on the same segment.
 
These closures are editable by editors in WME who have permission to use the RTC feature. If you do edit and/or delete one of these app-reported RTCs the effects are seen immediately. If you change the end date, the RTC will start affecting traffic like any regular RTC immediately.
translate-proofr
680
edits