Everybody is good, directing design a route how to design,
Basic information about this format, [route] + [POI] + [a bunch of latitude and longitude] + [POI] + [a bunch of latitude and longitude], POI series is the point of interest, said to a JAVA object, latitude and longitude is a two-dimensional array, the length is longer

Consider two ideas,
1 put a POI collection, a collection route, and the format of the route, POI, route deposit foreign keys; Benefit is to be updated separately POI, there is no sync problem, a little bit the idea of a relational database, is don't hesitate to do so,
2 the POI information directly in to a route in the document, embedded in, benefit is low frequency data not updated frequently, it'll take a lot effort to harm is synchronous information is, with the appropriate redundancy to improve performance,

Ask a digression, a string of track, how to save the object directly in cash or array, can not save the path between two points, can be called directly map to navigate, but in the case of the road, need to write their own navigation engine,