Here you have some reasons why I've decided to build another version instead of doing a PR for the existing koop-provider-csv :
Trying an alternative way to process streams with stream-chain . IMHO has performance and expressiveness advantages when you have to build a transformation pipeline.
Some code optimizations ( better memory usage). You will notice if you try it out :-)
The previous csv provider fails with some valid csv's ( I attached one example) . One of the dependencies csv-reader doesn't parse csv properly as anyone would expect. If you test it with the csv file provided here, you will notice that parses latitude field as a string instead of a number
Hi!
I've developed an alternative version for koop-provider-csv . You can check it out: @ntkog/koop-provider-csv
NPM package
An example
Here you have some reasons why I've decided to build another version instead of doing a PR for the existing koop-provider-csv :
m30.csv.zip
Hope people find useful,
Cheers!