Please find in the following link a zip file with 5 mca files with traffic lights (Traffic signals).

I quickly added CZ, DE, GB, NL and PL for the persons in this conversation. They are not searchable, as that is simply not possible with the OSM options as they only have an OSM id. They are only displayed as such on the map.

But that's not the point at all. I don't care as such for a nice red-orange-green icon on my screen.

It would be much better to have them integrated in the maps. And as soon as you have them in the map you can also speed penalties to them if they are on your route.

This will make calculation of "in city" route duration times much more precise and realistic. The fact that Navigator does not take speed penalties into account makes that the route duration times are sometimes half of what they should be.

Next to that: Navigator sometimes calculates wrong routes inside cities because only based on speed and distance the route is faster, but in reality it is not.

However, some other Nav apps use the traffic signs on the route and therefore calculate another route that might look a little longer and slower, but in reality is (much) faster due to the fact that it contains less traffic signs (or other speed regulating options like bumps).

It is not only the traffic signs though. In a city with much cross-roads and roundabouts, which also reduce average speed, Navigator simply calculates the fastest route without taking into acount all those "speed reducers" while sometimes a "short route around" without all those crossroads (and traffic signs) is both faster and more relaxed to drive.

On long "out of town" drives these speed penalty options only have minor impact.

- and when going into details: road smoothness, which is an additional tag for highway. In some countries the shortest road can also be the worst road. Taking road smoothness into account (even if it is an user selectable option) would improve it as well.

But it will make Navigator a much better route planner within cities and for road smoothness also outside cities, even though that is less of a problem in Western-Europe.

As mentioned: on long drive outside towns speed penalties don't make a big difference.

Not being part of the team :) I would suggest a scrum approach: small steps at a time. You have already all crossroads and roundabouts in the maps. Use these for speed penalties. Simply calculate another 10-15 seconds.

Then add traffic_signals and add 30 seconds or so.

Etcetera, etcetera.

Edit: Note that taking the reduced speeds for motorway exits and the like is also a form of a speed penalty.

So it might not be too difficult but it requires quite some work in the if-then-else functions for all situations, and I assume it takes some modifications of your maps.

printf "You should now have your gpx file(s) ready. Run them through digger"

And the link to the traffic_lights image/icon I created from an open source image and made transparent (background). I simply loaded the gpx in digger with standard settings (based on the icon size) and didn't specify anything in the name, note or map page.

Lubos is right about the digger MCAs. They are less optimized. When such an mca contains too many entries it is getting slow as well. I think the Navigator MCAs are indexed and the digger MCAs are not. I notice it as well with those wikipedia/wikivoyage mca files I have been working on. They become very slow.

On the other hand: a traffic light is actually not a POI. You can treat them more like the "external" speed cam MCA files coming with Navigator.

Either you can implement the traffic lights as POI in the general mca files or as some road tag in the mca files.

With regard to POI icons: Should that really take so long? I used to be heavily involved in another open source nav app and it was relatively easy to add another POI there.