hiposfer.kamal.io.gtfs — hiposfer/kamal 0.18.0

namespace for handling GTFS to Datascript convertion and vice versa.

The algorithms coerces GTFS csv files into entities that reference each other through IDs. The IDs are taken directly from GTFS.

A small dynamic renaming is performed to make it more compatible with Datascript design. The renaming is based on the GTFS naming convention, for example: stop_lon, stop_url, trip_id, trip_headsign.

We transform those strings into: :stop/lon, :stop/url, :trip/id, :trip/headsign, respectively.

This is important to be able to create relationships between entities through transactions, for example {:trip/id 1, :trip/route [:route/id 1]}. This allows us to create relationships between entities without using java references ... just data

date-format clj

decode clj

(decode text)

dump! clj

(dump! network outstream)

writes the complete GTFS information from network into outstream as a Zip file

encode clj

(encode k v)

feed-hidrator clj

keywords clj

parse clj

(parse zipstream filename)

takes a filename and parses its content if supported by this parser. Entries that do not conform to the gtfs spec are removed. Returns a vector of conformed entries

re-date clj

re-duration clj

re-number clj

re-timezone clj

read-order clj

ref? clj

(ref? field)

a reference is a field that links to a unique field in another file and that is not that field itself

resource clj

(resource entity)

takes a datascript entity and checks if any of its values are entities, if so replaces them by their unique identity value

transaction! clj

(transaction! zipstream)

returns a Datascript transaction of the complete gtfs feed

truncators clj

map of GTFS filenames to post-processing functions. Useful to remove unnecessary information from the GTFS feed; just to reduce the amount of datoms in datascript

uniques clj