Note that there are some explanatory texts on larger screens.

plurals
  1. PONavigation algorithm implementation in j2me for mobile devices
    text
    copied!<p>As part of my college project I'm developing a customized mobile navigation application. I'm using J2ME.</p> <p>By customized I mean the application can be used in places only where the user wishes to use them. Now, the 'customized' area is my college premises. So if any student needs directions to reach his classroom or block he will be guided to that location. </p> <p>I cannot use the google maps because the campus is not totally covered in them. So i take coordinates of all the blocks and roads and store in my landmarkstore and create a mini map of coordinates. </p> <p>Now the real problem is 'How do i implement the navigation part of the application'? This is what is my current plan of action for the implementation.</p> <p>I decided to use the Dijkstra's algorithm to find the shortest path. I'll just add the current position of the user into the graph and call it the source. The cost-adjacency matrix will be populated within the program.</p> <p>Now the algorithm works and the shortest path is generated with the first instruction saying eg. Move 100mts due north.</p> <p>The user proceeds as such but makes a mistake and goes in the wrong direction . How do I constantly check if the user is proceeding in the right direction? If i do check with his position every 10seconds and alert him if he is on the wrong course,(I dont know how to do this either! ie, checking if he is on the right course) and generate new directions again won't I be slowing the application down?</p> <p>Is there a better way of implementing it?</p> <p>PS: Please help me with how the coordinates must be stored in my database(landmarkstore) Should i store the coordinates for every small distance(eg. 5mts) or should i use a longer distance so that the number of nodes in the graph is reduced and the algorithm works faster.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload