working with tsvs
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 373
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
I'm using the npm install method and i'm having a terrible time working with tsv files. none of the commandline options seem to work as expected. the header line wasnt even recognized until i swapped it out for a csv one. now looking at the resulting file the translation is all skewed for some reason. Can someone show me the correct syntax for this?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report using the npm install method and the command-line options with a TSV containing a header. Compare the generated GeoJSON against the input, including delimiter and header handling; done means a confirmed correct invocation or a documented bug with a reliable reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100