UnicodeDecodeError in `tilesets upload-source` after converting file using `tippecanoe`
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 430
- PR merge metrics
- No merged PRs in 30d
Description
I downloaded a file from download.geofabrik.de and applied some filters using `osmium tags-filter`. Then I used `osmium export` to get a `.geojson`file.
I converted my `.geojson` file with `tippecanoe` to get a `.mbtiles` file and then using `tilesets upload-source` I get this error:
```
[...]
File "/usr/lib/python3.9/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xae in position 11: invalid start byte
```
When using `tippecanoe` with different parameters on the same file, the error is slightly different:
`UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc0 in position 27: invalid start byte`
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
Reproduce the reported pipeline from the downloaded data through osmium, tippecanoe, and tilesets upload-source, then inspect the full UnicodeDecodeError traceback. Compare uploads produced with the differing tippecanoe parameters and identify which generated input is being decoded as UTF-8. Done means the reported MBTiles output can be uploaded without this decoding error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100