Skip to content
A Python module for performing bulk imports of GIS data into SimpleGeo
Find file
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

README.rst performs a bulk import of a CSV file containing latitudes and longitudes, or a GIS point dataset into the SimpleGeo database.

If available, uses the Python bindings to the OGR library ( to read dozens of GIS vector formats, including ESRI Shapefiles, GML, KML, GeoRSS, GeoJSON, GPX, and more.

The library uses the python-simplegeo library to write to the SimpleGeo API.

You can set your SimpleGeo credentials in one of two ways: Either set them in the script at the very top, or create environment variables in your shell named SIMPLEGEO_TOKEN and SIMPLEGEO_SECRET that contain your credentials.

You can use in one of two ways: First, as a command line script:

$ python <SimpleGeo layer> <GIS dataset> [<ID column>]


$ python net.nocat.cities cities.gml name

IMPORTANT NOTE FOR CSV FILES: The CSV file must begin with a header line, and the columns containing the latitude and longitude must be called "latitude" and "longitude", respectively. This requirement may be relaxed in a future version.

SimpleGeo records require a unique ID. If your dataset has a unique ID column, you can provide it. If you leave out the ID column, IDs will be assigned to records from the dataset sequentially.

If a simple bulk upload isn't sophisticated enough, you can use as a library, using a callback from your own script to mutate or reject records before they are added to your SimpleGeo layer. An example is given in, where we want to reject records that lack a "fullname" attribute:

from bulk_import import create_client, add_records
import sys

def skip_unnamed_landmarks(id, point, attrs):
    if not attrs["fullname"]: return None
    return attrs["pointid"], point, attrs

client = create_client()
for input_file in sys.argv[1:]:
    add_records(client, "net.nocat.tigerlm", input_file, skip_unnamed_landmarks)

As you can see, we create a callback that takes a sequential ID, a (lat, lon) tuple, and a dict of attributes. The callback returns None if we don't want to store a record from the dataset; otherwise, it returns a tuple (ID, (lat, lon), attrs) that is used to create the SimpleGeo record. We then call add_records() from with a client object, the name of an OGR-readable dataset, the name of the SimpleGeo layer, and the callback.

Something went wrong with that request. Please try again.