Aleksander Vines

I probably have exact same issue here. Some info on my system: Windows 7 >npm version { 'ditecross-bot.js': '1.0.0', npm: '3.10.8', ares: '1.10.1-DEV', http_parser: '2.7.0', icu: '57.1', modules: '48', node:...

As expected, had to do with linebreaks in windows. This fix fixed it: ditecross.js: ``` function read_token(fileName) { var lines = fs.readFileSync(fileName).toString().split(require('os').EOL) ```

It does sound nice to skip the step where we choose the platform. But I believe a few more featureTypes should be implemented before you switch that, it's not point...

+1 :)

I'm looking into an implementation of this which is based on regex instead. Your specific examples could be matched like this: ``` Station Name: "Site ID:([^,]+)" Latitude: "Latitude([^,NS]*)[NS]," Latitude Units:...

This allows the user to write regex to extract metadata from header:  Simple validation of the pattern entered is implemented in the UI.  If the conversion process fails...

Also just noticed that in the variable specifications, degree_north is used and in platform specification, degrees_north. Both are recognized and accepted by udunits, but wouldn't it be an idea to...

> Currently, if you mark those two lines as "header" lines in the wizard interface, they should be ignored. This works for each specific case, but it requires for this...

Both please :) In general, the user should select the keyword from a list, but he should also be allowed to add custom keywords if they have requirements that does...

Also, why are non-standard attribute names used (at least I'm not aware of the standard, please feel free to enlighten me :) Specifically: dataAuthor and dataSource E.g. in ACDD, you...