[SERVER-9220] allow more than two values in the coordinate-array when using 2dsphere index Created: 03/Apr/13  Updated: 25/Jan/17  Resolved: 12/Mar/15

Status: Closed
Project: Core Server
Component/s: Geo
Affects Version/s: 2.4.0, 2.4.1
Fix Version/s: 3.0.3, 3.1.0

Type: Improvement Priority: Trivial - P5
Reporter: Robin Wagner Assignee: Siyuan Zhou
Resolution: Done Votes: 16
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File geoparser.cpp     File geoparser_test.cpp    
Issue Links:
Duplicate
is duplicated by SERVER-21607 2dsphere index does not accept valid ... Closed
Backwards Compatibility: Fully Compatible
Backport Completed:
Participants:

 Description   

GeoJSON allows more than two values in coordinate-array (http://geojson.org/geojson-spec.html#positions).
Of course 2dsphere honours only the first two, but it should be allowed to add more (altitude, measure, etc).
-> should be considered in geoparser, see attachments



 Comments   
Comment by Githook User [ 25/Apr/15 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-9220 allow more than two values in the coordinate-array when using 2dsphere index

(cherry picked from commit bd489b1c2c76a7ee84105db758839c4d47ffcbcb)
Branch: v3.0
https://github.com/mongodb/mongo/commit/ef30b10fac26dc9ef4e93eb8d78fe7005a8967f5

Comment by Githook User [ 12/Mar/15 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-9220 allow more than two values in the coordinate-array when using 2dsphere index
Branch: master
https://github.com/mongodb/mongo/commit/bd489b1c2c76a7ee84105db758839c4d47ffcbcb

Comment by Robin Wagner [ 03/Jan/15 ]

I've recognized option 'allowAddlFields' (geoparser.cpp) in branch 2.8.0-rc4. How is that switch going to be configured? Additional parameter during index creation?

static Status parseFlatPoint(const BSONElement &elem, Point *out, bool allowAddlFields = false)

Comment by Hans Kristian [ 22/Nov/14 ]

Com on! Fix this already!

Comment by Ludovic Fleury [ 23/Dec/13 ]

Same here, the altitude isn't important for the query, but we need it once we retrieve the document.

Comment by Hans Kristian [ 06/Nov/13 ]

Please accept this. We are heavily relying on the altitude to be able to display a contour of the geometry – and all of our tools support 3D GeoJSON (so does the GeoJSON spec). We don't need to query altitude, just keep it together with the other coordinates.

Comment by Andy Ennamorato [ 30/Oct/13 ]

Querying and specifying altitude in the query is less important to us than just being able to include it in with our geo data, as outlined in the GeoJSON spec. This would be a nice feature to have.

Generated at Thu Feb 08 03:19:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.