Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fails when asked for diff sample rate #11

Open
sbma44 opened this issue Aug 13, 2015 · 3 comments
Open

fails when asked for diff sample rate #11

sbma44 opened this issue Aug 13, 2015 · 3 comments

Comments

@sbma44
Copy link
Member

sbma44 commented Aug 13, 2015

I have a trace I'd like to simplify -- see here gist

When I specify a sample rate other than the input (1s), only two points are returned gist

If I use the 1s input sample rate, I get back something with 100 points that looks pretty good (input is 900+ points) gist

This is a problem because the map matching API seems to expect data samples at 5s intervals.

cc @planemad

@planemad
Copy link
Contributor

@sbma44 saw your comment that the problem was in the exported trace. Is this still open?

@sbma44
Copy link
Member Author

sbma44 commented Aug 13, 2015

Yeah, left this open because I'm still curious about the behavior. My problem was having multiple LineStrings in the submitted FeatureCollection. geojson-tidy produced okay results when minimumTime is set to 1 but not when set to 5.

When the traces are combined, however, the default value (5) works fine. So I guess this is okay to close, though perhaps it would be desirable to throw an error when there's more than one feature?

@ZephD
Copy link

ZephD commented Apr 12, 2019

Is this caused by #16 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants