geo_vba VS VBA-CSV-interface

Not sure if it is of any use to you, but OSM has quite some data too. I have some code in a repository that could be of assistance: https://github.com/krijnsent/geo_vba

After this publication, which details the reason why VBA Expressions turned out to be the most feasible option to solve the problem of integrating an expression evaluator with CSV Interface, it is time to address the process of integrating the evaluation capabilities and the ease with which this goal was achieved.

In spite of what I discovered, I was convinced that I could incorporate the referred library to CSV Interface, so I dedicated myself to study the methodology with which variables are handled in stdLambda. I found it difficult to understand why the variables must be passed in terms of a pre-established order ($1 refers to the first value passed as parameter of the evaluate function, $4 the fourth... and so on). Thus, the user is forced to write the expressions taking into account the order in which the values will be passed.

If you want to do something really useful, you can contribute to one of the many amazing libraries around like stdVBA (you can see the backlog here), CSV Interface or VBCorLib

The new release of CSV interface includes substantial improvements and changes to the way users interact with the tool, as well as fixing some programming bugs. What's new in the latest version?

Here are the two procedures that solve your problem in a simple way using CSV files and the CSV interface. Note that if in the column where the file name is taken there is a repeated name, the contents of the array will be appended to the existing CSV file. Here is a link with the solution and the 2 outputs after execute it.

This is a great scenario to use CSV interface. With few lines of code, all files will be made by applying a simple for loop through the rows. You just need to encode the data copy to an array and the filename generator, the CSV job will be done by the interface. Reply to this if the issue is not solved yet.

If the performance still isn't acceptable then /u/ws-garcia has a dedicated CSV parser that they've worked hard at making very high performance.

With CSV interface you can solve this problem in three (3) different ways:

Working from Notepad++ gave me an idea of how the text strings should be manipulated from VBA. The first thing to do from the VBA CSV interface will be to import only the fields that contain the relevant data to solve the problem (the_geom and NAME). The files created in this step (temporary) will be saved in the same folder.

This can be great! here you can download some CSV samples.