On jeudi 31 mai 2018 14:02:32 CEST Rahkonen Jukka (MML) wrote:
> Hi,
>
> I wonder what would it need to store vector tiles into GeoPackage instead of
> MBTiles. Officially probably a new extension like the Tiled Gridded
> Coverage Data extension, but wouln't it technically be rather simple to
> wr
On mercredi 27 juin 2018 14:51:23 CEST Deschamps, Benjamin (EC) wrote:
> Hi everyone,
>
> I am burning values from a KMZ into an existing GeoTiff. When I do it on the
> command line using gdal_rasterize (2.1.3), it works correctly:
>
> gdal_rasterize -burn 0 -dialect SQLITE -sql "SELECT * FROM My
Hi everyone,
I am burning values from a KMZ into an existing GeoTiff. When I do it on the
command line using gdal_rasterize (2.1.3), it works correctly:
gdal_rasterize -burn 0 -dialect SQLITE -sql "SELECT * FROM MyLayer WHERE (Name
IS NOT '01') AND (Name IS NOT '02')" myfile.kmz existingfile.ti
Homme,
>
> The contents of a tag might be a comma separated list for multiband
> rasters.
>
>
> Would an enhancement request to support this be acceptable?
Sounds reasonable to me. Do you intend to propose a PR for this ? Ideally you
would do the similar adaptation to the WMTS driver.
Even
Hello,
I'm currently running a TMS tile server generating geotiff tiles from DEM data
which I'm consuming with the GDAL TMS driver using an XML file along the
following lines:
http://localhost:8080/terrain/${z}/${x}/${y}.tif
-20037508.34
20037508.34
+1
Howard
> On Jun 26, 2018, at 1:41 PM, Daniel Morissette
> wrote:
>
> +1
>
> Daniel
>
>> On 2018-06-25 9:18 AM, Even Rouault wrote:
>> Hi,
>> Motion: GDAL/OGR 2.3.1 rc2 is promoted to be the official 2.3.1 final
>> release.
>> ---
>> My vote: +1
>> Even
>
>
> --
> Daniel Morissette
A S57 file with only 6 feature object classes? Normally there should be
many more.
I would add triggers to each table in the database for timestamps.
Potential workflow:
1 ogr for initial import into own schema
2 Postgre script, reading all tables in the schema using the
information_schema info