2018-05-11 23:36 GMT+02:00 Martin Landa :
> --config GDAL_DRIVER_PATH C:\OSGeo4W64\apps\gdal-dev\bin\gdalplugins
>
> In progress, Ma
works like a charm, from 3 hours to 3 minutes! Thanks for packaging
gdal-mss :-) Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentor
Hi,
2018-05-11 23:15 GMT+02:00 Martin Landa :
> I missed on testing Windows server to install gdal-dev-mss package.
> But unfortunately, no improvement. BCP is still not working in my
oh, sorry for noise, I forgot to define
--config GDAL_DRIVER_PATH C:\OSGeo4W64\apps\gdal-dev\bin\gdalplugins
I
Hi,
2018-05-11 9:10 GMT+02:00 Martin Landa :
I missed on testing Windows server to install gdal-dev-mss package.
But unfortunately, no improvement. BCP is still not working in my
case. I tried all available drivers, same behaviour, I am getting to
be lost. Martin
--
Martin Landa
http://geo.fsv.
Jukka,
I believe I understood what is going on.
OSGeo4W builds do use libiconv for recoding and iconv is rather lax regarding
the spelling of
the source and target encodings. It supports at least "8859_1", "ISO-8859-1",
"ISO8859-1",
"ISO88591" and ..."ISO_8859-1" (or "LATIN1" as well)
Wherea
Andrew C Aitchison-2 wrote
> On Fri, 11 May 2018, Rahkonen Jukka (MML) wrote:
>
>
>> For example in my case I had to use exactly "-oo encoding="ISO_8859-1".
>
> ... with an odd number of quotes ? Wierd.
Sorry for lazy proof reading. In the command line exactly
-oo encoding="ISO_8859-1"
In htt
Hi,
I will send a download link for you. I made conversion into GeoPackage which
requires UTF8 encoding. In the following list OK means no warnings and
correctly UTF encoded characters (åäöÅÄÖ) saved into gpkg database. In the "not
a valid UTF-8" case I get warnings and non-ASCII characters are
On Fri, 11 May 2018, Rahkonen Jukka (MML) wrote:
I need to run a certain job that requires open option
"-oo encoding="ISO_8859-1" and while it runs fine on Windows with the
OSGeo4W installation with version GDAL 2.2.4, released 2018/03/19 it
leads to loads of warnings "Warning 1: Value of field
Jukka,
AFAIR there shouldn't be significant differences of behaviour in the shapefile
driver between
2.2.4 and 2.3.0 . Can you share the problematic shapefile ?
>
> Is there anything else that an end user could do for finding out why the
> gisinternals build fails with recoding?
Probably not
Hi,
I need to run a certain job that requires open option "-oo
encoding="ISO_8859-1" and while it runs fine on Windows with the OSGeo4W
installation with version GDAL 2.2.4, released 2018/03/19 it leads to loads of
warnings "Warning 1: Value of field 'name_field' is not a valid UTF-8 string."
Hi,
On behalf of the GDAL/OGR development team and community, I am pleased to
announce the release of GDAL/OGR 2.3.0. GDAL/OGR is a C++ geospatial
data access library for raster and vector file formats, databases and
web services. It includes bindings for several languages, and a variety
of comm
On mercredi 9 mai 2018 08:58:13 CEST Even Rouault wrote:
> Hi,
>
> No critical issues have been raised on RC1, so
>
> ---
>
> Motion: GDAL/OGR 2.3.0 RC1 is promoted to be the official 2.3.0 final
> release.
>
> ---
>
> My vote: +1
I declare this motion passed with +1 from PSC members:
Hi,
2018-05-10 19:18 GMT+02:00 Martin Landa :
> It took more than 3hours! Tested on Windows computer with SQL Server
> 2012. I used SQL Server Native Client 11.0.
sorry, typo, I have SQL Server 2014. Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
__
mj10777 wrote
> Would adding a '-gcp_file' as a input parameter, that would contain the
> list of gcp's to be used, be considered useful?
>
> Often the gcp list could be created programmaticly and saved to file,
> which
> would simplify the use from a script.
>
> Mark
Hi,
Have you tried the gen
13 matches
Mail list logo
