Comment by MrDrMcCoy
7 hours ago
Expecting support globally is of course unreasonable. Expecting it to be designed to be somewhat location-agnostic for contributors and including some obvious docs (which could just be "coming soon" or "here's what we need to expand") is pretty reasonable to me.
I don't get why there isn't even a stub repo for a mobile app to contribute with. Or am I just not finding it?
The repos are there: https://codeberg.org/opentrafficmap
https://codeberg.org/opentrafficmap/its-g5-receiver: "Current ordering situation
(as of 2026-04-23)
After the talk on Grazer Linuxtage (media.ccc.de, youtube.com) we got many responses from people also wanting to buy this receiver. We fixed a few issues of the first revision and ordered 200pcs of Revision 2.
We expect the 200pcs to arrive in the first week of May, 2026. The cost of one complete receiver (excluding case and mechanical parts) is about 20 €.
If you want to purchase a receiver PCB, please contact us at the email liked in the Imprint/Impressum of opentrafficmap.org"
That's for a hardware receiver. It does not appear to have mobile app or API doc accompanyment or a doc on what is needed for expansion. I would imagine that there is a minimum critical mass and municipal buy-in for such devices to work. Theoretically, mobile apps would require far less barriers to start being useful.
It sounds like you have an idea/proposal for a separate (complimentary) product. It seems like a good idea - I'd like to see someone build that. But... this is not that.
Someone has some something cool here & people seem to be annoyed that they have not done something entirely different.