hiposfer / kamal

A routing engine service using Open Street Maps and GTFS as data source

hiposfer/kamal Issues

consider removing the maneuver message
Closed 6 years ago
bug: incorrect mapping of gtfs stops to nodes
Updated 6 years ago
bug: invalid step data returned
Updated 6 years ago
consider creating a merge gtfs feed script
Updated 6 years ago
consider enabling gzip for responses
Updated 6 years ago
GTFS values with leading zeroes break preprocessing
Closed 6 years ago
consider using "elide meta" compiler options to minimize java jar
Updated 6 years ago
consider implementing validation on gtfs feeds
Updated 6 years ago10
refactor directions response to handle frequencies.txt entities
Closed 6 years ago
consider allowing a BBOX as argument for preprocessing
Updated 6 years ago
refactor graph edges to avoid duplicate data
Closed 6 years ago
consider delaying graph entity creation until runtime
Closed 6 years ago
consider relying on a database for network dumps
Updated 6 years ago5
consider making all entity values primitive types
Updated 6 years ago
stop directions computation on timeout
Closed 6 years ago1
consider having the preprocessing step for OSM in datascript
Closed 6 years ago1
refactor travis config to use env vars
Closed 6 years ago2
Extend the overpass query to fetch all public transit nodes
Closed 6 years ago12
add support for frequencies.txt from GTFS feed
Closed 6 years ago
Consider checking EDN file integrity upon loading.
Updated 6 years ago1
consider making the road network a combination of a graph and datascript
Closed 6 years ago2
consider using raw index access
Closed 6 years ago1
consider creating an "edge" entity
Closed 6 years ago1
consider adding route/id to the information on stop/successors
Closed 6 years ago1
consider allowing Router/weight to return a full Valuable not just the diff
Closed 6 years ago
consider adding a LinkData record to pedestrian routing
Closed 6 years ago
allow dumping back a gtfs feed
Closed 6 years ago
consider creating an ID record to support cross type comparisons
Closed 6 years ago1
only allow querying for gtfs data
Closed 6 years ago
provide a bbox of the requested area
Closed 6 years ago
replace uuid with squuid for sequential directions responses
Closed 6 years ago1
consider implementing transfer patterns for GTFS data
Updated 6 years ago
consider implementing contraction hiearchies
Updated 6 years ago
consider using for loops inside dijkstra for lazy path evaluation
Closed 6 years ago1
consider removing "bridge" nodes from db
Closed 6 years ago1
investigate difference in performance of raw leiningen use VS cursive ide use
Closed 6 years ago
consider replacing agent with a simple future
Closed 6 years ago
Setting area OSM env variable breaks the preprocessor
Closed 6 years ago3
consider cleaning the git history of big files
Closed 6 years ago3
consider creating a docker compose image for processing
Updated 6 years ago2
Consider adding start/end-with-bike to routing
Updated 6 years ago
consider storing datascript dump in `transit` format
Closed 6 years ago1
consider making gtfs preprocessing based on regex
Closed 6 years ago
add missing step/departure spec to directions
Closed 6 years ago
investigate directions response without stop_times
Closed 6 years ago
rename route response to directions
Closed 6 years ago
remove namespaces from Json responses
Closed 6 years ago
export gtfs spec as data
Closed 6 years ago1
return namespaced id for reference objects
Closed 6 years ago
consider using the recomendations for performance on gcloud
Updated 6 years ago