[mapguide-users] Fdo2Fdo

[Paul Ramsey]

Yes, it's a very SDE-esque approach.  "There is just one way to store  
spatial data in a database: our way."  When you control the  
horizontal and the vertical, it must be mighty tempting to solve  
impedance mismatch problems through a fiat approach. (How does Bill  
Gates change a light bulb?  He doesn't, he just declares dark to be  
the new standard.)

P

On 6-Nov-06, at 11:30 AM, Frank Warmerdam wrote:

> Jason Birch wrote:
>> It believe that what this means in the short term is that it may  
>> be necessary to use Autodesk tools to populate it, and that you  
>> can not just access existing data.  Longer-term, I'm sure that  
>> "foreign" schema support will be added to this provider, but I  
>> think that this still requires that you keep the metadata in the  
>> same data source (possibly in a different schema?).  What I would  
>> really like to see is a third level of function where all of the  
>> mappings are kept internally to FDO without affecting the  
>> datasource.  I hope that over time FDO will give priority to "on- 
>> the-fly" access to my data without making the data store  
>> essentially proprietary to FDO.
>
> Jason,
>
> I'm with you on this one.  I am very frustrated to discover that  
> the FDO
> postgis provider won't support access to existing PostGIS  
> datasets.  It
> seems antithetical to what I think a "data access" api ought to be  
> doing
> for me.
>
> Best regards,
> -- 
> --------------------------------------- 
> +--------------------------------------
> I set the clouds in motion - turn up   | Frank Warmerdam,  
> warmerdam at pobox.com
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush    | President OSGeo, http:// 
> osgeo.org
>