ProjectNeura
Get GPS Data from HotSpot Phone Using Phyphox
Description of Requested Feature For LEADS implementation with a WiFi Hotspot device being a mobile smartphone, it would make sense to have the option of retrieving GPS data from the mobile phone as a cost saving to implementing a duplicate hardware solution connected directly to the LEADS computer.
Description of Solution Ideally, the solution would be an app on the mobile smartphone that accesses the phone's GPS sensor and logs the GPS data to a cloud server that is accessible remotely. However, there is an app, phyphox - by RWTH Aachen University that does most of the "heavy lifting" and provides a remote access feature that is designed around a webserver running on the phone so all functions are available as documents below the devices URL and can be exploited by writing a Python script to access the live GPS data needed.
Alternatives Considered The alternative to retrieving GPS data from the mobile smartphone is to implement a separate hardware solution connected directly to the LEADS computer.
Additional context @ATATC has documented issues with this method in #39 citing the significant "Know How" and coding expertise required to pull of writing an app from scratch. However there might be some value here for entry-level programmers to develop some experience writing some code to retrieve GPS data from phyphox by enabling the remote access feature and controlling phyphox through a REST API.
@ATATC please review for feasibility. There's other built-in sensors (like the accelerometer) on a smartphone that we could possibly take advantage of in a similar fashion.
This solution is feasible, but it will destroy the integrity of the system. It is good as a transitional solution, but it will not be our ultimate solution. Using Restful API is a lazy choice. This too-high-level protocol is not suitable for communication between non-Web programs, especially embedded programs. It will waste considerable network bandwidth and is hard to debug.
It also leaves many potential loopholes because it involves external network traffic although we do not necessarily care about that.
I agree with all of the above. This is just a proposal for a temporary solution - if we can't afford the BW and computing resources (RPi4) costs, we don't do it. Your recent #39 post of the prepackaged VK-162 G-Mouse USB GPS Dongle for $24.99 would alleviate having to implement this solution.
That's exactly what I was thinking - something for either @HaydenHour or @fz20181223luogu to cut their teeth on with Python.
This is definitely not a task for newbies, but it is possible if they take the time. I can have a quick kick-off and they can do it during the summer break.
I can handle the integration between this feature and our core codes. They'll just have to implement the part that gets data through Restful API.
#72 is obviously a milestone that comes before this. They'll need the knowledge in #72 to realize this new feature.
Then it might make sense to have @HaydenHour working on this since he is working on #72 extracting GPS data from GPX.
Due to considerations regarding the construction period, this matter has been abandoned.