I am experimenting with the new Map region, and seeing different runtime behaviour depending on the source of the geospatial data specified in the Geometry Column Data Type attribute.
Using the SDO_GEOMETRY setting with the OEHR_CUSTOMERS.CUST_GEO_LOCATION demo table column as the data source, a runtime error is reported in the browser console:
desktop_all.min.js?v=21.1.0-13:5 Server debug log message written: View Identifier = 973303386, Level = ERROR.
The debug log lists errors for all rows in the table where OEHR_CUSTOMERS.CUST_GEO_LOCATION is null:
SDO_GEOMETRY column for row with primary key 308 is NULL.
SDO_GEOMETRY column for row with primary key 308 is of the wrong geometry type.
SDO_GEOMETRY column for row with primary key 309 is NULL.
SDO_GEOMETRY column for row with primary key 309 is of the wrong geometry type.
...
However, when Geometry Column Data Type is set to Longitude/Latitude and the points returned as separate number columns, no error is raised:
select
c.customer_id
, c.cust_geo_location.sdo_point.x
, c.cust_geo_location.sdo_point.y
from
oehr_customers c
Treatment of rows with incomplete data where the geopoint is set to (0, null) is also different. When the source is SDO_GEOMETRY, these points are plotted on the map at (0°, 0°), whilst with data sourced from separate longitude and latitude columns they are not plotted at all.
Shouldn't there be consistent behaviour irrespective of the source of the data?