Foreward

This is a WIP.

Devices

I like doing things manually as they just work. The steps are as follows:

1. scrcpy into the ATV
2. disable RGC and PD daemons
3. remove existing pogo
4. install atlas
5. install correct pogo version for atlas
6. setup atlas on ATV and enable on website

Moving data to RDM

RDM/Atlas is fast enough to not worry about bringing over gyms and pokestops. Just take the area of interest, put into RdmTools and bootstrap a route for the area. Then init away.

Spawnpoints are another matter, if you have them in MAD not need to redo an init for them in RDM. Do note that MAD stores data in timestamps and RMD works in seconds. So I needed to move my spawnpoints from MAD to RDM. So I opened up MS Access and linked in the MAD trs_spawn table and RDM spawnpoints table. I then used this SQL query to move the data from MAD to RDM: INSERT INTO [RDM-spawnpoint] ( id, lat, lon, despawn_sec ) SELECT [MAD-trs_spawn].spawnpoint, [MAD-trs_spawn].latitude, [MAD-trs_spawn].longitude, iif([MAD-trs_spawn].calc_endminsec > '',left([MAD-trs_spawn].calc_endminsec,2)*60 + right([MAD-trs_spawn].calc_endminsec,2) ,null) AS end_time FROM [MAD-trs_spawn]; Modify as you see fit to make it work.

Doing routes is rough even with RdmTools, so why not use MAD. Shut down your MAD. Go ahead and open the following file from the root folder of MAD: ./mapadroid/utils/MappingManager.py. In this file you can set radiuses for generating routes by editing the appropriate data at the start of the file. Restart MAD and re-calc routes with the specified radius. View the route data and paste this into RDM for the instance.