Another use of the CW API to add to the growing list.
mechstats.com has been around for a while to capture individual stats, and so it seemed easy enough to add the CW information as well.
https://www.mechstats.com/CW
mechstats captures the PGI pubs and restructures things, getting some value from differences from one pull to the next. All that info is stored in SQL and easily accessible. Ive included a list of the existing web APIs that can get to this, in a doc at http://1drv.ms/1uYtBpr
The current layout of the CW page is crap as I wanted to get a) the timely reliable gathering, the correct differencing conclusions and storage of data, and c) the functional APIs out of the way first.
As with all things for mechstats, its really just a project for me to play with deployments, so if you do spot some API that you want to use keep in mind that I will moving things soon to a custom dev portal (azure managed api) at https://mechstats.portal.azure-api.net, and URLs as documented will change.
1
Another Cw Api Use
Started by Escobar, Dec 24 2014 03:45 PM
2 replies to this topic
#1
Posted 24 December 2014 - 03:45 PM
#2
Posted 24 December 2014 - 05:38 PM
Escobar, on 24 December 2014 - 03:45 PM, said:
Another use of the CW API to add to the growing list.
mechstats.com has been around for a while to capture individual stats, and so it seemed easy enough to add the CW information as well.
https://www.mechstats.com/CW
mechstats captures the PGI pubs and restructures things, getting some value from differences from one pull to the next. All that info is stored in SQL and easily accessible. Ive included a list of the existing web APIs that can get to this, in a doc at http://1drv.ms/1uYtBpr
The current layout of the CW page is crap as I wanted to get a) the timely reliable gathering, the correct differencing conclusions and storage of data, and c) the functional APIs out of the way first.
As with all things for mechstats, its really just a project for me to play with deployments, so if you do spot some API that you want to use keep in mind that I will moving things soon to a custom dev portal (azure managed api) at https://mechstats.portal.azure-api.net, and URLs as documented will change.
mechstats.com has been around for a while to capture individual stats, and so it seemed easy enough to add the CW information as well.
https://www.mechstats.com/CW
mechstats captures the PGI pubs and restructures things, getting some value from differences from one pull to the next. All that info is stored in SQL and easily accessible. Ive included a list of the existing web APIs that can get to this, in a doc at http://1drv.ms/1uYtBpr
The current layout of the CW page is crap as I wanted to get a) the timely reliable gathering, the correct differencing conclusions and storage of data, and c) the functional APIs out of the way first.
As with all things for mechstats, its really just a project for me to play with deployments, so if you do spot some API that you want to use keep in mind that I will moving things soon to a custom dev portal (azure managed api) at https://mechstats.portal.azure-api.net, and URLs as documented will change.
Wow, that's awesome information. Thank you for your work on it.
#3
Posted 24 December 2014 - 06:54 PM
Wow.
Such professional, very math.
Really solid groundwork, I'm sure we'll see some great outputs from this project
Such professional, very math.
Really solid groundwork, I'm sure we'll see some great outputs from this project
3 user(s) are reading this topic
0 members, 3 guests, 0 anonymous users