All our products have been updated on Sep 26, 2024 with the releases associated to this Sprint 116.

1 Chouette
- 1.1 Display Charts with Daily Service Counts
- 1.2 Statistics and Charts in Import Search
- 1.3 Manage Line Groups
- 1.4 Manage Stop Area Groups
- 1.5 Control code uniqueness in Datasets
- 1.6 Searches
- 1.7 Import GTFS
- 1.8 Workgroup Transport Modes EOL
2 Ara
- 2.1 Collect & Broadcast Situation Publishing Actions into SIRI SX payload
- 2.2 Collect & Broadcast Situation with AllLines affect

Chouette

Display Charts with Daily Service Counts

The user can display charts on Service Counts in a given DataSet.

At any step of the data workflow (after import, in merged or aggregated dataset), the user can create and display statistics on daily service counts.

Statistics and charts are fully configurable by the user. Some examples:

screenshot-chouette-core-test_enroute_mobi-2024_09_30-17_49_46.png

Daily Service Counts on the last 30 days

screenshot-chouette-core-test_enroute_mobi-2024_09_30-17_51_12.png

Daily Service Counts on 10 major lines

Chouette SaaS computes daily service counts for each Journey Pattern. The user can use the raw data and filter targeted Service Counts by:

lines
companies (associated to lines)
network
transport mode
a date period
selected days of week

The user can display charts with these options:

by grouping by
- Line
- Company
- Network
- Line Provider
- Transport Mode
- Route Wayback
- Date
- Date by Week
- Date by Month
- Day of week
only sum/average on daily count (no count).

Statistics and Charts in Import Search

The user can create statistics and charts on imports:

The user can group imports by:

by status
by creator (when Workbench imports are displayed)
by Workbench (when Workgroup imports are displayed)
by date (according to creation time)
by hour of day (according to creation time)
by day of week (according to creation time)

The values can be computed by:

counting imports
summing/averaging import durations

These features around Statistics and Charts will be generalised in all Chouette searches in the next Sprints

Manage Line Groups

The user can create a Line Group. Each Line Group is described by:

a name (mandatory)
a description
one or several lines (mandatory)
a Line Provider (mandatory)
codes

The user can select any lines available in the Workbench scope.

Several future features will include these new Line Groups: NeTEx import/export, Macro to update Line Groups, export or publish lines of a selected Line Groups, export to Ara, etc

Manage Stop Area Groups

The user can create a Stop Area Group. Each Stop Area Group is described by:

a name (mandatory)
a description
one or several Stop areas (mandatory)
a Stop Area Provider (mandatory)
codes

The user can select any Stop Area available in the Workbench scope.

Several future features will include these new Stop Area Groups: NeTEx import/export, Macro to update Stop Area Groups, export to Ara, etc

Control code uniqueness in Datasets

The user can control the code uniqueness on DataSet models:

Route
Journey Pattern
Vehicle Journey
Timetable

Searches

The user can now use the new Search interface to search:

networks
Lines in a dataset
Line routes in a dataset

Import GTFS

The user can import a GTFS file with (very invalid) GTFS Stop Times not associated to a defined GTFS Trip. In the case, the other (valid) GTFS Stop Times are read and imported.

Workgroup Transport Modes EOL

The Transport Modes associated to the Workgroup are no longer defined. The user can control which transport modes are associated in a Workgroup by using dedicated Controls. in a Workgroup by using dedicated Controls.

Ara

Collect & Broadcast Situation Publishing Actions into SIRI SX payload

When a SIRI Situation Exchange payload contains PublishingActions, Ara associates to the Situation the related information.

Ara supports 3 kinds of PublishingActions:

PublishToWebAction
PublishToMobileAction
PublishToDisplayAction

Other kinds of PublishingActions are ignored.

PublishingAction

For any kind of PublishingAction, Ara manages these attributes:

ActionStatus
Description (free string)
Name (free string)
Type (free string)
Value (free string)
Prompt (Translated String)
PublishAtScope
- ScopeType
- Affects
PublicationWindow

All these attributes are optional for Ara when the information is collected.

PublishToWebAction

The additional attributes are supported:

Incidents (optional boolean: true, false or undefined)
HomePage (optional boolean)
Ticker (optional boolean)
n SocialNetwork (free string)

<siri:PublishToWebAction>
  <siri:ActionStatus>published</siri:ActionStatus>
  <siri:Description>Toget vil bytte togmateriell på Dovre. Du må dessverre bytte tog på denne stasjonen.</siri:Description>
  <siri:ActionData>
    <siri:Name>Name</siri:Name>
    <siri:Type>short</siri:Type>
    <siri:Value>dummy</siri:Value>

    <siri:Prompt xml:lang="NO">Toget vil bytte togmateriell på Dovre. Du må
      dessverre bytte tog på denne stasjonen.</siri:Prompt>
    <siri:Prompt xml:lang="EN">You must change trains at Dovre. We apologize for the
      inconvenience.</siri:Prompt>
  </siri:ActionData>

  <siri:PublicationWindow>
    <siri:StartTime>2017-01-01T09:00:00.000Z</siri:StartTime>
    <siri:EndTime>2017-01-01T17:00:00.000Z</siri:EndTime>
  </siri:PublicationWindow>

  <siri:Incidents>true</siri:Incidents>
  <siri:HomePage>true</siri:HomePage>
  <siri:Ticker>false</siri:Ticker>

  <siri:SocialNetwork>facebook.com</siri:SocialNetwork>
  <siri:SocialNetwork>mastodon</siri:SocialNetwork>
</siri:PublishToWebAction>

PublishToMobileAction

The additional attributes are supported:

Incidents (optional boolean)
HomePage (optional boolean)

<siri:PublishToMobileAction>
  <siri:ActionData>
    <siri:Name>dummy</siri:Name>
    <siri:Type>dummy</siri:Type>
    <siri:Value>dummy</siri:Value>

    <siri:Prompt xml:lang="FR">Message specifique pour l'app mobile</siri:Prompt>
    <siri:Prompt xml:lang="EN">Specific message for mobile app</siri:Prompt>
  </siri:ActionData>

  <siri:PublicationWindow>
    <siri:StartTime>2017-01-01T09:00:00.000Z</siri:StartTime>
    <siri:EndTime>2017-01-01T17:00:00.000Z</siri:EndTime>
  </siri:PublicationWindow>

  <siri:Incidents>true</siri:Incidents>
  <siri:HomePage>false</siri:HomePage>
</siri:PublishToMobileAction>

PublishToDisplayAction

The additional attributes are supported:

OnPlace (optional boolean)
OnBoard (optional boolean)

<siri:PublishToDisplayAction>
  <siri:ActionData>
    <siri:Name>dummy</siri:Name>
    <siri:Type>dummy</siri:Type>
    <siri:Value>dummy</siri:Value>

    <siri:Prompt xml:lang="FR">Afficher sur les ecrans de la Ligne 1</siri:Prompt>
    <siri:Prompt xml:lang="EN">Displayed in Line 1</siri:Prompt>

    <siri:PublishAtScope>
      <siri:ScopeType>line</siri:ScopeType>

      <siri:Affects>
        <!-- likes other Affects structure -->
        <siri:Networks>
          <siri:AffectedNetwork>
            <siri:AffectedLine>
              <siri:LineRef>LineID1</siri:LineRef>
            </siri:AffectedLine>
          </siri:AffectedNetwork>
        </siri:Networks>
      </siri:Affects>
    </siri:PublishAtScope>
  </siri:ActionData>

  <siri:PublicationWindow>
    <siri:StartTime>2017-01-01T09:00:00.000Z</siri:StartTime>
    <siri:EndTime>2017-01-01T17:00:00.000Z</siri:EndTime>
  </siri:PublicationWindow>

  <siri:OnPlace>true</siri:OnPlace>
  <siri:OnBoard>true</siri:OnBoard>
</siri:PublishToDisplayAction>

Collect & Broadcast Situation with AllLines affect

Ara can handle Situations which all affected lines of a network by using this SIRI SX payload: