What are the benefits of using GeoPtProperty() in Google App Engine models?

Question

Google Workspace

I'm using Google App Engine for a map site. Found out that in their database it is possible to store coordinates in the form of GeoPtProperty () type. Thought it would be right. No wonder they created this type. But in the course of work, I did not notice any advantage of using this type, instead of two separate fields: latitude and longitude. Anyway, when sending to template, you have to pull two coordinates from this field. If you think it's easier to select directly from the base by location, then no - it's easier with separately stored coordinates, because the > and < operators for the GeoPtProperty () field only work for the first coordinate - latitude, so the selection does not work as we would like . Maybe someone knows why I started using this type?