You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I stumbled upon a limitation in GeoJsonMultipoint which I find unnecessary - it requires to have at least 2 points. While there are no requirements in GeoJson RFC for MultiPoint to have this and Mongo itself works just fine with 1 point in the coordinates list
Was there a reason to implement it like this? Will it cause backward compatibility issues if this requirement is relaxed?
The text was updated successfully, but these errors were encountered:
mp911de
changed the title
GeoJsonMultipoint can be just one point
Relax requirement for GeoJsonMultiPoint construction allowing creation using a single point
Aug 25, 2021
mp911de
changed the title
Relax requirement for GeoJsonMultiPoint construction allowing creation using a single point
Relax requirement for GeoJsonMultiPoint construction allowing creation using a single point
Aug 25, 2021
…n using a single point.
Only 1 point is required per GeoJson RFC and Mongo works just fine with 1 point as well.
Closes#3776
Original pull request: #3777.
I stumbled upon a limitation in GeoJsonMultipoint which I find unnecessary - it requires to have at least 2 points. While there are no requirements in GeoJson RFC for MultiPoint to have this and Mongo itself works just fine with 1 point in the coordinates list
Was there a reason to implement it like this? Will it cause backward compatibility issues if this requirement is relaxed?
The text was updated successfully, but these errors were encountered: