GitXplorerGitXplorer
m

talk-ggextenders-ggtime

public
0 stars
0 forks
0 issues

Commits

List of commits on branch main.
Unverified
7cbfa8a37239bfcbb0db2f419ebce44e8842545b

Fix structure layout

mmitchelloharawild committed 4 days ago
Verified
758ef0b42733eb51b5d146af73838e7f15550309

Merge pull request #1 from mitchelloharawild/cynthiahqy-patch-1

mmitchelloharawild committed 4 days ago
Verified
927bdbbc945a75877125f739e99ad62c7745c08d

Update README.md

ccynthiahqy committed 4 days ago
Unverified
68f7f2693b99c3191aa51b1fc664ea2fcb88c23c

Add README

mmitchelloharawild committed 4 days ago
Unverified
63d13f93b31efd521a43ca89700016929ec9ba54

Add talk skeleton

mmitchelloharawild committed 4 days ago

README

The README file for this repository.

Designing ggtime: a grammar of temporal graphics

Slides and notes for an discussion presentation to the ggextenders group (XX February 2025).

Abstract

There are many visual idioms in place for plotting time series data, however little work has been done to express them as elements of a unified grammar of temporal graphics. The ggtime package extends ggplot2 with new grammatical elements for presenting temporal patterns. These elements can be composed together to create familiar visual idioms, and also recombined in new ways to create new informative plots. Temporal visualisation requires special handling to accomodate calendrical quirks (similar to spatial, graph, and uncertainty visualisation). In this ggextenders talk I will introduce some design-stage development of the ggtime package, and pose some technical discussion questions about engineering and designing ggplot2 extensions.

Structure

  • Background (time as a special dimension, relate mixtime/ggtime to distributional/ggdist)

  • Existing work producing visual idioms (feasts, sugrrants, gravitas)

  • Design philosophy: use grammar layers to extend time independently of other layers (ggtime ❤️ ggdist)

  • Design decision discussions

    Start with the question prompt, along with some related work and necessary info.

    • Design decision 1: implementation of coord_calender()
    • Design decision 2: geom_time_line() or position_civil()/position_absolute() for civil/absolute time
    • Design decision 3: circular time as a position? data pre-processing

Format

1 hour total (including discussion)