Recent changes to bugs with shape file loading2012-11-01T16:03:15Z2012-11-01T16:03:15ZSufyan Samara<div class="markdown_content"><p>shape files that contains more than one language (encoded with UTF-8) are not handeled correctly when they are loaded into oracle usgin georaptor<br /> I tried to load the same file into postgres using postgis shape file loader, it worked fine, the file was loaded correctly. I tried to migrate the tables from postgres to oracle using ogr2ogr and the loading was successful. all the names appeared in their correct formate (encoding). however, loading the same shape file directly into oracle using georaptor would distroy the encoding of the names and hence the names are not readable. I attached the shape file which I used, I think Georaptor should have the option to choose the correct encoding before loading shapefiles into oracle. Moreover, when using the insert statement use the UNISTR() function to inforce that any varchar2 would be encoded using UTF-8. This may solve the problem but I am not sure. </p></div>ZIAjjOjcusyFPpP2012-08-16T23:36:13Z2012-08-16T23:36:13ZAnonymous<div class="markdown_content"><p>J1bagA &lt;a href="<a href="" rel="nofollow"></a>"&gt;oyuyflcmhqqm&lt;/a&gt;, [url=<a href="" rel="nofollow"></a>]ipboeomszmny[/url], [link=<a href="" rel="nofollow"></a>]lbbwamkmkwwl[/link], <a href="" rel="nofollow"></a></p></div>Export to shape file2012-05-09T21:55:52Z2012-05-09T21:55:52ZChris Egan<div class="markdown_content"><p>New sample file for 3525041/3525042 includes date to create the database table</p></div>Export to shapefile - null values2012-05-09T08:12:37Z2012-05-09T08:12:37ZChris Egan<div class="markdown_content"><p>Null values in the database appear in the dbf file as the word NULL - or N, NU, NUL for a 1, 2, or 3 character field.<br /> This is very confusing. Filling the field with spaces would be much better.</p></div>Export to shapefile column order2012-05-09T08:08:49Z2012-05-09T08:08:49ZChris Egan<div class="markdown_content"><p>The column order in the shape file does not match that in the database. It would be good if it used the column_id from all_tab_cols to order the columns. The sample file should have the several RD_NAME?, RD_TYPE?, RD_SUF? sets in this order.</p></div>ORA-01438 during shp loading2012-01-20T21:27:12Z2012-01-20T21:27:12Zkjanecka<div class="markdown_content"><p>Hi, first, thank you for your excellent work and effort!</p> <p>I have tried to load my shapefile into Oracle XE 10g database using Georaptor 3. Everytime I got this error message:</p> <p>(GeoRaptor) warn: nazkr_eng( VARCHAR2 (28) ) = Praha<br /> (GeoRaptor) warn: SQL ERROR: ORA-01438: value larger than specified precision allowed for this column.</p> <p>I think that I understand what the message means but I do not understand why it appears.</p> <p>I enclose the file ( Everytime 9 out of 10 records are successfully converted. </p> <p>The error message appears only for the record with attribute NAZKR_ENG = \'Praha\' as reported above although the shapefile contains the larger values in this field.</p> <p>I will provide you with more details if necessary.</p> <p>Thank you very much.</p> <p>Karel</p></div>UTF-8 encoding in .shp files2011-12-20T08:49:23Z2011-12-20T08:49:23ZKrunoslav Hrnjak<div class="markdown_content"><p>I am using GeoRaptor for export of SDO_GEOMETRY with attributes encoded in UTF-8.<br /> During export characters are lost. There should be option to select character encoding before writing data to .dbf</p> <p>I have attached .shp file with ITF-8 encoded characters. Those characters can be properly imported and exported from Oracle Locator DB with other tools.</p> <p>OpenJUUMP is making nice UTF-8 shapefile export if during startup option -Dfile.encoding="UTF-8" </p></div>Problem with update spatial metadata with georaptor 3.0.12011-10-14T19:34:18Z2011-10-14T19:34:18ZAnonymous<div class="markdown_content"><p>Sometimes the diminfo X and Y values are inserted in the wrong order.<br /> so<br /> SDO_DIM_ARRAY(SDO_DIM_ELEMENT('X', 477000, 495250, .00005), SDO_DIM_ELEMENT('Y', 3762500, 3774000, .00005)) <br /> ended up as<br /> SDO_DIM_ARRAY(SDO_DIM_ELEMENT('Y', 3762500, 3774000, .00005),SDO_DIM_ELEMENT('X', 477000, 495250, .00005)) in the metadata.</p> <p>I've only noticed the error after failed executions of spatial queries (session ending).</p></div>Copy geometry to clipboard format2010-10-19T09:02:31Z2010-10-19T09:02:31ZBerend Veldkamp<div class="markdown_content"><p>I have a geometry column containing X, Y and M values. The coordinates are displayed correctly on the 'Data' tab (see attached image), but when copying a geometry to the clipboard, it seems that comma's are missing between the Y and M values. </p> <p>Actual result:<br /> MDSYS.SDO_GEOMETRY(3002, -1, NULL, MDSYS.SDO_ELEM_INFO_ARRAY(1,2,1), MDSYS.SDO_ORDINATE_ARRAY(626424.64, 5841538.450.0, 656800.859417039, 5863259.6853863637343.363169134, 656763.17606855, 5864458.8622856838543.1320096266, 688769.094509806, 5837727.79596619666090.905733056, 656767.277156878, 5864381.158696681293560.8678311, 626424.89, 5841540.941331538.96742139))</p> <p>Expected result:<br /> MDSYS.SDO_GEOMETRY(3002, -1, NULL, MDSYS.SDO_ELEM_INFO_ARRAY(1,2,1), MDSYS.SDO_ORDINATE_ARRAY(626424.64, 5841538.45, 0.0, 656800.859417039, 5863259.68538636, 37343.363169134, 656763.17606855, 5864458.86228568, 38543.1320096266, 688769.094509806, 5837727.79596619, 666090.905733056, 656767.277156878, 5864381.15869668, 1293560.8678311, 626424.89, 5841540.94, 1331538.96742139))</p></div>Can't see all of SQL windows in 'Layer Properties'2010-09-29T18:56:35Z2010-09-29T18:56:35ZJohn O'Toole<div class="markdown_content"><p>Running the current production build of GeoRaptor released on August 13th. </p> <p>The 'Layer Properties' dialog includes an 'SQL' text area where the default sql for the spatial query is shown. While this text area has scroll bars, it doesn't seem to be possible to see more than 8 lines of text. I can type them in, but they are not shown and I can't scroll down to see them. <br /> This makes it (a little) difficult to add extra predicates to the query.<br /> </p> <p>John</p></div>