-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
polyline document error PeliasModelError: invalid document type, expecting: truthy, got: #3
Comments
Can you provide more info about what file you were importing? Do the tests pass for you? |
This was runnin with the planet.polyline download. The tests pass, and I'm using Node.js 6.5 |
Let's discuss which node version we are all running in our local dev environments so that we are on the same page. When issues come up in future versions we can report them and wait to fix them until we sprint on upgrades. |
This has been happening in our production builds as well for some time. Node.js 4.4.7. We should investigate if anything bad is happening or make the logs less noisy |
Hi, Just attempted importing using Node Was there any conclusion as to whether this error invalidates the import? It appears |
Hey @jpan127, If you wanted to, a pull request to make this message less scary and drop it to the info or debug level rather than error would be merged :) |
Thanks @orangejulius. I made a PR with the minor change. |
Refer to the here. than I executed npm start and showed this error: 2018-11-27T05:56:33.223Z - error: [polyline] polyline document error message=invalid document type, expecting: truthy, got: , stack=PeliasModelError: invalid document type, expecting: truthy, got: |
I believe this issue has been resolved by #225. After running an import for a polyline extract of the road network for an OSM planet file, I didn't see any of these errors. If anyone does encounter them again please comment here with the error as well as information about your polylines file such as the origin, date of data, etc. |
Just got this error while importing polylines on my local machine.
The text was updated successfully, but these errors were encountered: