I think there are a couple of reasons why a vector map of, what I assume you refer too, is the Standard or OpenStreetMap-Carto styled layer is not planned or realistic anywhere in the near future: - As someone already pointed out, developer resources is one aspect. Knowing what I know from developing an OSM renderer from scratch for ArcGIS, it is an absolute huge undertaking to develop and maintain a style as complex as Carto / Standard, and the infrastructure to support it all. Converting the existing raster based style and infrastructure to a vector based one, would be a pretty massive task. - There is a second, much underappreciated aspect though. Despite all the flashy promotion of vector based maps as being "light-weight" and "fast" compared to raster tile services, this is only so for very basic simple maps with just a few vector layers (maybe 5-10 max). As soon as you start converting a style as complex as Carto, which would probably require a couple of hundreds of vector layers, things start to look ***entirely*** different... - Also, Carto currently displays buildings from a scale of about 1:50k. That would mean literally (tens of) thousands of vector building objects needing to be transferred and rendered on mobile devices with big screens if a 1:1 vector style conversion would need to be implemented with the same level of detail as Carto at each Z zoomlevel... Honestly, *have you ever seen a style even nearly as complex as Carto being served as pure vector tiles*? I haven't, I think that says enough. I think current mobile hardware simply is not yet up to the task to deal with such complex vector services. Maybe in another 10 years... Just testing of some vector services on my Samsung Tab S (first version), which is pretty high end as regards mobile with an octo-core processor, shows map rendering in the mobile browser to be very sluggish compared to opening the same vector service in a browser on my Core i5 desktop. And that is with a very basic style. Opening the Google Maps App, which does offer acceptable performance, and zooming all the way in, I only get to see any buildings when there are no more than maybe 50 50-500 buildings max in the viewport... Also, in this respect, I recently read an article where the author concluded that with the apparent switch to vector based services, a style like Google's was considerably simplified compared to the styling before the switch. Less objects were shown at each zoom level. So you can have vector on your mobile device now, but at the huge cost of great simplification of the styling and the number of features shown at each zoom level. Is that the price you want to pay for having vector?

I think there are a couple of reasons why a vector map of, what I assume you refer too, is the Standard or OpenStreetMap-Carto styled layer is not planned or realistic anywhere in the near future: - As someone already pointed out, developer resources is one aspect. Knowing what i I know from developing an OSM renderer from scratch for ArcGIS, it is an absolute huge undertaking to develop and maintain a style as complex as Carto / Standard, and the infrastructure to support it all. Converting the existing raster based style and infrastructure to a vector based one, would be a pretty massive task. - There is a second, much underappreciated aspect though. Despite all the flashy promotion of vector based maps as being "light-weight" and "fast" compared to raster tile services, this is only so for very basic simple maps with just a few vector layers (maybe 5-10 max). As soon as you start converting a style as complex as Carto, which would probably require a couple of hundreds of vector layers, things start to look ***entirely*** different... - Also, Carto currently displays buildings from a scale of about 1:50k. That would mean literally (tens of) thousands of vector building objects needing to be transferred and rendered on mobile devices with big screens if a 1:1 vector style conversion would need to be implemented with the same level of detail as Carto at each Z zoomlevel... Honestly, *have you ever seen a style even nearly as complex as Carto being served as pure vector tiles*? I haven't, I think that says enough. I think current mobile hardware simply is not yet up to the task to deal with such complex vector services. Maybe in another 10 years... Just testing of some vector services on my Samsung Tab S (first version), which is pretty high end as regards mobile with an octo-core processor, shows map rendering in the mobile browser to be very sluggish compared to opening the same vector service in a browser on my Core i5 desktop. And that is with a very basic style. Opening the Google Maps App, which does offer acceptable performance, and zooming all the way in, I only get to see any buildings when there are no more than maybe 50 buildings max in the viewport... Also, in this respect, I recently read an article where the author concluded that with the apparent switch to vector based services, a style like Google's was considerably simplified compared to the styling before the switch. Less objects were shown at each zoom level. So you can have vector on your mobile device now, but at the huge cost of great simplification of the styling and the number of features shown at each zoom level. Is that the price you want to pay for having vector?

I think there are a couple of reasons why a vector map of, what I assume you refer too, is the Standard or OpenStreetMap-Carto styled layer is not planned or realistic anywhere in the near future: - As someone already pointed out, developer resources is one aspect. Knowing what i know from developing an OSM renderer from scratch for ArcGIS, it is an absolute huge undertaking to develop and maintain a style as complex as Carto / Standard, and the infrastructure to support it all. Converting the existing raster based style and infrastructure to a vector based one, would be a pretty massive task. - There is a second, much underappreciated aspect though. Despite all the flashy promotion of vector based maps as being "light-weight" and "fast" compared to raster tile services, this is only so for very basic simple maps with just a few vector layers (maybe 5-10 max). As soon as you start converting a style as complex as Carto, which would probably require a couple of hundreds of vector layers, things start to look ***entirely*** different... - Also, Carto currently displays buildings from a scale of about 1:50k. That would mean literally (tens of) thousands of vector building objects needing to be transferred and rendered on mobile devices with big screens if a 1:1 vector style conversion would need to be implemented with the same level of detail as Carto at each Z zoomlevel... Honestly, *have you ever seen a style even nearly as complex as Carto being served as pure vector tiles*? I haven't, I think that says enough. I think current mobile hardware simply is not yet up to the task to deal with such complex vector services. Maybe in another 10 years... Just testing of some vector services on my Samsung Tab S (first version), which is pretty high end as regards mobile with an octo-core processor, shows map rendering in the mobile browser to be very sluggish compared to opening the same vector service in a browser on my Core i5 desktop. And that is with a very basic style. Opening the Google Maps App, which does offer acceptable performance, and zooming all the way in, I only get to see any buildings when there are no more than maybe 50 buildings max in the viewport... Also, in this respect, I recently read an article where the author concluded that with the apparent switch to vector based services, a style like Google's was considerably simplified compared to the styling before the switch. Less objects were shown at each zoom level. So you can have vector on your mobile device now, but at the huge cost of great simplification of the styling and the number of features shown at each zoom level. Is that the price you want to pay for having vector?