List countries a route traverses and add corresponding duration within

[TimMcCauley]

No description provided.

[rabidllama]

If we want to do this, then it would probably need to be a case where the border crossing feature gets extended so that rather then only ways that cross borders having country info stored, every way has country info added to the extended storage. This probably shouldn't require much extra time for processing as each way is checked anyway, the difference would be in terms of the amount of data being stored

[aoles]

the difference would be in terms of the amount of data being stored

One byte per edge should be enough to cover the IDs we use (up to 236).

[nilsnolde]

Right. I'd be in favor of this functionality. But it'd be nicer if country info would always be returned, not only when a route crosses a border. Always meaning, if the option to list countries is set.

[nilsnolde]

And if we want to do this, please re-open and include a fix for #195. I really think API users should not need to implement client-side mappings from our arbitrary ID's to ISO country codes. However, let's not alter the storage itself, but rather add a mapping.

[TimMcCauley]

@aoles sounds like a plan!
@sfendrich feel free to take this one on as a first task :-)

[rabidllama]

@nilsnolde the text values for countries has been reopened and @takb is looking into it

[MichaelsJP]

The current plan is to use the BordersGraphStorageBuilder.java and add two more shorts to every edge indicating, at a maximum of two, the countries it traverses. The countries will internally be represented by our integer country mapping consisting of max. 3 integers. This process of getting the edge countries will just be added to the normal borders preparation once a new graph is calculated and therefore be stored in the same external storage. At least one country will always be stored and can be accessed from within the ExtraInfoProcessor.java to be added as extra information to any request made.

[rabidllama]

Added in Release 5.0.2