In general I'd avoid using any kind of ORM library to work with spatial data in Golang. The query builders aren't made to support more complicated queries using spatial functions. This means you have to fall back to raw sql for certain parts of a query, which results in difficult to read and write code. I had to dive deep into the code of ent & sqlboiler to learn about undocumented behavior in order to write some of the queries in the experiments.
I'd say something like sqlc that generates the boilerplate code for you or raw sql with something like sqlx would be the way to go. There are fewer surprises and there's a lower learning curve when you need to get into a codebase.
- Spatial types in Go https://github.com/paulmach/orb
- Spatial types in Go https://github.com/twpayne/go-geom