OpenStreetMap insted of Mapbox

[florian-sabonchi]

Hello what do you think to use OpenStreet map instead of mapbox

[johan12345]

Mapbox maps are based on OpenStreetMap data and their client SDK (at least the older version that we are currently using) is open source. So what exactly are you proposing and what benefit would that bring?

• Using a different client library?
• Using a different OpenStreetMap tile provider?
• Using OpenStreetMap data for charging stations? (this is currently in development, see Support OpenStreetMap as data source #97)
• Using a different service for geocoding queries (search field)?

I already wrote some comments on #36 and #141 that might help understand why we are currently using Mapbox, which other options are available and why some of them are not currently feasible.

[florian-sabonchi]

Hello Thank you for the reply. I was actually not aware of that, I want to avoid unnecessary tracking services. Have you heard of warden? Warden is an open source application that detects trackers within APKs see here:
https://gitlab.com/AuroraOSS/AppWarden

Unfortunately, Warden seems to classify Mapbox as a tracker. I hope you can understand now why I opened this issue

[florian-sabonchi]

[florian-sabonchi]

I have read your comment I think the issue was unnecessary. thanks for your great work

[johan12345]

Hm okay, yeah, so this tool seems to just detect „trackers“ based on package names, not checking if tracking code is actually included and enabled. As stated in #141 all telemetry is disabled, there are just some concerns about the SKU token which is necessary for billing purposes. So I‘ll close this as a duplicate of #141.