Hi Mike
Thanks for pointing out the source of mentioned warning and nudging to a
solution.
Kind regards
Thiemo
24.06.2020 2:11:54 vorm. michael.smith.e...@gmail.com:
> You should try using the precision=no layer creation option. With the default
> of YES, it tries to set the precision on col
You should try using the precision=no layer creation option. With the default
of YES, it tries to set the precision on columns based on the first 50 values.
Often you have data that can exceed that. You could either precreate the table
with correct field definitions and then append, or set preci
Hei Bo
Well, I is just a project for myself so I made sverige superuser. :o)
Well again, I have on both ports PostGIS running but the 6543 has much
much more space. 5432 is on a small SSD so I moved from it to an
externel HDD.
As mentionned in the previous post, Thomas was right. I copie
Hi all
Eli, you are quite right. Typo of mine.
thiemo @ thiemos-toshi /mnt/schweden % ogr2ogr test.shp SCID_v4.0.gdb
HBVSv_intrans_HQloc100_rcp85_ensembleMean_diffPerc 2>/dev/null
Does work with me too, sort of. As you can see, I suppressed error
output. Without it, I get flooded with warn
Thimo -
The ogr2ogr command from your reply contains an factual error:
thiemo @ thiemos-toshi /mnt/schweden % ogr2ogr –f "PostgreSQL"
-overwrite –progress --config PG_USE_COPY YES
PG:"host='/var/run/postgresql' port='5432' dbname='sverige'
user='sverige'" SCID_v4.0.gdb
should be:
thiemo @
It looks to me like you are using two dashes: "--f" or perhaps an emdash,
and not just "-f" and that ogr2ogr thinks "PostgreSQL" is the name of your
datasource. Compare with how it is listed in your initial commands, as a
path.
On Tue, Jun 23, 2020 at 4:11 PM Jeff McKenna
wrote:
> Hi Thiemo,
>
Hi Thiemo,
What if you following my steps and create a new database (sverige2),
then connect to that empty database with ogrinfo, and then try ogr2ogr
on that new empty db.
-jeff
--
Jeff McKenna
MapServer Consulting and Training Services
co-founder of FOSS4G
http://gatewaygeo.com/
On 20
Hi Jeff
Thank you for sharing your steps. I tried to follow them and had an
insight though I am still stuck. I noticed that I was passing the gdb
file within the unzipped folder to ogr2ogr whereas you passed the
folder path. Switching to your pattern it looks as follows.
thiemo @ thiemos-
Hi Thiemo!
I have downloaded your data, to hopefully show you how I would tackle this.
First thing is to take this in very small steps, to confirm along the
way, otherwise you jump to ogr2ogr without confirming that it is even
possible on your system - in other words, live by *ogrinfo*, ogrinf
Hei Bo
Thanks for your suggestions. Unfortunately without effect.
The port is ok. I made a parallel PostgreSQL instance on a external
HDD. I tryed to use socket for efficiency. I use .pgpass file because
I am lazy . However, even when giving the password explicitely the
result is the same
Try change the line:
"PG:host='/var/run/postgresql' port='6543' dbname='sverige'
user='sverige'" \
to:
"PG:host='localhost' port='6543' dbname='sverige' user='sverige'" \
And:
Is port really 6543, not 5432 ?
What about the password ?, i.e something like: "PG:host='localhost'
port='6543' d
Hi
I am new to spacial data processing. For a project of mine I try to
load swedish climate data in to my PostGIS installation running/using
an openSUSE Tumbleweed installation.
I downloaded the data from
https://www.smhi.se/pd/klimat/rcp_scenario/scid/SCID_v4.0.gdb.zip
unzipped it and
12 matches
Mail list logo
