#2 The specified coordinate exceeds the valid coordinate range

[Anonymous]

I can't define the precision or scale... it always gives me
this:

C:\>dbms2sde -o point -l test6,geometry -xname
Easting -yname Northing -zname El
evation -D sdedata -u sdedata -p ********* -key UID -i
sde_sql -x -1000000,-10
00000,1000000.00

DBMS2SDE alpha 0.341 Nov 5 2002 - an ArcSDE 8.1
application

Running: dbms2sde -o point -l test6,geometry -x -
1000000.000000,-1000000.000000
,1000000.000000 -xname Easting -yname Northing -
zname Elevation -key UID -i sde_
sql -D sdedata -s GISDATA -u sdedata -p ***********

For fastest performance, use -stable, -load, and -buffer.
Prior spatial layer; ignoring -x -1000000.000000,-
1000000.000000,1000000.000000
-- Using -200.000000,-110.000000,1000000.000000
Summary information for rows being spatially enabled:

Column Count Minimum Maximum Average
Std. Dev.
--------- ------ ----------- ----------- ----------- ---------
Easting 209808 1895000.010 1899999.993
1897617.227 1419.941
Northing 209808 870000.049 874999.992
872484.172 1458.059
Elevation 209808 230.700 485.320 344.056
55.235
UID 209808 1 209808 104904.50
60566.50

Disagreement in row count: 209808 versus 0
Key column(s) is not unique -- 0 duplicate rows may
have incorrect shapes.

Rows Enabled Elapsed Time Estimated Time
------------ ------------ --------------

X-coordinate does not convert to ArcSDE internal
storage format.
x-coordinate is 1895400.6920000000 and converts to
1895600692000, but must be an
integer between 0 and 2147483647.
Try adjusting x offset (-200.0000000000) and/or scale
(1000000.0000000000)
Y-coordinate does not convert to ArcSDE internal
storage format.
y-coordinate is 874999.9920000000 and converts to
875109992000, but must be an i
nteger between 0 and 2147483647.
Try adjusting y offset (-110.0000000000) and/or scale
(1000000.0000000000)
Failed attempt to spatially enable where "UID=1"

SE_shape_generate_point encountered a -139 error:
The specified coordinate exceeds the valid coordinate
range

WHATS UP WITH THAT

brianfitzgerald@richlandonline.com

[Mark Ohrenschall]

Logged In: YES
user_id=586167

I'm sorry that this message got buried in the verbose output, but after the performance hint dbms2sde warns that a
prior spatial layer exists, and it will use the scale and offset from the existing layer, and not from your command
line arguments. This means that you are updating a spatial layer that already had its scale and offset defined
(when you first ran dbms2sde on that table to create the spatial layer).

So you need to delete the spatial layer, i.e., run sdelayer -o delete and then rerun dbms2sde.

The message about the row count is curious, but let's take care of the simpler problem first.