Correct, it is "forgotten" in the testset.This is a good test:
sql = "INSERT INTO CURVES VALUES (9, 'Compound polygon version 2', "
+ "sdo_geometry (2003, 32632, null, sdo_elem_info_array(1,1003,2),
sdo_ordinate_array(15, 145, 20, 150, 15, 155, 10, 150, 15, 145)))";
run(sql);
Can someone (with enough knowledge of this particular piece) please add it to
the testset and solve the issue?
The Oracle documentation says:
| 1003 or 2003 | 2 | Polygon made up of a connected sequence of circular arcs
that closes on itself. The end point of the last arc is the same as the start
point of the first arc.Each circular arc is described using three coordinates:
the start point of the arc, any point on the arc, and the end point of the arc.
The coordinates for a point designating the end of one arc and the start of the
next arc are not repeated. For example, five coordinates are used to describe a
polygon made up of two connected circular arcs. Points 1, 2, and 3 define the
first arc, and points 3, 4, and 5 define the second arc. The coordinates for
points 1 and 5 must be the same (tolerance is not considered), and point 3 is
not repeated. |
See
http://docs.oracle.com/cd/B28359_01/appdev.111/b28400/sdo_objrelschema.htm#SPATL493
On Thursday, 9 April 2015, 14:37, Andrea Aime
<andrea.a...@geo-solutions.it> wrote:
On Thu, Apr 9, 2015 at 2:28 PM, Ron Lindhoudt <rlindho...@yahoo.com> wrote:
Is it correct that compound curves are not yet supported?I know that since some
time there is support of curves.
For example, the following geometry is not rendered:
mdsys.SDO_GEOMETRY(2003, 90112, NULL, mdsys.SDO_ELEM_INFO_ARRAY(1, 1003, 2),
mdsys.SDO_ORDINATE_ARRAY(255047.728, 470840.788, 255057.728, 470850.788,
255047.728, 470860.788, 255037.728, 470850.788, 255047.728, 470840.788))
The Error is:
[2015-04-09 9:44:24:203] org.geotools.rendering SEVERE: ELEM_INFO
INTERPRETAION2 not supportedfor JTS Polygon Linear Rings.ELEM_INFO
INTERPRETATION 1,2 and 3 are supported
There is a contradiction in the error message: - Interpretation 2 is not
supported- Interpretation 1,2,3 are supported
Compound curves are supposed to be supported since 2.6.0, but maybe not that
particular case.Here is our test data (e.g., the geometries we actually test
against during builds):
// adding data sql = "INSERT INTO CURVES VALUES (0, 'Arc segment', "
+ "sdo_geometry (2002, 32632, null, sdo_elem_info_array (1,2,2),
sdo_ordinate_array (10,15, 15,20, 20,15)))"; run(sql);
sql = "INSERT INTO CURVES VALUES (1, 'Arc string', " +
"sdo_geometry (2002, 32632, null, sdo_elem_info_array (1,2,2),
sdo_ordinate_array (10,35, 15,40, 20,35, 25,30, 30,35)))"; run(sql);
sql = "INSERT INTO CURVES VALUES (2, 'Closed arc string', "
+ "sdo_geometry (2002, 32632, null, sdo_elem_info_array (1,2,2),
sdo_ordinate_array (15,65, 10,68, 15,70, 20,68, 15,65)))"; run(sql);
sql = "INSERT INTO CURVES VALUES (3, 'Compound line string', "
+ "sdo_geometry (2002, 32632, null, sdo_elem_info_array (1,4,3, 1,2,1,
3,2,2, 7,2,1), sdo_ordinate_array (10,45, 20,45, 23,48, 20,51, 10,51)))";
run(sql);
sql = "INSERT INTO CURVES VALUES (4, 'Closed mixed line', "
+ "sdo_geometry (2002, 32632, null, sdo_elem_info_array (1,4,2, 1,2,1,
7,2,2), sdo_ordinate_array (10,78, 10,75, 20,75, 20,78, 15,80, 10,78)))";
run(sql);
sql = "INSERT INTO CURVES VALUES (5, 'Circle', " +
"sdo_geometry (2003, 32632, null, sdo_elem_info_array (1,1003,4),
sdo_ordinate_array (15,145, 10,150, 20,150)))"; run(sql);
sql = "INSERT INTO CURVES VALUES (6, 'Compound polygon', "
+ "sdo_geometry (2003, 32632, null, sdo_elem_info_array(1,1005,2, 1,2,1,
5,2,2), sdo_ordinate_array(6,10, 10,1, 14,10, 10,14, 6,10)))"; run(sql);
sql = "INSERT INTO CURVES VALUES (7, 'Compound polygon with hole',
sdo_geometry(2003, 32632, null," + "
sdo_elem_info_array(1,1005,2, 1,2,1, 13,2,2, 19,2003,4)," + "
sdo_ordinate_array(20,30, 11,30, 7,22, 7,15, 11,10, 21,10, 27,30, 25,27, 20,30,
10,17, 15,22, 20,17)))"; run(sql);
sql = "INSERT INTO CURVES VALUES (8, 'Multipolygon with curves',
sdo_geometry(2007, 32632, null," + "
sdo_elem_info_array(1,1005,2, 1,2,1, 5,2,2, 11,2005,2, 11,2,1, 15,2,2,
21,1005,2, 21,2,1, 25,2,2)," + " sdo_ordinate_array(6,10, 10,1,
14,10, 10,14, 6,10, 13,10, 10,2, 7,10, 10,13, 13,10, 106,110, 110,101,
114,110, 110,114,106,110)))"; run(sql);
I guess your compound curve is different than our "compound line string" case?
(sorry, no time to check right now)
CheersAndrea
--
==GeoServer Professional Services from the experts! Visithttp://goo.gl/NWWaa2
for more information.==
Ing. Andrea Aime
@geowolfTechnical Lead
GeoSolutions S.A.S.Via Poggio alle Viti 118755054 Massarosa (LU)Italyphone:
+39 0584 962313fax: +39 0584 1660272mob: +39 339 8844549
http://www.geo-solutions.ithttp://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003Le informazioni contenute in questo
messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi
strettamente riservate. Il loro utilizzo è consentito esclusivamente al
destinatario del messaggio, per le finalità indicate nel messaggio stesso.
Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di darcene notizia via e-mail e di procedere alla distruzione del
messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio
stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003. The information in this message and/or
attachments, is intended solely for the attention and use of the named
addressee(s) and may be confidential or proprietary in nature or covered by the
provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's
New Data Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either dissemination,
either whole or partial, is strictly forbidden except previous formal approval
of the named addressee(s). If you are not the intended recipient, please
contact immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender does
not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes made
after they were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.
-------------------------------------------------------
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
