a-b-street/abstreet

Elevation data

Open

#82 opened on Jun 23, 2020

View on GitHub
 (18 comments) (0 reactions) (0 assignees)Rust (6,779 stars) (256 forks)batch import
good first issue

Description

This is a big project, but with small steps. Roughly:

  1. Get better elevation data, either fixing the bugs in the srtm.rs impl or preferably using the better LIDAR data around Seattle. I have some pointers for that in an email somewhere; remind me to post them

  2. Figure out how elevation change affects the standard bicyclist speed. Incorporate that in the simulation and pathfinding cost function

  3. Render the elevation layer much more understandably. Isochrones are the thing people are familiar with, probably should give that a shot

I can give pointers to relevant code when needed

Contributor guide

Tech stack
rust
Domain
backenddata
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Rustbasic simulation concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Start by examining the `srtm.rs` file to understand current elevation data handling. Look for previous discussions in the issue comments regarding LIDAR data sources. Ask the maintainer for the email pointers mentioned in the issue body. Then evaluate the feasibility of using LIDAR data versus fixing the SRTM parser. This will inform further steps on elevation speed modeling and rendering.