{"action":"opened","issue":{"url":"https://api.github.com/repos/opentripplanner/OpenTripPlanner/issues/2301","repository_url":"https://api.github.com/repos/opentripplanner/OpenTripPlanner","labels_url":"https://api.github.com/repos/opentripplanner/OpenTripPlanner/issues/2301/labels{/name}","comments_url":"https://api.github.com/repos/opentripplanner/OpenTripPlanner/issues/2301/comments","events_url":"https://api.github.com/repos/opentripplanner/OpenTripPlanner/issues/2301/events","html_url":"https://github.com/opentripplanner/OpenTripPlanner/issues/2301","id":164198350,"number":2301,"title":"Trips incorrectly show elevation as below sea level","user":{"login":"grant-humphries","id":1002875,"avatar_url":"https://avatars.githubusercontent.com/u/1002875?v=3","gravatar_id":"","url":"https://api.github.com/users/grant-humphries","html_url":"https://github.com/grant-humphries","followers_url":"https://api.github.com/users/grant-humphries/followers","following_url":"https://api.github.com/users/grant-humphries/following{/other_user}","gists_url":"https://api.github.com/users/grant-humphries/gists{/gist_id}","starred_url":"https://api.github.com/users/grant-humphries/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/grant-humphries/subscriptions","organizations_url":"https://api.github.com/users/grant-humphries/orgs","repos_url":"https://api.github.com/users/grant-humphries/repos","events_url":"https://api.github.com/users/grant-humphries/events{/privacy}","received_events_url":"https://api.github.com/users/grant-humphries/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-06T23:31:40Z","updated_at":"2016-07-06T23:31:40Z","closed_at":null,"body":"I've come across a few trips that return legs or steps as having an elevation below sea level where it seems unlikely that is true.  For the two trips below I've checked those stretches against other sources and they show them as being ~40m higher.  These we're initially found on TriMet's production instance (v0.10), but I set up a local instance of v0.20 on my PC and the issue persisted.  \r\n\r\nSee examples in the last leg of [this](http://ride.trimet.org?fromPlace=5700+N+KERBY+AVE::45.564285,-122.672290&toPlace=6700+Block+N+Basin+(Coast+Guard)::45.572468,-122.719890&mode=BICYCLE&min=TRIANGLE&triangleTimeFactor=0.33663366336633666&triangleSlopeFactor=0.32578714036354567&triangleSafetyFactor=0.3375791962701176&maxWalkDistance=4828) trip, and the latter half of [this](http://ride.trimet.org?fromPlace=2408%20SE%20ASH%20ST::45.521294,-122.641136&toPlace=4012%20SE%2017TH%20AVE::45.493725,-122.647520&mode=BICYCLE&min=TRIANGLE&triangleTimeFactor=0&triangleSlopeFactor=0&triangleSafetyFactor=1&maxWalkDistance=4828) one."}}
{"actor":{"display_login":"grant-humphries"}}