Fix geo retrieval of large element counts
Fix geo retrieval of large element counts

Previously the result was stack allocated, but that breaks if
your result set goes above a certain size.  For now, let's just heap
allocate the result.

TODO: potentially stack allocate if result is small enough then
switch to heap allocation only if we are too big.

kmiku7/krmt,mattsta/krmt,kmiku7/krmt,kmiku7/krmt,mattsta/krmt,mattsta/krmt