Thanks.
Fixed it for now by doing:
emit([doc.country,
doc.gender,
doc.birthdate],
[doc.sexual_o,
doc.geohash]
using a range query on
[“be”,1,19800101] to [“be”,1,19900101]
and doing the geohash filtering application side
Tried out the n1ql approach too as you stated but when trying out the latest release it kept running indefinitely… developer preview is not stable enough for my use case.
Underlying it also uses views… I rather have more control over what my query will use of index.