<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Juan Lucas,<br>
g-r-e-a-t!<br>
<br>
Best,<br>
Wolfgang<br>
<br>
<br>
Juan Lucas Dominguez Rubio schrieb:
<blockquote
cite="mid:E43C32BC5843E34FB4C00CDFAAAAF7D8017B4CA1@australia.prodevelop.local"
type="cite">
<title>[Gvsig_english] Question on GeoBD and Metadata when exporting
toOracle</title>
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.6000.16890" name="GENERATOR">
<div id="idOWAReplyText41022" dir="ltr">
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">Hello,</font></div>
<div dir="ltr"> </div>
<div dir="ltr">Ok yes, 0.5 meters is too much. I'll change it to
0.0005 and if I don't see any problem, I think it'll be like that in
the upcoming gvSIG 1.9.</div>
<div dir="ltr"> </div>
<div dir="ltr">According to the Oracle documentation, tolerance must
be smaller than the smallest hole in polygon layers. I don't think you
have a polygon layer with holes whose diameter is less than 0.0005
meters (1/2 mm), do you? ;-)</div>
<div dir="ltr"> </div>
<div dir="ltr">Regards</div>
<div dir="ltr"> </div>
</div>
<div id="idSignature17512" dir="ltr">
<div><font face="Courier New" size="2"><font face="Times New Roman"
size="3">Juan Lucas Domínguez Rubio<br>
</font>---</font></div>
<div><font face="Courier New" size="2"><font face="Courier New"
size="2"><font face="Courier New" size="2">Prodevelop SL, Valencia
(España)</font></font></font></div>
<div>
<div><font face="Courier New" size="2"><font face="Courier New"
size="2"><font face="Courier New" size="2">Tlf.: 96.351.06.12 -- Fax:
96.351.09.68<br>
</font><a moz-do-not-send="true" href="http://www.prodevelop.es/"><font
face="Courier New" size="2">http://www.prodevelop.es</font></a><br>
<font face="Courier New" size="2">---</font></font></font></div>
</div>
</div>
<div dir="ltr"><br>
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>De:</b> Wolfgang Qual
[<a class="moz-txt-link-freetext" href="mailto:wolfgang.qual@muenchen.de">mailto:wolfgang.qual@muenchen.de</a>]<br>
<b>Enviado el:</b> jue 24/09/2009 11:53<br>
<b>Para:</b> Users and Developers mailing list; Juan Lucas Dominguez
Rubio<br>
<b>Asunto:</b> Re: [Gvsig_english] Question on GeoBD and Metadata
when exporting toOracle<br>
</font><br>
</div>
<div>Hello Juan Lucas,<br>
thank you very much for this detailed information. I just found out
that SDO_TOLERANCE_1 and .._2 are parameters within the ESRI
application. Therefore, they refer to SDO_TOLERANCE values for X and Y.
According to my colleague, <br>
ESRI sets those values to 0.0005. The tolerance parameter of GeoBD
oracle export is set to 0.5 - does that mean that the tolerance is 0.5
meter? Can this be modified? As geometries of the common geodatabase
are used in different departments with different applications,
tolerance values should be identical, don't you think? Sorry, but I am
not that well schooled in this oracle stuff...<br>
<br>
Best,<br>
Wolfgang<br>
<br>
---8<---<br>
And resolution seems to be available in ESRI-software, too. <br>
Juan Lucas Dominguez Rubio schrieb:
<blockquote cite="" type="cite">
<div id="idOWAReplyText8409" dir="ltr">
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">Hello,
Wolfgang.</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">When
you export a vector layer to Oracle Spatlai/Locator, the sequence of
actions is as follows:</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">-
if a table with the same name exists, it's deleted (dropped in cascade
mode). This also removes spatial indices associated with the table</font></div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">-
the new table is created</font></div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">-
geometry metadata for this table name is removed (if existed)</font></div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">-
new geometry metadata is written in USER_SDO_GEOM_METADATA</font></div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">-
a spatial index on the geometry column is created</font></div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">-
table records are added (no commits here)</font></div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">-
a single final commit is performed</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">The
tolerance parameter in the metadata is always set to 0.5. Dimension
names are set to 'X', 'Y' and 'Z' (if needed) or 'LONGITUDE' and
'LATITUDE'. </font><font color="#000000" face="Times New Roman"
size="3">Max. and min. values for X and Y are set according to the
layer's bounding box. Min. and max. values for 'Z' (if needed) are
always set to 0 and 100 (this </font><font color="#000000"
face="Times New Roman" size="3">is not very nice, but has no bad
effect since the Z value does not currently take part in any geometric
operation). Dimension names can be anything you want. You could use
'BREITE' instead of 'LATITUDE', 'EASTING' instead of 'X' or whatever.</font></div>
<div dir="ltr"> </div>
<div dir="ltr">SDO_TOLERANCE_1 and SDO_TOLERANCE_2 refer to
tolerance for X and Y perhaps?</div>
<div dir="ltr"> </div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">Remember
that the tolerance unit is implicit and depends on the table's
coordinate system (SRID). If the SRID corresponds to a geodetic
coordinate </font><font color="#000000" face="Times New Roman" size="3">system
(latitude, longitude), then the tolerance is assumed to be expressed in
meters. If the SRID corresponds to a projected coordinate system (such </font><font
color="#000000" face="Times New Roman" size="3">as the German
EPSG:3146X series) then the tolerance is assumed to be expressed in the
same unit used by the coordinate system (usually meters). </font><font
color="#000000" face="Times New Roman" size="3">This also applies if
the SRID is NULL. According to this, it would be a bad idea to have a
table with geometries whose vertices are in latitude and </font><font
color="#000000" face="Times New Roman" size="3">longitude and setting
the SRID to NULL, because the tolerance (0.5) would correspond to a few
dozens of kilometers.</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">The
tolerance settings are very unlikely to have any effect when you work
with gvSIG because the application checks again the true relationship </font><font
color="#000000" face="Times New Roman" size="3">between geometries
after they have been converted to the gvSIG geometry model. In other
words: the 'select by rectangle' tool should not behave in a </font><font
color="#000000" face="Times New Roman" size="3">strange way even if
you have a bad tolerance value. Of course you will see the effects of a
bad tolerance value from other applications or when you </font><font
color="#000000" face="Times New Roman" size="3">execute a SQL
statement directly against your database.</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">So
the metadata stored for a Oracle Spatial/Locator table are:</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">-
Owner</font></div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">-
Table name</font></div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">-
Geometry column name (the metadata record will be replicated for
several values because a table can have more than one geometry column)</font></div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">-
Dimension info (for each dimension: dimension name, max value, min
value, tolerance)</font></div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">-
SRID (possibly NULL)</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">If
you have a 3D vector layer (for example a 3D shapefile) I think you
will not notice the third dimension while you work with views and
layouts, but if you </font><font color="#000000" face="Times New Roman"
size="3">export that layer to your Oracle Spatial/Locator database, it
will be stored with a 3D geometry column (you can see the number of
dimensions of each </font><font color="#000000" face="Times New Roman"
size="3">using Sqldeveloper for example)</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">As
you perhaps know, Oracle Spatial/Locator supports 4D geometries (XYZT,
I think Oracle normally uses the letter T instead of M for the 4th </font><font
color="#000000" face="Times New Roman" size="3">dimension). When you
open one of these tables with gvSIG, the resulting layer is a 3D layer
(4th dimension is discarded)</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">I
have never heard about a parameter called resolution in the table
metadata. Perhaps you are talking about some operations that allow you
to restrict </font><font color="#000000" face="Times New Roman"
size="3">the result by setting a min and max_resolution value, but
this is not connected to tables' metadata.</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">I
agree that it would be a good idea to let the user set the metadata
values.</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font color="#000000" face="Times New Roman" size="3">Regards,</font></div>
<div dir="ltr"><font face="Courier New" size="2"><font
face="Times New Roman" size="3">Juan Lucas Domínguez Rubio<br>
</font>---</font></div>
</div>
<div id="idSignature43918" dir="ltr">
<div><font face="Courier New" size="2"><font face="Courier New"
size="2"><font face="Courier New" size="2">Prodevelop SL, Valencia
(España)</font></font></font></div>
<div>
<div><font face="Courier New" size="2"><font face="Courier New"
size="2"><font face="Courier New" size="2">Tlf.: 96.351.06.12 -- Fax:
96.351.09.68<br>
</font><a moz-do-not-send="true" href="http://www.prodevelop.es/"><font
face="Courier New" size="2">http://www.prodevelop.es</font></a><br>
<font face="Courier New" size="2">---</font></font></font></div>
</div>
</div>
<div dir="ltr"><br>
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>De:</b> <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:gvsig_internacional-bounces@listserv.gva.es">gvsig_internacional-bounces@listserv.gva.es</a>
en nombre de Wolfgang Qual<br>
<b>Enviado el:</b> jue 24/09/2009 8:59<br>
<b>Para:</b> Users and Developers mailing list<br>
<b>Asunto:</b> [Gvsig_english] Question on GeoBD and Metadata when
exporting toOracle<br>
</font><br>
</div>
<div>
<p><font size="2">Hi list,<br>
in our City administration, different GIS software is used to work with<br>
spatial data. Among them, ArcMap and gvSIG allow to access a central<br>
oracle spatial database. Thanks to the great GeoBD extension, accessing<br>
that database via gvSIG is very comfortable, even exporting new layers<br>
to the database is possible.<br>
Yesterday, a colleague of mine who is in charge of the overall design of<br>
the geodatabase asked me to provide some details on GeoBD's<br>
capabilities. He asked me about metadata that is created by that<br>
extension when exporting a shapefile to the oracle spatial database and<br>
possibilities to set custom settings for the metadata. In this context,<br>
he also talked about "tolerance" (SDO_TOLERANCE_1, SDO_TOLERANCE_2),<br>
"resolution". I have no idea, whether GeoBD sets these values.<br>
Therefore, I would be very happy, if someone of you (maybe the<br>
developers from Prodevelop) could give me some details on the type and<br>
values of metadata that is written to new oracle spatial layers. That<br>
would be very great to have.<br>
<br>
Best regards and thank you very much for your help.<br>
Wolfgang<br>
<br>
--<br>
Wolfgang Qual<br>
Landeshauptstadt München<br>
Referat für Gesundheit und Umwelt<br>
RGU-UW 11<br>
Sg. 1 Gesundheits- und Umweltberichterstattung,<br>
Energie und Klimaschutz<br>
Bayerstr. 28a, 80335 München<br>
Tel.: +49 (0)89 233-477 17<br>
Fax.: +49 (0)89 233-477 05<br>
E-Mail: <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:wolfgang.qual@muenchen.de">wolfgang.qual@muenchen.de</a><br>
<br>
_______________________________________________<br>
Gvsig_internacional mailing list<br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:Gvsig_internacional@listserv.gva.es">Gvsig_internacional@listserv.gva.es</a><br>
<a moz-do-not-send="true"
href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</a><br>
</font></p>
</div>
<pre><hr size="4" width="90%">
_______________________________________________
Gvsig_internacional mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:Gvsig_internacional@listserv.gva.es">Gvsig_internacional@listserv.gva.es</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Wolfgang Qual
Landeshauptstadt München
Referat für Gesundheit und Umwelt
RGU-UW 11
Sg. 1 Gesundheits- und Umweltberichterstattung,
Energie und Klimaschutz
Bayerstr. 28a, 80335 München
Tel.: +49 (0)89 233-477 17
Fax.: +49 (0)89 233-477 05
E-Mail: <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:wolfgang.qual@muenchen.de">wolfgang.qual@muenchen.de</a> </pre>
</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Gvsig_internacional mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gvsig_internacional@listserv.gva.es">Gvsig_internacional@listserv.gva.es</a>
<a class="moz-txt-link-freetext" href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Wolfgang Qual
Landeshauptstadt München
Referat für Gesundheit und Umwelt
RGU-UW 11
Sg. 1 Gesundheits- und Umweltberichterstattung,
Energie und Klimaschutz
Bayerstr. 28a, 80335 München
Tel.: +49 (0)89 233-477 17
Fax.: +49 (0)89 233-477 05
E-Mail: <a class="moz-txt-link-abbreviated" href="mailto:wolfgang.qual@muenchen.de">wolfgang.qual@muenchen.de</a> </pre>
</body>
</html>