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
The current Relatify interface covers the roads in the background map with an overlay showing the route as selected and branching streets that can also be added to the route. This means that the names of the streets are covered up if they are displayed on the road. This can make it difficult to see if you are selecting the correct road in some instances.
Other than the option described in #45 this could be solved by rendering the road names on top of the overlay, which might hide important information or by choosing a background layer that draws the road names next to the roads rather than in them. The latter option is probably the least effort by far.
Potential background layers with pros (➕) and cons (➖):
Cycle map (Thunderforest),
-- ➕displays roads like this for everything below secondary
-- ➖secondary and higher roads have label in the way
-- ➖would probably need an API key or special permission
Transport map (Thunderforest),
-- ➕displays road names alongside roads for all ways
-- ➕shows existing bus routes, so could be used to assist the planned route selection mechanism (to guide a "show nearby routes" query)
-- ➖would probably need an API key or special permission
OSM Americana (ZeLonewolf)
-- ➖ needs vector tile support (although there is a leaflet plugin for OpenMapTile apparently)
-- ➖ Relatify domain would need to be whitelisted for use.
-- ➕ shows labels "alongside" for road below secondary
-- ➖ by default shows labels within the road for roads above secondary ... but as this is a vector map style this might be fixable with a "light" fork?
The text was updated successfully, but these errors were encountered:
The current Relatify interface covers the roads in the background map with an overlay showing the route as selected and branching streets that can also be added to the route. This means that the names of the streets are covered up if they are displayed on the road. This can make it difficult to see if you are selecting the correct road in some instances.
Other than the option described in #45 this could be solved by rendering the road names on top of the overlay, which might hide important information or by choosing a background layer that draws the road names next to the roads rather than in them. The latter option is probably the least effort by far.
Potential background layers with pros (➕) and cons (➖):
-- ➕displays roads like this for everything below secondary
-- ➖secondary and higher roads have label in the way
-- ➖would probably need an API key or special permission
-- ➕displays road names alongside roads for all ways
-- ➕shows existing bus routes, so could be used to assist the planned route selection mechanism (to guide a "show nearby routes" query)
-- ➖would probably need an API key or special permission
-- ➖ needs vector tile support (although there is a leaflet plugin for OpenMapTile apparently)
-- ➖ Relatify domain would need to be whitelisted for use.
-- ➕ shows labels "alongside" for road below secondary
-- ➖ by default shows labels within the road for roads above secondary ... but as this is a vector map style this might be fixable with a "light" fork?
The text was updated successfully, but these errors were encountered: