-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken pipe error with upload-source #101
Comments
@chintanp I was experiencing this same issue until I realized the API token I was using didn't have the right access. I created a new one with all tileset and upload permissions and it worked fine. |
I am facing the same issue. Same mapbox-tilesets info as @chintanp. I tried @kent-williams's method by generating a new token. It did not help. pip show mapbox-tilesets
|
@octopusabhiraj Not a solution to the above problem exactly, but if you want to upload tilesets to Mapbox, then I was able to achieve the same using a round-about way, which I describe here: https://evi-dss.readthedocs.io/en/latest/evi_des.html#plotting Let me know if you have any questions about the above method. |
@chintanp converting to .mbtiles is an efficient way to save space and upload time. The problem is that I want to programmatically upload the tileset to MapBox and I don't think there are any APIs to do so. Please let me know if there are any. I cannot upload the tileset manually to MapBox Studio. Thanks! |
Hello! Just wanted to say that I'm running into this as well but I confirmed it's not the token, because it works for a 377M file but not for a 607M file. Could it be because the file is too big? I'm running tilesets-cli v1.5.1 on a python:3.6.11-buster docker container.
|
Experiencing the same thing as @geohacker not working for certain files, but mine is of the magnitude of 500kb (succeeded) vs 2.3mb (did not succeeded) vs 122.6MB (succeeded) All three files are similar in geometry type and i used same function to create them, i was able to successfully create mbtiles from the three of them |
@mhuconcern I was able to speak to someone at Mapbox and they found that reducing the coordinate precision of my GeoJSON fixed my issue. I'm now using a GeoJSON that has a precision upto 5 digits. |
Mine is fixed by changing the id of the tileset, one of my files had a long name. The upload-source doesn't throw good error messages |
I had the exact same error uploading a 3.6 gig file, when I reduced the len of the ID then it uploaded correctly. This is cleary is a bug where they should check for the length of an ID and throw a better error. |
Similar to #77 , I get the broken pipe error with the following command:
tilesets upload-source <user-name> <project-name> populated_places.geojson.ld
with the environment variable and the --token flag. The json is from the example on the website, and I tried another geojson file that passes the validation test. Also, tried with--no-validation
flag with the same result.The error is below:
My OS info:
lsb_release -a
Mapbox-tilesets info:
pip show mapbox-tilesets
Any help in this regard is appreciated?
The text was updated successfully, but these errors were encountered: