Happy Festivus from the Rapid Team! Today we released v2.5 of the Rapid editor for OpenStreetMap just in time for the “Feats of Strength”
Here’s 4 new features that we’re really proud of!…
Pixi v8 Upgrade!
We upgraded Rapid’s render to use the latest version of PixiJS game engine. This version gives Rapid a welcome performance boost - if you’ve aired any grievances about Rapid being laggy, the new Rapid should perform much better for you!
Rapid can now detect whether curb ramps can been mapped at road crossings and prompt the user to add them with a one-click fix. These suggestions look different from the previous warnings raised by our validator - they show up with a small upgrade symbol
Another Festivus miracle! Overture Places is an open dataset of over 50 million places. We’ve added this dataset to Rapid as a read-only preview to make it easier to contribute missing businesses and points-of-interest to OpenStreetMap.
Meta has collected openly licensed data in 5 cities (more to come!) to make it easy to add missing sidewalks to OpenStreetMap. You can find this new dataset in the Rapid menu too!
And in some areas like Poland they are pure gibberish with occasional duplicate/triplicate/quadplicate of actually valid object, or repeat of what is already in OSM.
@bhousel Can you at least add a default filter for confidence: to hide the vast majority of them? In my experience, it has to be 0.9, to even 0.95. (Ironically you used a ~0.3 example) Not only are they usually wrong, but the overwhelming false positives also obstructs finding the few more likely candidates, if you really want it to be used.
I think at this point most people just want to look at the data, so “hiding the vast majority of them” would just frustrate people. There is value in seeing a whole lot of POIs overlaid on a largely empty OSM map. It’s a good signal to find places where OSM needs improvement. (AllThePlaces and Foursquare Places are 2 other similar POI datasets that people ask us about too, maybe we’ll add those so people can compare?)
We don’t have a mechanism yet for providing feedback on data back to their source (Microsoft, Facebook, Overture, etc). We might add this eventually.
I also agree with your suggestion that we should give users the ability to filter by confidence (other tags too) - we don’t have that and it would be a good thing to add. In general we need to improve the filtering in Rapid for all datasets.
This place does exist - But it’s definitely closed like everything else on the North Wildwood boardwalk in December. I don’t know whether seasonality of a business affects its confidence score in this dataset.
Before filtering is added, would it possible to change their symbology in the rendering, varying color or transparency by their attributes in the style?
Indeed, I haven’t checked whether the example area has good quality data. Certainly there can be correct ones with low confidence: , but I don’t expect them to be the majority. The crowding-out / dilution of usefulness should be worse in higher density cities.
Yes, we actually have an old issue to try this for the Facebook Roads layer: https://github.com/facebook/Rapid/issues/147
We can add some transparency where the data has a lower confidence number.
Most of the data that I see in Overture Places seems to be real stuff, but it’s often misplaced, like the marker is in the parking lot or street instead of in the building.
Some is also real stuff that doesn’t really belong in OSM. Scrolling around near where I took the screenshot, I see things like a local music festival, a triathalon, a beach volleyball tournament, or a bunch of home businesses. So these things probably have a Facebook page and they are real but don’t really belong in a general-purpose dataset like OSM.
For a while now I have been wanting to use Rapid as my primary web-based editor, but unfortunately it doesn’t seem to load the aerial images layers recommended for Portugal. Here’s Bing Maps:
Is this kind of issue known, or should I perform additional troubleshooting to help identify the cause? (Just to be clear, these layers work as expected with iD).
I took a look and it is being blocked by CORS. We aren’t able to display imagery in WebGL unless it’s configured for cross-origin-resource-sharing. We don’t have ability to do a fallback slippy map, but it might be possible eventually.
Probably the fastest way to fix the issue is to reach out to whoever runs https://cartografia.dgterritorio.gov.pt and ask them to configure their server to allow cross-origin requests.
(i.e. add the Access-Control-Allow-Origin: * header)
Great to see you keep making RapiD the most advanced OSM editor out there, Bryan - feel like you might add a turn:lanes editor UI quicker than the original iD…
Overture can be quite useful, although as others said the location of nodes might be somewhat random (confidence=null checks out), don’t mind that too much as it’s useful to have for those POIs.
I did get a few glitches where on zoom/pan Overture nodes changed/disappeared, but may have been my local issue
The confidence:null at the bottom is for the sources:
I do feel it’s difficult to visualize low positional accuracy features. Speaking fairly, some Overture records may exist somewhere around with wrong coords, which will cause them to be ignored and not investigated. However, it’s a large amount of effort to waste on detective work to salvage any value from them.
Ideally, the reliability should be measured separately, or some researching making a correlation between them. Then a fuzzy circle could be drawn to show a probable radius.
Pixi v8 Upgrade!
New Curb Validator
New Overture Places Dataset
New Open Footways Dataset
Switch to Rapid! Bookmark https://rapideditor.org/edit and make it your editor of choice.
Want to help us make Rapid better? Follow us on Github at GitHub - facebook/Rapid: The OpenStreetMap editor driven by open data, AI, and supercharged features or find us on our social media or OpenStreetMap community channels.
