From 9d88a4659fe8b8d69d05a39cd28c1adc9efdd06a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?I=C3=B1igo=20Medina=20=28aka=20MacGyver=29?= Date: Fri, 29 Mar 2019 19:03:25 +0100 Subject: [PATCH] fix typo The output in the Developer Center is not being properly rendered just because of a typo in the headline format. --- docs/guides/02-general-concepts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guides/02-general-concepts.md b/docs/guides/02-general-concepts.md index a30b54d7..1d85b454 100644 --- a/docs/guides/02-general-concepts.md +++ b/docs/guides/02-general-concepts.md @@ -37,10 +37,10 @@ All the endpoints, which might be accessed using a web browser, add CORS headers **Note:** By default, CARTO uses vector graphics for map rendering. Please [contact us](mailto:support@carto.com) if you need raster rendering enabled as part of your requirements. - ### Mapbox Vector Tiles (MVT) +### Mapbox Vector Tiles (MVT) [Mapbox Vector Tiles (MVT)](https://www.mapbox.com/vector-tiles/specification/) are map tiles that store geographic vector data on the client-side. Browser performance is fast since you can pan and zoom without having to query the server. CARTO uses a Web Graphics Library (WebGL) to process MVT files. This is useful since WebGL's are compatible with most web browsers, include support for multiple client-side mapping engines, and do not require additional information from the server; which makes it more efficient for rendering map tiles. - **Tip:** You can process MVT files with the [`ST_AsMVT` PostGIS function](https://postgis.net/docs/manual-dev/ST_AsMVT.html) with the [Maps API Windshaft renderer](https://github.com/CartoDB/Windshaft/blob/1000x/lib/windshaft/renderers/pg_mvt/renderer.js). \ No newline at end of file + **Tip:** You can process MVT files with the [`ST_AsMVT` PostGIS function](https://postgis.net/docs/manual-dev/ST_AsMVT.html) with the [Maps API Windshaft renderer](https://github.com/CartoDB/Windshaft/blob/1000x/lib/windshaft/renderers/pg_mvt/renderer.js).