Bentley Map Enterprise (SS2) and Oracle 11g

Re: Bentley Map Enterprise (SS2) and Oracle 11g

IanTidy — Mon, 21 Feb 2011 00:26:30 GMT

I think that would be the best approach, or even if it defaulted to polygons but the user had the ability to change the geometry type in the GDI when it can't be discovered.

Re: Bentley Map Enterprise (SS2) and Oracle 11g

Martin Roy — Fri, 18 Feb 2011 17:58:21 GMT

Glad to hear you made it work. In any case, a geometry-specific index cannot be bad. I took note that it would be better to let users define the geometry type in GDI when it can't be discovered automatically.

Martin

Re: Bentley Map Enterprise (SS2) and Oracle 11g

IanTidy — Fri, 18 Feb 2011 01:18:23 GMT

Thanks Martin and Jerry,

In this case I was going directly from BM and not using the GSA, when you go from BM you don't have the ability to specify the geometry type (as pointed out by Jerry). In this case I wanted to open the data directly from BM because it is not maintained by any of our Bentley products, and therefore I didn't want to include it in a GSA model.

I have also had some issues (with Bentley Water) not recognizing features when they have been registered with the GSA. And I have had to run through the registration process multiple times to get it to work. Unfortunatley, I haven't been able to consistantly re-create the problem, so I have no idea what it could be.

Again, thanks for your help. I have modified my scripts that upload my data to this Oracle server, and now the GTYPE is being included in the creation of the spatial index and this has fixed my problem.

Re: Bentley Map Enterprise (SS2) and Oracle 11g

Jerry Walter - Bentley — Thu, 17 Feb 2011 18:59:51 GMT

Yea, but if he is not going thru the GSA and registering the features, then I beleive he will have to update the spatial index. I can't really tell from his screen shot if this is the case, but it looks like he is doing a direct connect and not going thru a project.

But I agree if Ian is going thru the GSA, to register features this would be a option.

Re: Bentley Map Enterprise (SS2) and Oracle 11g

Martin Roy — Thu, 17 Feb 2011 18:51:01 GMT

Ian, just as a side note, I did a quick test and as far as I can see Map SS2 should ask you to specify the geometry type of a class in the register features wizard if it cannot automatically detect it. You should be able to specify the type there instead of changing your indexes if you prefer to leave them as they are.

Martin

Re: Bentley Map Enterprise (SS2) and Oracle 11g

Jerry Walter - Bentley — Thu, 17 Feb 2011 00:30:41 GMT

Fantastic !!!!

Re: Bentley Map Enterprise (SS2) and Oracle 11g

IanTidy — Thu, 17 Feb 2011 00:28:15 GMT

OK, it looks like BM is using the index for the geometry type.

I changed my index (on one table to start with) and specified the geometry type in the index:

SQL> create index sewermain_sx on sewermain(geoloc) indextype is mdsys.spatial_index parameters ('layer_gtype=LINE');

Index created.

SQL> commit;

Commit complete.

SQL>

And now BM recognises this as a line.

So, based on this I am guessing that I need to go and change my scripts to specify the geometry types on the indexes of the files being uploaded.

Cheers Ian

Re: Bentley Map Enterprise (SS2) and Oracle 11g

Jerry Walter - Bentley — Thu, 17 Feb 2011 00:16:49 GMT

So just drop and recreate them as I have posted above.

Re: Bentley Map Enterprise (SS2) and Oracle 11g

Jerry Walter - Bentley — Thu, 17 Feb 2011 00:14:41 GMT

Fantastic ! Now look at the Spatial Index as Martin has suggested. For the different feature types we typically set them as follows:

Point

CREATE INDEX VAULT_GEOM_SIDX ON VAULT_GEOM(OGC_GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX PARAMETERS('layer_gtype=point');

Linear

CREATE INDEX CONDUIT_ROUTE_GEOM_SIDX ON CONDUIT_ROUTE_GEOM(OGC_GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX PARAMETERS('layer_gtype=curve');

Polygon

CREATE INDEX L_SUBMAP_SIDX ON L_SUBMAP(OGC_GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX PARAMETERS('layer_gtype=polygon');

Jerry

Re: Bentley Map Enterprise (SS2) and Oracle 11g

IanTidy — Thu, 17 Feb 2011 00:11:56 GMT

Martin,

No we don't specify the geometry type in the spatial index.

The SQL to build the index is simply

CREATE INDEX "ASSET"."SEWERMAIN_SX" ON "ASSET"."SEWERMAIN" ("GEOLOC")

INDEXTYPE IS "MDSYS"."SPATIAL_INDEX" ;

Cheers Ian

Re: Bentley Map Enterprise (SS2) and Oracle 11g

IanTidy — Thu, 17 Feb 2011 00:08:35 GMT

Hi Jerry,

I have run your query

"select p.geoloc.sdo_gtype, count(*) from asset.sewermain p group by p.geoloc.sdo_gtype;"

And the result I get is:

GEOLOC.SDO_GTYPE COUNT(*)

---------------------- ----------------------

2002 6473

1 rows selected

Cheers Ian

Re: Bentley Map Enterprise (SS2) and Oracle 11g

Martin Roy — Wed, 16 Feb 2011 18:20:39 GMT

Does your spatial index on that geometry column specify a geometry type or is it "collection" ? Not sure, but we may infer the geometry type from the index type.

Re: Bentley Map Enterprise (SS2) and Oracle 11g

Jerry Walter - Bentley — Wed, 16 Feb 2011 06:05:03 GMT

The Bentley Map help file suggest using this query instead, slightly different than yours.

select p.geometry.sdo_gtype, count(*) from <your_table> p group by p.geometry.sdo_gtype;

Jerry

Re: Bentley Map Enterprise (SS2) and Oracle 11g

IanTidy — Wed, 16 Feb 2011 05:28:13 GMT

Hi Jerry,

I have checked the GTYPE in the tables, and the are correct. The example below is the SEWERMAIN table.

SQL> SELECT a.geoloc.get_gtype() from asset.sewermain a group by a.geoloc.get_gtype();

A.GEOLOC.GET_GTYPE()

--------------------

SQL>

As you can see, this table has a GTYPE of 2 (which is a LINE or CURVE - See download.oracle.com/.../sdo_objrelschema.htm for details) and there is only one GTYPE for this table, but as you can see from my original post BM says this is a Polygon.

Any other ideas?

Thanks Ian

Re: Bentley Map Enterprise (SS2) and Oracle 11g

Jerry Walter - Bentley — Wed, 16 Feb 2011 03:29:41 GMT

From my experience, this is a issue with the gtype in the tables. It looks like all are defined as polygon. Also note that there can only be one gtype in a table, else the Oracle Spatial interface will not correctly register it.