That one's out of my hands as a content developer, alas, as it's an engine bug with how static world map elements are parsed, and new engines release on a relatively infrequent schedule (more monthly than weekly).
Had a poke at our ticketing system to see what's up. Looks to have initially been reported in May, investigated quite extensively (looks like it was quite a tricky issue to isolate) and then a fix developed in September. Given the defect's relative gameplay impact severity, it's flagged as minor priority, so presumably some more critical engine fixes have beaten it to the testing suite a couple times.
Looks like the fix has been QAed and ready to merge since early December. Wasn't included in the most recent (January) client update, so presumably it's waiting for the next full stack (server & client) engine release.
EDIT: Investigated further. It won't be in the next engine (releasing mid Feb), but is scheduled in for the one after that.
Hope that helps!