This is one example where an idea sounds simple, but in fact it is not. There are many tasks that you need to solve, some of which have already been discussed.
1) How to simulate an office. This should be done so that it is easy for you to model, but the file is small. It should be in a format that your path-finding algorithm can understand. This means that when designing the path, you will make changes to the data.
2) Search / enter location. Done by hardware (gps will not clip it), or the user says where they are. It can be done with NFC and tags located in the office, and not an ideal solution, tags should be visible. The user can enter their location, but they may be lost and do not know where they are.
3). As the data is presented, you can write a magical 3D application showing the mission of impossible building layout. It will be six months of work in it! Remember that your map is in 3D; roadmaps tend to be 2D. (with some volatiles ...)
4) progress tracking. The application really needs to know how you do it, if you leave the route, it will tell you to return. This will again be difficult to achieve indoors. Tracking tracking is one of the areas in which PND (Personal Navigation Device) operates, as it really enhances user confidence in the software.
Working at TomTom, I can say that you can be in this for years.
How is this a collage project, can I offer a simpler project?
Do it with a 2D map, a simple map-based grid that looks a bit like a classic mouse in a maze problem. Enter A * to find the path. After that, you can, if you have time, extend it for your original plan.
The book I found very well in the past is "Programming a Game AI with an Example." ISBN 1-55622-078-2. Chapter 8 talks about finding paths and has a very nice role in *.
Good luck. :)
Richard E Collins
source share