Per Liedman

3.0 will be developed on the [develop branch](https://github.com/perliedman/leaflet-routing-machine/tree/develop).

Version 3.0 was released to support OSRM's new API, so I've updated the issue title. This ticket is really about "next major revision" of LRM's API.

@sourc7 the `develop` branch has full Leaflet 1.0.0 support, AFAIK. Any help very welcome, though!

@WilliamWalker hi there, if you mean making waypoints draggable to rearrange, I'm not likely to include it in the core of LRM. Having said that, it's _really_ easy to add...

Hi there! It's been quite a while since I used this myself, but it looks like you're missing a projection definition. If you look at the docs for [`heightmap.py`](https://github.com/perliedman/shadow-mapper#heightmappy), it...

There's no clear plan at this point. It's only a suggested feature. Help getting this done, in the form of a PR, or sponsorship for developing it would be welcome.

Yes, set alternatives takes an _array_ of routes (the alternative**s**), but it looks like you're passing a single route. ``` javascript control.setAlternatives([JSON.parse($scope.trip.lineString)]); ``` would probably fix this.

Yes, you are right. I remember that the code assumes a route's `coordinates` to be `L.LatLng` instances since a couple of versions back. As a hack, you can of course...

@esurnet as mentioned above, the issue is that the JSON's `coordinates` property isn't deserialized to an array of `LatLng` objects, which `setAlternatives` expect. As a workaround, you can parse the...

Hi there, it not possible for me to understand what issue you want to report here. While those routes look weird, I have no idea how they were produced or...