GPS Slow Update Rate

Our team has tried to use a GPS in the past and learned that its slow update rates don’t result in a usable device. It updates so slow that it doesn’t work good enough for it to be used in our autonomous. We currently use Blocky but will be switching to c++ soon. We want to figure out how to utilize the GPS in a way that we can use it in auton and have it update fast enough to make it work. In our code we have 6 motors that we use singularly (because there is no 6 motor drivetrain in blocky) and we have a GPS set up. I was wondering if it works better as a drivetrain element and what teams have in their code to successfully use it. @jpearman Have you used the GPS to make a auton before. I know you have said in multiple different topics that it updates fast. I was wondering if there is a reason that it won’t update fast enough? Also for all successful teams that use a GPS on their autons. What do you have in your code to use it and did you have any fails? I know this topic has been brought up a lot but I think it needs a refreshed page.