Messages

Mine has exceeded 1 GB, a real challenge, for backups e.g. and space in general.

OK did some testing. Everything is fine.

a) Deleted several 1000 of tracks from LM database via the trackmanager. After exit LM4, the db file immediately went from >300 MB down to 160. So for some reason now it instantly did the cleanup action.

b) sqlite3.exe alternatives also lead to a result, a working and small db.

Code Select Expand

sqlite3.exe tracks.db "VACUUM"
or
sqlite3.exe tracks.db ".dump" | sqlite3.exe new.db

Hi Andrew, I can't change it, it's specific and due to the way the mappers have drawn the bridge plus my offset.

The equivalent of my striped line in Johns theme is the semi transparent white line on the center of the bridge.

If we center the line you won't see a problem. But adding an offset you can see, there is a short part appearing in the south. While in the north there is a longer line, over the whole bridge.

v1.3.8

• Visibility cycling route captions
• Dependency markers in menu
• Visibility industrial area captions
• Industrial area captions part of suburb name display
• Fine tuned hiking/cycling relation offsets

"Dependency markers": without the above parent option checked, the child option will not display.

@Andrew, Re: Hobart bridge.

The cycleway is painted at the right place. But there's 3 relations (togglable in my theme via "Cycling network"). One on bridge center, one on both cycleways.

Problem: I display them with an offset, because in the theme hiking relations are on one side, cycling in other side of roads. I want to keep this system. In case of this bridge it gets a bit messy.

Screenshots, without relations, with offset, without offset.

This can only be solved by centering the relations, but then displaying hiking + cycling at the same time is difficult. Need to think about it.

EDIT: Nah, it should be OK. Offset only a thing in high zooms. I have tamed them. Please try latest release. I like it now.

Btw, it was a full line by accident. Now it's striped (rcn|lcn|ocn), full=icn/ncn

Can you give me a position, would also like to look. Just to be safe: you're aware there's tag transform documentation on the OAM homepage?

v1.3.7

• Improvements in visibility of hiking/cycling relations in lowest zooms
• Improvement in visibility primary..tertiary roads
• Fixed a bug where borders of major roads were overpainted by minor paths asphalt layer. Resulting in reduced visibility because their black border wasn't visible.

The last one is a bit dangerous, I changed paint order for a bigger block, but lack overview on my smartphone. Need to look at the bigger code image on my computer at some point. All those tons of road/path code layers are hard to deal with on a small screen.
Still haven't touched the Andrew issue. 😩

.db=poidb
.map=map
.poi not used by Locus

v1.3.6 (accidentally skipped 1.3.5 😂)

• Fine tuning to city/suburb name sizes
• Slight pink coloring for residential area town masses
• No more residential roads in zoom level 12
• Some fixes to width of mtb routes
• Several small fixes

@AndrewHeard haven't yet looked to that cycle relations issue, but will do.

I will look at it. What I instantly see is, Karl draws two lines, left and right from roads. I draw one - hiking relations are drawn on the other.
I think it's this: depending how mappers draw the ways, the  relations sometimes interrupt and skip to the other side. So what we see may be a drawback from using an offset to only one side of the way. Sigh. If I draw it later it would appear on top of the main road. EDIT: which it usually does and should to. I will find it. A priority issue maybe.

No, I love to forget to change version inside the xml. You can use https://github.com/TapioOfTapiola/oam_theme_tapiola/blob/main/Tapiola.xml
- Has some few changes.

Google will den IT-Pöbel vor sich selbst schützen und gibt ihm immer weniger Möglichkeiten in die Hände. Das ist der Hintergrund. Apfelisierung. Selbstverständlich müssen die User noch umerzogen werden, damit sie auch Brechdurchfall gut finden. Bei Apple hat das ja auch funktioniert.

Intent problem > this is unfortunate. The plugin uses a hardcoded name of the starting screen, but this has changed in the latest version and this old screen no longer exists.

Problem with recording > problem with the start may be connected to the crash at start. The worst is "action: stop".

So should I report to Falcos Github? My impression is, plugin is pretty much abandoned. It would be great if ASAMM could take over the plugin if he agrees. And it's open source after all.

Nicht "anlegen", sondern definieren, welche Ordner Locus verwenden soll.

Komisch, anders als bei mir ist bei Dir gar nicht der große "+"-Botton, die "..."-Menüs auch nicht, worunter man Ordner entfernen kann. Keine Ahnung. Bug wg. Android-Restriktionen? Im Helpdesk fragen.
Oder stelle mal testweise Locus auf Hell um.

You cannot view this attachment.
Evtl. in den Einstellungen dauerhaft aktivieren.

Also. Wenn Du dort auf den passenden Ordner zeigst und das einschaltest... UND Deine Fotos Geodaten haben, dann werden sie in Locus auch angezeigt. Schaue Dir das System genau an, es ist sehr gut und flexibel.

"Fotopunkt" - das System hingegen nutze ich nicht.

tapio - the download page still only has 1.3.3?

Thx, please retry. After I clicked "publish" nothing happened, now I see it was just saved as a draft.

Most recent xml has SAC Scale captions and traffic lights ("public transport, traffic" category).