CSV Files: What Do Some of the Headers Stand For?

chucksabr · 09-04-2020, 02:15 PM

I am want to download CSV files from my league and create an Excel pivot table (PVT) where I can keep track of offensive and pitching performances for the league in a format I can easily manipulate, and without having to open the game itself to look at them.

I have successfully set up PVTs using the players_game_batting and players_game_pitching_stats file, both of which report game-level results for individual players, which I can also scope outward to provide team- and league-level stats as well.

Now I am trying to do the same for individual at bats (i.e., using the players_at_bat_batting_stats.csv), so I can essentially develop a PVT for batting and pitching splits. Problem is, I cannot decode what several of the columns and their data mean.

I was hoping (still am) that there is a guide or manual that delineates what all the headers and data in all the CSV files mean, but I haven't found anything like that yet, so hopefully someone here can help me decode at least these.

The columns I need help are these:

Result: the data range from 1 through 11. What outcomes do each of these refer to?
Hit location: The data range from 0 through 105, as well as 255. Where do these refer to?
Hit_xy: The data range from 0 through 255, where do these refer to?

If anyone knows what these mean, would really appreciate the info. Even better, if anyone knows if there's a resource explaining what all the columns mean on all the files, that would rock.

Thanks!

Matt Arnold · 09-04-2020, 02:49 PM

I don't know if we directly enumerate them anywhere.

Result are the following:
K
BB
OUT (generic, likely shouldn't appear in csv outputs since it usually gets translated to GO/FO)
GROUND_OUT
FLY_OUT
SINGLE
DOUBLE
TRIPLE
HOMERUN
HP
CI

Hit Location should basically map to the ballpark locations you can set in 3D: https://manuals.ootpdevelopments.com...park_locations It may end up being +/- 1 depending exactly on indexing, and there may be a few special case elements near the end of the list that don't mark to those park locations, but are stuff like home plate/1B/etc.., although I don't know off-hand which may or may not be used in the csv outputs.

hit_xy is a little complicated, but it's basically an index into the above zone for where the ball lands (or for infield plays, where the fielder supposedly picks up the ball). It's probably not really necessary or useful for what it sounds like you're trying to build, since it's more useful internally for mapping game action and 3D action.

chucksabr · 09-04-2020, 05:37 PM

Great, Matt, thanks!

09-04-2020, 02:15 PM	#1
chucksabr Hall Of Famer Join Date: Sep 2013 Location: In the canyons of your mind Posts: 3,190	CSV Files: What Do Some of the Headers Stand For? I am want to download CSV files from my league and create an Excel pivot table (PVT) where I can keep track of offensive and pitching performances for the league in a format I can easily manipulate, and without having to open the game itself to look at them. I have successfully set up PVTs using the players_game_batting and players_game_pitching_stats file, both of which report game-level results for individual players, which I can also scope outward to provide team- and league-level stats as well. Now I am trying to do the same for individual at bats (i.e., using the players_at_bat_batting_stats.csv), so I can essentially develop a PVT for batting and pitching splits. Problem is, I cannot decode what several of the columns and their data mean. I was hoping (still am) that there is a guide or manual that delineates what all the headers and data in all the CSV files mean, but I haven't found anything like that yet, so hopefully someone here can help me decode at least these. The columns I need help are these: Result: the data range from 1 through 11. What outcomes do each of these refer to? Hit location: The data range from 0 through 105, as well as 255. Where do these refer to? Hit_xy: The data range from 0 through 255, where do these refer to? If anyone knows what these mean, would really appreciate the info. Even better, if anyone knows if there's a resource explaining what all the columns mean on all the files, that would rock. Thanks! __________________ The (English) Baseball League (est. 1888): A History The 1932 Season is Underway Dynasty Mission \| Creation Story \| Subscribe 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 (Great War Hiatus) 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 The OOTP Interview about the Baseball League

09-04-2020, 05:37 PM	#3
chucksabr Hall Of Famer Join Date: Sep 2013 Location: In the canyons of your mind Posts: 3,190	Great, Matt, thanks! __________________ The (English) Baseball League (est. 1888): A History The 1932 Season is Underway Dynasty Mission \| Creation Story \| Subscribe 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 (Great War Hiatus) 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 The OOTP Interview about the Baseball League

09-04-2020, 02:49 PM	#2
Matt Arnold OOTP Developer Join Date: Jun 2009 Location: Here and there Posts: 15,720	I don't know if we directly enumerate them anywhere. Result are the following: K BB OUT (generic, likely shouldn't appear in csv outputs since it usually gets translated to GO/FO) GROUND_OUT FLY_OUT SINGLE DOUBLE TRIPLE HOMERUN HP CI Hit Location should basically map to the ballpark locations you can set in 3D: https://manuals.ootpdevelopments.com...park_locations It may end up being +/- 1 depending exactly on indexing, and there may be a few special case elements near the end of the list that don't mark to those park locations, but are stuff like home plate/1B/etc.., although I don't know off-hand which may or may not be used in the csv outputs. hit_xy is a little complicated, but it's basically an index into the above zone for where the ball lands (or for infield plays, where the fielder supposedly picks up the ball). It's probably not really necessary or useful for what it sounds like you're trying to build, since it's more useful internally for mapping game action and 3D action.