geodb

Process base mapping data used by other modules. Mandatory Module for ASDC

Quick start

Add “geodb” to your INSTALLED_APPS setting like this:

INSTALLED_APPS = [
    ...
    'geodb',
]

If necessary add "geodb" in (check comment for description):
    DASHBOARD_PAGE_MODULES,
    GETRISKEXECUTEEXTERNAL_MODULES,
    QUICKOVERVIEW_MODULES,
    MAP_APPS_TO_DB_CUSTOM

For development in virtualenv add GEODB_PARENT_DIR path to VENV_NAME/bin/activate:
    export PYTHONPATH=${PYTHONPATH}:\
    ${HOME}/GEODB_PARENT_DIR

Include the geodb URLconf in geonode/urls.py like this:
```
url('', include('geodb.urls')),
```
Run python manage.py migrate geodb to create the geodb models.

Metadata

Release files for isdc-geodb 0.1.dev1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for isdc-geodb 0.1.dev1
File	Size	Uploaded	Provenance
isdc-geodb-0.1.dev1.tar.gz	5.1 MB	Nov 28, 2018	Without provenance	Details

Release files / isdc-geodb-0.1.dev1.tar.gz

Download URL	isdc-geodb-0.1.dev1.tar.gz
Size	5.1 MB
Tags	Source
SHA-256 checksum How to use checksums	`7e68fe92fc76442af10a31cb44ec7a70c929d6b869a879549472bc0cf31773e1`
BLAKE2b-256 checksum How to use checksums	`ef134d6f676dcdbfe32ce299846244ac7f02661824b1942222623e48379d7bce`
Upload date	Nov 28, 2018
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/1.12.1 pkginfo/1.4.2 requests/2.18.4 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.23.3 CPython/2.7.6`

Security for isdc-geodb 0.1.dev1

Report project as malware

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.