<HTML dir=ltr><HEAD><TITLE>Re: [Gvsig_english] Question on GeoBD and Metadata when exporting toOracle</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6000.16945" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText8454 dir=ltr>
<DIV dir=ltr><FONT face="Times New Roman" color=#000000 size=3>
<DIV dir=ltr><FONT face="Times New Roman" color=#000000 size=3>Hello, Wolfgang. When you choose a connection to see the available Oracle Spatial tables, the metadata of some of those tables is written in the gvSIG log file (one out of ten, I think, for sampling purposes).</FONT></DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>I have exported a few shapefiles with gvSIG 1.9, and these lines appear in the gvSIG log file:</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>=========<BR>OWNER: LLEIDA, TABLE_NAME: GV_SEE_TOL, COLUMN_NAME: GEOMETRY, SRID: 82337<BR>DIMINFO: DIMENSIONS: 2<BR>DIMENSION 0: , NAME: X, MIN: 4070148.67213375, MAX: 5192210.139323162, TOL: 0.0005<BR>DIMENSION 1: , NAME: Y, MIN: 5238407.7711313, MAX: 6196031.330266247, TOL: 0.0005<BR>=========</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>So yes, the tolerance is set to 0.0005 meters as you suggested.</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Regards,</DIV></FONT></DIV>
<DIV dir=ltr><FONT face="Times New Roman" color=#000000 size=3></FONT> </DIV></DIV>
<DIV id=idSignature50458 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></DIV>
<DIV>
<DIV><FONT face="Courier New" size=2>Tlf.: 96.351.06.12 -- Fax: 96.351.09.68<BR></FONT><A 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></DIV></FONT></DIV></FONT></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>De:</B> gvsig_internacional-bounces@listserv.gva.es en nombre de Wolfgang Qual<BR><B>Enviado el:</B> vie 18/12/2009 13:01<BR><B>Para:</B> gvsig_internacional@listserv.gva.es<BR><B>Asunto:</B> Re: [Gvsig_english] Question on GeoBD and Metadata when exporting toOracle<BR></FONT><BR></DIV>
<DIV><BR>
<P><FONT size=2>Hello Juan Lucas, list.<BR>A few weeks ago, I wrote a post regarding metadata and Oracle spatial. The<BR>tolerance value I was referring to was 0.5 in the past, but you mentioned<BR>that it could be changed. Is this change already reflected in gvSIG 1.9?<BR>Short answer would be that great!<BR><BR>Best,<BR>Wolfgang<BR><BR><BR>Juan Lucas Dominguez Rubio schrieb:<BR>> Hello,<BR>> <BR>> Ok yes, 0.5 meters is too much. I'll change it to 0.0005 and if I<BR>> don't see any problem, I think it'll be like that in the upcoming<BR>> gvSIG 1.9.<BR>> <BR>> According to the Oracle documentation, tolerance must be smaller than<BR>> the smallest hole in polygon layers. I don't think you have a polygon<BR>> layer with holes whose diameter is less than 0.0005 meters (1/2 mm),<BR>> do you? ;-)<BR>> <BR>> Regards<BR>> <BR>> Juan Lucas Domínguez Rubio<BR>> ---<BR>> Prodevelop SL, Valencia (España)<BR>> Tlf.: 96.351.06.12 -- Fax: 96.351.09.68<BR>> <A href="http://www.prodevelop.es/">http://www.prodevelop.es</A> <<A href="http://www.prodevelop.es/">http://www.prodevelop.es/</A>><BR>> ---<BR>><BR>> ------------------------------------------------------------------------<BR>> *De:* Wolfgang Qual [<A href="mailto:wolfgang.qual@muenchen.de">mailto:wolfgang.qual@muenchen.de</A>]<BR>> *Enviado el:* jue 24/09/2009 11:53<BR>> *Para:* Users and Developers mailing list; Juan Lucas Dominguez Rubio<BR>> *Asunto:* Re: [Gvsig_english] Question on GeoBD and Metadata when<BR>> exporting toOracle<BR>><BR>> Hello Juan Lucas,<BR>> thank you very much for this detailed information. I just found out<BR>> that SDO_TOLERANCE_1 and .._2 are parameters within the ESRI<BR>> application. Therefore, they refer to SDO_TOLERANCE values for X and<BR>> Y. According to my colleague,<BR>> ESRI sets those values to 0.0005. The tolerance parameter of GeoBD<BR>> oracle export is set to 0.5 - does that mean that the tolerance is 0.5<BR>> meter? Can this be modified? As geometries of the common geodatabase<BR>> are used in different departments with different applications,<BR>> tolerance values should be identical, don't you think? Sorry, but I am<BR>> 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:<BR>>> Hello, Wolfgang.<BR>>> <BR>>> When you export a vector layer to Oracle Spatlai/Locator, the<BR>>> sequence of actions is as follows:<BR>>> <BR>>> - if a table with the same name exists, it's deleted (dropped in<BR>>> cascade mode). This also removes spatial indices associated with the<BR>>> table<BR>>> - the new table is created<BR>>> - geometry metadata for this table name is removed (if existed)<BR>>> - new geometry metadata is written in USER_SDO_GEOM_METADATA<BR>>> - a spatial index on the geometry column is created<BR>>> - table records are added (no commits here)<BR>>> - a single final commit is performed<BR>>> <BR>>> The tolerance parameter in the metadata is always set to 0.5.<BR>>> Dimension names are set to 'X', 'Y' and 'Z' (if needed) or<BR>>> 'LONGITUDE' and 'LATITUDE'. Max. and min. values for X and Y are set<BR>>> according to the layer's bounding box. Min. and max. values for 'Z'<BR>>> (if needed) are always set to 0 and 100 (this is not very nice, but<BR>>> has no bad effect since the Z value does not currently take part in<BR>>> any geometric operation). Dimension names can be anything you want.<BR>>> You could use 'BREITE' instead of 'LATITUDE', 'EASTING' instead of<BR>>> 'X' or whatever.<BR>>> <BR>>> SDO_TOLERANCE_1 and SDO_TOLERANCE_2 refer to tolerance for X and Y<BR>>> perhaps?<BR>>> <BR>>> Remember that the tolerance unit is implicit and depends on the<BR>>> table's coordinate system (SRID). If the SRID corresponds to a<BR>>> geodetic coordinate system (latitude, longitude), then the tolerance<BR>>> is assumed to be expressed in meters. If the SRID corresponds to a<BR>>> projected coordinate system (such as the German EPSG:3146X series)<BR>>> then the tolerance is assumed to be expressed in the same unit used<BR>>> by the coordinate system (usually meters). This also applies if the<BR>>> SRID is NULL. According to this, it would be a bad idea to have a<BR>>> table with geometries whose vertices are in latitude and longitude<BR>>> and setting the SRID to NULL, because the tolerance (0.5) would<BR>>> correspond to a few dozens of kilometers.<BR>>> <BR>>> The tolerance settings are very unlikely to have any effect when you<BR>>> work with gvSIG because the application checks again the true<BR>>> relationship between geometries after they have been converted to the<BR>>> gvSIG geometry model. In other words: the 'select by rectangle' tool<BR>>> should not behave in a strange way even if you have a bad tolerance<BR>>> value. Of course you will see the effects of a bad tolerance value<BR>>> from other applications or when you execute a SQL statement directly<BR>>> against your database.<BR>>> <BR>>> So the metadata stored for a Oracle Spatial/Locator table are:<BR>>> <BR>>> - Owner<BR>>> - Table name<BR>>> - Geometry column name (the metadata record will be replicated for<BR>>> several values because a table can have more than one geometry column)<BR>>> - Dimension info (for each dimension: dimension name, max value, min<BR>>> value, tolerance)<BR>>> - SRID (possibly NULL)<BR>>> <BR>>> If you have a 3D vector layer (for example a 3D shapefile) I think<BR>>> you will not notice the third dimension while you work with views and<BR>>> layouts, but if you export that layer to your Oracle Spatial/Locator<BR>>> database, it will be stored with a 3D geometry column (you can see<BR>>> the number of dimensions of each using Sqldeveloper for example)<BR>>> <BR>>> As you perhaps know, Oracle Spatial/Locator supports 4D geometries<BR>>> (XYZT, I think Oracle normally uses the letter T instead of M for the<BR>>> 4th dimension). When you open one of these tables with gvSIG, the<BR>>> resulting layer is a 3D layer (4th dimension is discarded)<BR>>> <BR>>> I have never heard about a parameter called resolution in the table<BR>>> metadata. Perhaps you are talking about some operations that allow<BR>>> you to restrict the result by setting a min and max_resolution value,<BR>>> but this is not connected to tables' metadata.<BR>>> <BR>>> I agree that it would be a good idea to let the user set the metadata<BR>>> values.<BR>>> <BR>>> Regards,<BR>>> Juan Lucas Domínguez Rubio<BR>>> ---<BR>>> Prodevelop SL, Valencia (España)<BR>>> Tlf.: 96.351.06.12 -- Fax: 96.351.09.68<BR>>> <A href="http://www.prodevelop.es/">http://www.prodevelop.es</A> <<A href="http://www.prodevelop.es/">http://www.prodevelop.es/</A>><BR>>> ---<BR>>><BR>>> ------------------------------------------------------------------------<BR>>> *De:* gvsig_internacional-bounces@listserv.gva.es en nombre de<BR>>> Wolfgang Qual<BR>>> *Enviado el:* jue 24/09/2009 8:59<BR>>> *Para:* Users and Developers mailing list<BR>>> *Asunto:* [Gvsig_english] Question on GeoBD and Metadata when<BR>>> exporting toOracle<BR>>><BR>>> 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: wolfgang.qual@muenchen.de<BR>>><BR>>> _______________________________________________<BR>>> Gvsig_internacional mailing list<BR>>> Gvsig_internacional@listserv.gva.es<BR>>> <A href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</A><BR>>><BR>>> ------------------------------------------------------------------------<BR>>><BR>>> _______________________________________________<BR>>> Gvsig_internacional mailing list<BR>>> Gvsig_internacional@listserv.gva.es<BR>>> <A href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</A><BR>>> <BR>><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: wolfgang.qual@muenchen.de<BR>> ------------------------------------------------------------------------<BR>><BR>> _______________________________________________<BR>> Gvsig_internacional mailing list<BR>> Gvsig_internacional@listserv.gva.es<BR>> <A href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</A><BR>> <BR><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: wolfgang.qual@muenchen.de<BR><BR><BR>_______________________________________________<BR>Gvsig_internacional mailing list<BR>Gvsig_internacional@listserv.gva.es<BR><A href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</A><BR><BR><BR><BR>--<BR>View this message in context: <A href="http://n2.nabble.com/Question-on-GeoBD-and-Metadata-when-exporting-to-Oracle-tp3704488p4186183.html">http://n2.nabble.com/Question-on-GeoBD-and-Metadata-when-exporting-to-Oracle-tp3704488p4186183.html</A><BR>Sent from the gvSIG international mailing list archive at Nabble.com.<BR>_______________________________________________<BR>Gvsig_internacional mailing list<BR>Gvsig_internacional@listserv.gva.es<BR><A 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></BODY></HTML>