Fixture for HelloGo fares and NTFS fares v2

[woshilapin]

This is a first version of a fixture from HelloGo fares to NTFS fares v2. A few edge cases will be added in the future like:

• What if the line is not defined for a ticket? A few possible errors can happen:
  • line_id doesn't exist in NTFS
  • contentValidityCondition doesn't exist
  • TriggerObjectRef{ref} doesn't exist in ServiceFrame/Network
• What if the input NTFS is prefixed?

[papailio]

We've already discussed about the fixtures, but I'm sharing my feedback here anyway :)
In the input xml files:

• each DistanceMatrix should be associated with a different line (so that, in the output, the same origin-destination tickets specified over different lines are distinguishable)
• the lines referenced in the DistanceMatrix should be defined in the ServiceFrame (after the Network)
• I think that two ScheduledPoints should have different associated ProjectedPoints (even though technically this might be correct).

As for the advanced future test cases that you suggest, if the line for a ticket is not defined, then no ticket (with no associated ticket use) is created.
The NTFS is supposed to be prefixed, in which case the object ids should be considered without the prefix. Otherwise (if no prefix is present), the object ids are considered as is.

[woshilapin]

I've updated a few things:

• Add the <lines> section in the <ServiceFrame> so the <Network> section can do references to <Line> objects.
• Add another <Line> named T42 (both in NTFS and in Netex files) so each DistanceMatrix can refer to a different one
• Change all <ScheduledStopPoint> to make them represent one and only one Stop Area (I did one exception with syn:sp:different:stop:area in the file2.xml.zip to test when multiple ProjectedPointRef match multiple Stop Area)
• One consequence of the above changes is the apparition of one OD on 2 different lines (mat:16 on B42 and mat:21 on T42)