New answers tagged

1

GeoServer uses the top of the spatial index to quickly compute a rough bounding box by default, but you can go in the store configuration and disable the "Estimated extends" flag, this will make it compute the bbox going row by row. Mind, with a few million rows that will take minutes, and the GeoServer UI will be locked down during all that time, all you ...


3

"In Oracle, calculating the distance on WGS-84 gets me the result in degrees." That can only happen if your geometries are defined without any explicit SRID (= SDO_SRID is set to NULL). In that case, the database has no clue about what you are actually storing: it does not know that your data is actually geodetic. All it sees is some numbers that it assumes ...


1

Have you tried specifying the units. Based on this https://docs.oracle.com/cd/B19306_01/appdev.102/b14255/sdo_objgeom.htm#i857957 "Unit of measurement: a quoted string with unit= and an SDO_UNIT value from the MDSYS.SDO_DIST_UNITS table (for example, 'unit=KM'). See Section 2.8 for more information about unit of measurement specification." I would think: ...


2

The problem comes from the projection name. In Oracle, the proper name for the 2SP Lambert Conformal Conic projection is "Lambert Conformal Conic" (notice: no "2SP", spaces instead of underscores). The following definition will work: 'PROJCS["Customized Lambert", GEOGCS["WGS 84", DATUM["WGS_1984", SPHEROID["WGS ...



Top 50 recent answers are included