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
EV chargers from shell are branded as Shell Recharge. They also work with other business (workplace, retail, hotels etc) to install chargers at the sites. The brand they use for their business to business activities is "Shell Recharge Solutions"
It is this second name that appears as operator in the naming index. Instead I believe the naming index should use "Shell Recharge".
P.s. the actual company name various by country. In the UK it is "Shell EV Charging Solutions UK Ltd."
P.p.s. I'm assuming the maintenance and operation of the EV charger continues to be via Shell for both Shell direct to consumer sites, plus shell business to business "solutions" installations but this isn't 100% sure.
The text was updated successfully, but these errors were encountered:
I'd be happy to drop the "solutions" text, as even if some Countries brand / label the charger as "Shell Recharge Solutions", I think "Shell Recharge" on its own would still clearly highlight which brand / operator it was.
Would this be best moved from the operator tree to the brand tree however? Do Shell operate all these chargers themselves?
Spotted on OSM community forum.
EV chargers from shell are branded as Shell Recharge. They also work with other business (workplace, retail, hotels etc) to install chargers at the sites. The brand they use for their business to business activities is "Shell Recharge Solutions"
It is this second name that appears as operator in the naming index. Instead I believe the naming index should use "Shell Recharge".
P.s. the actual company name various by country. In the UK it is "Shell EV Charging Solutions UK Ltd."
P.p.s. I'm assuming the maintenance and operation of the EV charger continues to be via Shell for both Shell direct to consumer sites, plus shell business to business "solutions" installations but this isn't 100% sure.
The text was updated successfully, but these errors were encountered: