SDO_GEOM.VALIDATE_GEOMETRY - Simple Im Sure
Hi all,
When trying to validate some geometries in oracle spatial using the SDO_GEOM.VALIDATE_GEOMETRY function I get the following error:
-6533 ORA-06533: Subscript beyond count
Does anyone know what this could be?
I'm using oracle 8i with PL/SQL Developer.
Cheers
Andy
Not sure whether this will do the trick but I have seem similar errors when trying to validate against unmigrated spatial data.
Might be worth executed the migration functions on the data then try again.
Similar Messages
-
N73 Help Simple im sure but i have no idea!!!
I am having trouble with my N73.
I either hold the power button or click it once then click switch off.
It never actually switches off it just goes to a screen which has the clock etc as it would if i left it for a period of time.
I don't know how to turn it back on after that either and am resorting to pulling the main battery out.
Can you please help this is a major pain for me and i bet its a small thing to fixthere's seems to be a fault, i'd suggest take it to a nokia repair center
Blackberry Bold -
Simple geometry gets ORA-29532 error on all SDO_GEOM calls
Hi all,
I have a single point in a table such that the query:
select SDO_GEOM.VALIDATE_GEOMETRY(geomObj, 0.05) from testvalid;
/* Returns */
SDO_GEOM.VALIDATE_GEOMETRY(GEOMOBJ,0.05)
'TRUE'However the query:
select SDO_GEOM.VALIDATE_GEOMETRY_with_context(geomObj, 0.05) from testvalid;Receives the following error:
ORA-29532: Java call terminated by uncaught Java exception: java.lang.NumberFormatException: empty String
ORA-06512: at "MDSYS.SDO_3GL", line 658
ORA-06512: at "MDSYS.SDO_GEOM", line 519
ORA-06512: at "MDSYS.SDO_GEOM", line 558
ORA-06512: at line 1The data itself is a single sdo_point:
select GEOMOBJ from testvalid;
/* Returns: */
GEOMOBJ
'(3001, , (174.092329032787, 129.420551704918, -71.2857142857142), , )'I think that the problem is something to do with the precision of the stored X, Y and Z values in the point because if I run the following:
update TESTVALID set GEOMOBJ.sdo_point.x = cast(GEOMOBJ.sdo_point.x as number(8,3));
select SDO_GEOM.VALIDATE_GEOMETRY_with_context(geomObj, 0.05) from testvalid;
/* Returns: */
SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(GEOMOBJ,0.05)
'TRUE'Similarly, running a direct comparison from an object made on the fly from the point's text representation works fine:
select SDO_GEOM.VALIDATE_GEOMETRY_with_context("MDSYS"."SDO_GEOMETRY"(3001,NULL, "MDSYS"."SDO_POINT_TYPE"(174.092329032787,129.420551704918,-71.2857142857142),NULL,NULL), 0.005) from dual;
/* Returns */
SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT("MDSYS"."SDO_GEOMETRY"(3001,NULL,"MDSYS"."SDO_POINT_TYPE"(174.092329032787,129.420551704918,-71.2857142857142),NULL,NULL),0.005)
'TRUE'Note that I only noticed this problem after upgrading from v11 to v11 R2. Also, the same ORA-29532 error comes up when running any of the SDO_GEOM.[x] function calls such as SDO_GEOM.DISTANCE(). The problem is not limited to SDO_POINT type geometries, yet the problem occurs only on some geometry entries in my database. It is repeatable in that the same geometry will continue to fail and the only solution I've found is to try to round down its precision in x, y, and/or z. I only know how to easily round down the precision for SDO_POINT types, so one of my problems is that I'm left with a whole scattering of other geometries that I can no longer spatially query.
The datas themselves were inserted from MATLAB (which connects using v11 Oracle ODBC Java drivers) which converts my coordinates to java.math.BigDecimal and binds them to an oracle prepared statement.
One possibility that I'm considering is that the insertion is done from various computers, some of which are 64-bit machines. Maybe somehow those machines are pumping in coordinates to a precision too great for oracle geometry?
Any help would be fantastic as I'm pretty lost here.
If the precision is indeed the problem, does anyone know how I can trim off those excess values after the decimal point for all geometry types?
Thanks,
Sven.The problem is with the way the ordiantes are created via java programs pre 11.2.
There was a bit alignment problem in the internal representation of the number when these numbers are created from a java program.
In 11.2 this corruption is fixed, but as a result the data that is already corrupted gives this "empty string" error.
It is very easy to fix. Follow the steps in the script below.
create or replace function id_geom ( g in sdo_geometry)
return sdo_geometry deterministic as
g1 sdo_geometry ;
idx number;
ords sdo_ordinate_array;
x number;
y number;
z number;
point_t sdo_point_type;
begin
if (g.sdo_point is not NULL) then
x := NULL; y := NULL; z := NULL;
if (g.sdo_point.x is not NULL) then
x := g.sdo_point.x * 10;
x := x / 10;
end if;
if (g.sdo_point.y is not NULL) then
y := g.sdo_point.y * 10;
y := y / 10;
end if;
if (g.sdo_point.z is not NULL) then
z := g.sdo_point.z * 10;
z := z / 10;
end if;
point_t := SDO_POINT_TYPE(x,y,z);
else
point_t := NULL;
end if;
if (g.sdo_ordinates is not NULL) then
ords := sdo_ordinate_array();
ords.extend(g.sdo_ordinates.count);
for idx in 1 .. ords.count loop
x := g.sdo_ordinates(idx);
x := (x*10.0);
x := x/10.0;
ords(idx) := x;
end loop;
g1 := sdo_geometry(g.sdo_gtype, g.sdo_srid,point_t,g.sdo_elem_info,ords);
else
g1 := sdo_geometry(g.sdo_gtype, g.sdo_srid,point_t,g.sdo_elem_info, NULL);
end if;
return g1;
end;
And then update the rows with geometry data with SQL like this:
update geom_table set geom = id_geom(geom); -
Simple polygon is not valid (ORA-13050)?
I am using Oracle Spatial 8i (DB version:8.1.7), but when i try to create a polygon and validate it, there is an error ORA-13050. Here are the details:
1.
CREATE TABLE TEST_GEOMETRY (
ID VARCHAR2(30),
GEOM MDSYS.SDO_GEOMETRY);
2. Insert a simple polygon:
INSERT INTO TEST_GEOMETRY VALUES(
'H',
MDSYS.SDO_GEOMETRY(
3003, null, null,
MDSYS.SDO_ELEM_INFO_ARRAY
(1,1003,1),
MDSYS.SDO_ORDINATE_ARRAY
(200,100,0,150,200,0,300,200,0,300,100,0,200,100,0))
3.
INSERT INTO USER_SDO_GEOM_METADATA(TABLE_NAME,COLUMN_NAME,SRID,DIMINFO) VALUES(
'TEST_GEOMETRY', 'GEOM', NULL,
MDSYS.SDO_DIM_ARRAY(
MDSYS.SDO_DIM_ELEMENT('X',0,800,0.5),
MDSYS.SDO_DIM_ELEMENT('Y',0,600,0.5),
MDSYS.SDO_DIM_ELEMENT('Z',-90,90,0.5))
4.
CREATE INDEX TEST_GEOMETRY_IDX ON TEST_GEOMETRY(GEOM)
INDEXTYPE IS MDSYS.SPATIAL_INDEX;
5.
SELECT SDO_GEOM.VALIDATE_GEOMETRY
(s.geom,
(SELECT diminfo
FROM user_sdo_geom_metadata
WHERE table_name = 'TEST_GEOMETRY'
AND column_name = 'GEOM')) STATUS
FROM TEST_GEOMETRY s
WHERE s.ID='H'
The output is: STATUS=13050
I have rechecked the polygon, but it is sure valid. Then why do i get the ORA-13050 error when i validate it?
thanks!sorry, i have solved this problem. It is because the direction should be counterclockwise for outer ring.
-
easy question I'm sure. imac hard full (500gb) mostly from iphoto. no capacity left. what are my options? I've thought of an external drive of 1tb and then a 2nd external drive of 3tb to back up both???? please help.
Those are the options - more space is more space.
Moving the iPhoto Library is simple:
Make sure the drive is formatted Mac OS Extended (Journaled)
1. Quit iPhoto
2. Copy the iPhoto Library from your Pictures Folder to the External Disk.
3. Hold down the option (or alt) key while launching iPhoto. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
Regards
TD -
SDO_RELATE AND SDO_GEOM RELATE MASK PROBLEMS
I am trying to use the SDO_RELATE operator on my spatial table.
I have been experiencing problems.
I also get the same problems if I use the SDO_GEOM.RELATE geometry function.
Background
Table2 contains about 20 000 rows.
Table1 contains about 1 000 000 rows.
Both tables contain area geomteries.
I can not get the following 'masks' to return any results.
-- OVERLAPBDYINTERSECT
-- COVEREDBY
-- COVERS
-- OVERLAPBDYDISJOINT
The all return -
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Elapsed: 00:00:20.00
However the mask INSIDE does work!!! And it returns the correct results.
The query syntax I am using is below. And substituting any of the above mentioned masks for INSIDE results in the ORA-03113 error.
I have validated all the geometies in my table using SDO_GEOM.VALIDATE_LAYER. They are all valid.
Query Syntax
SELECT /* ORDERED */ count(g2.parcel_ref)
FROM table2 g2
WHERE 1 < (SELECT /*+ ORDERED */ count(*)
FROM table1 g1
WHERE SDO_RELATE (g1.geometry,
g2.geom,
'MASK=INSIDE querytype=WINDOW') ='TRUE');
SELECT /* ORDERED ORDERED_PREDICATES */ count(g2.parcel_ref)
FROM table2 g2
WHERE 1 < (SELECT /*+ ORDERED */ count(*)
FROM table1 g1
WHERE SDO_FILTER (g1.geometry, g2.geom, 'querytype=WINDOW')='TRUE'
AND SDO_GEOM.RELATE (g1.geometry, 'inside', g2.geom,0.001)='INSIDE');
Does anybody have any ideas why all the masks (except INSIDE) fail?
Thanks,
BobDan,
I have finally got back to looking at my problem queries.
The first discovery I have found is that I can repeat the problem using one feature in one of the geometry tables.
You can see the syntax that I am using below. As I stated before, the INDSIDE query works, but the COVEREDBY fails.
OVERLAPBDYINTERSECT,COVEREDBY,COVERS,OVERLAPBDYDISJOINT also return the same ORA-03113 error.
SELECT /* ORDERED */ count(g2.parcel_ref)
FROM table2 g2
WHERE g2.id = 3658
AND 1 < (SELECT /*+ ORDERED */ count(*)
FROM table1 g1
WHERE SDO_RELATE (g1.geometry, g2.geom, 'MASK=INSIDE querytype=WINDOW') ='TRUE');
*** THIS ONE WORKS!
SELECT /* ORDERED */ count(g2.parcel_ref)
FROM table2 g2
WHERE g2.id = 3658
AND 1 < (SELECT /*+ ORDERED */ count(*)
FROM table1 g1
WHERE SDO_RELATE (g1.geometry, g2.geom, 'MASK=COVEREDBY querytype=WINDOW') ='TRUE');
*** THIS ONE DOES NOT WORK! The error is below.
SELECT /* ORDERED */ count(g2.parcel_ref)
ERROR at line 1:
ORA-03113: end-of-file on communication channel
I have also been running some other queries on my data.
Again, one query works, the other does not.
SELECT /*+ ORDERED ORDERED_PREDICATES */ count(*)
FROM table2 g1, table2 g2
WHERE g1.id = 194
AND SDO_FILTER (g2.geom, g1.geom, 'querytype=WINDOW')='TRUE'
AND SDO_GEOM.RELATE (g2.geom, 'overlapbdyintersect', g1.geom,0.0001)='OVERLAPBDYINTERSECT';
*** THIS ONE WORKS!
SELECT /*+ ORDERED */ count(*)
FROM table2 g1, table2 g2
WHERE g1.id = 194
AND SDO_RELATE (g2.geom, g1.geom, 'MASK=OVERLAPBDYINTERSECT querytype=WINDOW') ='TRUE';
*** THIS ONE DOES NOT WORK! Again, the error is below.
SELECT /*+ ORDERED */ count(*)
ERROR at line 1:
ORA-03113: end-of-file on communication channel
I have checked that the two problem geometries are 'valid'.
SQL> select sdo_geom.validate_geometry(geom, 0.001) from table2 where id=194;
SDO_GEOM.VALIDATE_GEOMETRY(GEOM,0.001)
TRUE
SQL> select sdo_geom.validate_geometry(geom, 0.001) from table2 where id=3658;
SDO_GEOM.VALIDATE_GEOMETRY(GEOM,0.001)
TRUE
Below is a print of the geometry of each of the problem features.
Have you got any ideas as to why the queries are failing?
Thanks in advance,
Bob
SQL> select geom from sample_lr_prm_iacs2002 where id=3658;
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
SDO_GEOMETRY(2003, 81989, NULL, SDO_ELEM_INFO_ARRAY(1, 1003, 1), SDO_ORDINATE_AR
RAY(475710.144, 133881.126, 475714.379, 133844.065, 475723.656, 133762.89, 47572
4.07, 133759.271, 475964.952, 133791.345, 475963, 133796.9, 475959, 133806.2, 47
5956.8, 133812.5, 475955.2, 133816.1, 475951.3, 133824.1, 475944.3, 133838.6, 47
5933.5, 133861.8, 475932, 133864.5, 475928.5, 133869.7, 475918.8, 133885.8, 4759
12.5, 133897, 475907.6, 133903.9, 475898.6, 133914.2, 475888.8, 133922.7, 475824
.2, 133974.3, 475809.9, 133976.2, 475808.1, 133974.6, 475805.5, 133972, 475796.3
, 133955.7, 475783.99, 133933.51, 475782.67, 133931.44, 475780.87, 133927.97, 47
5780.14, 133927, 475778.95, 133924.69, 475778.12, 133923.03, 475775.33, 133919.3
4, 475773.51, 133917.39, 475768.42, 133913.14, 475765.56, 133911.12, 475757.25,
133906.26, 475751.77, 133903.28, 475741.52, 133897.2, 475714.92, 133883.62, 4757
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
10.86, 133881.5, 475710.144, 133881.126))
SQL> select geom from table2 where id=194;
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
SDO_GEOMETRY(2003, 81989, NULL, SDO_ELEM_INFO_ARRAY(1, 1003, 1), SDO_ORDINATE_AR
RAY(467345.544, 109699.287, 467345.379, 109699.279, 467345.288, 109698.752, 4673
44.9, 109696.5, 467339.8, 109665.2, 467325.9, 109583.1, 467311.35, 109500, 46730
9.1, 109487, 467308.27, 109482.113, 467308.242, 109482.142, 467307.491, 109478.1
99, 467307.44, 109477.435, 467307.3, 109475.9, 467307.331, 109475.837, 467307.02
4, 109471.295, 467306.963, 109471.307, 467306.831, 109471.334, 467306.831, 10946
9.765, 467307.192, 109469.68, 467310.196, 109468.973, 467345.545, 109459.288, 46
7363.626, 109453.84, 467395.576, 109447.4, 467444.616, 109440.217, 467457.247, 1
09439.474, 467460.715, 109437.245, 467461.458, 109436.255, 467467.251, 109435.39
6, 467468.145, 109435.264, 467468.264, 109435.663, 467481.7, 109435.2, 467487.2,
109435.3, 467488.8, 109435.4, 467490.6, 109435.5, 467493.4, 109435.9, 467495.6,
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
109435.9, 467500, 109435.8, 467505.75, 109435.8, 467515.85, 109436.2, 467525.2,
109436.45, 467531.95, 109436.5, 467534.7, 109436.55, 467541.45, 109436.8, 46754
4.65, 109437.05, 467547.65, 109437.3, 467551.3, 109437.7, 467551.95, 109437.75,
467555.6, 109438.1, 467556.4, 109438.15, 467558.6, 109438.25, 467562.95, 109438.
35, 467585.5, 109439.1, 467593.55, 109439.35, 467597.5, 109439.35, 467600.45, 10
9439.3, 467603.65, 109439.35, 467606.8, 109439.3, 467607, 109439.3, 467610.15, 1
09439.2, 467613.35, 109439, 467615.7, 109438.8, 467618, 109438.55, 467620.3, 109
438.25, 467623.3, 109437.65, 467626.2, 109437.1, 467626.85, 109437, 467629.8, 10
9436.5, 467631.6, 109436.25, 467634.15, 109435.95, 467635.05, 109435.85, 467636.
95, 109435.7, 467637.35, 109435.65, 467639.25, 109435.4, 467640.1, 109435.25, 46
7641, 109435.1, 467643.7, 109434.5, 467644.3, 109434.3, 467652.15, 109432.45, 46
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
7653.35, 109432.2, 467654.4, 109431.95, 467656.8, 109431.25, 467658.35, 109430.7
5, 467659.75, 109430.15, 467660, 109430.05, 467662.95, 109429.15, 467667.25, 109
427.9, 467667.8, 109427.8, 467668.5, 109427.7, 467670, 109427.5, 467670.7, 10942
7.4, 467671.45, 109427.35, 467671.7, 109427.35, 467678.95, 109427.45, 467680.4,
109427.5, 467681.75, 109427.55, 467683.2, 109427.55, 467684.55, 109427.5, 467685
.95, 109427.45, 467687.35, 109427.35, 467688.55, 109427.25, 467695.4, 109426.55,
467696.8, 109426.45, 467698.15, 109426.3, 467699.55, 109426.1, 467700.75, 10942
5.95, 467703.45, 109425.35, 467703.95, 109425.2, 467708.85, 109423.95, 467717.8,
109421.4, 467721.2, 109420.5, 467726.4, 109419.2, 467729.8, 109418.5, 467731.45
, 109418.15, 467735.95, 109417.45, 467737.5, 109417.25, 467742.8, 109417.05, 467
748.2, 109416.7, 467748.95, 109416.6, 467749.7, 109416.45, 467750.5, 109416.3, 4
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
67752, 109415.9, 467752.75, 109415.65, 467753.4, 109415.45, 467753.95, 109415.2,
467754.55, 109415, 467755.1, 109414.75, 467755.6, 109414.45, 467756.15, 109414.
2, 467756.45, 109414, 467762.25, 109409.8, 467768.8, 109404.9, 467770.4, 109403.
7, 467771.3, 109403.1, 467771.513, 109402.932, 467772.658, 109403.214, 467772.92
9, 109403.281, 467777.496, 109404.803, 467790.963, 109405.789, 467804.758, 10940
7.103, 467810.013, 109407.431, 467821.181, 109409.73, 467831.035, 109410.716, 46
7843.188, 109412.03, 467849.757, 109412.686, 467853.992, 109414.38, 467854.15, 1
09416.85, 467854.85, 109427.6, 467855.35, 109436.3, 467855.75, 109443.95, 467856
.25, 109451.7, 467854.7, 109460.35, 467852.45, 109472, 467850.5, 109482.45, 4678
48.45, 109493.25, 467847.15, 109500, 467846.25, 109505.2, 467845, 109511.7, 4678
44.25, 109515.9, 467843.15, 109521.5, 467841.85, 109528.55, 467840.65, 109534.95
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
, 467840.05, 109538.2, 467839.65, 109542.4, 467839.05, 109548.35, 467838.55, 109
553.6, 467837.9, 109560.6, 467837.2, 109568, 467836.45, 109576.3, 467836.05, 109
581.45, 467835.45, 109588.4, 467834.55, 109597.9, 467833.1, 109614.5, 467832.35,
109622, 467831.2, 109634.4, 467830.6, 109640.2, 467830.55, 109640.5, 467828.5,
109642.15, 467824.2, 109642.3, 467821.1, 109642.35, 467819.75, 109642.4, 467818.
9, 109642.4, 467818.6, 109642.45, 467818.4, 109642.45, 467818.25, 109642.5, 4678
18.05, 109642.5, 467817.85, 109642.55, 467817.65, 109642.5, 467817.45, 109642.5,
467817.2, 109642.55, 467816.95, 109642.55, 467816.7, 109642.6, 467816.45, 10964
2.6, 467815.85, 109642.7, 467815.35, 109642.7, 467814.65, 109642.8, 467812.25, 1
09643.05, 467811.4, 109643.1, 467810.55, 109643.2, 467809.1, 109643.4, 467807.1,
109643.7, 467805.75, 109643.85, 467804.45, 109643.95, 467800.55, 109644.5, 4677
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
98.75, 109644.7, 467795.9, 109645, 467794.95, 109645.15, 467793.6, 109645.3, 467
792.15, 109645.55, 467790.65, 109645.75, 467787.25, 109646.05, 467782.8, 109646.
5, 467778.15, 109646.95, 467774.5, 109647.4, 467770.1, 109647.85, 467765.75, 109
648.3, 467760.85, 109648.9, 467753.35, 109649.65, 467748.7, 109650.1, 467745.15,
109650.45, 467741.05, 109650.85, 467739.95, 109650.95, 467736.45, 109651.35, 46
7732.1, 109651.95, 467729.1, 109652.3, 467724.95, 109652.7, 467723.05, 109652.95
, 467720.5, 109653.2, 467716.65, 109653.75, 467712.05, 109654.45, 467708.65, 109
654.9, 467704.45, 109655.4, 467700.35, 109655.95, 467695.65, 109656.65, 467692.4
, 109657.1, 467690.4, 109657.25, 467682.65, 109657.8, 467679, 109658.1, 467676.1
5, 109658.35, 467674.75, 109658.5, 467674.3, 109658.5, 467674.1, 109658.55, 4676
73.7, 109658.55, 467673.3, 109658.65, 467673, 109658.7, 467672.7, 109658.8, 4676
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
72.1, 109658.9, 467671.4, 109659, 467670.9, 109659.1, 467670, 109659.25, 467669.
75, 109659.3, 467668.75, 109659.4, 467668.3, 109659.4, 467667.85, 109659.45, 467
665.4, 109659.65, 467661.9, 109660.05, 467659.5, 109660.3, 467656.65, 109660.7,
467652.55, 109661.25, 467648.35, 109661.8, 467644.65, 109662.25, 467641.7, 10966
2.65, 467639.5, 109662.9, 467636.75, 109663.25, 467633.25, 109663.6, 467631.7, 1
09663.75, 467631.5, 109663.8, 467631.1, 109663.8, 467630.9, 109663.85, 467630.55
, 109663.85, 467630.35, 109663.9, 467630.2, 109663.95, 467629.85, 109663.95, 467
629.05, 109664.05, 467628.35, 109664.15, 467628.05, 109664.2, 467627.7, 109664.3
, 467625.95, 109664.55, 467623.15, 109665.1, 467622.85, 109665.15, 467622.6, 109
665.25, 467622.3, 109665.3, 467622.05, 109665.35, 467621.9, 109665.35, 467621.65
, 109665.4, 467621.4, 109665.4, 467621.15, 109665.45, 467620.95, 109665.5, 46762
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
0.7, 109665.6, 467620.5, 109665.65, 467620.3, 109665.65, 467619.8, 109665.75, 46
7619.5, 109665.8, 467619.15, 109665.8, 467618.45, 109665.9, 467616.8, 109666.1,
467613.2, 109666.6, 467610.15, 109667.05, 467608, 109667.3, 467605.85, 109667.5,
467603.75, 109667.7, 467602.25, 109667.9, 467601.05, 109668, 467597.05, 109668.
35, 467592.6, 109668.8, 467589.7, 109669.1, 467587.1, 109669.4, 467583.65, 10966
9.75, 467580.7, 109670.1, 467576.3, 109670.65, 467567, 109671.85, 467562.25, 109
672.4, 467556.85, 109673, 467553.95, 109673.3, 467550.35, 109671.95, 467545.1, 1
09670, 467540.35, 109668.3, 467539.9, 109668.15, 467539.75, 109668.15, 467539.6,
109668.1, 467539.5, 109668.05, 467539.35, 109668, 467539.2, 109668, 467539, 109
667.95, 467538.75, 109667.95, 467538.55, 109667.9, 467538.35, 109667.9, 467534.8
, 109667.7, 467530.65, 109667.35, 467523.9, 109666.75, 467519.5, 109666.4, 46751
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
6.2, 109666.1, 467511.8, 109665.65, 467508.1, 109665.3, 467504.85, 109664.9, 467
501.35, 109664.5, 467500, 109664.4, 467498.7, 109664.3, 467480.5, 109673.4, 4674
73.7, 109677, 467468.4, 109680, 467461.5, 109683.8, 467453.2, 109688.1, 467448.1
, 109690.4, 467441.4, 109693, 467439.6, 109693.6, 467430, 109696.2, 467424, 1096
97.7, 467420.3, 109698.5, 467419.444, 109698.653, 467419.409, 109698.708, 467397
.983, 109702.395, 467373.562, 109709.767, 467362.964, 109719.213, 467362.94, 109
718.668, 467362.504, 109719.213, 467347.528, 109705.39, 467346.459, 109701.945,
467346.01, 109700.498, 467345.636, 109699.291, 467345.544, 109699.287)) -
PLAYBACK - Missed something simple
New comer to FCE. have tried to read the helpPDF - big, isnt it?
Imported a .mov clip. Dragged into timeline - fine. Put audio deliberately out of sync, ok so far. I can not see how to playback to check the effect of out of sync. The VIEWER plays back the original clip. The CANVAS plays nothing back and then BEEPS when the out of sync audio should come in. There must be a way and its "simple" Im sure.
Any help gratefully taken.
Steve10Tom Wolksy is about (well- he was half an hour ago to reply to me) and he'd know the answer to the Can't Abide To Wait For Render in this case.
I had to accept that plight due to the fact that I was not able to import from my camera directly at one point (turns out the camera was set up wrong at first) and regularly ended up with rendering more than I was actually working on editing.
But that was because I was working with four layers of video to one imported HQ audio.
So- ARE you seeing a thin red line above your timeline window? -
Impossible d'utiliser After Effects CS6 11.2.2, sur MAC OS X 10.9.5
En essayant d'ouvrir After Effects un message d'erreur apparait : Impossible d'ouvrir cette version de l'application "Adobe After Effects CS6" avec cette version d'OS X. Vous avez "Adobe After Effects CS6 11.0.2.
Comment faire pour activer l'application ?
Merci de m'aider à résoudre ce problème.
AnyTMerci pour le retour rapide.
Bonne journée.
Pier..
Le 13 oct. 2014 à 17:26, any611 <[email protected]> a écrit :
Impossible d'utiliser After Effects CS6 11.2.2, sur MAC OS X 10.9.5
created by any611 in Forums en français - View the full discussion
Bonjour,
en fait je suis allé sur le chat en ligne d'Adobe (car ils n'ont pas d'aide par support téléphone) et là j'ai discuté avec des techniciens qui m'ont redirigé vers l'aide en ligne Américaine (ma licence est Canadienne) puis un technicien m'a aidé à faire la manipulation. Sur le chat en direct, il faut écrire le 1er message et attendre qu'un technicien soit libre pour répondre, cela peut prendre un peu de temps. Sinon, si je me souviens bien, j'ai téléchargé une mise à jour sur le site Adobe, là j'ai obtenu 2 icones, et j'ai simplement cliqué sur AF ingéniering en premier puis sur AF application, ensuite et tout s'est mis en place (si on clique directement sur AF application, ça ne marche pas). Mais je ne peux que vous conseiller de demander l'aide en ligne par chat qui à mon avis est très efficace.
Bonne chance.
AnyT
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at https://forums.adobe.com/message/6820144#6820144
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
To unsubscribe from this thread, please visit the message page at . In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Forums en français by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0. -
How to create point where validate_geometry find invalid geometry element?
Hi,
I'm intrested in, is it possible to find the coordinates (or create point layer directly) where sdo_geom.validate_geometry is not 'True'. I want to see wich element of the polygon has error, in a point-type layer.
Can anybody help me?
Thanx for advandce!
Edited by: user465421 on Sep 28, 2009 2:17 PMPost your questions here in Spatial
-
Oracle Spatial Performance with 10-20.000 users
Does anyone have any experience when Oracle Spatial is used with say 20.000 concurrent users. I am not interested in MapViewer response time, but lets say there is:
- an app using 800 different tables each having an sdo_geometry column
- the app is configured with different tables visible on different view scales
- let's say an average of 40-50 tables is visible at any given time
- some tables will have only a few records, while other can hold millions.
- there is no client side caching
- clients can zoom in/out pan.
Anwers I am interested in:
- What sort of server would be required
- How can Oracle serve all that data (each Refresh renders the map and retrieves the data over the wire as there is no client side caching).
- What sort of network infrastructure would be required.
- Can clients connect to different servers and hence use load balancing or does Oracle have an automatic mechanism for that?
Thanks in advance,
PatrickPatrick, et al.
There are lots of things one can do to improve performance in mapping environments because of a lot of the visualisation is based on "background" or read-only data. Here are some "tips":
1. Spatially sort read-only data.
This tip makes sure that data that is close to each other in space are next to each other on disk! Dan gave a good suggestion when he referenced Chapter 14, "Reorganize the Table Data to Minimize I/O" pp 580- 582, Pro Oracle Spatial. But just as easily one can create a table as select ... where sdo_filter() where the filtering object is an optimized rectangle across the whole of the dataset. (This is quite quick on 10g and above but much slower on earlier releases.)
When implementing this make sure that the created table is created such that its blocks are next to each other in the tablespace. (Consider tablespace defragmentation beforehand.) Also, if the data is READ ONLY set the PCTFREE to 0 in order to pack the data up into as small a number of blocks as possible.
2. Generalise data
Rendering spatial data can be expensive where the data is geometrically detailed (many vertices) esp where the data is being visualised at smaller scales than it was captured at. So, if your "zoom thresholds" allow 1:10,000 data to be used at 1:100,000 then you are going to have problems. Consider pre-generalising the data (see sdo_util.simplify) before deployment. You can add multiple columns to your base table to hold this data. Be careful with polygon data because generalising polygons that share boundaries will create gaps etc as the data is more generalised. Often it is better to export the data to a GIS which can maintain the boundary relationships when generalising (say via topological relationships).
Oracle's MapViewer has excellent on-the-fly generalisation but here one needs to be careful. Application tier caching (cf Bryan's comments) can help here a lot.
3. Don't draw data that is sub-pixel.
As one zooms out objects become smaller and smaller until they reach a point where the whole object can be drawn within a single pixel. If you have control over your map visualisation application you might want to consider setting the SDO_FILTER parameter "min_resolution" flag dynamically so that its value is the same as the number of meters / pixel (eg min_resolution=10). If this is set Oracle Spatial will only include spatial objects in the returned search set if one side of a geometry's MBR is greater than or equal to this value. Thus any geometries smaller than a pixel will not be returned. Very useful for large scale data being drawn at small scales and for which no selection (eg identify) is required. With Oracle MapViewer this behaviour can be set via the generalized_pixels parameter.
3. SDO_TOLERANCE, Clean Data
If you are querying data other than via MBR (eg find all land parcels that touch each other) then make sure that your sdo_tolerance values are appropriate. I have seen sites where data captured to 1cm had an sdo_tolerance value set to a millionth of a meter!
A corollary to this is make sure that all your data passes validation at the chosen sdo_tolerance value before deploying to visualisation. Run sdo_geom.validate_geometry()/validate_layer()...
4. Rtree Spatial Indexing
At 10g and above lots of great work went in to the RTree indexing. So, make sure you are using RTrees and not QuadTrees. Also, many GIS applications create sub-optimal RTrees by not using the additional parameters available at 10g and above.
4.1 If your table/column sdo_geometry data contains only points, lines or polygons then let the RTree indexer know (via layer_gtype) as it can implement certain optimizations based on this knowledge.
4.2 With 10g you can set the RTree's spatial index data block use via sdo_pct_free. Consider setting this parameter to 0 if the table/column sdo_geometry data is read only.
4.3 If a table/column is in high demand (eg it is the most commonly used table in all visualisations) you can consider loading (a part of) the RTree index into memory. Now, with the RTree indexing, the sdo_non_leaf_tbl=true parameter will split the RTree index into its leaf (contains actual rowid reference) and non-leaf (the tree built on the leaves) components. Most RTrees are built without this so only the MDRT*** secondary tables are built. But if sdo_non_leaf_tbl is set to true you will see the creation of an additional MDNT*** secondary table (for the non_leaf part of the rtree index). Now, if appropriate, the non_leaf table can be loaded into memory via the following:
ALTER TABLE MDNT*** STORAGE(BUFFER_AREA KEEP);
This is NOT a general panacea for all performance problems. One should investigate other options before embarking on this (cf Tom Kyte's books such as Expert Oracle Database Architecture, 9i and 10g Programming Techniques and Solutions.)
4.4 Don't forget to check your spatial index data quality regularly. Because many sites use GIS package GUI tools to create tables, load data and index them, there is a real tendency to not check what they have done or regularly monitor the objects. Check the SDO_RTREE_QUALITY column in USER_SDO_INDEX_METADATA and look for indexes with an SDO_RTREE_QUALITY setting that is > 2. If > 2 consider rebuilding or recreating the index.
5. The rendering engine.
Whatever rendering engine one uses make sure you try and understand fully what it can and cannot do. AutoDesk's MapGuide is an excellent product but I have seen it simply cache table/column data and never dynamically access it. Also, I have been at one site which was running Deegree and MapViewer and MapViewer was so fast in comparison to Deegree that I was called in to find out why. I discovered that Deegree was using SDO_RELATE(... ANYINTERACT ...) for all MBR queries while MapViewer was using SDO_FILTER. Just this difference was causing some queries to perform at < 10% of the speed of MapViewer!!!!
6. Consider "denormalising" data
There is an old adage in databases that is "normalise for edit, denormalise for performance". When we load spatial data we often get it from suppliers in a fairly flat or normalised form. In consort with spatial sorting, consider denormalising the data via aggregations based on a rendering attribute and some sort of spatial unit. For example, if you have 1 million points stored as single points in SDO_GEOMETRY.SDO_POINT which you want to render by a single attribute containing 20 values, consider aggregating the data using this attribute AND some sort of spatial BUCKET or BIN. So, consider using SDO_AGGR_UNION coupled with Spatial Analysis and Mining package functions to GROUP the data BY <<column_name>> and a set of spatial extents.
6. Tablespace use
Finally, talk to your DBA in order to find out how the oracle database's physical and logical storage is organised. Is a SAN being used or SAME arranged disk arrays? Knowing this you can organise your spatial data and indexes using more effective and efficient methods that will ensure greater scalability.
7. Network fetch
If your rendering engine (app server) and database are on separate machines you need to investigate what sort of fetch sizes are being used when returning data from queries to the middle-tier. Fetch sizes for attribute only data rows and rows containing spatial data can be, and normally are, radically different. Accepting the default settings for these sizes could be killing you (as could the sort_area_size of the Oracle session the application server has created on the database). For example I have been informed that MapInfo Pro uses a fixed value of 25 records per fetch when communicating with Oracle. I have done some testing to show that this value can be too small for certain types of spatial data. SQL Developer's GeoRaptor uses 100 which is generally better (but this one can modify this). Most programmers accept defaults for network properties when programming in ADO/ODBC/OLEDB/JDBC: just be careful as to what is being set here. (This is one of the great strengths of ArcSDE: its TCP/IP network transport is well written, tuneable and very efficient.)
8. Physical Format
Finally, while Oracle's excellent MapViewer requires data its spatial data to be in Oracle, other commercial rendering engines do not. So, consider using alternate, physical file formats that are more optimal for your rendering engine. For example, Google Earth Enterprise "compiles" all the source data into an optimal format which the server then serves to Google Earth Enterprise clients. Similarly, a shapefile on local disk to the application server (with spatial indexing) may be faster that storing the data back in Oracle on a database server that is being shared with other business databases (eg Oracle financials). If you don't like this approach and want to use Oracle only consider using a dedicated Oracle XE on the application server for the data that is read only and used in most of your generated maps eg contour or drainage data.
Just some things to think about.
regards
Simon -
A bizarre ORA-13349 case in 9i
Hi all,
We have just migrated from 8.17 to 9.2 and encountered a rather strange validation error on a particular polygon geometry.
Subject Geometry:
Parcel polygon composed of 4 polylines and 3 arcs.
Validation SQL:
SELECT SDO_GEOM.VALIDATE_GEOMETRY(SPATIALAREA, mtolerance) FROM PARCEL835105;
Error:
ORA-13349 (polygon boundary crosses itself) ONLY occurs when mtolerance is between 0.05 and 0.009. The geometry is considered fine when mtolerance is above 0.06 or below 0.008
Observation:
We examined the polygon using GeoMedia tool by traversing its vertices and could not find any apparent error.
If you want to try the geometry you may create the following files by cutting-&-pasting the content underneath each file heading. Then run at the system prompt (DOS) IMPORT.BAT usr/pass@connectionstring.
Bo Guo
Maricopa County Assessor's Office
Phoenix, AZ
602-506-0930
**************** PARCEL835105.DAT ********
1525|2003| |pt||||1|1005|7|1|2|1|5|2|2|9|2|2|13|2|1|15|2|2|19|2|1|21|2|1|;658946.23100000003|870467.35999999999|658884.96200000006|870464.85400000005|658829.65517262102|870462.59209484397|658778.28773826023|870459.781195155|658727.01800000004|870455.54700000002|658692.40116387932|870451.87949395797|658657.85900000005|870447.56499999994|658657.79700328002|870442.51112167106|658743.64884854865|870452.05702360102|658829.85199999996|870457.59600000002|658941.16799999995|870462.14899999998|658946.23100000003|870467.35999999999|:||||
**************** PARCEL835105.PRE ********
CREATE TABLE PARCEL835105 (
ID NUMBER(10,0),
SPATIALAREA MDSYS.SDO_GEOMETRY,
APN VARCHAR2(12),
FLOOR NUMBER(10,0),
DGN VARCHAR2(12),
SOURCE_CD VARCHAR2(2), primary key (ID) );
Exit;
**************** PARCEL835105.POS ********
insert into USER_SDO_GEOM_METADATA values('PARCEL835105', 'SPATIALAREA' ,MDSYS.SDO_DIM_ARRAY( MDSYS.SDO_DIM_ELEMENT('X', 232850, 993600, 0.03), MDSYS.SDO_DIM_ELEMENT('Y', 526000, 1134000, 0.03)), NULL );
Commit;
Exit;
**************** PARCEL835105.CTL ********
LOAD DATA
INFILE 'PARCEL835105.Dat'
APPEND INTO TABLE PARCEL835105
FIELDS TERMINATED BY '|' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
ID,
SPATIALAREA COLUMN OBJECT
( sdo_gtype INTEGER EXTERNAL,
sdo_srid INTEGER EXTERNAL,
isnull FILLER CHAR,
SDO_POINT COLUMN OBJECT NULLIF SPATIALAREA.isnull="pt"
( X INTEGER EXTERNAL,
Y INTEGER EXTERNAL,
Z INTEGER EXTERNAL),
SDO_ELEM_INFO VARRAY terminated by ';'
(SDO_ORDINATES char(38)),
SDO_ORDINATES VARRAY terminated by ':'
(SDO_ORDINATES char(38))) ,
APN,
FLOOR,
DGN,
SOURCE_CD )
**************** IMPORT.BAT********
@echo off
REM Copyright (c) 1999-2002 by Intergraph Corporation. All Rights Reserved.
Rem Use this script to create tables and metadata with PL/SQL and populate tables with SQL*Loader.
if "%1"=="" goto usage
SQLPLUS %1 @"PARCEL835105.PRE"
SQLLDR %1 CONTROL= PARCEL835105
SQLPLUS %1 @"PARCEL835105.POS"
goto end
: usage
@echo Syntax of the command is: "Import <username>/<password>@<ConnectString>"
echo Examples:
echo Import scott/tiger@db_orcl
: end
pauseDoc ID: Note:1020247.102,Subject: Validating Geometry Returns ORA-13349 or ORA-13356 [published @ metalink]
Problem Description:
====================
Validating geometries for polygons in the Spatial Data Cartridge, may give: ORA-13349: polygon boundary crosses itself or ORA-13356 adjacent points in a geometry are redundant However, examining the polygon data shows that there are no crossing lines and no redundant points. This error may also be raised by SDO_BUFFER, which will appear to create an invalid polygon. Solution
Description:
=====================
This is caused by the SDO_TOLERANCE being set to an inappropriate value for the data in the layer. The tolerance will be taken into account when validating whether two points are the same or if two lines cross.
Explanation:
============
SDO_VALIDATE_GEOMETRY generates an ORA-13349 when it detects that the geometric properties of the data are incorrect, and that the shape crosses itself. The reason for the errors is that the buffer function sometimes needs to generate very small shapes, typically circular arcs. There are situations where the ordinates generated have a precision higher than the SDO_TOLERANCE setting. Once rounded using the SDO_TOLERANCE setting, then it is possible that the shape appears to cross itself (ORA-13349). Setting the tolerance to 0.0 will remove the errors, since rounding will no longer happen. An simple example is if there are two points on the polygon: 2.60, 3.00 and 2.56, 3.00 with the tolerance set to .05 When rounded these will both appear to be 2.6, 3.00 and give the ORA-13356 error. Setting the tolerance to .005 would avoid this error. For SDO_BUFFER this error should not be reported from 8.1.6 onwards. -
Accurate distance between points, lat/long to miles?
Hi,
I have a bunch of points as lat/long data in SRID 8307 format. From reading this forum, I understand than in Oracle 8.1.7 to get accurate distances I need to transform these points into a cartesian coordinate system.
My data is US-based, so I am using SRID 32775 in a command like the following:
EXECUTE SDO_CS.TRANSFORM_LAYER('restaurant_locations', 'location', 'restaurant_locations_32775', 32775);
This creates a new table with new point geometries and a rowid that I assume points back to the original 8307 table.
I've tried creating an index on the new table with cartesian coordinates, but I get this error:
CREATE INDEX restaurant_csp_idx
ON restaurant_locations_32775(geometry)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS('SDO_LEVEL=9 sdo_commit_interval=1000 layer_gtype=POINT' );
2 3 4 CREATE INDEX restaurant_csp_idx
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13200: internal error [POINT] in spatial indexing.
ORA-29400: data cartridge error
ORA-13003: the specified range for a dimension is invalid
ORA-06512: at "MDSYS.MD", line 1673
ORA-06512: at line 1
ORA-13003: the specified range for a dimension is invalid
ORA-06512: at "MDSYS.MD", line 1673
ORA-06512: at line 1
ORA-06512: at "MDSYS.SDO_INDEX_METHOD", line 8
ORA-06512: at line 1
Here's the entry for the 32775-transformed points in the metadata table:
INSERT INTO USER_SDO_GEOM_METADATA
VALUES (
'restaurant_locations_32775',
'geometry',
MDSYS.SDO_DIM_ARRAY( -- 20X20 grid, virtually zero tolerance
MDSYS.SDO_DIM_ELEMENT('X', 1951908.05, 16230214.8, 0.005),
MDSYS.SDO_DIM_ELEMENT('Y', -6858801, 13168375.5, 0.005)
32775 -- SRID (reserved for future Spatial releases)
My questions are;
Do I need to build a new spatial index? It seems like once I transform the lat/long data to cartesian I need to build a new index as well ( on the 32775-transformed table ).
Is this the best way to approach distance queries with lat/long data? It seems like a lot of work, plus the second index and table really add to the overhead if a location changes.
Any ideas on why I can't build an index on the output table from my SDO_CS.TRANSFORM_LAYER() call? I used SDO_TUNE.ESTIMATE_TILING_LEVEL() and SDO_GEOM.VALIDATE_GEOMETRY() and got no complaints. I'm at a loss.
I also can't seem to get set autotrace to work. It works fine for any non-spatial query, but if I try to trace a spatial query, I get this error:
SQL> SELECT /*+ INDEX(restaurant_locations restaurant_sp_idx) */ r_a.restaurant_id
FROM restaurant_locations r_a, restaurant_locations r_b, user_sdo_geom_metadata m
WHERE r_b.restaurant_id != r_a.restaurant_id
AND SDO_GEOM.WITHIN_DISTANCE(r_a.location, m.diminfo, 1, r_b.location, m.diminfo) = 'TRUE'
AND r_b.restaurant_id = '5999';
2 3 4 5
RESTAURANT_ID
456999
456999
Execution Plan
ERROR:
ORA-01031: insufficient privileges
SP2-0612: Error generating AUTOTRACE EXPLAIN report
Statistics
49 recursive calls
28 db block gets
83 consistent gets
0 physical reads
0 redo size
415 bytes sent via SQL*Net to client
425 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
11 sorts (memory)
0 sorts (disk)
2 rows processed
I've looked at the arraysize, and I've made sure to run the trace-enabling sql and granted plustrace to my DB user.
Thanks for any help,
_jasonHi Jason,
The error on the index create is likely due to data being outside the bounds of the coordinate system as specified in user_sdo_geom_metadata.
If the data is stored in the point field then you can check the bounds by doing queries like the following, altering them for your table/column name (my table is cities_test, the geometry column name is location):
SQL> select min(a.location.sdo_point.x) from cities_test a;
MIN(A.LOCATION.SDO_POINT.X)
-157.80423
SQL> select max(a.location.sdo_point.x) from cities_test a;
MAX(A.LOCATION.SDO_POINT.X)
-71.017892
SQL> select max(a.location.sdo_point.y) from cities_test a;
MAX(A.LOCATION.SDO_POINT.Y)
61.178368
SQL> select min(a.location.sdo_point.y) from cities_test a;
MIN(A.LOCATION.SDO_POINT.Y)
21.31725
Do you need to build a spatial index?
Only if you are going to use spatial operators such as sdo_filter, sdo_relate, sdo_within_distance, and sdo_nn. If you have no requirements for these operators, then there is no reason to build a spatial index. From the trace query at the end of the posting, I suspect that you will need to have a spatial index.
Is this the best approach? Maybe, it depends on what your requirements are. If the data is static and performance is your highest priority, then maybe it is. If you have a requirement for a spatial index, then certainly it is. If you are only getting the distance between a few few known geometries, and you don't care about the time it takes to convert data on the fly, then you can use the sdo_cs.transform function within the sdo_geom.sdo_distance function to convert both geometries to the equal area projection.
The validation routines should have caught this - I checked and they do not for 8.1.7, and they do for 9i.
Regarding the set autotrace command, I'm not sure why it isn't working for you. It works for my generic scott/tiger account from a typical install.
hope some of this is useful.
dan
null -
Query for spatial data with a GeometryCollection fails
There are exact 538 CurvePolygons (only exterior rings at this
sample). All of them are valid geometries and equal in dimension
and so on. Now I connect them to a GeometryCollection and query
for other relating spatial data in some tables. It seems that
the use of around (not exact!) 200 CurvePolygon in one
GeometryCollection works fine but the adding of more
CurvePolygon result in an error with the Spatial Index (I could
add the ORA- error numbers if I have some data in my test tables
again next days).
Is there anybody else having trouble with these mysterious
problem? Maybe there is a border by the number of points in
GeometryCollection?
(More details, programming code could be delivered)
(working with Java 1.3.1, oracle.sdoapi.*, Oracle 8.1.7.)Hi Lutz,
Could you provide more info or samples of what is going wrong?
Also, could you try making sure the geometry you are passing in
as the query window is valid (i.e. instead of passing it in as a
query window, pass it into sdo_geom.validate_geometry).
Thanks,
Dan -
an unfinished " story " yet to be written as a script... and storyboarded etc ( not to mention revised a zillion times ).
Its the nature of my several unfinished projects to be sorta... well...
unfinished.
this could be the first " ever " ... " Movie Made In A Forum " !
ITS BEER THIRTY ! YIPEE !
ROBODOG, SPACE ALIEN, SAVING PLANET EARTH
Early Spring
'Robodog, Space Alien' by Rodney Bauer
1
Nobody expected, in their wildest dreams, the appearance of Robodog. The third planet from the sun had been spinning around lackadaisically, introducing another Springtime in the Northeast of North America with orbital regularity, giving everyone with the time or inclination to notice a feeling of mathematical certainty. On this particular day, where millions of earthlings could be seen driving about from high above the planet's surface, in Northeast North America that is, not one of them thought such a thing as Robodog even existed, let alone this was the day he would appear.
Dave was driving to work on the expressway in his car-like truck, listening to a news station on the radio. He wasn't concerned with electro-magnetic waves even though that's how he was able to chuckle in his self satisfied way at all the moronic things going on in the world, which the news was happy to focus on. "Ha Ha,” said Dave, after the news guy said, "The president of France has announced that America is arrogant.” Then Dave laughed again, "Ha Ha,” as the news guy said, "Germany doesn't want to go to war.” Meanwhile Dave was driving about 10 times faster than everyone else, weaving and dodging through traffic. He wasn't in a real hurry. This was the way he always drove. After 15 years of living too far away from where he worked driving 10 times faster than everyone else was just his way of catching up on having a life. Some of those he passed also thought about their lives, and how lucky they were the jerk who just sped by didn't slam into them. Dave didn't worry much about getting a speeding ticket, cause he had a little shield pinned to the inside of his wallet. Whenever he opened his wallet to get at his license the shield sorta popped right out, it was so shiny. That's because he had family members who were cops and firemen. Not long ago a lot of those guys got killed trying to rescue people trapped in the World Trade Center’s twin towers on 9-11. Nobody expected, in their wildest dreams, that someone would build the world's tallest buildings out of toothpicks and wood glue and then turn that model into a real structure that couldn't support itself. Oddly enough nobody caught on afterward there's a good chance many other buildings of the same impossible proportions are just as questionable. In fact, the owner of that part of the world wanted to build something just as big, maybe even bigger ! What a great idea.
Dave didn't feel the world spinning around. To him everything was steady and only his car and the slower cars around him were moving.
The feeling of normalcy which was unknowingly mathematically mushed into everyone's head by the planet's steadfast activity of spinning in space was shared by those whom some might say had lives hardly worth living. The hungry expected, as usual, to be hungry. The homeless, homeless, the wretched, hopeless, and so on. Most people are like bees. Bees are hard workers and collect pollen. Dave was like a worker bee insomuch as he would soon be working, and that would turn into honey, or food as the case may be, a mortgage payment, car payment, insurance payment, and so on. From way up it looked like everyone was moving around, some fighting, some laughing, some hanging out, but generally looking sort of busy. Lots of movement.
For thousands of years (nobody knows for sure) all the busy humans like Dave had fights over who was really in control, who ate the most. How to act. What's right. Who deserved what. That sort of thing. In the beginning it was brutal and in a way easy to figure out. Might makes right. Then people got civilized. Dreams like the ones that made a really tall building out of toothpicks started to make people less diligent about what is responsible and what is really silly. That's the nature of dreams. Some are great and some are silly. Some are a little of both. Throughout 'history' the on again off again advent of people who had big dreams, thinking the world was their oyster, and that it could be utopia, managed to amass great armies and kill a lot of people they didn't consider having lives worth living. That still goes on. Dave listened to news snippets about those things as he drove to work.
He listened to a snippet about how some jerks who didn't have two nickels to rub together murdered a neighboring family because they didn't have the same dot on their forehead, in some far away country, thank God, with rifles and ammunition that cost about three thousand dollars. Dave didn't even wonder how someone who can't afford to dig a well for water, so they can irrigate some land, and make a farm so they don't starve every few years, happened to have a three thousand dollar rifle and ammunition. How weird is that? Thinking of firearms Dave remembered how a few days earlier he had seen the president of the National Rifle Association, on the news, in an argument with some protesters who had disrupted his meeting of thousands of members, say, "I'll KEEP my rifle, YOU DAMN APE!” The N.R.A. president had been in a movie once about apes who ruled the world. The funny thing is, even though a lot of people only see movie stars on the news or in movies, they really feel they know those people. Someday someone might see the president of the National Rifle Association and say, "Ha Ha, YOU DAMN APE!" And the NRA president wouldn't have a clue what the heck the person was talking about, and might even have a bodyguard drag them away.
Way up in the sky, looking down on stuff, there's all these busy bee humans and mostly they are making ends meet, miraculously, since not a single one of them knew how the economy really worked, how someone who doesn't farm for a living can actually manage to eat anything. They manage by making cars that spew out poison gases, and zip around really fast in them. They get fat doing that, going fast, eating fast food, on the go. Why is 'fasting' a word for not eating? Should be the opposite, a word meaning 'gobble'. Also, they make do with producing things like movies and entertainment shows. They show people doing the most outrageous things, lots of killing and explosions. Lately there has been a shortage of utopia minded dreamers with the wherewithal to do anything about this crazy behavior. A shortage of Napoleons, Stalins, Hitlers, people like that. A lot of people like Dave, who do think of it once every 5 years or so, how the level of humanitarian diligence seems to be slipping, usually because of some family crisis, like some family member under 18 got pregnant out of wedlock or arrested or addicted to drugs or something, push the question aside as soon as possible, cause they don't know the answers and they hope they can just make enough money to get out of the rat race and then everything will be OK. "Ha Ha,” said Robodog. But he hasn't shown up yet, so nobody heard him.
Robodog's been around longer than people. But he hadn't been paying attention to earth during most of the time people have been spinning through space. He was busy elsewhere. He just got brought up to speed on things here recently. It didn't take long, because Robodog is smarter than humans. He can do just about anything. He doesn't show off, of course, and doesn't even consider that much of an option. He won't say where he came from, how old he is, what he can really do. But I'm getting ahead here.
When Dave parked his car-truck in the Silvercup East stage parking lot in Queens he stopped thinking about anything. This was an art he developed over the years, like driving a million miles an hour. It was simply the mental survival technique best suited to deal with the most curve balls thrown his way during the work day. In most businesses 'working' follows more or less the same predictable patterns and activities week after week. In the film business anything is possible. Most normal people can't survive long in this sort of atmosphere. Dave thrives in it.
In any normal business it follows that those most likely to successfully lead others will rise to the leadership positions. Like the military, where officers with the most experience and know-how will rise to higher rank to lead those less familiar with the rigors of war, most commercial business will also adhere to a common sense hierarchy. In the film business, contrary to the rest of the world, you will find people who normally wouldn't be given the responsibility of standing in a field shepherding a few sheep in charge of an entire department of men. In short anything is possible not only with regard to who is in charge but what will happen with the day's schedule. Dave's genetic and experiential qualities enabled him long ago to approach any film job, as soon as one foot hit the pavement out of his car cocoon, with a totally blank mind. A somewhat dead smile was the only indication his mind was blank, as he could function more or less normally even without thought.
On this particular day, much to Dave's credit, he is not the boss of his department. Instead someone else is boss, who is already racing around inside his own head with an overwhelming sense of fear and futility for the coming day's schedule, mostly worried about how to do twelve pages, and who is eating a breakfast burrito at the stage door Dave steps over to.
"Morning Tom,” says Dave.
"Mmmphh,” replies Tom.
Dave continues inside to the grip room, where he puts his coat, bag and morning paper down. Everything gets an immediate coating of sawdust. He goes outside again and says hi hi hi to everyone as he gets coffee from the catering truck and after a while, filled now with brief social pleasantries and coffee in hand, follows the slowly milling crowd of crew and extras into the stage to find out what is going to happen first. Meanwhile, his mind is still fairly blank.
"Well, it looks like we're just going to start with the same scene we were doing last night at wrap,” says Tom the key grip to the few grip crew members inclined to be next to him and find out what's going on. "Oh,” "OK,” "Ahhh, time for more food,” they mumble in response. There's nothing to do, it's lit already, everyone is content to find someplace to wait for the scene to be over so they can strike it and get on to the next one. Tom and some other department heads and production people mosey over to the set and mill about, some talking about what fun stuff happened in the last 10 hours since they left this same set the night before. The A.D. makes jokes and several walkie talkies are squawking away while someone tries to find out if talent is going to show up soon. The house lights go off, set lights on. Dave moves over to the camera dolly, his job on this show, and puts his coffee on the back. The brief thought, "It's a dolly, not a deli,” goes through his almost blank mind. It's not the first time he's had vagrant thoughts like that go flitting through his mind while on the job.
"OK, everybody, listen up!” says the A.D. Everyone tries to listen to those things that effect them or their departments. It’s hard to actually get a whole crew to listen to everything all day long. Minds wander.
"Talent will be here in 10 minutes, we're going to start off with scene 5….ugh…Mary?" Mary the script girl, right there when needed as usual fills in with, "Scene 5, take 4,” looking now over toward the camera guys, one of whom is doing the clapper and nods, while the others snicker over private jokes, and build the camera.
Suddenly, like a special effect nobody was anticipating, a gold colored dog appeared with a popping noise right in the middle of the set ! "POP!” Nobody moved except for heads turning in the direction of the popping noise. Then everyone just stared, frozen in their various attitudes, all suddenly quiet on the set.
"I am Robodog,” said the dog.
It's voice was electronic, not screechy or synthetic. Dave's mind went from blank to totally full in about 1 nanosecond. "Holy ****!" said Dave. He was the first to talk and that started the panic. Everyone yelled and a couple screamed, and all but Dave ran off the set in a rush, pushing and yelling more as they screamed at others on the stage what had just happened, more and more noise rising from outside the set walls, as a stampede of people exited the building in fear and confusion. Robodog just stood there, hadn't moved an inch since it first popped in, hadn't even moved its head or nothing. Dave was just like Robodog, he didn't move either, and even his mouth, when he said, "Holy ****,” had barely moved. The only thing that moved, and this with lightning speed, was Dave's thoughts, which came from out of nowhere, just like the dog.
A tingling sensation washed over Dave, like static electricity, as he stood transfixed behind the camera dolly, motionless as a statue. He began to look more closely at the dog's features, while slowly his head full of thoughts began to turn from confusion and nonsense to half formed ideas with beginnings and endings. The dog still didn't move. It was as if the thing was waiting for something. Dave hoped it wasn't waiting for him to make some movement, at which point it would do something awful and unexpected. Meantime Dave figured (the first real coherent thought since the dog's arrival) it was best not to move. Except his eyes. He moved his eyes, just a little, and started to try and figure out what in the hell this dog was. It wasn't real. That much was definite. Not a flesh and bone dog. It had skin like gold. Smooth. It looked like liquid almost. No joints were obvious, where it's legs, head, tail were connected. The legs just melted into the body sort of. There were no eyes. No mouth. It had two ears and also very thin antennas, two of them, one behind each ear, on top of it's head, with, and this he faintly thought amusing, a little ball of black material at the tip of each one. Like antennas you might buy for your kids at some space play land. Outside the set, somewhere near the doors to the stage, people were murmuring. Someone was explaining what had happened. Some authority had arrived maybe. Who? The stage manager? That wouldn't be much help Dave thought. This was something very different than a 'problem with the stage' sort of thing the stage manager was used to.
Then the dog moved. Just as Dave was thinking the stage manager wasn't going to be much help, that someone really important should deal with this thing, the dog's tail wagged. Several times, back and forth, just like a real dog! Dave almost jumped, did jump, inside, but outwardly he was still a statue. His hands were holding onto the dolly steering post as if he'd been doing the most difficult and tricky dolly move in the world, his knuckles almost white. He thought, "boom up" and "beam up,” in quick succession, more vagrant thoughts, of little use. He took a slow, deep, silent breath trying to make himself relax. Then his thoughts got back to normal. Not normal for a job, in which case he would be thinking nothing except "as needed.” Now he was really thinking normally, which in Dave's case was pretty good.
As if the dog sensed Dave's new found mental equilibrium, it's tail began wagging more, this time keeping it up, like a metronome, back and forth. It made the dog look friendly. "What are you?" asked Dave. Nothing. Then it's antenna vibrated slightly and it turned it's head toward the noises coming from beyond the set walls, toward the stage doors, toward where some people might be on their way back in to see what was going on. "Hey, anyone out there?" called Dave. "Hey, Dave is that you?” someone yelled back. The dog looked at Dave. Look is not really accurate. It had no eyes. It turned it's head toward him. It's head was like a short cylinder on a small cylindrical neck, connected to it's cylindrical body. All of it like liquid gold, reflecting lights and stuff like a mirror. It's head was now pointed at Dave. "****,” thought Dave, not having any idea what to make of this business. Robodog's feet were not like regular feet at all, but small flat rounded silver discs. "Hey, this thing is moving a little, and it's looking at me I think, and whatever you do, do it slowly,” called Dave to whoever was out there on the stage beyond the set walls. "OK,” said the voice out there. It was louder and closer. The dog looked away from Dave toward the set doorway, and just then the stage manager stuck his head into the doorway to see what was going on. He saw the dog and his eyes got wide. He sorta froze like that for a moment, no longer thinking this was some kind of joke everyone had been telling him outside. "What's that Dave?,” asked the stage manager. "How the hell should I know?” replied Dave.
"Well, look, it's wagging it's tail,” said the stage manager.
"No ****"
"Where'd it come from? Is it a prop or something?"
"Nope,” Dave said. Dave moved away from the dolly and the dog turned it's head to him. Dave stopped moving. The tail still wagged. The stage manager came slowly into the room, the dog turning to him now. Then, as if it suddenly lost interest in these two humans, the dog just walked around the set sniffing things, just like a real dog, wagging his tail, moving it's head around objects and the floor, making electronic sniffing noises! Dave took the opportunity to get the hell out of there and went outside. When he looked back, the dog was following him! It sniffed things on the way, but it was definitely following him. Everyone gave Dave and the dog lots of room, backing away, some running for a bit, before stopping to see what was going to happen. Everyone thought more or less the same thing, which was, "Wow!"
"OK, don't follow me, nice dog, go away now, go home now,” said Dave. Robodog acted like Dave hadn't said anything at all, but looked at him and stopped wagging his tail. They were just outside the stage door now, and Dave could see his car. Dave wanted to get in that car and be in his own space. He didn't know how big space really was, how he was in fact spinning through space on planet earth. Dave had bought the idea of car cocoons a long time ago, when he had his first car and turned on the radio and bobbed his head to the rhythm of his favorite music. That was a long time ago, before he started to drive really fast to catch up to something. The stage manager, thinking he was an authority over weird **** happening in his domain, walked briskly over to Robodog, emboldened by the dog's obvious affinity for Dave. When within a few feet, extending his arms as if to shoo the dog away, he said, "Hey, nice doggy, how bout we just get you…” Zap! That's what it sounded like. Everyone jumped, but mostly it was the stage manager who jumped, because this thin line of blue light went from Robodog's antennas right into the stage manager's chest, who got knocked backwards in mid stride and now sat on his butt on the pavement with a shocked look on his face. Everyone thought the same thing, "Wow!"
Then there was the sound of sirens coming closer. Dave thought that was predictable, here come the cops. Maybe they will know what to do. The A.D. said, "I called the police, everyone go over to stage B and wait, while they take care of this. Then we'll get back to work, but for now just go over there and wait, OK everyone?" The A.D. thought the show should go on. He wasn't sure what to do but this seemed a reasonable request. Some people were moving away toward their cars, and the announcement arrested their movement. Now they were interested in what the cops could do about this alien creature, sure they might witness some totally new event in the history of the world. Someone was taking pictures with a little video camera and speaking into their hand, just in case anyone watching later on couldn't figure out what was going on by image alone. The camera did not record any images though, which became apparent later on. Dave moved backwards, toward his car, slowly, still watching the dog who hadn't moved since zapping the stage manager. The dog matched Dave's movement, slowly moving forward, wagging his tail. Dave stopped, and 2 police cars came into the parking lot, their lights flashing and sirens droning down to a low rumble. When they stopped 4 police people got out and moved toward the crowd of crew people with the gold dog in the middle. They stopped, staring for a moment, as they became part of the crowd, all thoughts of normal police work out the window.
"My name is Robodog,” said the dog.
"What's going on here?” asked the most senior of the police officers. He addressed the dog but was half looking at the crowd, the sitting stage manager, and Dave, who was the one closest to, and the focus of the dog. Everyone started talking at once, some yelling louder and arguing a little about what happened, and the policeman had to yell "Stop!” to make everyone calm down. Dave was surprised that with all the noise, arm waving, pointing, and near panicky voices the dog hadn't seemed disturbed. It stood there now, looking at him, without wagging his tail, just waiting. "That dog stung me!” said the stage manager, still afraid to get up off the pavement.
2
"What? You don't say, uh huh, yeah, Oh, OK, sure, it did what? OK, hmmm.”
Nancy the secretary could hear what the assistant director of the F.B.I. was saying because the door to his office was open, as usual, and her desk was close by. Sometimes the door would be closed, but only when really important people came by to talk about sensitive things, or if Dick, her boss the assistant director, had to make some important phone call. This call had come to her through the switchboard operator and the person on the other end was a captain of a police precinct in Queens, which was unusual, and she wondered why a policeman would want to talk to her boss, an assistant director of the F.B.I. in Manhattan.
"You must be joking,” said her boss. "Right.” "Uh huh.” "OK, bye!” and he hung up the phone with a loud thump. "Nancy!"
"Yes sir,” said Nancy, as she scrambled out of her chair and hurried to the open doorway.
"Call information, get this Queens precinct on the phone, then ask for, uh, this officer, oh here, get this guy on the phone,” and he handed her a sheet of paper. On it was a precinct number, a name and several doodles of a small dog with lightning bolts coming out of antenna on its head. Nancy was used to weird things from her boss, so she didn't think twice about it, and dialed information, got the number for the police station, asked for the person on the paper, and heard a man say, "Yeah! It's me! See? It's NOT A JOKE!"
"Please hold on, sir, the assistant director will be with you in a moment, sir." She took a couple steps to the open door where her boss gave her an incredulous look, looked at the phone on his desk as if he were reluctant to pick it up, and then grabbed for it.
"Alright," he said, "So you're who you say you are, and this isn't a prank call. You expect me to believe an alien dog landed in Queens and you want me to do something about it? Are you OUT OF YOUR MIND?!" After a moment of silence and obvious discomfort from what the other man said Dick looked at Nancy and told her to tape the call, get the director on the phone, and call Bill Fenly. "OK, Captain, you've made your point, and now we're going to calm down and begin again from the beginning. I am taping this call now, so we all have a nice clear record of this conversation, OK? Good, now please state again what you believe has happened in your precinct, how you and your men have dealt with it and how you are asking for our assistance, just like you said earlier…for the record. When that's done I'm going to talk to my director, and some field agents who will be dispatched to the scene, and we'll also get in touch with the agencies we feel are necessary to contact, OK?"
Nancy thought, "Wow, something weird is going on,” and did as Dick had asked, first calling the Director’s office in Washington D.C. and then calling Bill Fenly. She got through to their secretaries only and they promised to have their respective bosses call the assistant director as soon as possible, which wasn’t fast enough for Dick but would have to do.
3
"Are you getting all this?” asked Deputy Director Bates over the shoulder of the technician on console 30 below Cheyenne Mountain.
"Yes sir,” and the technician wiped his forehead with a free hand while his other moved the mouse that moved the space based telescope and sensor array to keep up with his "bogey.” The unidentified object, now labeled "bogey 3,” was being looked at in real time, and a bunch of numbers on the large computer screen at console 30 gave constant data updates as to the objects location, speed, distance and so on.
"Good, you're doing great, just take it easy and stay with it,” Bates said, as he turned on his cell phone and dialed the White House.
Hundreds of miles out in space, looking down at earth, was a very large space ship. It had appeared out of nowhere, and surprised a whole lot of earth based space oriented spy equipment and personnel who ran the equipment. Several governments had alerted their armed forces and were scrambling around to respond to a military threat of some unknown source. About 30 seconds after the initial appearance of the spaceship 1/5 of the world's military establishments had gone bonkers and put into play all sorts of wild plans to save themselves from the unknown. 4/5th of the world had nothing they could do about it anyway, so they watched what the other guys did. If anyone had thought to fire something at the spaceship it wouldn't have had any effect, but nobody did that. For the first time in thousands of years humans acted with restraint. It didn't matter.
"Ugh, let me just confirm this with you, son, since we're both seeing this data here,” said Bates, now looking at the screen again. "That data I am seeing says this object is roughly 3 miles long, is that right?"
"Yes sir.”
"And it's in a stable orbit now?"
"Yes sir. Geosynchronous. I am hardly moving our sensor array any longer to keep up with it's movement. It is stationary now. I've never heard of anything like this before, sir. It didn't need to establish an orbit by increments, but appeared to just be there, if you know what I mean, sir.”
"Yes, I guess I do. Stay with it son, you're doing great.”
The room where console 30 was situated was very large. Cavernous. It was full of computers, consoles, screens, maps, and every high tech electrical gadget necessary for impressive global snooping and deployment of forces. It also had the average TV in a few places, usually so management could keep an eye on sensitive news around the world, which sometimes helped give them a well rounded view of what was going on from different points of view. At this time the TV picture that was on was replaced by a TV picture of what console 30 was looking at and tracking. Someone noticed it and brought it to everyone else's attention. All the TV's had the same image of what was on console 30. It was a public TV, and when someone changed the station, all the channels had the same thing. All the data and the image that console 30 saw was on all the TV channels. This was true around the whole world, though nobody knew that yet.
"Hey !” yelled Bates, "What the heck is going on here! This is supposed to be a secret !"
4
In Washington the House Of Representatives emptied out, everyone running for cover, except Senator McCain, as if a new dose of suspicious white powder had been discovered in someone's mailbox. They left messages on their answering machines, saying things like, "We're not in at the moment, but please leave your name and a message and we'll get back to you as soon as possible.” The White House smuggled various people out of town to house them in secret subterranean camps, safe from threats and able to carry on as the new government if something terrible happened to the old government topside. Alien spaceships appearing out of nowhere constituted a “threat” according to the protocol covering generic situations where nobody knew what was going on but things were far from normal.
Everywhere around the world people were talking about the alien spaceship. A lot of people, who had been fans of U.F.O. stories for many years, kept saying, "I told you SO!" They were no more prepared for what to actually DO now that one had appeared as anyone else. However, despite a lack of knowing how to react to the appearance of a spaceship those who always believed in them felt superior to those who didn’t believe in them, for the first time. Some of them thought they could now boss their family members around and wound up in fist fights. It was a short lived feeling of superiority for most. Many people kept looking up, although they couldn't see anything new, and many imagined seeing things that weren't there. From way up in the sky, looking down, the busy people rushing about with their daily lives seemed much the same as before. Only now a lot more faces could be seen (a few with black eyes), where before only the tops of their heads were visible.
Emergency meetings and high level talks rushed into session all over the world, but nobody saw those people on a day to day basis anyway, so they weren't missed. It seemed to those in the meetings and talks that the separations that existed between them and the rest of the world got more noticeable, and some of them wondered if whether it was a good thing to be "in control" at this time, because nobody was in as much control as they thought. Aliens with a giant spaceship put a very big question mark over everything. In some ways civilization was a very fragile thing.
Looting in Los Angeles began in earnest when the TV's started broadcasting console 30's images. Nobody knows why the people of Los Angeles go on a looting rampage whenever something of significance happens in the world. The city was unable to deal with it and called out the National Guard. There were a few National Guardsmen in California rather than in Iraq, and they came to Los Angles to watch people loot the city. Eventually everyone looting got pretty tired carrying heavy appliances and went home.
In isolated cases those who were angry got angrier. These, the disaffected people of the United States in particular, started yelling about how the government was corrupt, the President was evil, Corporations ran the world (not too far off on that one - but even a blind squirrel will find a nut sometimes), and now the aliens were probably going to demand free trade and further erode the working man’s ability to make a decent living. Luckily this sort of person stays home mostly, as few people in public places have much patience with them. Their spouses suffer the most. Some of these people couldn’t wait to ask the aliens what they thought about gay marriage and stem cell research.
The stock market plummeted and the exchanges had to stop trading to keep it from crashing. Gold prices soared. Many rich people thought they could go anywhere they wanted with their pockets full of gold, which they could trade in for food and so on.
The gold dog would change that, but not yet, and not in this story.
Some of the more far out alien worshipping church groups demonstrated in front of the U.N., appearing so suddenly and quickly after the TV showed the spaceship many people wondered how they could possibly get there so fast. The demonstrators chanted slogans about "Aliens Are Here To Save Us.” Oddly enough they were right. Some of the demonstrators wore little antennas on their heads. New Yorkers ignored them as they rushed back and forth trying to make money, which is just about all New Yorkers do nowadays. Well, not the younger ones so much, as they are generally living with roommates and have tons of social activities and boundless energy. Within an hour of the spaceship sighting the U.N. called together an emergency meeting of the General Assembly to address the issue. They could be seen making their way through the hundreds of alien worshippers, some of whom tried to sell alien antenna headgear to the diplomats, without much success.
Dave was still standing outside the stage, hoping against hope he could reach the safety of his car, with Robodog sitting close by, watching him.
5
Dave took out his cell phone and tried calling his home, to tell his wife everything was OK, which it wasn't, and for her to tell the kids not to worry, cause he was, and that he would be home soon, which was unlikely. If he had got through she would have seen through this typical Dave stuff right away, but she wouldn't have let on. As it happens his cell phone didn't work. He wasn't surprised, and looked at Robodog.
"Are you making my cell phone not work?” asked Dave.
"Affirmative,” said Robodog, which surprised Dave, since the dog didn't talk too often. It also surprised the crowd of people and police officers standing around wondering how long it would be before something solved this mystery of the dog's appearance and purpose, and when it would go away. Everyone knew about the spaceship, thanks to the fact the whole world was seeing it and talking about it. At the moment the dog was of more interest to these people than a spaceship hundreds of miles up in the sky. This dog, they figured, was certainly connected with the spaceship, or they would eat their hats.
A bunch of black cars drove into the now police protected gates to the stage complex and parked nearby. Some men in black suits got out and walked over to the crowd and one of the men in a black suit talked with the senior policeman near the crowd. As usual the newcomers had that bewildered look after seeing Robodog. Robodog didn't turn his head or move, but kept looking at Dave. The policeman introduced the stage manager to the man in the black suit, who turned out to be an F.B.I. agent. There was also a State Department agent, a D.E.A. agent, a C.I.A. agent and other agents who preferred to remain anonymous, who had come in the newly arrived cars. They all tried making calls on their cell phones, but found the phones didn't work. One went back to a car, but came out again quickly, because the car phone didn't work either. There was some muttering and mumbling and general conversation about procedure, plans and priorities. One of the men in black looked up into the sky but didn't see anything unusual. It was becoming a sort of nervous tic, looking up.
"Hey you guys,” said Dave.
Everyone looked at Dave now, instead of the dog.
"I'm going to get in my car and get out of here, if you don't mind. I've had enough of this standing around, and I don't care what the dog does, I'm getting in my car now.”
"You can't do that, sir,” said the F.B.I. man. "Nobody is going to do anything until our van gets here so we can get the dog in the van safely and without incident."
Robodog looked at the F.B.I. man. That made the man nervous, cause he hadn't seen the dog move before, hadn't seen how the reflections and skin of the dog shimmered and flowed when it moved. He was certain the dog was an alien now, there was absolutely no doubt the dog was not from anywhere on earth.
"Can you understand me, sir?” asked the man of Robodog.
"Yes,” said Robodog. "My name is Robodog. I am going with Dave in his car. Dave will be OK,” and Robodog looked over at Dave and wagged his tail, to reassure him. Dave thought, "Oh God, this is really one messed up day.”
Robodog said to Dave, "Come drive me in your car. I am a friendly dog. I won't hurt you or anybody, and you can't hurt me either, so don't worry." With that the dog just walked right over to Dave's car, whereupon the two front doors opened all by themselves, and Robodog jumped into the passenger seat, looking for all the world like a regular dog wanting to go for a ride. "Don't do it, sir, Stand where you are!” said the F.B.I. man. For some reason that bossy attitude bothered Dave, and the thought of driving away with the dog didn't seem such a terrible idea. Now he really wanted to get away from all these official agents and police people, and if the dog wanted to go with him, fine. He walked over to his car, and as he did a few of the agents started to move toward Dave, but stopped short as they felt themselves blocked by some kind of mushy invisible force. Like walking into a giant invisible marshmallow. "Don't go anywhere, that's an order!" they yelled at Dave. Dave got in the driver's side, closed his door, rolled down the window and said to everyone, "Look out, I'm driving out of here!"
Most of the crowd of film people moved aside and even started to think about getting in their cars too, and head for home, where they thought they might find out more about what was going on. But for now they couldn't budge from wanting to see what would happen to Dave and the dog. Some thought, "Poor Dave, he's bewitched or something by that dog,” while others thought, "Poor Dave, he's going to be alien-knapped.” But the agents and police people thought only one thing, and it was shared without variation by all of them, "That damn idiot and that dog are deliberately disobeying our orders!" The F.B.I. man, still trying to walk through the invisible marshmallow, drew his weapon and yelled, "Oh no you don't mister, GET OUT OF THAT CAR NOW!" The pistol went flying out of his hand and up in the air about 4 stories, where it veered over to land on the roof of the stages.
"Don't worry,” said Robodog, "We won't be harmed or stopped. Just drive out and take it easy, and head east when you can."
"OK,” said Dave. And he started his car, put it into gear, and headed slowly out of his parking spot, toward the front gate. What Dave saw as he drove slowly out was a magical invisible force moving everyone and everything slowly and carefully out of his way, as if a giant invisible hand was simply moving people and cars to the side. People's feet didn't move, but their whole bodies just kind of slid easily off to the side, staying in the same pose they were in when they began to be moved. It reminded Dave of a Christmas gift he gave to his mom one year. It was a music box with skating figures, and a little winter park scene around a frozen pond. The figures had steel disks for feet and inside the music box were magnets that moved under the pond, making the figures move about like gliding statues. The cars moved out of the way like that, the crowd, the agents, the police people at the gate, everything just slid away to the side. Their shouts and orders to Dave sounded muffled, as if he were surrounded by invisible cotton. "Oh boy,” said Dave, as he thought maybe he would take it easy driving for once, and not try to race anywhere to catch up with his life. He felt like everything was starting fresh. He sighed deeply, and thought, "Why me?” and drove away from Silvercup Studios.
After the shock of coming under some weird force field control was over, all the people in the Silvercup complex became themselves again, shouting wildly and waving their arms and running in circles as Dave's car drove out of sight.
"Did you SEE that?” said the stage manager to the script girl. She was crying and terrified and trying to get out of the crowd to her car, but she forgot where she parked it, and she got more terrified, thinking her forgetfulness was the result of alien stuff screwing around with her brain. The stage manager grabbed her, shook her like a rag doll, "I said, Hey, pay attention damn it," shaking her more, "This could be the end of the whole world, do you REALIZE THAT?!" The stage manager was losing control. He looked wild.
The police and many agents from all the agencies ran frantic to their cars and jumped in them so they could race after Dave. Some were already on their cell phones, yelling into them, "It's an alien DOG I say! It's loose! It's in a car now! It took control of us and moved us around with some kind of force field!" The people on the other end of these calls started to feel the panic of the callers. They wanted to be where the agents were so they could get things under control, since apparently the agents already there had failed to do so. "We are in pursuit now, and will keep you updated. Meantime, get the president to declare the city in a state of emergency, get the mayor on it, the governor, get the command center on it!" The cars screeched out of the Silvercup complex, a couple of policemen at the gate jumping out of the way just in time. The cars disappeared from view, but their sirens, horns and screeching tires could be heard for some time. Everyone they left behind also ran to their cars and starting talking on their cell phones, and with only a couple of minor fender benders, and a little screaming at each other, managed to get the hell out of there and head for home. The stage manager stared after them all, and yelled at them, saying, "It's the end of the world I tell you!” his eyes crazy.
6
Bates, at console 30, under the mountain, held a red phone to his ear as he watched the screen over the shoulder of his technician. The TV's still had the image of console 30, even after they tried to turn off console 30 and cut power off to console 30. For some reason console 30 would not be turned off and the TV's would not show anything but the image and data that console 30 saw through the space telescope and sensor arrays it was monitoring.
"Yes, Mr. President, It is a live image, real time, and it hasn't moved for the past 90 minutes. Yes, sir, we have patched all this data through to our space based platforms and several are within range of the U.F.O. Yes, Sir, I understand."
Just then, just when Bates was on the point of feeling confident about the president's calm sensibility, the alien space ship turned about 30 degrees in half a second, as if it had simply snapped around, and then shot off so fast it almost looked like it disappeared. As Bates tried in vain to think something could possibly move that fast, especially in space, the president asked if what he just saw on TV was what Bates saw on console 30.
"Yes, sir. Uh, yes, it just turned and shot off. The last data on it's speed, before it went off the scale, or out of range, was something like close to half the speed of light, sir. I think it was still accelerating, by the figures we see here, sir. No, nothing has it anymore,” Bates was looking around the cavernous room and everyone was waving and saying "it's gone from here,” indicating nothing under the mountain had any more contact with the space ship, "It's just gone I guess.” He hung up the phone, the president had hung up already, and asked the technician, "Do you think it was accelerating when we lost it?" "Yep,” said the technician. Then he whistled like he was very impressed. The TV's switched back to their regular channels and on the closest one to console 30 there were several people wearing gym clothes exercising on tubular frames with giant rubber bands. Some of the people in the room got embarrassed, thinking, gee, I hope the aliens don’t see this ****. They would think we're a bunch of morons.
7
"Get the dog? Yes sir, we're trying, I mean, we're looking for it sir!” the F.B.I. man said into his cell phone. His driver was speeding along Queens Blvd heading east, with his siren wailing away. Pedestrians jumped and ran out of crosswalks as the car and those behind roared through the intersections, the bruised pedestrians screaming after the cars, "You idiots!" Luckily the pedestrians had a lot of practice diving out of the way of cars in the intersections, due to the almost death a day rate of pedestrians being struck by cars. The road was a virtual highway through the most populated residential areas of Queens. "I feel we may have lost it though, just to let you know, sir.” The F.B.I. man hated to say that, and he winced as he did, knowing that his boss on the other end of the cell phone was going to explode like a stick of dynamite.
Dave drove as if it was a perfectly normal day on the expressway heading east, the dog sitting on the floor of the passenger side, his head resting on the seat. His little antennas vibrated now and then from bumps in the road, but otherwise he was motionless. Now and then Robodog would issue a little electronic sounding "woof.” As if it was thinking aloud.
"Sooo,” said Dave, still looking straight ahead, thinking now would be a good time, not knowing how much longer he would be alive this day, to get to know the dog a little, "Do you think you could tell me a little about yourself before the authorities catch us and we end up dead?"
"We won't be harmed, Dave, Don't worry.”
"OK, let's say that's true, sooo, tell me about yourself anyway. What are you doing here, for example? What ARE you, for example? Call me crazy, but somehow I don't think it's going to be a simple answer, and I'm not the smartest guy in the world, so could you tell me without getting too technical? Keep it simple?"
"Sure. I am Robodog. I am from another planet. Your planet needs some help. I am here to help."
Dave glanced at Robodog, who was still in the same position, his head resting on the passenger seat. The voice of Robodog seemed to come out of the front of the dogs head, where you would think he'd have a mouth, if he had a mouth. But it's head was a solid cylinder, even though it didn't look solid really, being made of that weird gold material that wasn't earthly. "Are all the, um, people from your planet like you? Are they all your shape?"
"No. I am not a people or anything like the beings on any planet. I was made. I am a robot. I am half dog, and half junk yard, Ha Ha Ha Ha,” laughed Robodog.
Dave thought maybe the dog was going nuts, and glanced at it again. At this point the dog also glanced at Dave and a very quick, darting 'smile' appeared on the front of Robodog's head. It was uncanny. The skin or substance of it's head simply morphed into a quick smile, with teeth and dog lips, and then disappeared, to become the cylinder again. Dave swerved but got control swiftly and took a deep breath.hehe.. yeah, i have to admit when I saw this " super pee wee IV " I was flabbergasted...
chapman is cool.. emailed them and a tech guy ( on the road no less -- out of office ) called me and we had a nice chat ...he explained quite a lot of stuff on phone..and will send me pdf attached to email etc..( manual ).
he answered the most pressing questions I had re: the new stuff on it.
very cool ... nice company.
like theres this " lever" thing that I found out is to basically " correct" for different wheel positions to line up the " round " steering radius... know what I mean? so the rear wheels match the correct radius of round 'radius' at different angles OUT from the chassis....maybe you have to see it to get this...but anyway, when I saw this lever I had no clue what it was...
luckily that job was locked off burning some stupid door frame keyed against black...and all I had to do was put camera on and roll it somewhere and put brakes on...and boom up and down now and then...to line up shots... easy. Otherewise I woulda been screwed...the dolly is so new...which is why I pursued the issue today...
moving on to the next thing... shiny text stuff is ( odd but I shoulda known this already ) only really effective when its moving and the reflections are 'changing'... once it settles.. to a still frame... it loses a lot.. ( separation from background etc then becomes an issue , plus levels of text etc at that end frame ).
see sample...end frame...new deal... ( new camera title safe area etc )
SOOOO, this adds more challenge... the end (static) frame of shiny text as titles.
I tried moving the " light" ( animated ) to see what happens with surface .. and lo and behold.. guess what? NOTHING HAPPENS ! LOL.... wasted about an hour on THAT baloney....so I am learning and figuring out what I can do and so on.. having fun... last night thought up all sorts of crazy " title sequence " and " trailer" scenarios... but I'm still in the extremely baby stages of this..
At least I made a new camera and got the thing positioned for basic title safe frame.. and got a bunch of nasa and hubble images... and will test some more now...and guess what ??
ITS BEER THIRTY ... YIPEEE ! -
Submitting multiple job on teh same table via trigger
Hi All,
I have a trigger that run multiple jobs using dbms_job on the same table. I am trying to refresh two materialized views complete via dbms_job.
Issue is when data is inserted into NET_CAB table , the trigger kicks off the bothe procedures but only the first materialized view is refreshed and not the other one.
Attached is the trigger, the procedure and materialized view
<pre>
create or replace
TRIGGER NET_CAB_TRG
AFTER INSERT OR UPDATE OR DELETE ON NET_CAB
DECLARE
pbl NUMBER;
pbl1 number;
BEGIN
SYS.DBMS_JOB.SUBMIT( JOB => pbl,what => 'P_CAB_PROC;' ) ;
SYS.DBMS_JOB.SUBMIT( JOB => pbl1,what => 'P_CABAS_PROC;') ;
END;
</pre>
<pre>
create or replace
procedure P_CAB_PROC
is
BEGIN
dbms_mview.REFRESH('P_CAB','C');
COMMIT;
END;
</pre>
<pre>
create or replace
procedure P_CABAS_PROC
is
BEGIN
dbms_mview.REFRESH('P_CABAS','C');
COMMIT;
END;
</pre>
<pre>
CREATE MATERIALIZED VIEW P_CAB
BUILD DEFERRED
USING INDEX
REFRESH COMPLETE ON DEMAND
USING DEFAULT LOCAL ROLLBACK SEGMENT
DISABLE QUERY REWRITE
AS
SELECT
seq_nextval AS ID,
NAME,
SEGMENT_ID,
reproject(geometry) AS GEOMETRY
FROM NET_CAB
where sdo_geom.validate_geometry(geometry,0.005) = 'TRUE'
</pre>
<pre>
CREATE MATERIALIZED VIEW P_CABAS
BUILD DEFERRED
USING INDEX
REFRESH COMPLETE ON DEMAND
USING DEFAULT LOCAL ROLLBACK SEGMENT
DISABLE QUERY REWRITE
AS
SELECT
seq_nextval AS ID,
NAME,
SEGMENT_ID,
reproject(geometry) AS GEOMETRY
FROM NET_CAB
where sdo_geom.validate_geometry(geometry,0.005) = 'TRUE'
AND cis > 4;
</pre>
Edited by: CrackerJack on May 22, 2012 8:58 PMI can run many procedures in a job:
BEGIN
SYS.DBMS_SCHEDULER.CREATE_JOB
job_name => 'JOB_REPORT_FPD'
,start_date => TO_TIMESTAMP_TZ('2012/05/31 23:30:00.000000 +07:00','yyyy/mm/dd hh24:mi:ss.ff tzh:tzm')
,repeat_interval => 'FREQ=MONTHLY;BYMONTHDAY=-1'
,end_date => NULL
,job_class => 'DEFAULT_JOB_CLASS'
,job_type => 'PLSQL_BLOCK'
,job_action => '
DECLARE
BEGIN
ibox_file.fpd_nbot_report;
ibox_file.fpd_nbot_report(''NBOT'');
ibox_file.order_report;
COMMIT;
EXCEPTION
WHEN OTHERS THEN ROLLBACK;
END;
,comments => 'USED FOR REPORTING FPD'
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
( name => 'JOB_REPORT_FPD'
,attribute => 'RESTARTABLE'
,value => FALSE);
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
( name => 'JOB_REPORT_FPD'
,attribute => 'LOGGING_LEVEL'
,value => SYS.DBMS_SCHEDULER.LOGGING_RUNS);
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL
( name => 'JOB_REPORT_FPD'
,attribute => 'MAX_FAILURES');
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL
( name => 'JOB_REPORT_FPD'
,attribute => 'MAX_RUNS');
BEGIN
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
( name => 'JOB_REPORT_FPD'
,attribute => 'STOP_ON_WINDOW_CLOSE'
,value => FALSE);
EXCEPTION
-- could fail if program is of type EXECUTABLE...
WHEN OTHERS THEN
NULL;
END;
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
( name => 'JOB_REPORT_FPD'
,attribute => 'JOB_PRIORITY'
,value => 3);
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL
( name => 'JOB_REPORT_FPD'
,attribute => 'SCHEDULE_LIMIT');
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
( name => 'JOB_REPORT_FPD'
,attribute => 'AUTO_DROP'
,value => FALSE);
SYS.DBMS_SCHEDULER.ENABLE
(name => 'JOB_REPORT_FPD');
END;
/
Maybe you are looking for
-
Device info AT&T Blackberry 8900 smartphone (EDGE,Wi-Fi) v4.6.1.319 (Platform 4.2.0.108) Cryptographic Kernel v3.8.5.50a Branding version: 1.0.102.211 Micro Edition Configuration: CLDC-1.1 Micro Edition Profile: MIDP-2.0 etc. (tell me if you need mor
-
Account Tree suppression issue
Hello, My report has multiple sections, the group footer section showing account headers (acct type H) and account details (acct type R) and all amounts associated with these accounts. In the Section Expert of the Group Footer I conditionally suppres
-
Hi everybody I'm using Oracle 11g Release 11.2.0.3.0. I have created this table (the schema also) : CREATE TABLE DATA_XML ( NOUVEAUX_CODES_DATA XMLTYPE) XMLTYPE NOUVEAUX_CODES_DATA STORE AS BINARY XML XMLSCHEMA "chgt_codes_clients.xsd" ELEMENT "codes
-
Bdc recording of screen having table control
hi all, how to trap scroll in bdc recording of table control. regards deepak
-
Content Viewer for Desktop not showing/working
Hi, After updating the DPS Desktop Tools for CS6 (2.04.1) on windows for my Creative Cloud CS6, the Content Viewer isn't working anymore: pressing the preview button open the preview popup loading progress bar (which I guess prepare all the files), d