Messages

I can only speak for myself.

Most changes I do on Android, with QuickEdit+. I make edits on an extra file /_themes/Tapiola.xml, which I then copy (Totalcmd) into /_themes/Tapiola.zip/Tapiola/Tapiola.xml - then re-apply theme in Locus for testing.

On PC, far better overview, code folding etc. I use (MS Visual Studio) Codium. Sometimes PSPad. I copy the xml with Totalcmd/Android (accessing a Windows share) into the zip file.

No, no specific theme editor.

Yes. Every syntax error results in a blank display. Reminds me of my Perl job years ago. Syntax error results in http/500, internal server error.

having a super boring theme showing no points, names or features than other roads, would allow those searched points to be highly visible.

You probably know this is possible in Tapiola ("Basic features without POI" has this use case in mind). And I had a related suggestion, but IIRC Menion disagreed: Add Offline/Online Lopoi setting to presets. Because then you can easily a) turn on the theme (which displays no poi at all) + b) turn on lopoi.

A quick test showed me that amenity=bicycle_parking is not included in OAM...

And (2015): https://www.openandromaps.org/oam-forums/topic/inclusion-of-bicycle_parking

EDIT: Haha, lol - you kept 3 theme authors busy with this 😁

Where can I find the xml files on my phone?

menion.android.locus/MapsVector/_themes

Inside of the themes zip file.

Ja, danke Wole! Echt super.

When i activate the theme the standardmap oam world is not shown in lower zoom levels.

I don't think this is themes responsibility. I use OAM-World-1-8-min-J80.mbtiles and it shows up as usual.

It's always interesting to look at other solutions, great release. OMG, legend is probably really time consuming. I'm hesitant to start working on it.

There's some significant color change ZL 14->15, is that intended? Screenshots, pos is at 51.49046,8.0039
EDIT: Ah, solved, it's an area overlay, "national park..." option. I'd default them to Off.

Menu has a typo or french leftover, "motor vehicule"

I'll make changes to this, maybe a pattern, other border, different color, will see.

I can add a border around protected areas, but that will also result in some unwanted lines (renderer problem).

The green could still be slightly more transparent.

Hmm. It looks different on my LM4, see attachments. On my smartphone, this overlay is already barely visible in forest areas.

I am old and rusty and no IT guru, so would not know how to do that. Sorry.

OK, then try the attached one.

I was exploring the region near Faro Portugal for our next hike. Using "all features" of your nice theme, activating protected areas gives an unwanted effect

Please try https://raw.githubusercontent.com/TapioOfTapiola/oam_theme_tapiola/main/Tapiola.xml
(replace it inside the zip)
Edit: Still changes needed to protected area overlays, for better visibility in forest areas.

Re: import 100s of single files, I've created a test set and sent you a link. Select all on import, it makes my LM crash.

A secondary database (archive) is not planned, sorry.

Can you maybe implement an easy logic, eg if it finds an additional db, it would include it into track or wp manager... but create no backup from it, or sync it? But well, maybe intransparent behaviour. Or hidden feature...

Secondary db is just what I did. Imported tons of stuff into it which I need to analyse rarely. It has my complete movement over years.

Der Offset ist ja auch für gemessene Höhe via Sensoren/GPS da. Wenn man aber die statischen Lidar-Daten nimmt - und bessere haben wir nicht - dann wird deren Wert auch genommen. Da würde ich auch immer "Replace" einstellen, wenn man Aktionen auf der Erdoberfläche macht.

Also Lidar nehmen, Sensoren aus, "GPS ersetzen", glücklich sein. Und beim Import von GPX etc. immer die Höhe neu eintragen lassen. Es sei denn, es kommen Flughöhen und Tauchtiefen vor.

15 vs. 19 m sind übrigens noch kein dramatischer Unterschied. Ich bin zh auf 53m, reines GPS zeigt ca. 100 an. Ein Kollege von mir war in der Schwäbischen Alb und er hat lt. Info seiner Komoot-App einmal knapp die 1000m überlaufen. Tja, es waren allerdings nur 950. Ich glaube, ich war da die fiese Partybremse.

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