The user can manage Shapes in a dedicated referential (like stop areas or lines). Shapes are not included into each data set (with Routes, Journey Patterns, etc) but can exist separately.
Base Shape Management
The user can list the Shapes present into the Shape Referential, by default, only the Shapes associated to its Workbench.
Each Shape contains:
an oriented geometry
an optional name
codes of several kinds (like “gtfs”, “kml”, etc) to identify the Shape in several contexts
remaining references (to be associated automatically with data set resources)
Associate shapes with data set resources
Each Shape contains be associated to one or more data set resources like Journey Patterns, and next, Routes, Lines and Vehicle Journeys.
The user can associate a given Journey Pattern to one of the Shapes:
The user can create a sticky association. In this case, the Shape will keep a reference (by checksum or by identifier) to provide an automatic association with the “same” resource later.
When any Data Set resource associated to a Shape is used in merged or aggregated data sets, the Shape is no longer editable. The user can duplicate this Shape (and editable associations) to make a new version.
The user can start an automatic shape association operation in a data set:
According to the chosen options, Chouette SaaS will perform an automatic search of the best shape for each data set resource (like Journey Patterns).
To match shapes with resources, Chouette SaaS provides several algorithms:
Idea proposal: The user could setup the KML import to generate a Shape reference according to the KML content. For example, the KML import can create a JourneyPattern id reference according to a KML LineString attribute (like id or targetId), directly or via a (simple) value transformation.