Hi all, I am developing an application with django that requires some geographical data, both some points and tracks. I have some questions regarding the model design.
I know Postgres and MySQL have geographic extensions. I have used MySQL's in the past but now I am mostly interested in Postgres. Should I design using those db extension? They provide some handy geographical calculations but maybe those should be better done in the views, not in the db. But, I guess, the indexing in the db will be optimized for geo data, which can improve the db performance. Also, using those extensions, points and tracks can all be defined as the same geo type column, which will allow me to store both points and tracks (list of points) in one single table. A workaround to avoid using geo specific db extensions but keeping data in one single table can be pickling the list of points and storing it, but I don't have much practical experience. My application will be using Google Maps API. The API supports a method of encoding point arrays which convert a track info into an ascii sequence. I may be storing this encoded data in a text field in the db. One more: Is the best way of defining a geographical point in a model defining lat / lng fields separately? Postgres has a Point data type. Can I use it in my models? I feel like avoiding db specific extensions and going with the basic model types would be the best. And ideas and experiences to share? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
