Hi.

That's a good point. I'll add a CSV import/export functionality to the package.

I hacked up my own JavaScript location map solution based on Google's API but it's more fragile than I'd like it to be. With 6000 locations the lookup time could be lengthy so I filter the locations for 100 mile radius first based on Lat and Long before plotting all the locations within the radius. I'm not sure how your engine looks stuff up but 6000 locations was a serious problem.

I use clustering in HERE maps. I don't know how it works with thousands of items, as I can't afford testing with so many transactions with a free account.

So overall, I have added a CSV import/export to the package, that should handle them easily. But geocoding thousands of items can be problematic because of the network, input and HERE internal stuff issues. I've also added forward and reverse geocoding to the package. It works on tens of items fine. I won't test it on thousands. I'd say it's better to enter all coordinates in the CSV and then import it.