-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
function to get TFL traffic calming data from CID #2
Comments
Hi @PublicHealthDataGeek! Can you elaborate in case I want to get a draft of this. "ct" stands for? |
@layik actually the work is already done as part of an earlier package Robin I wrote https://github.com/PublicHealthDataGeek/CycleInfraLnd to extract TFL Cycling Infrastructure Database data. This was a placeholder to remind us to include it here. The snippet from CycleInfraLnd is below with the type in this case being "traffic_calming" (the CID contains other data types too) get_cid_points = function(type) { so would the function be 'get_cid_trafficcalming' or similar depending on what you have named other functions. ct stands for Caroline Tait! |
Just noted that there is already a fucntion in safeactive for obtaining OSM traffic calming data: the CID has different strengths and weaknesses compared to OSM. Perhaps this is more of a conceptual/strategic issue for @Robinlovelace to be involved in. would be a shame to not include the CID data which is 'official'. |
Yes we should include CID data and functions to ease getting it is my thinking. One question @PublicHealthDataGeek can we use your functions here? You could put in a PR to contribute them directly... |
OK, now I know what "CT" stands for, happy to leave it for her. |
Yes we can use my functions here. Might just need to think about naming of the function so that it differentiates it from the 'traffic_calming_points'. How about 'TFL_CID_traffic_calming_points'? As mentioned on issue #15 I am happy to draft some code but might just need a hand to incorporate into package etc. |
ct has code
The text was updated successfully, but these errors were encountered: