Bug 255671 - In "Atlas" view label of vietnam is placed inside laos
Summary: In "Atlas" view label of vietnam is placed inside laos
Status: CONFIRMED
Alias: None
Product: marble
Classification: Applications
Component: data (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: some future version
Assignee: marble-bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-30 15:43 UTC by Simon Schmeisser
Modified: 2025-01-09 10:55 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Schmeisser 2010-10-30 15:43:51 UTC 
Version:           unspecified (using Devel) 
OS:                Linux

Hi,

in "Atlas" view the label for Vietnam is placed here 105° 07' 49.9"E,  16° 38' 39.6"N . I guess this is the center of mass of Vietnam or something. It is in Laos however.

cu Simon

Reproducible: Always

Steps to Reproduce:
Choose "Atlas" as Map View
Go to 105° 07' 49.9"E,  16° 38' 39.6"N
See the label of Vietnam being inside Laos

Actual Results:  
label of Vietnam inside Laos

Expected Results:  
label of Vietnam here 105° 41' 51.7"E,  20° 24' 56.7"N (from center of Mass move it in direction of the capital until you reach the country it belongs to)

some other place would work as well

OS: Linux (x86_64) release 2.6.34.7-0.5-desktop
Compiler: gcc
Comment 1 disabled account 2011-05-26 18:09:32 UTC 
I can confirm this for 4.6.2!
Comment 2 John 2012-10-27 03:38:05 UTC 
Confirmed in Marble v. 1.4.1 (stable)
Comment 3 Justin Zobel 2021-03-09 22:51:29 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 4 Matan Ziv-Av 2025-01-09 10:55:43 UTC 
(In reply to Justin Zobel from comment #3)
> Thank you for the bug report.
> 
> As this report hasn't seen any changes in 5 years or more, we ask if you can
> please confirm that the issue still persists.
> 
> If this bug is no longer persisting or relevant please change the status to
> resolved.

This bug still exists in 24.08.3