Samir Moussouni comments

Results 6 comments of


                                            Samir Moussouni

Support for refPath and dynamic population

You can just declare your field with the regular mongoose syntax, inside your ts-mongoose schema: For example: ```ts const MyModelSchema = createSchema( { type: Type.string({ required: true, index: true, enum:...

Map matching: very difficult to get a route with coordinates

Here is a list of coordinates with an error for the route calculation: ``` 1. 48.846413943401 2.3445725440979 2. 48.86271029257 2.313244342804 3. 48.8592281 2.2671622 4. 48.859844609102 2.1876311302185 5. 48.8733692 2.1689624 6....

Map matching: very difficult to get a route with coordinates

I'm looking for a workaround and maybe the issue is that the option `radiuses` is missing in the request sent by `Directions.shared.calculateRoutes`. This option is available in the Android SDK....

Map matching: very difficult to get a route with coordinates

Update: I have created a variant of `NavigationMatchOptions` to set the maximum (49 meters) for each location's `coordinateAccuracy`, used to set radiuses in the request (the existing `NavigationMatchOptions` set `coordinateAccuracy`...

Map matching: very difficult to get a route with coordinates

@1ec5 I answered you on this issue. The workaround is here: https://github.com/mapbox/mapbox-navigation-ios/issues/1907#issuecomment-460666967

NavigationMatchOptions should not clear out coordinate accuracies

@1ec5 I have tried your workaround previously but it didn't work. Now, I understand why. This is because the `NavigationMatchOptions` constructor modifies each waypoints by setting their `coordinateAccuracy` to -1....