Latest Contributions by NicolasPy

‎01-31-2011

"If it has no geometry, it cannot participate in topological relationships. And if it cannot participate, it has no place being in a Feature Dataset (FD)." (dananrg ) i don't agree. Geodatabases (personnal, file or sde) works on DBMS theorys, including relation between tables and normalization (http://en.wikipedia.org/wiki/Database_normalization). Thus, a table has a place being in a fd...

‎08-24-2010

same as https://c.na1.visual.force.com/apex/ideaView?id=087300000008A49

‎05-31-2010

To link with "Provide a way to extend the topology rules framework" at https://c.na1.visual.force.com/apex/ideaView?id=0873000000087rgAAA

‎04-12-2010

'tables' means naturally 'standalone tables'...

‎04-11-2010

Would be nice if tables could be stored into FeatureDatatset. Now, the only place to write them is the geodatabase root level... Some tables belong to a FeatureDataset logical theme and so have to be into it.

‎04-11-2010

The rich APIs (either for flex, silverlight or javascript) should be able to consume, at least, non transactional OGC layers without development... I mean WFS, WMS, tiled WMS

Online Status	Offline
Date Last Visited	‎11-11-2020 02:24 AM

My Ideas

Latest Contributions by NicolasPy

Re: Allow tables to be stored into FeatureDataset

Re: Allow tables to be stored into FeatureDataset

Re: Additional Topology Rules and Functionality

Re: Allow tables to be stored into FeatureDataset

Allow tables to be stored into FeatureDataset

Full support of OGC layers in rich APIs

Re: Allow tables to be stored into FeatureDataset

Full support of OGC layers in rich APIs

Allow tables to be stored into FeatureDataset