Ari Jolma gmail.com> writes:
>
> Dash,
>
> I have only a limited experience with tiles and gdal2tiles, so I'm not
> sure the correctness of this but anyway. I'd also like to see if I have
> understood correctly, so please anybody correct if I'm wrong.
>
> The tiles are in a two-level directo
Dash,
I have only a limited experience with tiles and gdal2tiles, so I'm not
sure the correctness of this but anyway. I'd also like to see if I have
understood correctly, so please anybody correct if I'm wrong.
The tiles are in a two-level directory tree, where the top level has the
zoom lev
Hi everyone,
I have been sent an imagery dataset in what looks like an ADS imagery
format, and to my great surprise, it does not seem to be supported by GDAL.
The dataset is a directory starting with a set of header files
15_20140507_1441_RGBNN00L1.ads
15_20140507_1441_RGBNN00L1.hist
15_20140
Le mardi 22 septembre 2015 16:07:56, Maxime Demers a écrit :
> Hi,
>
> I have notice something bad when converting a geojson to mapInfo tab with
> ogr2ogr. The .dat which contain the table feature's properties is getting
> way too big after conversion.
>
> To test, I have converted a mapInfo tab
Hey folks,
I have a slight problem that is stumping me. I created a large set of
tiles using gdal2tiles only to notice that I was missing 2 images. So,
instead of creating all new tiles I created a set of tiles (with the same
extent) for just the 2 missing images. However, now I don't know how
Hi,
I have notice something bad when converting a geojson to mapInfo tab with
ogr2ogr. The .dat which contain the table feature's properties is getting
way too big after conversion.
To test, I have converted a mapInfo tab to geojson using:
ogr2ogr -f "GeoJSON" test.geojson test.tab
and then I c
