Open aerostitch opened 13 years ago
Screenshot.png
(207.9 KiB)Screenshot-1.png
(165.8 KiB)Korrosa, which graphics driver are you using?
Sorry, should have said: internal.
<graphics type="gtk_drawing_area"/> <gui type="internal" keyboard="false" enabled="yes"> ...
Is this working for you then? It wouldn't surprise me if this was specific to me, but it'd be nice to work out why...!
navit.xml
(164.5 KiB)My navit.xml
I think this might be a speed cameras in binfile vs speed cameras in csv file issue: the OSD works fine for speed cameras defined in csv files, but I get the problem in this ticket for speed cameras defined in the binfiles.
Is the problem occur with binfile cameras created from csv file (csv->textfile->binfile conversion) or with cameras come directly from OSM data?
If the problem is with OSM cameras can you pls link the place in osm to be able to reproduce the bug.
Binfiles are created from OSM data - i.e. the speed camera is embedded in the binfile, along with all the other OSM data (streets, POIs etc). Just as if I'd have downloaded the binfile from the Navit map extractor.
An example node is http://www.openstreetmap.org/browse/node/918608677
Apparently the rectangle is supposed to be empty when using speed cameras from OSM binfiles. I thought this got fixed in 4185 (Fix:osd/core: speedcam osd can now use both binfile and csv cameras) ?
After rev 4228 distance to osm based cameras is displayed. Korrosa, what attributes can an osm camera have?
Of itself, a highway=speed_camera node has no other attributes. http://wiki.openstreetmap.org/wiki/Tag:highway%3Dspeed_camera. When using this node, the renderer/router is expected to look at the road the speed camera is on/next to and judge the speed-limit etc from that. Not very easy.
However, there is an enforcement relation from which you can - if used correctly - deduce the following:
- Type of enforcement: maxheight / maxweight / maxspeed / mindistance / traffic_signals / check
- Enforcement value (if applicable): maxheight / maxweight / maxspeed
- Direction of enforcement
The relationship includes as members:
- Device (i.e. speed camera). This can be a node, way or area (i.e. for a HGV scale)
- From: where the enforcement starts
- To: where the enforcement ends (thus giving you direction)
The wiki page is: http://wiki.openstreetmap.org/wiki/Relation:enforcement. The original proposal which includes many examples is at: http://wiki.openstreetmap.org/wiki/Proposed_features/Relation:enforcement.
To be honest, I don't expect Navit to support this relationship anytime soon. To me this doesn't matter too much: I can tell what the speed limit is from the speed_warner OSD (and, of course, actually concentrating on driving!), and the direction of the camera is not important as most cameras can (and are) turned around to face the other way very often!
Korrosa, thanks for the detailed info. I guess most of the time these tec relations are set up correctly in osm data. Possibly when navit will support relations we can utilize these relations if statistics shows that large part of camera data is filled correctly.
I updated to 4702 today, and tried speed_cam for the first time. However on my device the background_color= setting/transparency has no effect at all, I get a white box displayed even without any camera event. The background setting works fine for other text labels.
Device is a wince 6.0 type, WayteQ-N800.
<osd enabled="yes" type="speed_cam" w="550" h="40" x="0" y="250" font_size="450" text_color="#ff0000" label="${distance} | ${camera_type} | ${camera_dir} | ${direction} | ${speed_limit}" path="$NAVIT_SHAREDIR/ie-allcam_speedcamerapoi.com.txt" background_color="#11111100" />
On other text items, background_color="#00000000" works fine being completely transparent.
Hello Polarbear,
Currently background_color attribute is not used in speedcam osd. Speedcam osd should disappear when out of range and it is red when active(in range). Disappearing is done by disabling the osd. Maybe the problem is in the implementation of osd disable for wince.
So how is the state of this issue? Can anybody please reproduce it on current SVN/binfile?
Sounds like a ugly bug, if somebody gets confused while riding a road -> scheduled to next hotfix.
Issue migrated from trac ticket # 777
component: osd/core | priority: minor | keywords: traffic, OSD, speed, speedcam
2011-02-18 14:50:40: korrosa created the issue