summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormvglasow <michael -at- vonglasow.com>2018-10-06 22:29:52 +0200
committermvglasow <michael -at- vonglasow.com>2018-10-06 22:29:52 +0200
commit32dde1e3cfca442f2416c64284d00de6f32f1d24 (patch)
treeb92b347c0d4b441632c374363713f9bde2e0974d
parent777ceb4d34497646f6d175c4e8dca87923f3c903 (diff)
downloadnavit-32dde1e3cfca442f2416c64284d00de6f32f1d24.tar.gz
Refactor:traffic:Comment why we don't parse restriction_speed_limit
Signed-off-by: mvglasow <michael -at- vonglasow.com>
-rw-r--r--navit/traffic.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/navit/traffic.c b/navit/traffic.c
index 5071ce586..5fd71b9ad 100644
--- a/navit/traffic.c
+++ b/navit/traffic.c
@@ -3306,6 +3306,9 @@ static struct seg_data * traffic_message_parse_events(struct traffic_message * t
/* Contraflow: assume 80, unless explicitly specified */
speed = 80;
break;
+ /* restriction_speed_limit is not in the list: either it comes with a maxspeed attribute, which gets
+ * evaluated regardless of the event it comes with, and if it doesn’t come with one, it carries no
+ * useful information. */
default:
break;
}