blocks|key|5791152|text|route|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5791153|City+is+locality|unordered-list-item|5791154|
|5791155|State+is+administrative_area_level_1|5791156|5791157|ZIP+is+postal_code|5791158|5791159|Country+is+country|5791160|
的街道地址是|5791161|+street_number|5791162|5791163|请注意，Google忽略任何类型的单元号(例如‘'Apt+13A')。您必须将其重新添加到您自己中。|5791164|通过地理编码器运行您的数据样本并手动检查结果，应该可以确认您正在获得所需的内容。|5791165|entityMap^0|0|5|0|8|8|0|0|9|R|0|0|7|B|0|0|B|7|0|0|1|D|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|I|3|J|5|6|7|19|8|@]|D|@]|E|$]]|$1|K|3|L|5|H|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|M|3|J|5|6|7|1D|8|@]|D|@]|E|$]]|$1|N|3|O|5|H|7|1E|8|@$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|P|3|J|5|6|7|1H|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1I|8|@$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1L|8|@]|D|@]|E|$]]|$1|U|3|V|5|H|7|1M|8|@$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1P|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|Z|3|10|5|6|7|1R|8|@]|D|@]|E|$]]|$1|11|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]]|12|$]]

<ul>
<li>Street address is <code>street_number</code> and <code>route</code></li>
<li>City is <code>locality</code></li>
<li>State is <code>administrative_area_level_1</code></li>
<li>ZIP is <code>postal_code</code></li>
<li>Country is <code>country</code></li>
</ul>

Note that Google ignores any kind of unit number (e.g. 'Apt 13A'). You'll have to add that back in yourself.

Running a sample of your data through the geocoder and checking the results manually should confirm that you're getting what you need.

blocks|key|549842|text|documentation似乎很清楚地涵盖了各个字段的含义。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|549843|你还没有说你正在用什么语言工作，但我认为这将help。|549844|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/apis/maps/documentation/geocoding/#StatusCodes|1|http://jasonjano.wordpress.com/2010/02/10/address-geocoding/^0|0|D|0|0|M|4|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

The <a href="http://code.google.com/apis/maps/documentation/geocoding/#StatusCodes" rel="nofollow">documentation</a> seems to cover what the various fields mean quite clearly.

You havent said what language you are working in, but I think this will <a href="http://jasonjano.wordpress.com/2010/02/10/address-geocoding/" rel="nofollow">help</a>.

blocks|key|3677890|text|我在搜索页面的Nearlots.com上做反向地理编码。基本上，用户在地图上的某处放置一个标记，然后我在搜索框中打印一个地址。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3677891|我只是简单地打印'formatted_address‘，如果它不在那里就放弃。这将给你这样的东西：“275-291Bedford+Ave，Brooklyn，NY+11211，USA”。这已经足够了--你总是可以在最后去掉美国。|3677892|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 am doing reverse geocoding on Nearlots.com in the search pages. Basically, the user drops a marker somewhere on the map and I print an address in a search box. 

I am simply printing 'formatted_address' and giving up if it's not there. This will give you something like this: "275-291 Bedford Ave, Brooklyn, NY 11211, USA". This is more than sufficient - you can always strip out the USA at the end.

blocks|key|5791105|text|我认为你需要使用'route‘作为街道地址。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5791106|我使用相同的服务，根据我的经验，'route‘总是等同于街道地址，即使该位置实际上不是一条街道！|5791107|我想您已经确定了如何计算城市名称。这与我采用的方法相同；查看几个不同位置的各种API结果，看看哪个字段提供的结果最一致。|5791108|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I think you need to use 'route' for the street address.

I use the same service and from my experience 'route' is always the equivalent of a street address, even when the location is not actually a street!

I think you have already determined how to figure out the city name. etc. It is the same approach I take; have a look at a variety of API results for a few different locations and see which field gives you the most consistent results.

blocks|key|3677972|text|经过几个小时的工作，我无法始终如一地提取公寓/房间/子房屋。拥有这个细节比能够明确地分离它更重要，所以我用这个绕过了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3677973|var+componentForm+=+{
++++locality:+'long_name',
++++administrative_area_level_1:+'short_name',
++++country:+'long_name',
++++postal_code:+'short_name'
};

function+fillInAddress(place)+{
++++for+(var+component+in+componentForm)+{
++++++++document.getElementById(component).value+=+'';
++++++++document.getElementById(component).disabled+=+false;
++++}
++++for+(var+i+=+0;+i+<+place.address_components.length;+i%2B%2B)+{
++++++++var+addressType+=+place.address_components[i].types[0];
++++++++if+(componentForm[addressType])+{
++++++++++++var+val+=+place.address_components[i][componentForm[addressType]];
++++++++++++document.getElementById(addressType).value+=+val;
++++++++}
++++}
++++var+parts+=+$("#searchField").val().split(",");
++++$("#street_number").val(parts[0]);
}|code-block|syntax|javascript|3677974|我像往常一样从自动补全中提取了信息，尽管跳过了"street_number“和"route”。然后在选择后对自动完成值进行简单的拆分，并使用第一部分，返回整个街道地址(包括工厂/公寓/场所和街道名称)。|3677975|这项工作给了我很好的结果，满足了我的需求。祝好运!|3677976|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

After many hours of working on it, I wasn't able to consistently extract the flat / room / sub premise. Having that detail was more important than being able to specifically separate it, so I got around it using this.

<pre><code>var componentForm = {
 locality: 'long_name',
 administrative_area_level_1: 'short_name',
 country: 'long_name',
 postal_code: 'short_name'
};

function fillInAddress(place) {
 for (var component in componentForm) {
 document.getElementById(component).value = '';
 document.getElementById(component).disabled = false;
 }
 for (var i = 0; i &lt; place.address_components.length; i++) {
 var addressType = place.address_components[i].types[0];
 if (componentForm[addressType]) {
 var val = place.address_components[i][componentForm[addressType]];
 document.getElementById(addressType).value = val;
 }
 }
 var parts = $("#searchField").val().split(",");
 $("#street_number").val(parts[0]);
}
</code></pre>

I've extracted the information from the auto complete as normal, although skipped "street_number" and "route". Then did a simple split on the auto complete value after selection and used the first portion, returning the street address as a whole (including factory / flat / premise and street name).

This work around gave me results that work well for what I need. Good luck!

I'm using <a href="http://code.google.com/apis/maps/documentation/geocoding/" rel="nofollow">Google's Geocoding API</a> to process free-form address data and am trying to make sense of the results (<code>subpremise</code>, <code>administrative_area_level_2</code>, etc.). At this point I'm only interested in addresses in the US, and would like to format the results as a street address, city, and state code. The state code seems straightforward (<code>administrative_area_level_1</code>), but the others are more vague. Is city <code>locality</code> or <code>sublocality</code> or both or even more? The street address itself seems like it could be any number of combinations of the other fields.

Ideally, I'd like to just take the <code>formatted_address</code>, strip off the city, state, zip, and country code, and keep what is left as my "street address". Are there any guidelines or recommendations for handling all these fields, at least for the majority of cases (regular addresses, addresses with unit numbers, etc.)?

Making sense of Google Geocoding API results

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯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编辑器全新改版上线，欢迎大家体验!

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

社区新版编辑器体验调研

我正在使用处理自由格式的地址数据，并试图理解结果(subpremise、administrative_area_level_2等)。在这一点上，我只对美国的地址感兴趣，并希望将结果格式化为街道地址、城市和州代码。州代码看起来很简单(administrative_area_level_1)，但其他代码则比较模糊。city是locality还是sublocality，或者两者兼而有之，甚至更多？街道地

问理解Google Geocoding API结果
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问理解Google Geocoding API结果EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问理解Google Geocoding API结果
EN