Geospatial capability has varied maturity in different systems, particular
of interest is those in Azure Cloud as compared to PostGIS.
Is there any publication on this topic?
Regards,
David
___
postgis-users mailing list
postgis-users@lists.osgeo.org
Got it, Thanks Regina!
On Tue, Aug 29, 2023 at 6:55 PM Regina Obe wrote:
> I doubt we’ll be ending support of 3.1 in 2024 but we haven’t voted on it.
>
> We still need to EOL 3.0 too which we haven’t voted on either.
>
> So 3.0 will most likely be in 2023. 3.1 probably not because we don’t
>
Shaozhong SHI writes:
> Geospatial capability has varied maturity in different systems, particular
> of interest is those in Azure Cloud as compared to PostGIS.
>
> Is there any publication on this topic?
Postgis lives firmly in the open source world so I suspect you are
getting a lot of silent
> Shaozhong SHI writes:
>
> > Geospatial capability has varied maturity in different systems,
> > particular of interest is those in Azure Cloud as compared to PostGIS.
> >
> > Is there any publication on this topic?
>
> Postgis lives firmly in the open source world so I suspect you are getting
I'm not sure this is considered Azure Cloud, but one more interesting tidbit
in the Microsoft Geospatial space and this I know because many people in
OSGeo seem to be obsessed by it.
This whole STAC and Earth Science wave dominating the market
Suprio Ray and Ahmed Eldway are two researchers that do a lot of spatial
computation work on big data (Hadoop, Spark, and parallel computation
frameworks). In my opinion, PostGIS is a more robust tool for spatial
operations. However other tools and platforms can be very good for specific
spatial
Hi Regina,
One quick question, as per doc regd EOL
The PostGIS project strives to support each minor version of PostGIS for
2-4 years after initial release and at the very least until the lowest
PostgreSQL version supported by the PostGIS minor version is EOL’d
For PostGIS 3.1(released in
I have performance related question as I noticed strange PostGIS behaviour
I can not explain, that degrades query performance.
I do have a table with North America continent split into 1mln irregular
sectors based on population density. Some of the sectors are 100mx100m
(cities) and some are
I doubt we’ll be ending support of 3.1 in 2024 but we haven’t voted on it.
We still need to EOL 3.0 too which we haven’t voted on either.
So 3.0 will most likely be in 2023. 3.1 probably not because we don’t like to
EOL two versions in 1 year.
Also if there is no pressing reason to EOL,
