Uber Movement SANRAL Cape Town Challenge
'%3e%3cpath fill='%23001489' d='M0 0v6h9V0z'/%3e%3cpath fill='%23e03c31' d='M0 0v3h9V0z'/%3e%3cg stroke='%23fff' stroke-width='2'%3e%3cpath id='d' d='m0 0 4.5 3L0 6m4.5-3H9'/%3e%3cuse xlink:href='%23b' stroke='%23ffb81c' clip-path='url(%23c)'/%3e%3c/g%3e%3cuse xlink:href='%23d' fill='none' stroke='%23007749' stroke-width='1.2'/%3e%3c/g%3e%3c/svg%3e)
Helping South Africa
$5 500 USD
Completed (~6 years ago)
Prediction
Anomaly Detection
Forecast
859 joined
133 active
Start
Oct 11, 19
Close
Feb 09, 20
Reveal
Feb 10, 20
 scale(.21174)'%3e%3cpath d='m52.487 177.086 13.018 11.852 11.762-11.762 11.896 12.266 12.846-11.358 11.827 12.43 13.339-11.013 10.897 12.728 13.27-10.145 13.947 12.319'/%3e%3ccircle cx='89.425' cy='154.584' r='5.167'/%3e%3ccircle cx='111.237' cy='156.047' r='5.167'/%3e%3ccircle cx='30.05' cy='16.5' r='4'/%3e%3c/g%3e%3c/svg%3e){kind=small}
Some tutorials to get going
Notebooks · 21 Oct 2019, 12:44 · 9
Hello all,
I've written a few posts on getting going with this contest. Part 1 (https://datasciencecastnet.home.blog/2019/10/19/zindi-uberct-part-1-getting-started/) basically re-caps the starter notebook I shared earlier and is useful for getting a quick entry on the board. The second part (https://datasciencecastnet.home.blog/2019/10/21/zindi-uberct-part-2-stepping-up/) shares some next steps (adding features, using fast.ai) to boost the score (to >0.08 wthout much tweaking). Both have accompanying notebooks on Google Colab for easy duplication.
I'll be working on part 3, so please share any tips for things to include. Looking forward to questions and feedback :)
Thanks for Making the notebook for a startedstarted
Sweet, thank you for the starter code notebook and the blog posts. They're useful so far.
By the way, I get an error when I try to run this part of the notebook:
locations = data.groupby('road_segment_id').mean()[['longitude', 'latitude']] locations.head(2)
The error is as follows:
KeyError: "['longitude'] not in index"
It seems that this could be a Pandas bug, resulting from the groupby function going funky. I have updated my Pandas but the error persists in the latest version. I verified that the longitude column is in the data object after loading, and that it disappears right after the groupby method is called, by running nothing but the groupby function and checking for the longitude column again. It disappears.
Turns out there wasn't a bug in Pandas after all, but the train.csv file has a few dirty data entries. I suppose data cleaning is inevitable, but just a heads up to anyone else who is pulling their hair out.
Here's a tip: After loading the csv file say in a dataframe called data, call data.info(). If your longitude and latitude columns are not float64 types, you are not going to have a good time.
Hi DevilEars. Have you been able to find your way around the dirty data entries?
No other way around than going ahead with data wrangling operations to reformat your data..
Yes, I just clean it up with data wrangling operations. I remove all the longitude entries with the value Closed, and then I change the dtype of the longitude column to float.
Awesome. Thanks for sharing
Hi, could you please share a pyautogui code for automating download of uber data, which you mentioned in part 3?