1) if all the SQL requests required to produce a map are in the style file
or else if there are other SQL requests not if in this file ( and where they
are ).
Part of SQL is wrapping and table discovery logic in Mapnik's PostGIS
driver, look for all text strings in
>
>
> 1) if all the SQL requests required to produce a map are in the style file
> or else if there are other SQL requests not if in this file ( and where
> they
> are ).
>
Part of SQL is wrapping and table discovery logic in Mapnik's PostGIS
driver, look for all text strings in
-Message d'origine-
From: Paul Norman
Sent: Tuesday, March 20, 2018 9:51 PM
To: dev@openstreetmap.org
Subject: Re: [OSM-dev] about Carto and SQL
On 3/20/2018 1:40 PM, sav123 wrote:
Kompza covered the variables you mentioned, but I if you're looking at
benchmarking, I recommend
On 3/20/2018 1:40 PM, sav123 wrote:
Kompza covered the variables you mentioned, but I if you're looking at
benchmarking, I recommend you set up the full rendering stack rather
than trying to generate queries yourself. The latter can be tricky to
get right, and you have to handle parallelism
-Message d'origine-
From: Paul Norman
Sent: Tuesday, March 20, 2018 8:36 PM
To: dev@openstreetmap.org
Subject: Re: [OSM-dev] about Carto and SQL
Hello
Kompza covered the variables you mentioned, but I if you're looking at
benchmarking, I recommend you set up the full rendering stack
On 3/20/2018 9:13 AM, sav123 wrote:
I hope to be able to grab enough information to partition some or all
the postgresql tables and to publish the resulting comparison boards.
I know that it is possible to setup logs and to check them, but this
method may miss rare calls ...
Kompza covered
Hi,
This comes from Mapnik's PostGIS driver:
https://github.com/mapnik/mapnik/wiki/PostGIS#other-tokens
All SQL happens only on Datasource level.
вт, 20 мар. 2018 г. в 19:50, sav123 :
> Hello,
>
> Is there a documentation of the Carto sql mechanism ?
>
> In fact, I should want
7 matches
Mail list logo