Timestamp, can't represent too-large feature.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 430
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I have a csv with a column named timestamp. When I execute tippecanoe with this csv file I get the following warning:
`Warning: Can't represent too-large feature ID 0`.
I have converted the timestamp column values to string values assuming it could not represent the attribute because of the size of the integer values (1e09) and it could represent a nine character string, but the same warning is appearing possibly because even though I converted the values to string, it may be inferring is an integer, I do not know.
In anycase is there any solution to be able to use tippecanoe and represent the feature attribute timestamp?
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 warning in tippecanoe with a CSV containing a timestamp column, testing both numeric and string timestamp values. Trace how the CSV input is interpreted and how feature ID 0 is handled. Done means the timestamp attribute can be represented without the warning, or the limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100