Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature] Export Quays for NeTEx France #520

Merged
merged 1 commit into from
Jan 28, 2020

Conversation

woshilapin
Copy link
Contributor

No description provided.

Copy link
Contributor

@prhod prhod left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good for me at functional level

@@ -10,7 +10,7 @@ The fare data expected at the input of the connector comes in the form of XML fi

The supported fare structures depend on origin-destination (OD) stop pairs in two ways:
- the ticket price between an origin and a destination is directly specified (*DirectPriceMatrix*)
- the price for a fare distance unit is specified, as well as the fare distance between an origin and a destination (*UnitPrice* & *DirectMatrix*). The ticket price between the origin and destination stops is computed by multiplying the fare distance by the fare distance unit. In this case, one and only one frame of type *UnitPrice* is expected: if none or more than two are provided, the file is considered invalid and should be discarded.
- the price for a fare distance unit is specified, as well as the fare distance between an origin and a destination (*UnitPrice* & *DistanceMatrix*). The ticket price between the origin and destination stops is computed by multiplying the fare distance by the fare distance unit. In this case, one and only one frame of type *UnitPrice* is expected: if none or more than two are provided, the file is considered invalid and should be discarded.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

strange to have this here, but thx for the fix 👍

@woshilapin woshilapin force-pushed the netex-france-stop-points branch 8 times, most recently from d459ab9 to c8db079 Compare January 27, 2020 12:43
// FIXME: String 'EPSG:4326' is failing at runtime (string below is equivalent but works)
let from = "+proj=longlat +datum=WGS84 +no_defs"; // See https://epsg.io/4326
let to = "EPSG:2154";
let converter = Proj::new_known_crs(from, to, None).ok_or_else(|| {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will we have a performance issue if we instantiate proj for each stop point?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, I should be able to create a field of StopPointExporter and initialize it at the construction... I'll rework that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 6039817.

@woshilapin woshilapin force-pushed the netex-france-stop-points branch from 7628b7b to f1006a1 Compare January 27, 2020 15:34
@datanel datanel merged commit 3ba706d into hove-io:master Jan 28, 2020
@woshilapin woshilapin deleted the netex-france-stop-points branch January 28, 2020 13:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants