Hi Sandro! Thank you for the reply!
On Wed, Mar 16, 2022 at 3:18 AM Sandro Santilli wrote:
> Thanks Chris for your experience, comment below
>
> On Tue, Mar 15, 2022 at 08:27:37PM -0700, Chris Tooley wrote:
>
> > so I made sure
> > I copied the original `proj4text` string and bit the bullet and
On Wed, Mar 16, 2022 at 09:20:10AM -0400, Greg Troxel wrote:
> Sandro Santilli writes:
>
> > Another solution proposed was to still keep a single table but NEVER
> > automatically upgrade it, providing a function to select "system
> > entries" to use for populating the single table, when needed.
Sandro Santilli writes:
> So what you did was modifying what we call a "system entry"
> (srid=3310) to fix a (possible) bug you found in PostGIS itself.
>
> Now I guess you'll want YOUR version of the proj4text value to survive
> upgrades.
>
> At the moment PostGIS soft upgrades are NOT going
Thanks Chris for your experience, comment below
On Tue, Mar 15, 2022 at 08:27:37PM -0700, Chris Tooley wrote:
> so I made sure
> I copied the original `proj4text` string and bit the bullet and modified
> the table with the following query:
>
> > update spatial_ref_sys set proj4text = '+proj=aea
Howdy!
Pardon any mailing list _faux pas_ here, it's been a while.
It was suggested on IRC that I detail my experience on the mailing list
with the `spatial_sys_ref` table, specifically with this thread. Please
forgive me if there is any incorrect terminology, I am not a GIS expert, I
am but a
On Thu, Feb 10, 2022 at 09:10:38AM -0600, Jim Klassen wrote:
>
> How do other people handle conflicting srids?
That's a good question. For sure at the time PostGIS doesn't
give official advice about this. Current state of things is:
- PostGIS upgrade via EXTENSION won't touch spatial_ref_sys
On Wed, Feb 09, 2022 at 01:28:13PM +, Robert Coup wrote:
> On Fri, 4 Feb 2022 at 17:05, Sandro Santilli wrote:
> > - Do you ever update the table with entries from newer
> > spatial_ref_sys.sql ?
>
> Yes. We keep postgis' spatial_ref_sys synchronised with the Proj DB version
> we're
On Thu, Feb 10, 2022 at 10:43:29AM -0800, Paul Ramsey wrote:
> > On Feb 10, 2022, at 7:10 AM, Jim Klassen wrote:
> > How do other people handle conflicting srids?
>
> My guess is that it's pretty rare, since most people who have defined
> custom ranges for operational use have done what you
> On Feb 10, 2022, at 7:10 AM, Jim Klassen wrote:
>
> On 2/9/22 03:31, Sandro Santilli wrote:
>> Would you be disappointed/surprised by a PostGIS upgrade
>> replacing your custom entries above 20 with some new
>> "official" entry ? What strategy did you set in place to
>> prevent this ?
>
On 2/9/22 03:31, Sandro Santilli wrote:
Would you be disappointed/surprised by a PostGIS upgrade
replacing your custom entries above 20 with some new
"official" entry ? What strategy did you set in place to
prevent this ?
I missed the second part in my first reply.
As it stands it would
On Wed, Feb 09, 2022 at 09:55:14AM -0600, Jim Klassen wrote:
> I always thought it
> was cumbersome that I had to maintain the custom coordinate system in
> so many places (PROJ, PostGIS, older versions of GDAL, older versions
> of QGIS) when most of them are reaching back to PROJ to do the
Hi Jim,
On Wed, 9 Feb 2022 at 15:55, Jim Klassen wrote:
> I also looked into submitting the SRSs to EPSG so we could have official
> numbers assigned, but at the time they didn't appear interested in county
> sized coordinate systems.
For what it's worth, my understanding is that EPSG are
On 2/8/22 19:12, Greg Troxel wrote:
Paul Ramsey writes:
On Fri, Feb 4, 2022 at 2:23 PM Jim Klassen wrote:
We've been starting at 20 and using EPSG (misusing the "EPSG"
auth kept Proj 4/GDAL/MapServer happier, this likely isn't necessary
with Proj 8). We maintain matching record(s)
On 2/9/22 03:31, Sandro Santilli wrote:
On Fri, Feb 04, 2022 at 04:23:48PM -0600, Jim Klassen wrote:
We've been starting at 20 and using EPSG
I shall note 200,000 is also not in the "user range" as proposed in
https://lists.osgeo.org/pipermail/postgis-devel/2012-February/018440.html
Hi Sandro,
On Fri, 4 Feb 2022 at 17:05, Sandro Santilli wrote:
> The question I have for you is: do you keep your custom CRSs
> in the spatial_ref_sys table ? If so:
>
Yes.
> - How many ?
>
A dozen or so. We use 800xxx numbering for no particular reason, but we try
and avoid exposing
On Fri, Feb 04, 2022 at 04:23:48PM -0600, Jim Klassen wrote:
> We've been starting at 20 and using EPSG
I shall note 200,000 is also not in the "user range" as proposed in
https://lists.osgeo.org/pipermail/postgis-devel/2012-February/018440.html
The official PostGIS Manual doesn't
Hi,
Projections I use are all standard:
- EPSG:4326 for unprojected OpenStreetMap
- EPSG:3857 for tiles and quick 2D calculations
- EPSG:3395 for some legacy systems that can't go to 3857
- EPSG:4978 for 3D XYZ calculations like all-globe clustering
On Fri, Feb 4, 2022 at 8:05 PM Sandro
Paul Ramsey writes:
> On Fri, Feb 4, 2022 at 2:23 PM Jim Klassen wrote:
>
>> We've been starting at 20 and using EPSG (misusing the "EPSG"
>> auth kept Proj 4/GDAL/MapServer happier, this likely isn't necessary
>> with Proj 8). We maintain matching record(s) in our proj4 epsg
>> database
On Fri, Feb 4, 2022 at 2:23 PM Jim Klassen wrote:
> We've been starting at 20 and using EPSG (misusing the "EPSG" auth kept
> Proj 4/GDAL/MapServer happier, this likely isn't necessary with Proj 8). We
> maintain matching record(s) in our proj4 epsg database file (again this will
>
On 2/4/22 11:04, Sandro Santilli wrote:
- How many ?
Mainly one, but could potentially be up to every county in MN (87) as the
country coordinate systems generally don't have EPSG codes. Also OGR tends to
add entries automatically if it doesn't find a perfect match. This is mostly a
Sandro Santilli writes:
> Following earlier may from Regina, I'm writing this as a user
> inquiry, to get help in shaping the future of PostGIS handling
> of custom CRSs.
>
> The question I have for you is: do you keep your custom CRSs
> in the spatial_ref_sys table ? If so:
>
> - How many ?
- How many ? We have 54 custom entries that we store in
spatial_ref_sys.sql.
- Do you also keep the entries installed by spatial_ref_sys.sql ? Yes.
- Do you ever update the table with entries from newer
spatial_ref_sys.sql ? No.
On 2/4/22, 11:05 AM, "postgis-users on
Following earlier may from Regina, I'm writing this as a user
inquiry, to get help in shaping the future of PostGIS handling
of custom CRSs.
The question I have for you is: do you keep your custom CRSs
in the spatial_ref_sys table ? If so:
- How many ?
- Do you also keep the entries
23 matches
Mail list logo
