serializations for geodjango geometry about django-rest-framework

[tomchristie]

Is there any chance you'd be able to provide a simple test for the current and the expected behavior?
(Ideally fork the project and add it to the existing tests.)
I'd be very happy to see this fixed, but it'll likely stay low priority otherwise.

[dmeehan]

What would need to happen in order to add support for GEOSGeometry fields? I'm new to django-rest-framework, but I'm interested in taking a look a how to implement. Tastypie has built support for this by creating a GeometryApiField which is a subclass of their ApiField. (https://github.com/philipn/django-tastypie/blob/gis/tastypie/contrib/gis/resources.py). What would be the equivalent for DRF?

[tomchristie]

@dmeehan - The same thing really. Override WriteableField, and implement appropriate to_native and from_native methods.

[dmeehan]

I've started a project that will act as a GeoDjango enabled plugin to DRF.

https://github.com/dmeehan/django-rest-framework-gis

I've written a GeometryField implementation of WritableField and will be working to implement additional features.

@tomchristie, I'd like to get your insight on the best way to tackle this issue:

openwisp/django-rest-framework-gis#2

I'm thinking perhaps as a renderer? I'm still trying to figure out how all the pieces of DRF fit together to produce the output.

[tomchristie]

Given https://github.com/dmeehan/django-rest-framework-gis and https://github.com/mjumbewu/django-rest-framework-gis, I'm going to close this ticket for now. My preference is for Geo integration to be a third-party concern. That might change in the future, but on balance it seems like the best option right now.