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

emit more than one spatial key document #4

Open
normanb opened this issue Jul 18, 2010 · 4 comments
Open

emit more than one spatial key document #4

normanb opened this issue Jul 18, 2010 · 4 comments
Labels

Comments

@normanb
Copy link

normanb commented Jul 18, 2010

It is useful when working with non-geojson documents to be able to emit more than one spatial key per document since you are not always working with geometry collections. Currently GeoCouch only works with one spatial key emitted per document.

@vmx
Copy link
Owner

vmx commented Aug 18, 2010

Do you mean one than more emit call per function?

@normanb
Copy link
Author

normanb commented Aug 18, 2010

yes, this is possible in couchdb and is used quite a bit (megaview in Raindrop for example),

@vmx
Copy link
Owner

vmx commented Aug 19, 2010

I had a quick look. It's not trivial, so I'll have a look at it after I merged the current fork with current CouchDB trunk.

@normanb
Copy link
Author

normanb commented Aug 19, 2010

that would be great thanks, I have already merged geocouch with trunk if that helps, it needs minor changes in couch_view_group and couch_query_servers, exporting hidden functions.

vmx pushed a commit that referenced this issue Mar 9, 2013
This can be used to serve up files like /crossdomain.xml from a
CouchDB instance. For example, you could add:

    [httpd_global_handlers]
    crossdomain.xml = {couch_httpd_misc_handlers, handle_file_req, "/usr/share/couchdb/www/crossdomain.xml" }

To your local.ini to serve up crossdomain.xml.

Closes #4
vmx pushed a commit that referenced this issue Jul 15, 2013
Router remove(), log clean up and fix couchapp grunt tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants