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.

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

Relation to ckanext-spatial #37

Open
letmaik opened this issue Sep 9, 2015 · 1 comment
Open

Relation to ckanext-spatial #37

letmaik opened this issue Sep 9, 2015 · 1 comment

Comments

@letmaik
Copy link
Contributor

letmaik commented Sep 9, 2015

Does ckanext-dcat work together with ckanext-spatial? Especially considering the supported formats of the spatial fields in both. I think this should be remarked somewhere in the readme.
@letmaik
Copy link
Contributor Author

letmaik commented Oct 29, 2015

I had a look at the ckanext-spatial extension. It says the spatial field must be a GeoJSON geometry. I assume ckanext-dcat follows the same convention, but I'm not sure what happens in cases like <dct:spatial>Newark</dct:spatial>. Is that written simply as spatial="Newark" and ckanext-spatial ignores that then since it's not a GeoJSON geometry?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@letmaik