You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently show and Terms and Conditions link the bottom right hand corner that links to Mapbox. It's not clear to the user what the link relates to and it doesn't even link to terms currently.
Some options to consider:
Display terms and conditions behind an 'I' if we are allowed to (proposed by @bhousel).
Utilize Meta's Canterbury style so that we can show labels at low zoom levels. Could ask Jonah for some advice here and it would mean we can swap out Mapbox's locator overlay. Examples below from Mapillary:
The text was updated successfully, but these errors were encountered:
Good idea - I've never been really happy with how we show attributions for overlay layers.
If the user adds more overlays, we add more attributions down in this section, and it's not clear which overlay goes with which attribution text. I also put the MapWithAI attribution text here too.
I think we could probably move them to a separate popup screen behind an ℹ️ button.
One other point about the Mapbox overlay - I'm fine with swapping it out for something else, but we currently only support raster for this, not vector, and it includes some roads and places and other details too. Not sure whether that would be a dealbreaker, (cc @jonahadkins)
iirc using the raster services requires a discovery mechanism to get the users country and language to adhere to policy. there would probably need to be some type of access token as well so we identify requests from Rapid. there may also be some 1P/3P concerns from legal. all doable, but would need to drive this internally.
Description
We currently show and Terms and Conditions link the bottom right hand corner that links to Mapbox. It's not clear to the user what the link relates to and it doesn't even link to terms currently.
Some options to consider:
The text was updated successfully, but these errors were encountered: