{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"closed","user":{"avatar_url":"https://secure.gravatar.com/avatar/89294e6e0a46788090e76c03ef732774?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"89294e6e0a46788090e76c03ef732774","url":"https://api.github.com/users/hunterhacker","login":"hunterhacker","id":321454},"milestone":null,"labels":[],"assignee":null,"updated_at":"2011-11-13T22:24:04Z","closed_at":"2011-11-13T22:24:04Z","comments":1,"url":"https://api.github.com/repos/marklogic/Corona/issues/43","body":"http://developer.marklogic.com/pubs/5.0/apidocs/cts-query.html#cts:element-geospatial-query says\r\n\r\n\"$weight (optional): A weight for this query. The default is 1.0. This option is currently ignored; geospatial queries do not contribute to the score.\"\r\n\r\nSo I'd remove that feature from Corona until such time as we can implement it.  It's OK with me if you keep the code the same, but remove it from the docs.\r\n","html_url":"https://github.com/marklogic/Corona/issues/43","title":"Weight on geo is currently ignored, should prob not expose","number":43,"id":2223415,"created_at":"2011-11-13T21:50:47Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/6c2516d72f329cf0b853fcf66bb34a70?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"6c2516d72f329cf0b853fcf66bb34a70","url":"https://api.github.com/users/isubiker","login":"isubiker","id":221752},"updated_at":"2011-11-13T22:24:04Z","url":"https://api.github.com/repos/marklogic/Corona/issues/comments/2724856","body":"Remved from the docs, code still exists.","id":2724856,"created_at":"2011-11-13T22:24:04Z"}}