News for hackers. Stuff that matters.
Re:Parsing city of origin and destination city from a string by seanhunter on Monday July 06, 2020 @10:17AM (#23748113)
Rather than as a general parsing problem, isn't it possible to reformulate this in a different way that is much easier to solve by using the fact that these are strings describing flights we want to get destination and sources from?

So what you could do is take a general database of all flights (which is structured data and easy to work with) and then the problem is to label the unstructured input data with the probability it relates to a particular source, destination pair.

For example, there are no flights from York (lovely though York is) to Venice, so that mistake isn't one such a model could even make. Whereas there are a lot of flights to and from New York (including to Venice), and since that number is large it's a much higher probability labeling than some others.

Re:Parsing city of origin and destination city from a string by talliedthoughts on Monday July 06, 2020 @11:17AM (#23748814)
This would help but it's not foolproof, since there is no way to be sure the strings refer only to direct flights between the two locations. Flight deals often involve transfers and/or complicated routings.
Re:Parsing city of origin and destination city from a string by robk on Monday July 06, 2020 @01:56PM (#23750669)
Doesn't have to be direct. It would at least show up as a possible route. Bonus if you score by airport size (where it relates to city not country of course)