Case A: Incorrect Naming and Rejection of Relocation (Seungjaejeong vs. Hamwonjeon) The POI at location A is currently named ‘Seungjaejeong,’ but this is actually ‘Hamwonjeon.’ The real Seungjaejeong is located far away in the Secret Garden area (AA). I requested a relocation to fix this, but it was rejected. Interestingly, most photos uploaded to POI A are actually of Hamwonjeon. I eventually got a new POI for Seungjaejeong approved at the correct location (AA), but my request to rename the incorrect POI A to ‘Hamwonjeon’ was rejected again. Now, two different locations share the same name on the map.
Case B: Coordinate Displacement of New POI (Hamyangmun Ticket Office) While organizing data for Changgyeonggung, I applied for a new POI called ‘Changgyeonggung Hamyangmun Ticket Office’ at location BB. I used a desktop PC to pin the location with surgical precision. It was approved, but to my surprise, the POI appeared near Aeryeonji Pond in Changdeokgung (B), far from where I placed the pin. Despite my accurate input, the system displaced the coordinate. My subsequent request to move it back to BB was also denied.
In densely populated POI areas like these palaces, such coordinate drifts cause extreme confusion for visitors. This is precisely why I emphasized this issue in my proposal (refer to Item 1). Is this a bug unique to South Korea or Seoul? Has anyone else experienced similar issues in other regions?
If you have a fundamental solution to these errors or can share your experiences, I would deeply appreciate your insights. Thank you for your time and for reading this long post.
Sorry. But creating a duplicate place was the wrong move. In cases where your edit to move a pin is not approved your next step should be to request help in the Google Maps Help Community. You will need to attach some supporting evidence for this to work.
Morten, I am not raising this issue because I am unaware of how to merge places. The core of the problem lies in the sequence of events and the systemic failure.
If one simply analyzes the photos already uploaded to that POI, it is blatantly obvious that the building is ‘Hamwonjeon,’ not ‘Seungjaejeong.’ Yet, Google Maps’ AI failed to detect this discrepancy. Furthermore, even when a geographer and expert who lives nearby and frequently visits the site submitted a correction based on clear evidence, the system rejected it.
The creation of a duplicate POI at the correct location was a direct consequence of Google Maps repeatedly rejecting legitimate edit requests. Even after that, my request to rename the incorrectly placed POI to its rightful name, ‘Hamwonjeon,’ was denied again. There are currently two POIs with the same name; simply renaming the old, incorrectly placed one to ‘Hamwonjeon’ would resolve the entire issue instantly.
You should not blame the user for a situation caused by a system that preserves incorrect information and ignores expert input. This is precisely why I am advocating for a fundamental reform of the system.
@geoKoreaSong This isn’t directly related to the topic, but I’m curious. During my last visits to Seoul, the navigation feature in Google Maps wasn’t functional. This was the only place where I encountered this issue (aside from the special case of China). Is this still the case?
Hello! That is a very keen observation. To answer your question: Yes, as of now, that is still the case.
Due to South Korea’s unique security situation and regulations regarding the export of high-precision map data, Google Maps has been unable to provide full navigation and walking directions.
However, there is some very positive news. The South Korean government and Google have recently reached an agreement, and work is underway to integrate high-precision data into Google Maps. This means we can expect significant improvements in the near future.
Anticipating this change, I have recently submitted a proposal to Google consisting of 11 key items. My suggestions focus on how Google can best implement this new data—such as refining place categories, improving the hierarchy of geographic names, and resolving systemic UI bugs—to ensure the new service is as accurate and user-friendly as possible.
I am hopeful that these suggestions will be reflected in the upcoming updates. In the meantime, if you visit again soon, I recommend using ‘Naver Map’ or ‘KakaoMap,’ both of which offer excellent English support for navigation within Korea!
@geoKoreaSong Thanks, and good luck with your proposal to Google, but I wouldn’t hold my breath. For many reasons, ideas from end customers don’t usually make it into products.
Hi @Gaby7, I appreciate your honest perspective and the ‘reality check.’
I know it’s a long shot,
but I believe sharing these ideas is the first step toward potential change.
Thanks for the well wishes!
Case B의 잘못 지정된 위치는 정위치로 이동 배치되어 문제가 잘 해결되었습니다.
그래서 (제가 그 리뷰에서 약속한 바대로) 리뷰에 적어 두었던 첫 문장은 삭제하였습니다.
그런데 이렇게 위치를 수정한 후,
제게 알려주었더라면 제가 더 신속하게 처리할 수 있지 않았을까요?
(신고한 LG가 다시 그 내용을 확인하라고 하지 말고,
구글이 시스템적으로 자동 안내하도록 처리하는 것이 더 낫지 않을까요?)
