Can multiple geometry columns be selected in a spatial view for an outer join?

[JamesFox1]

Is there anyway to select multiple geometry columns in a spatial view for an outer join? I have several normalized feature classes and tables I need to join in spatial view and to show the multiple records. A spatial view is driven by the displyed geometries so to see both geometry columns but the sdotable command gives an error for more than one geometry column in a spatial view definition (I could try the prefered way for spatial views for ST_GEOMETRY columns of building a database view and registering it using sdelayer but I have not had any success building spatial views using this method!) 

The option would be to de-normalize and flatten these tables into one table but that would result in a huge number of redundant sparse columns from the join. We looked at using relationship classes and drill down into the normalized tables but our users would rather see one attribute table. 


Client: 10.0
Server: ArcGIS 9.2
           Oracle 10g (10.2.5)



-Jim

[JamesFox1]

As a workaround, I am able to build this query into a query layer in ArcMap which can be saved as layer file or a layer in an MXD but cannot be saved as database object. So to use this outer join this MXD or layer must be used or the outer join query must be constructed by the user in a new query view layer but it would be nice if this layer definition can exist as a database object as opposed to an operating system file.

As with the Spatial Views, only one geometry can be listed in the select list but the outer join selection of attributes can be done in this manner.

-Jim

[VinceAngelo]

No, 'sdetable -o create_view' does not support multiple geometry columns in a result set.

- V

[BrentPierce]

Layers in ArcGIS only support a single spatial field in the definition of the layer. This applies to �??Spatial Views�?� which were created through the ArcSDE Command Line Tools as well as Query Layers manifested as feature layers created through ArcGIS Desktop. When creating a Query Layer, the result set returned from the query can only have a single spatial field. With that being said, multiple spatial fields can still be used in the where clause of the query which defines the query layer. In this scenario, the spatial fields referenced in the where clause are used to restrict the rows returned from the query and will not be included in the fields (result set) returned to the query layer.

Hope this helps,
-Brent