-
Notifications
You must be signed in to change notification settings - Fork 53
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
Native CKAN synching #300
Comments
This is very interesting and would be happy to collaborate. The site that runs at chicago.opengrid.io is driven by Plenario, which can sync with CKAN instances by adding data. However, this has to be done one-by-one, which may not make sense. Likewise, there may be better approaches. We can chat here or we can schedule a time to chat on the phone. We have weekly calls with the OpenGrid and Plenario development team and this would make a good topic. (Pinging folks from the Plenario team). |
As per the Open Letter to the Open Data Community, open data platforms need to treat geospatial data as a first class data type.
Along those lines, we're planning to enable PostGIS by default on the CKAN datastore, and making sure that geospatial data are treated as such.
And instead of building it from scratch, consistent with our "best-of-breed" philosophy, helping our CKAN clients spin up OpenGrid to complement their CKAN instances, and loosely coupling the two.
The way we're thinking of doing this, is by allowing the data owner to create an OpenGrid view of an eligible dataset resource (i.e. well-formed dataset with geospatial/spatio-temporal, data) and directly registering it with the associated OpenGrid instance's MongoDB database.
What do you think of this approach?
The text was updated successfully, but these errors were encountered: