Skip to content
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.

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

Object Persistance #2

Open
Mappboy opened this issue Jun 10, 2016 · 2 comments
Open

Object Persistance #2

Mappboy opened this issue Jun 10, 2016 · 2 comments

Comments

@Mappboy
Copy link
Contributor

Mappboy commented Jun 10, 2016

Currently writing directly out to json. I am thinking of writing to a postgis table. I have tentatively added a pipeline for writing to postgis but would still need to write serializers for our item. Any other ideas ?

@keithamoss
Copy link
Contributor

Write to PostgreSQL and store it as a single JSON blob per release for now? Then use magic JSON querying to do what we want with it after.

Only thing I'd store separately is the URL that was crawled. Then we can go back and get info about the Minister when we start to care about that.

@Mappboy
Copy link
Contributor Author

Mappboy commented Jun 13, 2016

Cool although I might store the location data separately as it's a one to many relationship. Currently for each statement I am writing multiple features for each point, however it might make more sense to write them as a multipoint ? Secondly having them in there own table might make it easier to process the statements again later with retrained models.

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

No branches or pull requests

2 participants