Support 2dsphere queries #102

Closed
jmikola opened this Issue Mar 28, 2013 · 3 comments

Comments

Projects
None yet
2 participants
@EmiiKhaos

This comment has been minimized.

Show comment Hide comment
@EmiiKhaos

EmiiKhaos May 6, 2013

Contributor

I wanna take care of these, 'cause I need a subset of them in my project. So I want to give some work back to the community and this great work.

But one question. MongoDB validates GeoJSON strictly and requires numbers only in the coordinates array. So should do the bundle the conversion if a number-string was supplied, or only check and throw an error?

Contributor

EmiiKhaos commented May 6, 2013

I wanna take care of these, 'cause I need a subset of them in my project. So I want to give some work back to the community and this great work.

But one question. MongoDB validates GeoJSON strictly and requires numbers only in the coordinates array. So should do the bundle the conversion if a number-string was supplied, or only check and throw an error?

@jmikola

This comment has been minimized.

Show comment Hide comment
@jmikola

jmikola May 13, 2013

Member

So should do the bundle the conversion if a number-string was supplied, or only check and throw an error?

@patkar: Are you asking if we should check coordinate arguments for non integer/float values and raise and cast them as necessary? By default, I assume MongoDB would raise an error executing the query? (I haven't tested any of the new GeoJSON stuff yet).

Member

jmikola commented May 13, 2013

So should do the bundle the conversion if a number-string was supplied, or only check and throw an error?

@patkar: Are you asking if we should check coordinate arguments for non integer/float values and raise and cast them as necessary? By default, I assume MongoDB would raise an error executing the query? (I haven't tested any of the new GeoJSON stuff yet).

@EmiiKhaos

This comment has been minimized.

Show comment Hide comment
@EmiiKhaos

EmiiKhaos May 13, 2013

Contributor

Yes, should we check the values from the user and throw an (not checked) exception, or let the user do what he want, and Mongo raise its default exception, if the coordinates are not a number: MongoCursorException: [...] can't parse query (2dsphere) [...]

Contributor

EmiiKhaos commented May 13, 2013

Yes, should we check the values from the user and throw an (not checked) exception, or let the user do what he want, and Mongo raise its default exception, if the coordinates are not a number: MongoCursorException: [...] can't parse query (2dsphere) [...]

@jmikola jmikola referenced this issue May 15, 2013

Merged

Support GeoJSON and 2dsphere queries #109

3 of 3 tasks complete

@jmikola jmikola closed this in #109 Jul 11, 2013

@malarzm malarzm referenced this issue in doctrine/mongodb-odm Mar 10, 2015

Closed

mongo 2.4 support #551

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