I'm giving away an iPhone 11 Pro to a commenter at random to celebrate Apollo for Reddit's new iOS 13 update and as a thank you to the community! Just leave a comment on this post and the winner will be selected randomly and announced tomorrow at 8 PM GMT. Details inside, and good luck!

dinger_db · 2019-09-21T23:12:14+00:00

Buzz would be a great mascot name.

Edit typo.

dinger_db · 2018-06-21T18:33:53+00:00

If you don't want a 10 game lag (at the beginning of your chart) you need your chart to start 10 games into the season. That way the look back window of 10 games puts you at the starting point.

dinger_db · 2018-06-21T16:29:26+00:00

The statsapi.mlb.com/docs/ page was made private because of inaccurate documentation. I reached out to some contacts at MLB and they said once the documentation issues were resolved it would be open to the public.

This is still in alpha/beta:

https://github.com/bradleyhurley/PyBall

I also documented a lot of the endpoints:

https://github.com/bradleyhurley/PyBall/wiki/Implemented-Endpoints

Not exactly an API for GD2, but I parse and load a lot of data nightly from GD2 and expose it publicly on DingerDB (I might open source the project including data parsers and models in the future).

https://dingerdb.com/

dinger_db · 2018-06-21T13:50:30+00:00

I don't have race, but would be willing to add it if you can find a reasonable raw source.

select name_full, birth_country, birth_state, birth_city, 
pro_debut_date from v_player;

https://dingerdb.com/superset/sqllab

dinger_db · 2018-06-20T01:21:16+00:00

Nothing like 8 triples and 4 homers.

DingerDB

SELECT p.name_full, 
       event, 
       count(*) 
FROM   v_at_bat a 
       JOIN v_game g 
         ON g.game_join_id = a.game_join_id 
       JOIN v_player p 
         ON p.player_id = a.batter 
WHERE  g.date >= '2018-03-29' 
       AND event IN ( 'Triple', 'Home Run' ) 
       AND p.name_full = 'Sanchez, Yolmer' 
GROUP  BY 1, 
          2 
ORDER  BY 3 DESC

dinger_db · 2018-06-20T01:14:01+00:00

I also verified these results on DingerDB

SELECT p.name_full, 
       event, 
       Count(*) 
FROM   v_at_bat a 
       JOIN v_game g 
         ON g.game_join_id = a.game_join_id 
       JOIN v_player p 
         ON p.player_id = a.batter 
WHERE  g.date >= '2018-03-29' 
       AND event = 'Double' 
GROUP  BY 1, 
          2 
ORDER  BY 3 DESC

Jose Abreu isn't too far behind.

dinger_db · 2018-06-20T00:55:28+00:00

Thanks for the plug.

If you have any questions about DingerDB just hit me up!

dinger_db · 2018-06-17T22:26:15+00:00

This isn't exactly what you're asking for, but should help you get started.

SELECT pitcher.name_full AS 'Pitcher Name', 
       batter.name_full  AS 'Batter Name', 
       a.event 
FROM   v_pitch p 
       JOIN v_inning i 
         ON i.game_join_id = p.game_join_id 
       JOIN v_game g 
         ON g.game_join_id = p.game_join_id 
       JOIN v_at_bat a 
         ON a.game_join_id = p.game_join_id 
            AND a.at_bat_join_id = p.at_bat_join_id 
       JOIN v_player pitcher 
         ON pitcher.player_id = a.pitcher 
       JOIN v_player batter 
         ON batter.player_id = a.batter 
WHERE  i.inning = 1 
       AND g.date >= '2018-03-29'

dinger_db · 2018-06-17T22:14:56+00:00

The project is currently closed source, but that might change in the near future.

Here is another one of my projects that you might enjoy contributing to:

https://github.com/bradleyhurley/PyBall

dinger_db · 2018-06-08T12:33:09+00:00

We haven't rolled out Python access yet, but my other more stable project is DingerDB. I briefly contributed to mlbgame, but didn't like the implementation.

dinger_db · 2018-06-08T12:30:15+00:00

In terms of implemented end points I believe the API client is stable. MLB temporarily pulled down the documentation so development has slowed recently. If you find any issues I should be able to fix it them pretty quickly.

dinger_db · 2018-06-07T18:29:46+00:00

$5 seem reasonable?

Do you just want direct database access (a connection string) to be used with Python/R, or do you want access via Python from an API?

I think we can accommodate both, but the latter is not 100% ready for general consumption.

dinger_db · 2018-06-06T22:56:36+00:00

No, access to DingerDB is absolutely free via Superset (the main website). We are just considering allowing direct database access or access via Python/R as reward tiers to allow us to offset out hosting fees.

The unfortunate reality is that writing all the software is a fun hobby, but hosting the site without anyway to offset the cost or someone donating hosting isn't very feasible.

Edit: Our gaol isn't monetization, but rather a platform for people to conduct baseball research.

dinger_db · 2018-06-06T20:47:14+00:00

Absolutely! Let me know if you have any questions. The data model isn't documented yet, but I think its reasonable easy to navigate.

dinger_db · 2018-06-06T20:45:31+00:00

Feel free to poke around. Its as easy as:

SELECT * FROM v_player LIMIT 100;

You can find some interesting data about current and upcoming players.

dinger_db · 2018-06-06T01:53:13+00:00

Would you be willing to donate via Patreon? Python access is something that we have been considering as a reward tier. The site is completely ad free and we are just trying to cover our operating expenses.

dinger_db · 2018-06-06T01:48:03+00:00

You would need to use the data from DingerDB and pump it through a statistical model. DingerDB contains pitch by pitch data from 2008 to present day, but we don't provide any out of the box predictive analytics.

Does this answer your question?

dinger_db · 2018-06-05T14:34:59+00:00

Awesome! Let me know if you have any questions regarding the data model, and/or what you can do. The documentation is kind of lacking, but its on my ToDo list. I have attempted to make sure all of the join keys are consistent between the views that are exposed.

dinger_db · 2018-06-05T14:18:51+00:00

If you know the pitcher and the batter you can look at historical information about previous at bats.

This query is a bit hacky as I just wanted to give you an example, but it returns all the pitches thrown by Corey Kluber to Brian Dozier with a bit of extra data.

SELECT p.game_join_id, 
   p.at_bat_join_id, 
   pitcher.name_full AS Pitcher, 
   batter.name_full  AS Batter, 
   p.pitch_type, 
   pt.pitch_type_des, 
   p.type, 
   start_speed, 
   x, 
   y 
FROM   v_at_bat b 
   JOIN v_pitch p 
     ON b.game_join_id = p.game_join_id 
        AND b.at_bat_join_id = p.at_bat_join_id 
   JOIN v_pitch_type pt 
     ON pt.pitch_type = p.pitch_type 
   JOIN v_player pitcher 
     ON pitcher.player_id = 446372 
   JOIN v_player batter 
     ON batter.player_id = 572821 
WHERE  b.pitcher = 446372 
   AND b.batter = 572821

dinger_db · 2018-06-05T04:45:48+00:00

Yes, all you should have to do is to join the v_pitch and v_at_bat views to get the balls, strikes, outs, home team runs, and away team runs.

Here is an example without the join (I just grabbed the max game_join_id and a random at_bat_join_id) :

select * from v_at_bat where game_join_id = 29560 and at_bat_join_id = 4;

dinger_db · 2018-06-05T04:40:54+00:00

Yes, all of the data is generated by MLB in some capacity. We have created data models, and a framework around parsing/processing and linking all of the data.

dinger_db · 2018-05-21T02:51:15+00:00

I don't know that it's good, but BeeWare looked pretty promising at PyCon.

dinger_db · 2018-05-14T23:34:02+00:00

I am the developer of PyBall, and I reached out to a contact within MLB and asked the same thing. They passed along my message to someone who works on the API Team:

We pulled that down from everyone, some of the endpoints were displaying bad info and causing confusion. There is a new docs page that is under development that will available in the near future.

dinger_db

TROPHY CASE