Register features problem with oracle spatial

Offline Thad Clark-Soles over 8 years ago

I have several annotation sub features that are not being recognized as point / text features by the register features process. They are not showing up in the 'select columns for angle and x/y scale' dialog and the angle and scale properties are showing up as discovered properties.

The oracle spatial index is type multipoint.

I do have other text subfeatures that are multipoint and they are working.

Also after the register features process one of the features types is changed from point-text to linestring/curve.

map version is SS4 8.11.9.625 oracle 11g2

0 Offline Martin Roy Tue, Apr 19 2016 4:36 PM
Hi. I believe you are not seeing the angle and scale properties because the Geospatial Administrator is seeing your feature as linestring/curve. When we register sometimes we are not able to automatically determine the geometry type of a feature. In such a case I think we let the user change the geometry type. Could you verify if you can set the type of that subfeature to multipoint before advancing to the next registration wizard pages ?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Thad Clark-Soles Tue, Apr 19 2016 4:54 PM in reply to Martin Roy

They are set as point-cell/text features types prior to registration ( and the oracle index type is point or multi-point). There is no opportunity to change the feature type of these features during the registration process (the only feature type changes I see possible are the linear to linear collection and polygon to polygon collection changes dialog). Curiously they do show up in the point geometry text dialog.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Martin Roy Tue, Apr 19 2016 5:00 PM in reply to Thad Clark-Soles
Ok, so that means we do recognize them as point geometry which is good. The next thing I can think of is to check that the columns you want to use for angle and scale are defined using the proper numeric datatype in that subfeature table in Oracle.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Thad Clark-Soles Tue, Apr 19 2016 5:27 PM in reply to Martin Roy

I am using ms_angle, ms_x_scale and ms_y_scale all defined as number with no precision. My other point/ text features either primary or sub use this data type as well and work just fine.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Martin Roy Thu, Apr 21 2016 2:03 PM in reply to Thad Clark-Soles
Ok, thanks. I'm not thinking of anything specific that would cause this at the moment. Let's try to see if there are differences between the cases that work and those that don't. Any difference in the table name, maybe it's a view instead of a table, that sort of thing ?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel