8000 Doc edit: GeoJSON format used in Plotly follows the 2008 specification by Tortar · Pull Request #3829 · plotly/plotly.py · GitHub
[go: up one dir, main page]

Skip to content

Doc edit: GeoJSON format used in Plotly follows the 2008 specification #3829

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update choropleth-maps.md
  • Loading branch information
Tortar authored Jul 27, 2022
commit 3e0a59ebeacd0d9c2e15c9d9e1b869dd3c9d9203
2 changes: 1 addition & 1 deletion doc/python/choropleth-maps.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ Making choropleth maps requires two main types of input:

The GeoJSON data is passed to the `geojson` argument, and the data is passed into the `color` argument of `px.choropleth` (`z` if using `graph_objects`), in the same order as the IDs are passed into the `location` argument.

**Note** the `geojson` attribute can also be the URL to a GeoJSON file, which can speed up map rendering in certain cases.
**Note** the `geojson` attribute can also be the URL to a GeoJSON file, which can speed up map rendering in certain cases. Note also that Plotly requires that the GeoJSON file format follows the 2008 specification, which is **not** the latest one.

### Choropleth Map with plotly.express

Expand Down
0