The Plan

My geohashing alert2016-01-13 15:28-system at 123k.org shows the current geohash for my home graticule. The plan is to the nearest route which passes by.

Finding Something

As mentioned earlier I have all points i ever visited in a collection. This collection holds a geospatial index. Therefore I can issue mongo queries with the $nearSphere command. This command finds the first points from a given location.

So this just works. But what about other routes which may also be nice and just around the corner? We can select many points around the hash point and check which routes they’re on.

Introduction

When I started with my personal bike-track homepage at 123k.org a few years ago I decided to put all my tracks in a MongoDB. The model I use is very simple. I have a class Route which holds meta-data about the track and a class TrackPoint which represents a point and has a foreign key to the respective track (of course). After some years I have 612827 track-points. So 600k entries is not ‘big-data’ exactly, but it is too much to be displayed on a leaflet map at once. What I really wanted is a ‘Coverage View’, which just shows me where I’ve been with the bike.