[postgis-devel] Separating spatial_ref_sys from installed and user

[Paragon Corporation]

Better not sure, but you can look at what I have to tackle this issue.  Look
at the one I use to build the extension exclusion.

In extensions/compute_srid_contiguous_ranges.sql (which generates the ugly
filter you see in 
Extensions/postgis/sql_bits/mark_editable_objects.sql.in)

Which inspired this article:
http://www.postgresonline.com/journal/archives/255-Finding-contiguous-primar
y-keys.html


Someone showed me a more elegant way on the related reddit thread:

http://www.reddit.com/r/Database/comments/uss09/finding_contiguous_primary_k
eys/?already_submitted=true


Though unfortunately it seems we have quite a few gaps people can sneak
srids into.

So ideal would be of course if we can flag.




Thanks,
Regina 

-----Original Message-----
From: postgis-devel-bounces at lists.osgeo.org
[mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Bborie Park
Sent: Saturday, June 08, 2013 8:29 PM
To: PostGIS Development Discussion
Subject: [postgis-devel] Separating spatial_ref_sys from installed and user

I'm trying to distract myself from writing so I'm working on creating a
partitioned spatial_ref_sys (ticket #1831).

I've got an implementation working but have an issue with filtering an
existing spatial_ref_sys table into PostGIS-provided vs user-provided piles.
Currently, I'm using a crude SRID filter.

PostGIS: (srid <= 32776 AND auth_name = 'EPSG') or srid = 900913

user-provided: srid > 900913

Is there a better solution to filtering PostGIS-provided srids?

-bborie
_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel