The road-closure-ui is a great demonstrator how to capture street related road closure information.
What I really like, is that in addition the json format, the waze CIFS format can be exported.
However, it differs in some aspects from the current feed spec:
Instead of the entered reference, a referenceId property with an unurelated is generated
fromIntersectionClosed and toIntersectionClosed are added
fromStreetnames / toStreetnames which are not part of the feed spec are generated, while the feed spec allows an optional location_description which is not generated
modes are provided while apparently not supported (any longer?)
the spec requires a top level timestamp property, which is not generated
Could you give me a hint if the current CIFS spec evolved since this demo has been developed or if the added information is perhaps part of a discussion with waze to evolve the CIFS spec?
Is this project stil maintained and if by whom? Would you be interested in PRs addressing the differences above to generate an output closer to the CIFS spec?
The road-closure-ui is a great demonstrator how to capture street related road closure information. What I really like, is that in addition the json format, the waze CIFS format can be exported.
However, it differs in some aspects from the current feed spec:
reference, areferenceIdproperty with an unurelated is generatedfromIntersectionClosedandtoIntersectionClosedare addedfromStreetnames/toStreetnameswhich are not part of the feed spec are generated, while the feed spec allows an optionallocation_descriptionwhich is not generatedmodes are provided while apparently not supported (any longer?)timestampproperty, which is not generatedCould you give me a hint if the current CIFS spec evolved since this demo has been developed or if the added information is perhaps part of a discussion with waze to evolve the CIFS spec?
Is this project stil maintained and if by whom? Would you be interested in PRs addressing the differences above to generate an output closer to the CIFS spec?