Re: [Talk-GB] TfL Cycling Infrastructure Database - conflation
Sounds great. I have used Ilya's OSM Conflate tool for point data in the past. That might be a good option and could be adapted to show the TfL photos. Probably best to split by region to keep the task manageable. BTW. the lockdown means more people are looking at ways to give back. There was an article about crowdsourcing to digitise handwritten rain / weather reports. A big success. I wonder if we can find a good OSM project to promote. Would need to be simple and hard to make a mistake. Need not be TfL data related. Best regards Rob -- Sent from: http://gis.19327.n8.nabble.com/Great-Britain-f5372682.html ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
Re: [Talk-GB] TfL Cycling Infrastructure Database - conflation
Martin Lucas-Smith - CycleStreets wrote: > Richard will be doing the bulk of the scripting work, and is working > on converting each of the sections of data. This will naturally be > published on Github openly, as will the outputted data. This is > reasonably complex work given the number of attributes and the > data extent. We are keen to ensure the OSM community is > able to scrutinise the conversion easily and have input. Richard > will post to this list about the work, as it proceeds. A quick update on this one: Hoo boy, there's a lot of data! The good news is that it's consistently high quality, and lots of it isn't in OSM already. Our cycle parking and speed bump coverage, for example, will be massively enhanced by this. In a few of the datasets, particularly (traffic-free) cycleways, we already have most of the information but the TfL data has identified missing items - for example, a decent shared-use path (almost a mile long) beside Snakey Lane in Feltham, shared-use paths beside the A1 in Mill Hill, and so on. The line geometries (cycleways and footways) will require a fair degree of manual work to get into OSM, obviously to ensure connectivity but also for sanity checking. The point data (cycle parking, traffic calming) etc. varies, and I've been classifying the output as "easy new data" or "needs further review" accordingly. I'll push some code and output to Github in the next few days so people can have a play. The general approach is that the TfL data is compared against an OSM PostGIS database, which means we have the full power of PostGIS's spatial analysis to help match features. Don't underestimate how complex the matching is: I've been working for 8+ days on it (lockdown's not such a bad thing...) and it's not finished yet. Currently I'm outputting GeoJSON for easy visualisation, but depending on the conflation tools eventually used, there'll almost certainly be .osm files too. There is an elephant in the room, and that's the (on-road, painted) cycle lane data. Once again, this is really high quality data. It's all new tags on existing ways (because we have all the roads mapped), but because it'll mean splitting the ways to get the extents right, it'll be a challenge for conflation. I'm currently thinking through the best approach for this, but again, I think it'll ultimately involve classifying the data into levels of confidence: "this is already in OSM", "this can be added easily", "this will need further review", etc. etc. As Martin set out, TfL have dedicated some time to training up their staff and working on the data. That'll work well for cycle parking etc., but the in-depth work on cycle lane attributes is almost certainly going to be best done by experienced OSM mappers. Once I've got the first set of output up on Github it would be great to take a steer from interested people as to what they'd find most helpful. cheers Richard -- Sent from: http://gis.19327.n8.nabble.com/Great-Britain-f5372682.html ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
[Talk-GB] TfL Cycling Infrastructure Database - conflation
Dear all, As you may recall, Transport for London (TfL) released as open data a major new cycling infrastructure dataset. Various people within the OSM UK community met TfL in the run-up to its release, and it was well-received. The OSM wiki has a project page here: https://wiki.openstreetmap.org/wiki/TfL_Cycling_Infrastructure_Database and you can browse the data here: https://bikedata.cyclestreets.net/tflcid/ I'm pleased to say that TfL, through a project with London Cycling Campaign, has allocated resources to enable conversion of the data as well as officer time within TfL to help conflate what is a huge dataset. CycleStreets is working with Richard Fairhurst (cycle.travel, and of course well-known as a long-standing member of the community) to get this conversion work done. Richard will be doing the bulk of the scripting work, and is working on converting each of the sections of data. This will naturally be published on Github openly, as will the outputted data. This is reasonably complex work given the number of attributes and the data extent. We are keen to ensure the OSM community is able to scrutinise the conversion easily and have input. Richard will post to this list about the work, as it proceeds. We will be using the previously-discussed conversion table: https://bikedata.cyclestreets.net/tflcid/conversion/ https://github.com/cyclestreets/tflcid-conversion and the remaining issues will be mopped up during the work. The aim of the scripting is to get as much of the data conversion automated as possible, and matching of assets very reliable, so that the conflation (tool yet to be determined) can then be done with a high degree of confidence and as easily as possible. The conflation itself, using the output of the script, will be started by TfL personnel, with training from Richard/myself about both process and norms and quality expectations of the community. TfL only have a certain amount of time resource for this, so it is hoped the OSM community will also contribute time as we refine and document the process. As noted above, the converted data will be published along the script itself. Every asset also has two images (already publicly available) which will be useful for verification. Richard and I hope this news will be well-received within the OSM community - this is a great opportunity to enhance OSM data in London. For instance, cycle parking coverage and detail can be considerably enhanced as a result of this data. If you have feedback for TfL on the CID outside of this conflation task then they can be contacted via c...@tfl.gov.uk. Martin, ** CycleStreets - For Cyclists, By Cyclists Developer, CycleStreets ** https://www.cyclestreets.net/ ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
