List view
- No due date•58/58 issues closed
Phase 1 "Final Release"
Due by September 30, 2016•12/12 issues closedThe "Accurate" Release
Due by September 16, 2016•34/34 issues closedThe "Fast" Release Compute unstatisfied demand by subtracting capacity information from the filtered facilities from the demographics layer. By this release we should decide whether we compute that information from polygons or raster layers.
Due by August 25, 2016•31/31 issues closedThe "Good Enough" Release - Road network data fixed and preloaded. - Import facilities from ResourceMap and preprocess catchment areas for each facility. - Allow filtering of facilities by facility type and show results on the map (in the facilities tab) - Allow selecting travel time by car and show coverage area for the filtered facilities (in the transport means tab). - Show raster demographics layer (in demographics layer).
Due by July 28, 2016•35/35 issues closedFor a given point on a map, mark the catchment area by assuming constant catchment bank along roads. Support parameter tuning (velocities for roads, catchment bank along roads).
Due by July 1, 2016•8/8 issues closedFor a given point on a map, mark the catchment area through a convex hull. Support different velocities for types of roads.
Due by June 10, 2016•1/1 issues closedFor a given point on a map, given the road network information, create a isochrone, marking the furthest points that can be reached through each possible path, assuming 50 km/h * 2hours. Spike both a "radial binary search" and a "range dijkstra" (walking the graph). Goal is to determine: data source to be used (OSM, other graphs, 3rd party service/API) and algorithm for coverage area.
Due by May 28, 2016•3/3 issues closed