Expression Index Geo Nearest

An issue arose when a selection was created from an Geo Nearest Expression using an index. The problem was that the place was not corresponding to the coordinates on the map Visualisation. 

E.g. When choosing Warwick in the list on the selection and then dropping a plot map on top, the plots were showing in Pontefract instead of over Warwick. 

Looking at the expression, the index was doing its job correctly. The problem was that there were 60 lat/long coordinates and 61 locations in the index. So at some point in the list a lat/long was missed for an index location. So when the build was running on the map visualisation, it was reading down the list and finding Warwick and producing the plots with the coordinates given. Which were for Pontefract (which was next in that list) 

• Related Articles

• Import a list of dates and URNs and run a selection to find the date in the system with the same URN and previous to the one in the list.

  A client asked us for a method of importing a list of URNS and Dates, into an existing FastStats system, and then to suggest a method to compare the imported date to other dates for the same URN in order to then provide the previous date attached to ...

• Combining Table Results in Orbit using a CubeLookup Expression

  Sometimes it is useful to be able to get results from a Table in Orbit and use them in another Table. Within Orbit, it isn't currently possible to refer to results in one tile within another one. However, we can use a combination of some powerful ...