# Traffic signs, speedlimit wrong positive **URL:** \ **Category:** Map data and detections\ **Created:** [July 3, 2019, 6:15pm UTC](https://forum.mapillary.com/t/traffic-signs-speedlimit-wrong-positive/3106 "2019-07-03T18:15:51Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![AdVerburg](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/adverburg/32/772_2.png) [@AdVerburg](https://forum.mapillary.com/u/AdVerburg)\ **Post date:** [July 3, 2019, 6:15pm UTC](https://forum.mapillary.com/t/traffic-signs-speedlimit-wrong-positive/3106/1 "2019-07-03T18:15:51Z")
Bicycle route signs in the Netherlands are often misinterpreted as speed limit signs. Osmose uses (the traffic sign) detections to check the OSM for completeness, and generates with these wrong detection, false positives. An example [Mapillary](https://www.mapillary.com/app/?focus=photo&pKey=khjno9xxAdoySiIUCCOeXQ&signs=true&points=true&lat=51.34057195833333&lng=3.8706857708333473&z=17) Pictures and Dutch description can be found at [Overzicht van verkeersborden in Nederland | www.verkeersbordenoverzicht.nl](https://www.verkeersbordenoverzicht.nl/#BF). These signs have a rectangle shape and having an green encircled number between 1 and 99 on a white background. While the maxspeed signs in the Netherlands (and many other countries) have black numbers (multiples of 10) on a white background with a red border. Is it possible to improve the algorithm? ---
**Author:** ![pbb](https://avatars.discourse-cdn.com/v4/letter/p/3e96dc/32.png) [@pbb](https://forum.mapillary.com/u/pbb)\ **Post date:** [September 30, 2019, 7:42am UTC](https://forum.mapillary.com/t/traffic-signs-speedlimit-wrong-positive/3106/2 "2019-09-30T07:42:26Z")
I have created a verification project for this. I have no clue if this will work (it’s the first time I created a verification project), but we can see what it does. The link is: [Mapillary](https://www.mapillary.com/project/verification/ycPaA8MyAeHzBiaMy8zkYB)