Closed tadhgpearson closed 10 years ago
I slightly edited your PR for the Python code to display nicely.
I would agree with the rationale, e.g. having a main currency code associated with each point of reference could be useful. With the GeoBases
library this is fairly easy though.
from GeoBases import GeoBase
g = GeoBase('ori_por', verbose=False)
c = GeoBase('countries', verbose=False)
country = g.get('ORY', 'country_code') # 'FR'
currency = c.get(country, 'currency_code') # 'EUR'
Still, direct access to the currency may be useful to people using the raw ori_por_public.csv
.
Regarding the process, the ori_por_public.csv
file is generated with optd, and then just copied in this project. So any change to that file should be included in the optd project, and discussed with @denisarnaud :wink:.
So I am going to close this PR here, and suggest you reopen it here.
Helpful to determine which officeID should be used for a given origin when making faring queries.
Currency data taken from https://raw.githubusercontent.com/datasets/country-codes/master/data/country-codes.csv
Code for currency merge below: