blocks|key|765843|text|我在这件事上也很难过。我想出的唯一解决方案(虽然效果很好)是使用Google的snap。发送您的不准确的折线的坐标到API，它将返回校正的坐标。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|765844|希望这能有所帮助。|765845|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had a hard time with this as well. The only solution I managed to come up with (works great though) is to use Google's snap to road API. Send the coordinates of your inaccurate polyline to the API and it will give back the corrected coordinates.

Hope this helps.

blocks|key|1486092|text|几个月后，我终于得到了谷歌的回复。不幸的是，他们无法理解问题并提供帮助。我又看了看解码算法，现在我可以自己回答这个问题了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1486093|该算法将坐标旋转到1e5。|1486094|Google算法|offset|length|1486095|因此，不可能编码一条符合在最高变焦水平下具有较高精度的底层道路网络绘制的折线。|1486096|此图像显示坐标四舍五入至1e5的最大位置精度。|1486097|​|1486098|📷|atomic|1486099|1486100|entityMap|0|LINK|mutability|MUTABLE|url|https://developers.google.com/maps/documentation/utilities/polylinealgorithm|1|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/32dfa40e5114dd67fdd49038fe3b49bc.jpg|imageAlt^0|0|0|0|8|0|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|17|8|@]|9|@$F|18|G|19|1|1A]]|A|$]]|$1|H|3|I|5|6|7|1B|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1C|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1D|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1E|8|@]|9|@$F|1F|G|1G|1|1H]]|A|$]]|$1|Q|3|M|5|6|7|1I|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]|Z|$5|10|V|11|A|$12|13|14|-4]]]]

After a few months I finally got a reply from Google. Unfortunately they weren't able to understand the problem and help. I looked again at the decoding algorithm and I am now able to answer the question myself.

The algorithm rounds coordinates to 1e5.

<a href="https://developers.google.com/maps/documentation/utilities/polylinealgorithm" rel="nofollow noreferrer">Google Polyline algorithm</a>

It will therefore be impossible to encode a polyline which fits with the rendering of the underlying road network which has a higher accuracy at the highest zoom level.

This image shows the maximum positional accuracy with coordinates rounded to 1e5.

<img src="https://i.stack.imgur.com/irTai.jpg" alt="enter image description here">

blocks|key|1486152|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1486153|📷|atomic|offset|length|1486154|1486155|您还可以从|1486156|https://github.com/xomena-so/so47492459|1486157|不要忘记用您的API键替换API密钥。|1486158|我希望这能帮到你!|1486159|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/99c22e2a76e9676ad1d52403f590f84e.png|imageAlt|1|LINK|MUTABLE|url^0|0|0|1|0|0|0|0|0|13|1|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@$E|14|F|15|1|16]]|A|$]]|$1|G|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|18|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@$E|1A|F|1B|1|1C]]|A|$]]|$1|L|3|M|5|6|7|1D|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1E|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W|X|-4]]|Y|$5|Z|T|10|A|$11|K]]]]

<a href="https://i.stack.imgur.com/V96Sg.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/V96Sg.png" alt="enter image description here"></a>

You can also download a sample project from

<a href="https://github.com/xomena-so/so47492459" rel="nofollow noreferrer">https://github.com/xomena-so/so47492459</a>

Don't forget to replace the API key with yours.

I hope this helps!

blocks|key|1486219|text|你可以试试这个：订阅-3|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1486220|您可以尝试以下步骤(如果使用Node.js)：|1486221|npm+install+polyline|code-block|syntax|javascript|1486222|然后：|1486223|var+polyline+=+require('polyline');

//+returns+an+array+of+lat,+lon+pairs
polyline.decode('_p~iF~ps%7CU_ulLnnqC_mqNvxq`@')|1486224|从Google的响应中提取字符串"_p~iF~ps%7CU_ulLnnqC_mqNvxq`@“：根>路由>+overview_polyline+>点|1486225|​|1486226|📷|atomic|1486227|1486228|地图中的结果点可以如下所示：|1486229|1486230|1486231|1486232|entityMap|0|LINK|mutability|MUTABLE|url|http://zevross.com/blog/2014/09/23/convert-google-directions-to-geojson-points-or-polylines/?subscribe=success#blog_subscription-3|1|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/32d19e3fefec3f2784621b7d238b2dc1.png|imageAlt|2|https://developer.qcloudimg.com/http-save/yehe-900000/bb2d9e11a0f137f31bdabb5778f8f2e6.jpg^0|8|4|0|0|0|0|0|0|0|0|0|1|1|0|0|0|0|0|1|2|0|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@$A|1I|B|1J|1|1K]]|C|$]]|$1|D|3|E|5|6|7|1L|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1M|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1N|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|1O|8|@]|9|@]|C|$I|J]]|$1|O|3|P|5|6|7|1P|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|S|3|T|5|U|7|1R|8|@]|9|@$A|1S|B|1T|1|1U]]|C|$]]|$1|V|3|R|5|6|7|1V|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|1W|8|@]|9|@]|C|$]]|$1|Y|3|R|5|6|7|1X|8|@]|9|@]|C|$]]|$1|Z|3|T|5|U|7|1Y|8|@]|9|@$A|1Z|B|20|1|21]]|C|$]]|$1|10|3|R|5|6|7|22|8|@]|9|@]|C|$]]|$1|11|3|-4|5|6|7|23|8|@]|9|@]|C|$]]]|12|$13|$5|14|15|16|C|$17|18]]|19|$5|1A|15|1B|C|$1C|1D|1E|-4]]|1F|$5|1A|15|1B|C|$1C|1G|1E|-4]]]]

You could try this: <a href="http://zevross.com/blog/2014/09/23/convert-google-directions-to-geojson-points-or-polylines/?subscribe=success#blog_subscription-3" rel="nofollow noreferrer">http://zevross.com/blog/2014/09/23/convert-google-directions-to-geojson-points-or-polylines/?subscribe=success#blog_subscription-3</a>

You could try hhe following steps (if you're using Node.js):

<pre><code>npm install polyline
</code></pre>

And then:

<pre><code>var polyline = require('polyline');

// returns an array of lat, lon pairs
polyline.decode('_p~iF~ps|U_ulLnnqC_mqNvxq`@')
</code></pre>

Where the string "_p~iF~ps|U_ulLnnqC_mqNvxq`@" is extracted from the response of Google Maps API: root > routes > overview_polyline > points

<a href="https://i.stack.imgur.com/8Tj71.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/8Tj71.png" alt="enter image description here"></a>

The resulting points in a map could be shown like this:

<a href="https://i.stack.imgur.com/paECh.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/paECh.jpg" alt="enter image description here"></a>

I am trying to map routes which should match the Google Maps street network.

I know how to serialize the JSON result from the Google Maps Directions API.

I am looking now at encoding the polylines from the individual routing steps.

I have found some decoder algorithm here on stackoverflow but tested first Google's own <a href="https://developers.google.com/maps/documentation/utilities/polylineutility" rel="nofollow noreferrer">Interactive Polyline Encoder</a>. I would expect the encoded line to match the Google Map but it doesn't.

The screenshot shows the result of an encoded segment in the Interactive Polyline Encoder on the left and the result from a Google Maps route on the right.

<img src="https://i.stack.imgur.com/TKkQo.png" alt="enter image description here">

The encoded polyline is "uxhuBxrc|QPA@?@?B?B@@B@D@HDFD@B@H@JBB@DBFJ"

Is it possible that the Algorithm in Google's Interactive Polyline Encoder is wrong?

Has anyone tested <a href="http://jeffreysambells.com/2010/05/27/decoding-polylines-from-google-maps-direction-api-with-java" rel="nofollow noreferrer">Jeffrey Sambells algorithm</a> and knows whether the results match the results from Google's Interactive decoder?

Cheers,
Dennis 

EDIT: The problem is with the returned polyline segments and not the encoding algorithm. Even the sample segment which Google provides in the example response on the Directions API page fits very poorly with the underlying road geometry.

<img src="https://i.stack.imgur.com/NRc76.png" alt="enter image description here">

Google Directions API Encoded Polyline

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在试图地图的路线，应该匹配谷歌地图街道网络。我知道如何序列化Google方向API中的JSON结果。我现在看的是从各个路由步骤编码多行线。我已经在堆栈溢出上找到了一些译码器算法，但是首先测试了谷歌自己的。我希望编码行与Google相匹配，但它不匹配。屏幕截图显示了左侧交互式折线编码器编码段的结果和右侧Google路由的结果。​​编码后的折线是“uxhuBxrc x QPA@？？B?B@B@D@

问编码Polyline
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问编码PolylineEN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问编码Polyline
EN