[postgis-users] Enormous file geodatabase feature class > PostgreSQL/PostGIS? + attribute column standardization app or process?

[Paul Ramsey]

On 2/19/08, dnrg <dananrg at yahoo.com> wrote:

> And are there any known limitations on the size of
> feature classes (or whatever they may be called in
> PostGIS) you can manipulate with reasonable speeds?

Tables, they're called tables. Why must everything be re-named in
ESRI-land? Oh wait, I forgot, "GIS is different".

People have loaded the 500M features of UK Ordnance Survey into
PostGIS. Refractions has 20M feature hydrology databases.  TIGER has
been loaded many times (50M features).

> My system will be an OLAP, not an
> OLTP--so once the data is loaded, there won't be much
> editing to speak of.

Then it won't be particularly concurrent.  It's write contention that
causes concurrency issues, not read contention.

> Finally, does it look like ESRI will ever open its
> geodatabase format in the way they've opened up the
> shapefile?

That is an issue worth exploring, since the official pronouncements
have said it would be open, but I never really thought it was worth
agitating over since the format hadn't "arrived". But it's part of a
shipping product now. Hm. Where's our open access?