Skip to content

jupcan/osm-gps

Repository files navigation

uclm

a3 group intelligent systems lab project

designment and developement of an agent program to find the optimal route for a vehicle that circulates through a set of places of a town using data from openstreetmap - uclm computer science | osm graphml data

installation

whole project developed using python3

sudo apt-get install python3.6

using lxml library to represent the xml files data in a tree an then generate our own internal representation of it

sudo apt-get install python3-lxml

and also sorted containers one to use some of the data structures it offers such as ordered dictionaries

python3 -m pip install sortedcontainers

generation of a internal representation of a graph with geographical data from osm given a file in format grahml

below we are showing a command line output example for the 3 aforementioned methods:

file: ciudad real
ciudad real.graphml.xml
nodes: 796725819,765309509,827212358
True
[('38.9845189', '-3.9145536')]
{('796725819', '764039286'): ('Avenida de Europa', '4.148'),
 ('796725819', '797147422'): ('Calle Santa María de Alarcos', '9.129')}
0.0005040168762207031 seconds
True
[('38.9849254', '-3.9246998')]
{('765309509', '803292210'): ('Calle de la Mata', '38.067')}
0.0003075599670410156 seconds
True
[('38.9828974', '-3.9395137')]
{('827212358', '827212360'): ('Calle Goya', '47.442'),
 ('827212358', '827212476'): ('Calle Atalaya', '42.912')}
0.0003237724304199219 seconds

definition of the problem and implementation of the frontier

  • creation and organization of the code in more detailed classes: state, state space, frontier, treeNode and problem
  • use of new technologies such as .json and .md5 for some inputs/outputs of certain classes

given an json file used as input to initialize our problem class:

{
	"graphlmfile": "Ciudad Real/data/anchuras.graphml",
	"IntSt":{
			"node": "4331489739",
			"listNodes":["4331489528","4331489668","4331489711","4762868815","4928063625"],
			"id": "f4b616551965fb586e608397c308bf0f"
	}
}

we create a stateSpace class instance with the given path and read all the information stored in the graphml file so as to be able to compute all the operations we already were able to do in task1. we also create a state class instance with all the other information (node, listNodes, id) to have a start point and be able to make some other new operations:

  • successors(state): [(acc1,NewState1,costAct1), ... ,(accM,NewStateM,costActM)]; accM = string like 'I am in id origin and I go to id destionation'. NewStateM = adjacent node. costActM = street length
  • belongNode(state): true or false if it belongs or not to state space
  • creation of frontier as well as insertion of treeNodes objects, elimination and checking emptiness on it

below we are showing a command line output example for the 3 aforementioned methods:

json file: example
example.json
data/anchuras.graphml.xml
[(127.1360111900787, <treeNode.treeNode object at 0x7f33cc1c8fd0>), (591.7378136374725, <treeNode.treeNode object at 0x7f33cc1d9e80>), (612.2393770939552, <treeNode.treeNode object at 0x7f33cc1d9e10>)]
[(591.7378136374725, <treeNode.treeNode object at 0x7f33cc1d9e80>), (612.2393770939552, <treeNode.treeNode object at 0x7f33cc1d9e10>)]
True
4331489738 state md5: 331b41c249f9d392954ce4a36df65ca7
4331489740 state md5: 229da16d1c640e1e81747a47bdd716fa
4331489763 state md5: 6d7014c2db65e030d3ae0af84286edfe
[("I'm in 4331489739 and I go to 4331489738", "(4331489738, ['4331489528', '4331489668', '4331489711', '4762868815', '4928063625'])", '48.137'), ("I'm in 4331489739 and I go to 4331489740", "(4331489740, ['4331489528', '4331489668', '4331489711', '4762868815', '4928063625'])", '108.841'), ("I'm in 4331489739 and I go to 4331489763", "(4331489763, ['4331489528', '4331489668', '4331489711', '4762868815', '4928063625'])", '63.11')]

that is, for the initial state we look for its succesors updating each time the state by checking if the node im at the moment is in the state space and removing it from the list if so. also generating the new md5 representation of each state and printing the frontier of the problem once inserting three treeNode object examples and removing one of them.

basic version of the search algorithms

  • breath-first search
  • depth-first search, depth-limited search and iterative deepening dearch
  • uniform cost

we need all classes defined in task2 and some input values asked to the user to generate a txt file containing a sequence of states corresponding to the path solution if exists for each of the algorithms mentioned before. we have also implemented a visited list to be able to run all the algorithms with pruning which makes them much more efficient and fast.

here we have a possible inputs combination to our code and its corresponding output file

json file: example
example.json
0: breath-first search
1: depth-first search
2: depth-limited search
3: iterative deepening search
4: uniform cost search
strategy: 0
pruning(y/n): y
breath-first search w/ pruning
depth: 999
data/anchuras.graphml.xml
cost: 690.552, depth: 13, spatialcxty: 183, temporalcxty: 0.016545s
check out.txt for more info
output.txt
cost: 690.552, depth: 13, spatialcxty: 183, temporalcxty: 0.016545s
goal node: <treeNode.treeNode object at 0x7fc831f3bd68> - 4331489668
time and date: 19:39:02-19/11/2018

["I'm in 4331489739 and I go to 4331489738 c/Barrio Nuevo",
 "I'm in 4331489738 and I go to 4331489532 c/Barrio Nuevo",
 "I'm in 4331489532 and I go to 0946409139 c/sinNombre",
 "I'm in 0946409139 and I go to 4331489528 c/sinNombre",
 "I'm in 4331489528 and I go to 4331489718 c/Calle Arroyo",
 "I'm in 4331489718 and I go to 4331489716 c/Calle Arroyo",
 "I'm in 4331489716 and I go to 4331489709 c/Plaza España",
 "I'm in 4331489709 and I go to 4331489549 c/Calle Amirola",
 "I'm in 4331489549 and I go to 4331489550 c/Calle José María del Moral",
 "I'm in 4331489550 and I go to 4331489692 c/Calle José María del Moral",
 "I'm in 4331489692 and I go to 4331489662 c/Calle Periodista Antonio Herrero",
 "I'm in 4331489662 and I go to 4331489668 c/Calle Periodista Antonio Herrero"]

the generated file includes the cost of the solution, the depth where it is found and the time spent to reach it alongside all the actions path printed in order; i go from node1 to node2 and so on until we have passed throught all the desired nodes and reached the goal applying the given algorithm, if no solution is found an error is printed instead both on console and file.

addition of greedy and a* searches using as heuristic for a concrete state: h(state) = minimum distance between the osm node of current state and any node in the list of nodes to be traveled (computed by means of straight line distance in meters).

as an added feature, we have also generated a sequence of images representing the solution, that is, for a given algorithm solution we are creating a gpx file, representing it as a track and adding as waypoints the nodes we have to go through, that can be shown graphically in multiple track drawing websites, different software or uploaded directly to openstreetmap as stated in osm wiki. finally we are also generating a locally stored svg image as a way to see a more human friendly representation of the solution, it is computed converting the previous gps file with gpx2svg os script, shoutout to its creator.

sol on gpx visualizer a* search algorithm output as gpx for problema.json file shown in gpx visualizer website

task5

as a final task, we have implemented the use of a new heuristic (h0) better than the one we have had until now (h1)

given a state (x, [a, b, c]):

by adding another minimum distance with current node the first one to be visited, we obtain a bigger heuristic closer to the real cost of the path thus a better one to consider, we can appreciate a spacial complexity smaller when running the program.

delivered final documentation