This object is in archive! 

Contours in Vector Maps show wrong orientation in captions some times

Oliver Naumann shared this problem 9 years ago
Solved

Hi,


I noticed, that the caption on the contour lines in Vector maps (in this case from openandromaps) are not oriented properly. Normaly (at least in my experience) the orientation is always "head to peak", meaning the upper part of the letters face the peak, while the bottom or the letters show direction valley. I discussed this with the maker of the openandromaps, he could not help.

I understand this can be an issue with the underlying mapsforge library, but would be great if this can be solved.


Please see attached Screenshot for an example.

Replies (13)

photo
2

[DE]

Hallo Oliver

Was meint Christian denn genau dazu? Mal abgesehen von "could not help" :)

Hast du evtl. einen Link?

photo
2

Hi gynta,


hatte das in den Support Thread geposted:

http://www.openandromaps.org/support-de/comment-page-7#comment-7244

Er sacht: "Ja das mit der Ausrichtung der Beschriftungen können wir leider nicht Beinflussen, das ist in Mapsforge nich möglich, sorry"


Hast Du ne Idee?

photo
2

[DE]

Hab gerade den Beitrag gelesen.

Das ist Jammern auf hohen Niveau :)

Ich seh da wenig Licht am (derzeitigen) Ende des Tunnels.

Denn wenn die Library dies nicht hergibt, dann ist es eben so.

Die Idee ist gut - aber wahrscheinlich (noch) nicht umsetzbar.


Evtl. bekommst du hier noch Infos:

https://groups.google.com/forum/#!forum/mapsforge-dev

photo
1

jaja, soweit sind wir schon, daß wir über solche Kleinigkeiten reden :-) Will mich nicht beschweren, Locus und OSM sind eine tolle Kombi. Leider kann ich nicht programmieren, sonst würde ich versuchen mich da einzubringen... Bleibt OSM, da bin ich ja dabei.

Hoffe, daß sich bei dem Thema Höhenlinien vielleicht doch noch was tut...

photo
2

Tommi ?

photo
1

Because of German part, I do not know what you discuss, anyway we are aware of a problem with contour lines. Issue is anyway more complex and not so easy to solve.


During next months we will do some improvements on system we use for map generating, so we will try to fix also this issue. It's not a big problem, but it's confusing and it's something, that should definitely be fixed.

photo
2

Hi Menion, sorry for that :-) We were just discussing the result of the conversation with Christian (Openandromaps) and his conclusion that the caption of the contour lines is a matter of the displaying sowftware (mapsforge?), not of the map data. We were then agreeing that Locus is already a great piece of Software and this complaint is kinda luxury problem :-)

photo
2

No problem. Are you sure, it's a problem of rendering software? Because I think, it's more problem of orientation of lines in map file.


Or better. It depend on orientation of lines, on which side will be altitude value. And who should make these orientations in correct way? I think that map generator. Because this generator do it just once and not everytime when you want to draw map.


But I'll rather ask professional ... Peter? :)

photo
3

In the begining I thought that problem is in source data as Menion wrote. But problem is somewhere in Mapsforge. Maybe clipping data into metatiles or some render issue (I vote for second :)) You can compare it on attached images. One shows raw continious lines that are used for generation (note that there is no brake). Second one shows rendered map and you can see that caption has different orientation even on the "same" line.

Anywya we're planning some improvements of vector maps during summer so this is one point we can focus on.

photo
2

Oh fine Petr, waste your time

...and the mapforge lib v4.0 is coming soon :P

photo
2

Just warning: no matter what MapsForge v4.0 brings, it won't be used in Locus. It should be only in case, it will be more optimized than modified version that Locus use. Which is quite hard task :)

photo
1

I hope you can find a solution, this would be really great! ran into this issue again on our last hike...

photo
1

Good day guys,

oooold issue will be fixed in next Locus Map version.

Replies have been locked on this page!