Cygnus is a tool that helps the community improve the OSM map by comparing it with an external (local) map, and detecting differences between the two maps. The differences detected include road geometry and certain tags of interest (e.g.: ‘name’, ‘oneway’, ‘ref’, ‘maxspeed’) that are missing or have different value from OSM.
In this latest version of Cygnus, we have introduced new features and made a few overall improvements.
Minimum Way Length Distance
A new setting was added in this latest version: the minimum distance by which a way’s length in the OSM map may be extended using the external map.
Extending a way’s length can be very useful where section of a road may be missing or a new road needs to be added. Existing ways will be extended when the local map has a significantly longer way (as defined by the maximum connect distance). If it is possible to connect the extended way to any new ways, this will be done automatically.
New Grouped Settings and Checkboxes
We have grouped settings for ease of use into conflation, way-related and tag-related groups.
New checkboxes were also created for adding/extending ways (to allow more refined usage), adding/changing tags and specifying a minimum lexical difference.
The conflation zip file now contains a narration log detailing each change that is proposed by the conflation archive. The Cygnus+ output explains in the ‘telenav:action’ tag exactly what action was taken on each way (this same output goes into the narration log).
The conflation algorithm was improved and also the readability of parameters on jobs in the queue.
We hope you benefit from those changes, and let us know if you have any questions or ideas for further improvements.
When we first released ImproveOSM, the Telenav initiative to share millions of potential missing road, turn restriction and one-way locations based on massive anonymized GPS signals from drivers, we also launched a custom editor based on iD.
The editor provided an easy way to inspect ImproveOSM data and make OSM edits based on it.
Since then, we have worked hard to build out the functionality of the ImproveOSM JOSM plugin, and worked with the iD team to integrate ImproveOSM into the main OSM web editor.
These developments have made the custom editor obsolete, and we have decided to take it offline.
If you are interested in using ImproveOSM data to edit OpenStreetMap, please check out our JOSM plugin or select the ImproveOSM overlay in iD. You can also download the raw data from our ImproveOSM web site.
Thanks for using ImproveOSM and making OpenStreetMap better!
We decided to celebrate summer and the great driving weather that comes alongside it by launching a new OpenStreetCam competition! If you live in or happen to be nearby Miami, LosAngeles, Houston or Chicago, this is your chance to participate!
The kick-off date is June 12. Buckle up!
Download the free / open source OpenStreetCam app for Android or iOS.
Collect as many OpenStreetCam points as you can until August 12, 23:59 Eastern time. Every image uploaded gets you points, with more points awarded for roads that are being covered for the first time or that have been surveyed infrequently.
We will announce the winners on the 13th of August.
The top contributors will win an OpenStreetCam enhanced Waylens Horizon dashcam.
We will give out one dashcam per city to our top contributors.
Two runner ups will receive a $100 Amazon gift card.
You need to gather at least 500K points to be eligible to win the dash cam.
It costs nothing to compete.
Only the points collected between June 12 – August 12 are taken into account.
Points collected with Waylens dashcams are not eligible.
If you’re looking for additional insight, refer to the FAQ below:
How will I know my rank in the leaderboards?
We will post weekly updates on Facebook and Twitter. Make sure you check them once in while.
How can I earn more points?
Go to https://openstreetcam.org and check out where the magenta lines are missing. Those areas will guarantee the highest return.
I’m getting errors trying to install the app, record or upload.
The OpenStreetCam plug-in has once again brought a new
feature to help its users. It now allows displaying and filtering aggregated
detections based on their confidence level. The confidence level represents a
measure of confidence of the validity of the detection or aggregated detection.
New aggregated detections display
Aggregated detections can now be displayed using
a confidence level based color code. This is an optional behavior that can be
turned on in the plug-in preference settings by selecting the following
If selected, each aggregated
detection will be displayed with a border of the corresponding color, according
to the legend table displayed under the check-box.
Map display based on confidence level:
If the checkbox is not selected,
all aggregated detections are displayed with a white border.
Confidence level filtering
With the introduction of the confidence level attribute, a
new form of filtering was added. Filter data now allows setting a value for
minimum and/or maximum confidence level. When set, only the aggregated detections
with the appropriate confidence level will be displayed.
The latest version of the OpenStreetCam JOSM plugin has many design changes which make the usage more intuitive. The Telenav OSM team added new icons for the three main layers of the ImproveOSM plugin (Turn Restriction, Traffic Flow Direction, Missing Roads) and modified the cluster colors accordingly.
Also, some improvements were made regarding the visualization of turn restriction detections at a high zoom level. The color for the grouped detections was changed in order to match the aspect of the corresponding cluster and to facilitate spotting the detections from the map, the turn restriction icon was changed too.
feature has been added the OpenStreetCam plug-in that allows the visualization
of the OSM Elements corresponding to the selected detection or cluster. OSM
Elements are the basic components of OpenStreetMap’s conceptual data model of
the physical world.
How to use the new feature
step is to select a detection or a cluster. If the selected item has OSM Elements,
the Matched Data button from the
details panel will be enabled.
By pressing the button, the corresponding OSM element will be drawn in the OpenStreetCam layer and it will persist until selection changes or the item is deselected.
three possible cases of display:
The element is of type Node:
The element is of type Way:
The element is of type Relation:
have a checkable option under preferences for tag display.
this checkbox is selected, the tags associated with the OSM element members are
displayed on the map.
The Telenav OSM team is excited to announce a new OpenStreetCam imagery collection competition for Australia and New Zealand! This second edition will kick-off on the 15th of March and will last until the 15th of April. Buckle up!
How to compete
Download the free / open source OpenStreetCam app for Android or iOS.
Collect as many OpenStreetCam points as you can until April 15, 23:59 UTC+10. Every image uploaded gets you points, with more points awarded for roads that are being covered for the first time or that have been surveyed infrequently.
We will announce the winners on the 16th of April.
The top contributors will win a Waylens Horizon dashcam.
We will give out one dashcam per country to our top contributors.
The runners up will receive a $100 Amazon gift card.
You need to gather at least 250K points to be eligible to win the dash cam.
Points collected with Waylens dashcams are not eligible.
It costs nothing to compete.
those who don’t know OpenStreetCam, it is a free and open platform that uploads
street-level imagery captured by your smartphone and detects salient features
from the uploaded images such as signs, lanes and road curvature to improve
OpenStreetMap. The images are collected by mappers for mappers and can be used
in iD or JOSM to improve OpenStreetMap.
Last December and January, OpenStreetCam held a image collection competition in Australia and in New Zealand. The three mappers in each country who collected the most points during the months of December 2018 and January 2019 could each win a gift card: $100 for the winner, and $25 for the second and third place. We just announced the winners to the communities in both countries. Congratulations to steve91, robbie-bloggs, ConsEbt, david-blyth, ivss-xx, and nicknz!
We decided to do these competitions because we wanted more mappers in Australia and New Zealand to get acquainted with OpenStreetCam, and consider contributing to this free and open platform for street-level images. The more contributions, the more help OpenStreetCam can be for OSM mappers! There weren’t many contributions in either country yet, and if you go to the OpenStreetCam web site, you’ll quickly see that there are still large gaps to fill. Still, OpenStreetCam coverage grew by 800% since the beginning of December.
Head over to the ImproveOSM Blog for a step-by-step guide on how to get started with OpenStreetCam yourself!
OSM mappers can use the OpenStreetCam images to help with mapping. You can’t see everything from an aerial image. Signs are a great example of useful mapping information that requires an on the ground perspective. This is where OpenStreetCam is particularly handy, because we detect an increasing diversity of signs that appear on the photos for you automatically, using an open source machine learning platform.
For the sign detection platform to work and detect a variety of signs reliably, it needs training data. Your contributions during this competition have been invaluable to reach that goal. Our Map Team looked at tens of thousands of images collected by the community during the competition in Australia and New Zealand, and validated more than 160,000 traffic signs found in these images. After feeding that data into the platform, we can now reliably detect more than 80 types of signs in Australia and New Zealand. As we continue to look at more images that you contribute, the system will get smarter and we will detect more different types of signs.
Do you want to help train the OpenStreetCam sign recognition AI? You can do this right from the OpenStreetCam web site. Read all about it in this blog post.
The Telenav OSM team just released a new version of the OpenStreetCam JOSM plugin. In the last couple of months we had improved our sign detections and improved the detection map view, by displaying aggregated traffic sign detections instead of individual detections. Traffic signs are detected per OpenStreetCam photos, in dense areas the same traffic sign is detected several times. Checking several detected signs that represent the same traffic sign in real life is time-consuming and slows down the mapping process. In order to improve the mapping process, detections that represent the same traffic sign were aggregated into a single detection.
Map View Changes
Aggregated detections are displayed for high zoom levels starting with zoom level 16. Each aggregated detection is represented by a traffic sign cluster icon rotated based on the detection heading.
Aggregated detection data
An aggregated detection can be selected by a right click from the map and unselected by a double click. When an aggregated detection is selected the detection icon along with the belonging photo locations are highlighted on the map and its information is displayed in the right side OpenStreetCam Detection panel. The photo on which the detection has the best visibility is also loaded automatically.
Loading other photos that contains the detections can be done by either selecting a photo location from the map or by pressing the Next/Previous buttons from the OpenStreetCam Detection panel. For the associated shortcuts take a look at the OpenStreetCam shortcuts from JOSM Preferences.
By default, the plugin displays the photo locations of a selected cluster, but the plugin can be configured to display also the actual detections. This can be enabled from JOSM Preferences->OpenStreetCam plugin -> Aggregated detection settings.
If enabled individual detections are connected to the corresponding photo. This visualization is used mainly for debugging purposes.
The OSC plugin data can be filtered based on various new filters. Some of these filters were already present and others were extended.
data to display – the type of data to be displayed for high zoom levels; by default, we display OpenStreetCam photos and aggregated detections; if both detections and aggregated detections are selected then besides aggregated detections only the detections that do not belong to any aggregation are displayed
only mine – displays OpenStreetCam data contributed by the logged in user
not older than – filters out data based on a given timestamp
detection filters – are applied to detection/aggregated detection data
mode – is applicable only to individual detections; if set filters data based on detection mode; manual detections are detections that were manually marked on the OpenStreetCam photos, while automatic detections are detections recognized automatically by our platform
edit status – is applicable only to individual detections; if set filters detections based on edit status (if the user had edited or not in OSM the detection)
OSM comparison – filters the data based on the status; OSM comparison represents a status of a detection regarding its presence in OpenStreetMap; this filter is useful since the mapper can visualize only detections that need to added to the map
detection type – filter data based on detection type and subtype; this filter is useful if the mapper would like to focus on mapping only a certain type of signs
Default filter settings can be reset by pressing the “Reset” button.
Upcoming features The JOSM plugin is work on progress, we are working on improving the usability and plan to add new features from time to time. In the near feature, we plan to improve the detection mapping workflows.
We hope that you enjoy the new features! If you have ideas, suggestions or encounter any issue with the plugin during editing sessions please submit either to the GitHub issue page or to the Feedback forum .
Have fun improving the map by using OpenStreetCam images!
The Telenav OSM team just released a new version of the ImproveOsm plugin. We have added a location search box (helpful feature for reaching an area to be mapped) and a button for downloading previously selected ways.
Location search box
A new feature we added to the ImproveOSM plugin is the location search box. It enables the user to visualize the desired geographical point at a higher zoom level after entering its coordinates in the text field. The input of the search box should contain the values for latitude and longitude separated by a comma. If the plugin doesn’t understand your input, an intuitive message is displayed in order to help you. This works similar to the JOSM Jump to position but the search box brings advantages such as the single field for data collecting and more validations for the latitude-longitude values.
Download way button
Another feature is the download way button for the Traffic Flow Direction layer. This enables the user to download the ways of the selected road segments in a new Data layer. This option is only available if the Traffic Flow Detection Layer is active. Furthermore, the button becomes enabled when one or more road segments are selected.