'Personal Data' means any information relating to an identified or identifiable natural person ('data subject')
The route is "any information". If it is "relating to an identified or identifiable natural person ('data subject')" then it is Personal Data, if it doesn't, it isn't.
You say in your comment "We store the routes a user saves" - if you store enough information about that user to identify a natural person (like a username, a real name, an IP address etc. or a combination of data [including the routes they store]) then the route is part of that Data Subject's Personal Data.
In almost all cases you will be storing enough data to identify a natural person - they only time you wouldn't is if the 'user' was not a natural person (e.g. a corporation or a group of natural persons) and you didn't store data that would allow the actual natural persons who were making the inquiries to be identified. In this case, its not the route data that's 'Personal' its the fact that the person requested that route.
'Personal Data' is not necessarily personal - it is data that is linked to a person. The actual contents of the data may have nothing to do with the person: its the link that makes it 'Personal Data'. It doesn't matter if the data can identify the Data Subject (e.g the weather in Sydney can't identify anyone) but the linking of that data to a (or more than one) Data Subject makes it 'Personal Data'.