The transfer.txt specificity ranking is ambiguous

The specification do not distinguish between Stop and Station, I believe the Stop is more specific than a Station.

Also, in some cases the different combinations result in the same ranking. Consider these two examples:

*Case A*

1. Transfer from (Stop) to (Route, Stop)
2. Transfer from (Route, Stop) to( Stop)

*Case B*
1. Transfer from (Trip, Stop) to (Route, Stop)
2. Transfer from (Route, Stop) and (Trip, Stop)

In both these cases the specificity ranking is the same. My suggestion is to let the **From** transfer point take precedence if the ranking is the same.

When implementing this the following ranking sudo code would work:

**Ranking Transfer Point**

- 0 : Station
- 1 : Stop
- 2 : Route
- 3 : Trip

**Ranking Transfer**
`[from transfer point] x 11 + [to transfer point] x 10`

In case A, transfer 1 will have 31 `1x11 + 2x10` in ranking and transfer 2 will have 32 `2x11 + 1x10` -> Case A.2 will be used.

This problem is not limited to the case A and B above.