Details
Description
Rather recently it was raised that the example DB format for longitude is not very consistent with GeoJSON. The problem is that the sample data has geo.lng and geo.lon would be more consistent.
By making this more consistent, it will also work better with elasticsearch, per Marty's notes.
By making this more consistent, it will also work better with elasticsearch, per Marty's notes.
http://review.couchbase.org/#/c/22729/
It's very low risk for inclusion, and we'd like to do so such that we don't have to update this and change data later.