We want to share an important update with our Betfair Community users.
Over the coming months, the Betfair Community platform will be winding down. The final active day for the platform will be December 21st. From December 22nd, users will no longer be able to access the platform.
Your discussions, insights, engagement, and, most importantly, feedback have helped shape the platform and guided innovation. Your feedback continues to be important to us, and we will continue to listen via our dedicated feedback channels, as well as through product testing and innovations.
To share your feedback and experience, visit: https://support.betfair.com/app/home
General Betting
Welcome to Live View – Take the tour to learn more
Start Tour
There is currently 1 person viewing this thread.
23 Jul 11
00:59
Joined:
Date Joined:
27 Sep 03
If you pull data from RP (and if you don't there's probably no point in you reading any further...) prior to the last upgrade they used to have a meetingID field in the source which held the code for the racecourse, eg: meetingId=""202"" would be TIPPERARY.
Since the upgrade, meetingID is no more (swines, RP... swines) and the only racecourse code in the source seems to be in scorecards.sendSpecificDesc, the parameter before the date, ie 180 in the example below:
"scorecards.sendSpecificDesc("ruk_video", "180, 2011-07-22
Anyone else having problems with this?
ta
[also posted in General Betting]
Since the upgrade, meetingID is no more (swines, RP... swines) and the only racecourse code in the source seems to be in scorecards.sendSpecificDesc, the parameter before the date, ie 180 in the example below:
"scorecards.sendSpecificDesc("ruk_video", "180, 2011-07-22
Anyone else having problems with this?
ta
[also posted in General Betting]
Show More
Yes having same problem and a few others trying to extract form details using the horse ID URL
Most of the source code has been changed slightly which is always a sign of a new programming team coming on board. The last 'update' a few months back was proof of 'if it aint broke dont fix it' but I guess their programers didnt get their bid agreed for this year.
Most of the source code has been changed slightly which is always a sign of a new programming team coming on board. The last 'update' a few months back was proof of 'if it aint broke dont fix it' but I guess their programers didnt get their bid agreed for this year.
My scraping programme seems to have went into an infinite loop 
Apologies. Just as I gave up it finished and as yet I don't notice a difference. I can't find any reference to a MeetingID in my code.
and now it turns out that scorecards.sendSpecificDesc("ruk_video", "180, 2011-07-22 isn't even included on all UK races, check out:
http://www.racingpost.com/horses/result_home.sd?race_id=535306
Not a course code for Epsom (17) to be found in the source anywhere!
yeah, I know we can work off course string, but it's a pain.
Any kind souls form RP explain what's going on? ta
http://www.racingpost.com/horses/result_home.sd?race_id=535306
Not a course code for Epsom (17) to be found in the source anywhere!
yeah, I know we can work off course string, but it's a pain.
Any kind souls form RP explain what's going on? ta
My scraper looks for crs_id= and I've not had a problem.
I build the form from my own database rather than the horse id url, no point scraping what you've already scraped before... so maybe that's why I haven't had a problem.
But I just checked the page source for the horse id url page and it does have crs_id= if that helps
I build the form from my own database rather than the horse id url, no point scraping what you've already scraped before... so maybe that's why I haven't had a problem.
But I just checked the page source for the horse id url page and it does have crs_id= if that helps
Post Your Reply
Please login to post a reply.
Wonder
Instance ID: 13539