This release is a pre-release and may not be stable for production use.
Geocommit allows you to attach geolocation information to your commits for later analysis.
Everything happens on your machine to protect your privacy, you you need to push the geo annotations explicitly if you want to share them with others.
Installation
Use pip (or easy_install):
pip install --upgrade geocommit
(If you don’t have pip yet, use easy_install pip to get it.)
Usage
Geo-enable a repository (installs a few hooks that enable keep track of your location for this repository):
git geo setup
Attach geo-information to HEAD:
git geo note
Fetch geolocation information from remote:
git geo fetch
Fetch and merge geolocation information:
git geo sync
Developing
git clone https://github.com/peritus/geocommit.git python bootstrap.py ./bin/buildout
Crazy ideas
foursquare integration
3rd party service with badges: * jetsetter badge (commits at five different airports) * mountain badge (commits at over 4000ft altitude)
geocommit + git-remote-couch + geocouch === awesome!
git geolog foo..bar > foobar.kml
Chrome/Safari extension to display google maps all over github
Geocommit data format (v1.0)
We store a number of keys with values in git notes or hg commits. There is a long and a short format. Both define a set of key/value pairs in no particular order. The format version defines the allowed keys.
<version> is a version number of the format x.y <key> is an alphanumeric lowercase identifier without spaces or other special characters except _ and - <value> must not contain a linebreak, “,” or “;”
The short format is: geocommit(<version>): <key> <value>, …, <key> <value>;
The long format is, terminated by an empty line:
geocommit (<version) <key>: <value> … <key>: <value>
- Version 1.0 of the format defines the keys:
long (required) contains longitude value of a coordinate in WGS84
lat (required) contains latitude value of a coordinate in WGS84
src (required) contains the name of the data provider used to generate the geodata
alt (optional) contains altitude in metres
speed (optional) speed in metres / second
dir (optional) direction of travel
hacc (optional) horizontal accuracy of long/lat values in metres
vacc (optional) vertical accuracy of altitude value in metres
Metadata
Release files for geocommit 0.9.3beta1
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 |
|---|---|---|---|---|
| geocommit-0.9.3beta1.tar.gz | 14.3 kB | Without provenance | Details for geocommit-0.9.3beta1.tar.gz |
Release files / geocommit-0.9.3beta1.tar.gz
| Download URL | geocommit-0.9.3beta1.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9592671847b2c35bfd98bc5d97cdf6074e0c4d8bcf2a54926b144747ccc6909a
|
|
BLAKE2b-256 checksum How to use checksums |
035faa845192a28abd6b29f458ae889bbef4d7667bc0b5cb79d3ce3702a923f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for geocommit 0.9.3beta1
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.