as @srnet stated in post 43 it is
A good idea to have a full picture of the scope of a project and what the intended application really is.
otherwise sooner or later in the project new requirements appear which cannot be satisfied with the hardware/software implemented so far
a few questions
- how often is it planned to upload data (including GPS) to LoRaWAN
- how much data (bytes)
- what is the area being tracked by GPS (factory, farm, town, country, global, etc)
- what positional accuracy is required
for example in the river monitoring project I uploaded approximately 10 bytes of data every 10 minutes to LoRaWAN
noted that there is a version of the TTGO T-Beam with ESP32, LoRa, GPS, OLED, BME280 (temperature, pressure, humidity sensor), etc etc