GT(self data rowname_col=None groupname_col=None auto_align=Trueid=None locale=None)
Create a Great Tables object.
The GT() class creates the GT object when provided with tabular data. Using this class is the the first step in a typical Great Tables workflow. Once we have this object, we can take advantage of numerous methods to get the desired display table for publication.
There are a few table structuring options we can consider at this stage. We can choose to create a table stub containing row labels through the use of the rowname_col= argument. Further to this, row groups can be created with the groupname_col= argument. Both arguments take the name of a column in the input table data. Typically, the data in the groupname_col= column will consist of categorical text whereas the data in the rowname_col= column will often contain unique labels (perhaps being unique across the entire table or unique only within the different row groups).
Parameters
data:Any
A DataFrame object.
rowname_col:str | None=None
The column name in the input data= table to use as row labels to be placed in the table stub.
groupname_col:str | None=None
The column name in the input data= table to use as group labels for generation of row groups.
auto_align:bool=True
Optionally have column data be aligned depending on the content contained in each column of the input data=.
id:str | None=None
By default (with None) the table ID will be a random, ten-letter string as generated through internal use of the random_id() function. A custom table ID can be used here by providing a string.
locale:str | None=None
An optional locale identifier that can be set as the default locale for all functions that take a locale argument. Examples include "en" for English (United States) and "fr" for French (France).
Let’s use the exibble dataset for the next few examples, we’ll learn how to make simple output tables with the GT() class. The most basic thing to do is to just use GT() with the dataset as the input.
from great_tables import GT, exibbleGT(exibble)
num
char
fctr
date
time
datetime
currency
row
group
0.1111
apricot
one
2015-01-15
13:35
2018-01-01 02:22
49.95
row_1
grp_a
2.222
banana
two
2015-02-15
14:40
2018-02-02 14:33
17.95
row_2
grp_a
33.33
coconut
three
2015-03-15
15:45
2018-03-03 03:44
1.39
row_3
grp_a
444.4
durian
four
2015-04-15
16:50
2018-04-04 15:55
65100.0
row_4
grp_a
5550.0
five
2015-05-15
17:55
2018-05-05 04:00
1325.81
row_5
grp_b
fig
six
2015-06-15
2018-06-06 16:11
13.255
row_6
grp_b
777000.0
grapefruit
seven
19:10
2018-07-07 05:22
row_7
grp_b
8880000.0
honeydew
eight
2015-08-15
20:20
0.44
row_8
grp_b
This dataset has the row and group columns. The former contains unique values that are ideal for labeling rows, and this often happens in what is called the ‘stub’ (a reserved area that serves to label rows). With the GT() class, we can immediately place the contents of the row column into the stub column. To do this, we use the rowname_col= argument with the appropriate column name.
from great_tables import GT, exibbleGT(exibble, rowname_col="row")
num
char
fctr
date
time
datetime
currency
group
row_1
0.1111
apricot
one
2015-01-15
13:35
2018-01-01 02:22
49.95
grp_a
row_2
2.222
banana
two
2015-02-15
14:40
2018-02-02 14:33
17.95
grp_a
row_3
33.33
coconut
three
2015-03-15
15:45
2018-03-03 03:44
1.39
grp_a
row_4
444.4
durian
four
2015-04-15
16:50
2018-04-04 15:55
65100.0
grp_a
row_5
5550.0
five
2015-05-15
17:55
2018-05-05 04:00
1325.81
grp_b
row_6
fig
six
2015-06-15
2018-06-06 16:11
13.255
grp_b
row_7
777000.0
grapefruit
seven
19:10
2018-07-07 05:22
grp_b
row_8
8880000.0
honeydew
eight
2015-08-15
20:20
0.44
grp_b
This sets up a table with a stub, the row labels are placed within the stub column, and a vertical dividing line has been placed on the right-hand side.
The group column contains categorical values that are ideal for grouping rows. We can use the groupname_col= argument to place these values into row groups.
from great_tables import GT, exibbleGT(exibble, rowname_col="row", groupname_col="group")
num
char
fctr
date
time
datetime
currency
grp_a
row_1
0.1111
apricot
one
2015-01-15
13:35
2018-01-01 02:22
49.95
row_2
2.222
banana
two
2015-02-15
14:40
2018-02-02 14:33
17.95
row_3
33.33
coconut
three
2015-03-15
15:45
2018-03-03 03:44
1.39
row_4
444.4
durian
four
2015-04-15
16:50
2018-04-04 15:55
65100.0
grp_b
row_5
5550.0
five
2015-05-15
17:55
2018-05-05 04:00
1325.81
row_6
fig
six
2015-06-15
2018-06-06 16:11
13.255
row_7
777000.0
grapefruit
seven
19:10
2018-07-07 05:22
row_8
8880000.0
honeydew
eight
2015-08-15
20:20
0.44
By default, values in the body of a table (and their column labels) are automatically aligned. The alignment is governed by the types of values in a column. If you’d like to disable this form of auto-alignment, the auto_align=False option can be taken.
from great_tables import GT, exibbleGT(exibble, rowname_col="row", auto_align=False)
num
char
fctr
date
time
datetime
currency
group
row_1
0.1111
apricot
one
2015-01-15
13:35
2018-01-01 02:22
49.95
grp_a
row_2
2.222
banana
two
2015-02-15
14:40
2018-02-02 14:33
17.95
grp_a
row_3
33.33
coconut
three
2015-03-15
15:45
2018-03-03 03:44
1.39
grp_a
row_4
444.4
durian
four
2015-04-15
16:50
2018-04-04 15:55
65100.0
grp_a
row_5
5550.0
five
2015-05-15
17:55
2018-05-05 04:00
1325.81
grp_b
row_6
fig
six
2015-06-15
2018-06-06 16:11
13.255
grp_b
row_7
777000.0
grapefruit
seven
19:10
2018-07-07 05:22
grp_b
row_8
8880000.0
honeydew
eight
2015-08-15
20:20
0.44
grp_b
What you’ll get from that is center-alignment of all table body values and all column labels. Note that row labels in the the stub are still left-aligned; and auto_align= has no effect on alignment within the table stub.
However which way you generate the initial table object, you can modify it with a huge variety of methods to further customize the presentation. Formatting body cells is commonly done with the family of formatting methods (e.g., fmt_number(), fmt_date(), etc.). The package supports formatting with internationalization (‘i18n’ features) and so locale-aware methods all come with a locale= argument. To avoid having to use that argument repeatedly, the GT() class has its own locale= argument. Setting a locale in that will make it available globally. Here’s an example of how that works in practice when setting locale = "fr" in GT() prior to using formatting methods:
In this example, the fmt_currency(), fmt_scientific(), and fmt_date() methods understand that the locale for this table is "fr" (French), so the appropriate formatting for that locale is apparent in the currency, num, and date columns.