Indexing a Geoposition field

[khlumzeemee]

Hi,
This is more a question than an issue. I use geoposition to store POI. Then I want to find the POI located near the user. I want to use Postgres earthdistance and cube extensions.
I found this module on github which manages the two:
https://github.com/jneight/django-earthdistance

However for performance reasons it is highly recommended to create an index on the lat and long fields, which I cannot do because the geoposition field is a comma separated string value.

Is there an easy work-around? A hook to save the lat and long to distinct indexable fields on creation / modification?

Or put another way, is it possible to specify the way we want the data to be saved in the database, as two separate decimal fields or as a single comma separated string? That would be a great abstraction!

[asennoussi]

Did you get any workaround yet ?

[khlumzeemee]

Unfortunately no, the current work-around it to not use django-geoposition and generate the two long and lat fields separately.