Convert to GeoDjango

[jwhitlock]

django-multi-gtfs is using decimal fields for lat/long. We did this because GeoDjango has additional database requirements. However, GeoDjango is the right tool for the job.

Possible Steps:

1. Add GeoDjango to requirements
2. Migrate decimal fields to the correct spatial fields (one or more South migrations)
3. Update installation docs w/ references to external docs

[icotoi]

I am actualy working on this right now. Can you assign it to me?
On Mar 22, 2013 4:59 PM, "John Whitlock" notifications@github.com wrote:

django-multi-gtfs is using decimal fields for lat/long. We did this
because GeoDjango has additional database requirements. However, GeoDjango
is the right tool for the job.

Possible Steps:

1. Add GeoDjango to requirements
2. Migrate decimal fields to the correct spatial fields (one or more South
   migrations)
3. Update installation docs w/ references to external docs

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1
.

[jwhitlock]

Juha from Helenski (not sure if he is on github) approached me about doing this on March 14th. Any chance you are working together?

[icotoi]

Unfortunately I haven't talked to him...

On Friday, March 22, 2013, John Whitlock wrote:

Juha from Helenski (not sure if he is on github) approached me about doing
this on March 14th. Any chance you are working together?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-15302043
.

Ionut Cotoi
Centrul de Creatie Tehnica pentru Tineret

Tel: +4 0721.262.666
Web: http://inventeaza.ro
Facebook: http://facebook.com/inventeazaro
Twitter: http://twitter.com/inventeazaro

[jwhitlock]

I'm going to hold off on assigning until I hear how Juha is coming along. However, I think first code wins - fork and send me a pull request if you've made significant progress.

[juyrjola]

I'm busy working with other stuff right now -- we're making a City Navigator application that uses OpenTripPlanner for route planning and real-time transit info to make predictions on when the user should get to the stop. There's a competition that ends on Sunday, so my hands are full until then. If Ionut wants to implement this meanwhile, I'm happy not to have to do it myself. =)

[jwhitlock]

OK, icotoi, it sounds like this is your ticket for now. I'd have to make you a member of the Tulsa Web Devs to assign the ticket to you, but I think this thread makes it clear you are working on it. If you haven't used it before, you may want to get familiar with GitHub's fork / change / pull request model of contribution:

https://help.github.com/articles/fork-a-repo

[araichev]

Hi folks, any progress on this issue?

[jwhitlock]

Not that I've heard of. I'm planning on knocking out this and a few more issues over the holiday break, so it should be fixed in a couple of weeks.

[araichev]

Sweet as. Thanks to all the multigtfs contributors! The app plays a key part in a project of mine, and i'll continue to post issue reports here when i discover bugs. I hope to contribute code to multigtfs in the future as well.

[icotoi]

Hello, 

Yeah, I said almost 9 months ago that I will implement this, but I got sidetracked to other things. 
I’m sorry for that. 

John, I will also have spare time during the holiday break, and as this is also one of the key components of one of my project, I feel obliged to do it. Talk more about it after Dec 20. 
Is it ok? 

Best,
-- 
Ionut Cotoi
Sent with Airmail

On 12 Dec 2013 at 23:16:27, Alex Raichev (notifications@github.com) wrote:

Sweet as. Thanks to all the multigtfs contributors! The app plays a key part in a project of mine, and i'll continue to post issue reports here when i discover bugs. I hope to contribute code to multigtfs in the future as well.

—
Reply to this email directly or view it on GitHub.

[jwhitlock]

I'm about done with the first working GeoDjango version. Stops and ShapePoints have been converted from lat/long to Points, visible on maps in the admin. I've written South migrations, so you can convert existing data, or you can start with a fresh database if desired. I should get the code pushed this week.

The most painful part will be installing a GeoDjango-ready database. You may want to get started. I recommend PostgreSQL 9.x with PostGIS 2.x extensions. GeoDjango also works with Oracle, Spatialite, and MySQL, but PostgreSQL has all the features. To get myself up to speed with GeoDjango, I read the docs, installed and configured a database (Spatialite, then PostgreSQL later), and worked my way through the tutorial in a new project:

https://docs.djangoproject.com/en/dev/ref/contrib/gis/

I'll have some upgrade / installation instructions with the project, but you may want to go through the tutorial to get a head start on the world of GeoDjango.