Accessing lat/lon from Transects

[profseth]

Transects created with the GEOTRACES package display a table with stations, dates, lats, and lons (example pictured below). But it's not clear to me how one can access that information.

Cruise GA02
┌─────────┬─────────────────────┬──────────┬─────────┐
│ Station │                Date │      Lat │     Lon │
├─────────┼─────────────────────┼──────────┼─────────┤
│     001 │ 2011-03-05T19:28:00 │ -49.5472 │ 307.312 │
│     002 │ 2010-05-02T19:36:57 │  64.0001 │  325.75 │
│     002 │ 2011-03-06T23:17:05 │ -48.8942 │ 311.265 │
│     003 │ 2011-03-08T01:17:59 │   -46.92 │   312.8 │
│     003 │ 2010-05-03T21:30:00 │  62.3451 │ 324.002 │
│     004 │ 2011-03-09T01:31:59 │ -44.7068 │ 314.464 │
│     005 │ 2011-03-10T00:58:29 │ -42.3713 │ 315.974 │
│     005 │ 2010-05-04T15:39:59 │  60.4273 │  322.09 │
│     006 │ 2010-05-05T11:05:07 │  58.6022 │ 320.293 │
│     006 │ 2011-03-11T03:14:21 │ -39.9632 │ 317.583 │
│     007 │ 2011-03-12T05:31:52 │ -37.8398 │ 318.869 │
│     008 │ 2011-03-13T11:25:00 │ -35.0088 │ 320.563 │
│     008 │ 2010-05-07T19:50:09 │  54.0634 │ 314.165 │
│     009 │ 2011-03-14T17:22:26 │ -32.0894 │ 322.541 │
│     009 │ 2010-05-09T08:38:29 │  51.8209 │ 314.268 │
│     010 │ 2010-05-10T10:40:29 │   49.722 │ 317.553 │
│    ⋮    │          ⋮          │    ⋮     │    ⋮    │
└─────────┴─────────────────────┴──────────┴─────────┘
                                       39 rows omitted

[briochemc]

Agreed. If I find the time, I will try and revamp the API to focus on observations only when GEOTRACES IDP21 comes out (in less than 10 days). The idea would be that observations, which returns a table, would be manipulated directly to extract transects using the DataFrames framework, instead of the current API with all the nested structs.