felt-upload
What
Felt is "the best way to work with maps, together".
And this is a simple CLI application to upload your files to it from your console.
Why
The Felt API is pretty straightforward, but sometimes you just need a tool to upload a file from a command line and not deal with all the insides.
Install
pip install felt-upload
or you can use pipx:
pipx install felt-upload
API Token
To use it you need an API token from Felt. Get yours here.
You can either pass it directly as --token option or provide as an env variable FELT_TOKEN.
You can check token with the user command, which will print out a user for the given token.
export FELT_TOKEN="felt_pat_Ul8HIuHJZuMyxJJ7ZHajj3gBM6KAs4mnnE6f7GiJIPC"
felt-upload user
felt-upload user --token "felt_pat_Ul8HIuHJZuMyxJJ7ZHajj3gBM6KAs4mnnE6f7GiJIPC"
All further examples assume you have token set in the env.
Usage
Create a map with a single layer and upload your files.
felt-upload map data.geojson
You can also specify a bunch of optional parameters.
felt-upload map --title "My new map" --layer-name "Great data" data.geojson
Keep in mind, felt-upload is pretty straighforward and does not know much about different geo file formats, so if you use shapefiles, you need to specify all the files explicitly:
felt-upload map --title "My new map with shapefiles" shapefile.shx shapefile.shp shapefile.prj shapefile.dbf shapefile.cst
Or use a zip archive
felt-upload map --title "My new map with zipped shapefiles" shapefile_inside.zip
More use cases
Multiple layers
Create multiple layers on a single map
felt-upload map --title "Multilayer"
felt-upload layer <map-id> --layer-name "My point data" dataset.geojson
felt-upload layer <map-id> --layer-name "My other data" dataset-2.geojson
felt-upload layer-import <map-id> --layer-name "My layer from url" http://example.com/path-to-data
Existing map
Want to add layer to already existing map?
Grab map id from the url as explained here, e.g. for https://felt.com/map/Untitled-Map-Cwc6EdieQdyXgyPMgDmYBC?loc=37.807,-122.271,14z you need a part after the map name and before the ?: Cwc6EdieQdyXgyPMgDmYBC.
1 maintainer
Metadata
1 maintainer
Release files for felt-upload 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| felt_upload-0.1.3.tar.gz | 5.9 kB | With provenance | Details for felt_upload-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| felt_upload-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for felt_upload-0.1.3-py3-none-any.whl |
Total release size: 12.9 kB
Release files / felt_upload-0.1.3.tar.gz
| Download URL | felt_upload-0.1.3.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8109d87420c72a5be3f2b9ec5e92fb7ca0ce41cb4f5592f9f8e8682e5213dcfb
|
|
BLAKE2b-256 checksum How to use checksums |
890a760c19d637ee53d24d3a547b714e3b1ccda3270f2d0bd5879bddeded8381
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 10, 2024.
Transparency logRelease files / felt_upload-0.1.3-py3-none-any.whl
| Download URL | felt_upload-0.1.3-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ae6b13e026293a9821dc9a2a1e8aecfbdb9310f376e229fded7be8b14b6e832e
|
|
BLAKE2b-256 checksum How to use checksums |
5dd43670708114b790af0310c4f00b432b6f84fc0a588ebe82524e211c21b0a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 10, 2024.
Transparency logSecurity for felt-upload 0.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for felt_upload-0.1.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 10, 2024.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
