New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tell me more about the existing GeoDjango processor... #14

Open

mojodna opened this issue Jun 9, 2015 · 3 comments

Assignees

mojodna commented Jun 9, 2015

What does this currently look like? Should it handle the (database) entities that are created to wrap the input shapefiles and resulting topologies?

(Who knows more about this?)

danrademacher assigned cesandoval

Author

mojodna commented Jun 9, 2015

django-celery is a thing.

Member

danrademacher commented Jun 9, 2015

Here's the repo and branch: https://github.com/localcode/localco.de/tree/to_postgis

cesandoval commented Jun 11, 2015

I will re-structure: https://github.com/localcode/localco.de

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment