Here's a slightly different way to do the same thing. Instead of using a
LEFT JOIN to find the non-split lines, it checks whether the result of the
ST_Collect of intersecting lines, and then either computes the split or
keeps the original input line.
WITH
data AS (
SELECT * FROM (VALUES
On Thu, Sep 5, 2019 at 6:38 AM wrote:
>
>
>
> Result*: all of the lines* from LayerToBeSplitted where copied into tmp2*,
> not just the ones NOT intersecting*, and I don't know how to
>
> get the attributes to be transferred to tmp2 for those new lines.
>
To get the lines from LayerToBeSplitted
I can find commands I used, but when I used \s, it did not work.
Regards,
Shao
On Thursday, 5 September 2019, Tumasgiu Rossini wrote:
> As far as I understand it,
> it is the way it is stored.
>
> Le jeu. 5 sept. 2019 à 20:49, Shaozhong SHI a
> écrit :
>
>> Can history be stored in a file?
>> R
As far as I understand it,
it is the way it is stored.
Le jeu. 5 sept. 2019 à 20:49, Shaozhong SHI a
écrit :
> Can history be stored in a file?
> Regards,
> Shao
>
> On Thursday, 5 September 2019, Tumasgiu Rossini
> wrote:
>
>> Hi,
>>
>> I don't know if it is possible.
>> I use the cygwin versi
Can history be stored in a file?
Regards,
Shao
On Thursday, 5 September 2019, Tumasgiu Rossini wrote:
> Hi,
>
> I don't know if it is possible.
> I use the cygwin version of psql, which has history.
>
> Le jeu. 5 sept. 2019 à 20:10, Shaozhong SHI a
> écrit :
>
>> How to put this right?
>> Regar
Hi,
I don't know if it is possible.
I use the cygwin version of psql, which has history.
Le jeu. 5 sept. 2019 à 20:10, Shaozhong SHI a
écrit :
> How to put this right?
> Regards,
> Shao
> ___
> postgis-users mailing list
> postgis-users@lists.osgeo.or
How to put this right?
Regards,
Shao
___
postgis-users mailing list
postgis-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-users
On Thu, 5 Sep 2019 at 15:24, Gerry Creager - NOAA Affiliate
wrote:
>
> I'll also go look at this thread, but would this apply to NetCDF "rasters" as
> well?
Source image format should not matter. It is not relevant to PostGIS
storage and operations.
Best regards,
--
Mateusz Loskot, http://mate
Hi,
This is how far I got today:
LayerToBeSplitted is of type MultiLinestrings
DROP TABLE IF EXISTS tmp;
DROP TABLE IF EXISTS tmp2;
CREATE TABLE tmp AS
WITH
data AS (
SELECT * FROM "LayerToBeSplitted" AS t
),
cutter AS (
SELECT the_geom FROM "LayerToSplitWith" AS t
)
SELECT *, ST_Split(d.t
I'll also go look at this thread, but would this apply to NetCDF "rasters"
as well?
Thanks
Gerry
On Thu, Sep 5, 2019 at 5:25 AM Mateusz Loskot wrote:
> On Thu, 5 Sep 2019 at 10:40, Tobias Gerdin
> wrote:
>
>> Hello,
>>
>>
>>
>> We are trying to create somewhat large rasters (30-40 bands of dat
On Thu, 5 Sep 2019 at 10:40, Tobias Gerdin
wrote:
> Hello,
>
>
>
> We are trying to create somewhat large rasters (30-40 bands of data
> comprising a few GB of data uncompressed).
>
Check posts of the "Large GeoTIFF ingestion by PostGIS" thread in the
archive
https://lists.osgeo.org/pipermail/po
On Tue, Sep 3, 2019 at 7:48 PM wrote:
> It is not possible to use update on the table when splitting one geomety
> to two.
>
For cases where you want to change number of rows in processing, there's a
CTE trick that is INSERT FROM DELETE, you can find an example in
ST_Subdivide manual page and ad
We specified ”automatic” tiling which apparently amounted to no tiling. Tiling
properly seems like a good approach, thank you.
Från: postgis-users För Nicolas Ribot
Skickat: den 5 september 2019 10:47
Till: PostGIS Users Discussion
Ämne: Re: [postgis-users] Max size of rasters?
Hello,
We are
Hi,
This sounds more like a general PostgreSQL question !
However, the main doc about comment is here : [
https://www.postgresql.org/docs/current/sql-comment.html |
https://www.postgresql.org/docs/current/sql-comment.html ]
And the comments are stored in PostgreSQL catalog tables: have a lo
Hi,
Where is comment data stored in PostGIS?
One can type in text in the comment box. Where is this content be stored?
Can the content be accessed by other desktop applications?
For instance, can ArcGIS import this content as metadata?
Looking forward to hearing from you.
Regards,
Shao
_
Hello,
>
>
> We are trying to create somewhat large rasters (30-40 bands of data
> comprising a few GB of data uncompressed). At some point the import into
> PostGIS is failing. Supposedly there is a 1GB field size limit in Postgres.
> Is it really so that you cannot have raster fields larger than
Hello,
We are trying to create somewhat large rasters (30-40 bands of data comprising
a few GB of data uncompressed). At some point the import into PostGIS is
failing. Supposedly there is a 1GB field size limit in Postgres. Is it really
so that you cannot have raster fields larger than 1GB? See
17 matches
Mail list logo
