（巴西利亚24日综合电）谷歌地图已经成为许多人的日常工具，不仅可以直接搜寻地点、路名，更可以透过街景辨识当地情况，但近日却有网友发现，在谷歌地图搜寻“亚马逊雨林”，搜出的地点虽然没错，但点入街景一看，内容却十分“母汤”，让网友大呼：“这是三小？”
据悉，在谷歌地图中搜寻“亚马逊雨林”，地图随即会跳到南美洲巴西的亚马逊河流域，更附带注解“最大且蕴藏丰富物种的热带雨林”，一切看似正常，但当人点入该地点的街景一看，竟然变成一个对男女在房内“啪啪啪”的无码照，让人十分无言。
而这个“360度稀有动物做运动”的消息在网路上流传开来，许多网友纷纷都到谷歌地图朝圣，还在该地点留下评价：“有够帅气、我也想去”、“生态丰富”、“太牛逼了！雨林完全无码！！！”
有网友在搜寻结果分享在PTT（批踢踢实业坊），立即引起热议，有乡民大呼：“搜寻出来的街景是虾小…”、“太靠北了啦！”也有人被逗乐，笑称：“街景超好笑”、“google你在干什么阿”、“搜寻了Google maps关键字快笑死”。
文：综合报导
图：互联网
SQL: Array
(
[0] => Array
(
[query] => SELECT * FROM "wp_posts" WHERE "wp_posts"."ID" = :MeD0_mK AND "wp_posts"."post_status" = :MeD1_mK LIMIT 1
[params] =>
[time_ms] => 0.641823
)
[1] => Array
(
[query] => SELECT tt.term_id as tagid from wp_term_relationships tr
left join `wp_term_taxonomy` tt On tt.term_taxonomy_id = tr.term_taxonomy_id
WHERE tt.taxonomy IN ('post_tag')
AND tr.object_id = 3016947
[params] =>
[time_ms] => 2.365828
)
[2] => Array
(
[query] => SELECT "wp_terms"."term_id" AS "term_id","wp_terms"."name" AS "name","wp_terms"."slug" AS "slug","wp_terms"."term_order" AS "term_order","wp_term_taxonomy"."description" AS "description","wp_term_taxonomy"."parent" AS "parent","wp_term_taxonomy"."count" AS "count","wp_term_taxonomy"."taxonomy" AS "tax" FROM "wp_terms" LEFT JOIN "wp_term_taxonomy" USING ("term_id") WHERE "wp_terms"."term_id" = :MeD2_mK AND "wp_term_taxonomy"."taxonomy" = :MeD3_mK LIMIT 1
[params] =>
[time_ms] => 0.411034
)
[3] => Array
(
[query] => SELECT "meta_key","meta_value" FROM "wp_postmeta" WHERE "post_id" = :MeD4_mK
[params] =>
[time_ms] => 1.306057
)
[4] => Array
(
[query] => SELECT * FROM "wp_posts" WHERE "wp_posts"."ID" = :MeD5_mK AND "wp_posts"."post_status" = :MeD6_mK LIMIT 1
[params] =>
[time_ms] => 0.365019
)
[5] => Array
(
[query] => SELECT * FROM "wp_posts" WHERE "wp_posts"."ID" = :MeD7_mK AND "wp_posts"."post_status" = :MeD8_mK LIMIT 1
[params] =>
[time_ms] => 0.272989
)
[6] => Array
(
[query] => SELECT * FROM "wp_posts" WHERE "wp_posts"."ID" = :MeD9_mK AND "wp_posts"."post_status" = :MeD10_mK LIMIT 1
[params] =>
[time_ms] => 0.499964
)
[7] => Array
(
[query] => SELECT tt.term_id as tagid from wp_term_relationships tr
left join `wp_term_taxonomy` tt On tt.term_taxonomy_id = tr.term_taxonomy_id
WHERE tt.taxonomy IN ('post_tag')
AND tr.object_id = 3016947
[params] =>
[time_ms] => 0.226974
)
[8] => Array
(
[query] => SELECT "wp_terms"."term_id" AS "term_id","wp_terms"."name" AS "name","wp_terms"."slug" AS "slug","wp_terms"."term_order" AS "term_order","wp_term_taxonomy"."description" AS "description","wp_term_taxonomy"."parent" AS "parent","wp_term_taxonomy"."count" AS "count","wp_term_taxonomy"."taxonomy" AS "tax" FROM "wp_terms" LEFT JOIN "wp_term_taxonomy" USING ("term_id") WHERE "wp_terms"."term_id" = :MeD11_mK AND "wp_term_taxonomy"."taxonomy" = :MeD12_mK LIMIT 1
[params] =>
[time_ms] => 0.204086
)
)
Redis: Array
(
[0] => Array
(
[command] => RAW
[arguments] => Array
(
[0] => HGET
[1] => post_info:3016947
[2] => info
)
[time_ms] => 0.21
)
[1] => Array
(
[command] => RAW
[arguments] => Array
(
[0] => HGET
[1] => category_info:all
[2] => info
)
[time_ms] => 0.66
)
[2] => Array
(
[command] => RAW
[arguments] => Array
(
[0] => ZRANGE
[1] => termlist115076
[2] => 0
[3] => 7
)
[time_ms] => 0.23
)
[3] => Array
(
[command] => RAW
[arguments] => Array
(
[0] => HGET
[1] => post_info:3463774
[2] => info
)
[time_ms] => 0.22
)
[4] => Array
(
[command] => RAW
[arguments] => Array
(
[0] => HGET
[1] => post_info:3461236
[2] => info
)
[time_ms] => 0.22
)
[5] => Array
(
[command] => RAW
[arguments] => Array
(
[0] => HGET
[1] => post_info:3395556
[2] => info
)
[time_ms] => 0.21
)
[6] => Array
(
[command] => RAW
[arguments] => Array
(
[0] => HGET
[1] => post_info:3147421
[2] => info
)
[time_ms] => 0.18
)
)
