mapdata.py is a viewer for geographic coordinate data read from a CSV file, spreadsheet, or database. Both a map and a data table are displayed. When a location is selected on the map, the same location is highlighted in the table, and vice-versa. Single or multiple selections may be enabled. Locations may also be selected and highlighted by writing a query expression to select rows of the data table.
Coordinates should be in decimal degrees, in WGS84 (coordinate reference system [CRS] 4326), however, coordinates in other CRSs can be converted to 4326.
The map display can be customized in several ways:
-
Different raster tile servers may be used for the basemap. The default is OpenStreetMap. Several alternatives are provided, and other tile servers can be specified in a configuration file.
-
Locations identified by coordinates in the data file may be designated by different types of markers and by different colors. The default marker for locations, and the default marker used to flag selected locations can both be customized. Symbols and colors to use for location markers can be specified in a configuration file and in the data file. Different symbols and markers can be used for different selected locations.
-
Locations may be unlabeled or labeled with data values from the data file The label font, size, color, and location can all be customized.
The map can be exported to a Postscript, PNG, or JPEG file. Using command-line options, mapdata can be directed to load a data file and display location markers and then to export the map to an image file, and quit.
Selected rows in the data table can be exported to a CSV or spreadsheet file.
Data can also be displayed in several different types of plots: box plots, scatter plots, line charts, and counts of categorical and quantitative variables. Plots can use either all data or only data values that are selected in the map and table. Plots have a live connection to the data table, so when selections are changed the plots are automatically updated.
SQL commands can be used when pulling a data set from a database, to create a temporary table, for example, instead of using a base table. The SQL commands can be augmented with execsql metacommands and substitution variables.
Complete documentation is at https://mapdata.osdn.io.
A configuration file template, application icons for Linux and Windows, a .desktop file for Linux, and additional bitmap symbols, are available for download from OSDN.
Metadata
Release files for mapdata 2.10.0
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 |
|---|---|---|---|---|
| mapdata-2.10.0.tar.gz | 77.0 kB | Without provenance | Details for mapdata-2.10.0.tar.gz |
Release files / mapdata-2.10.0.tar.gz
| Download URL | mapdata-2.10.0.tar.gz |
|---|---|
| Size | 77.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
88a22ae5dea785cc4140dde0b0d946a679b5f5cbe2dcef32ea7529ba3a1583a9
|
|
BLAKE2b-256 checksum How to use checksums |
a2909f4b37895613ba2b33b1fa36b89fac3674859c41b86a5252fe91c39d4cd6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 colorama/0.4.4 importlib-metadata/4.6.4 keyring/23.5.0 pkginfo/1.8.2 readme-renderer/34.0 requests-toolbelt/0.9.1 requests/2.25.1 rfc3986/1.5.0 tqdm/4.57.0 urllib3/1.26.5 CPython/3.10.6
|
Security for mapdata 2.10.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.