Changes between Initial Version and Version 1 of Ticket #2727


Ignore:
Timestamp:
Dec 9, 2008, 6:27:23 AM (15 years ago)
Author:
warmerdam
Comment:

Hi, could you add a note (or set the version flag for this ticket) indicating what version of GDAL/OGR you are using? This sounds a bit like bug #990.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2727

    • Property Keywords odbc added
    • Property Status new → assigned
    • Property Component default → OGR_SF

  • Ticket #2727 – Description

    initial v1  
    22
    33This was seen with data in a SQL server 2008 express database.  To create a table and populate it with test data run the following script:
    4 
     4{{{
    55CREATE TABLE [dbo].[snhd_wkt2](
    66        [ID] [int] NULL,
    … …  
    1414INSERT INTO [dbo].[snhd_wkt2] VALUES
    1515('1', '424137.474088898', '140734.844325094', '424381.173359863', '140870.555478181', 'Polygon ((424141.423 140736.164,424141.415 140736.164,424141.432 140736.174,424141.860 140736.574,424142.512 140737.224,424143.353 140738.223,424144.103 140739.283,424144.787 140740.403,424145.356 140741.582,424145.851 140742.792,424146.230 140744.052,424146.544 140745.311,424146.692 140746.611,424146.791 140747.921,424146.758 140749.230,424146.634 140750.530,424146.387 140751.829,424146.041 140753.089,424145.604 140754.309,424145.480 140754.589,424144.870 140755.568,424144.120 140757.328,424143.246 140759.127,424140.929 140763.916,424137.474 140770.954,424158.928 140773.253,424179.037 140778.462,424194.835 140782.231,424243.481 140812.932,424280.105 140836.445,424296.257 140847.032,424330.903 140864.627,424359.448 140870.555,424372.013 140868.036,424379.195 140862.118,424381.173 140848.472,424374.528 140833.036,424356.397 140826.748,424323.004 140824.059,424266.460 140798.386,424235.945 140782.051,424209.016 140767.695,424196.088 140751.180,424173.472 140739.683,424151.573 140734.844,424141.423 140736.164))')
    16 
     16}}}
    1717Create an ODBC connection (in this case called 'SpatialTest' to the SQL Server database and run the following ogrinfo command (in this case with a user/password both of 'test'):
    18 
     18{{{
    1919ogrinfo -ro -so "ODBC:test/test@spatialtest" snhd_wkt2
    20 
     20}}}
    2121The following is returned:
    22 
     22{{{
    2323ERROR 1: Column Geometry requested for geometry, but it does not exist.
    2424INFO: Open of `ODBC:test/test@spatialtest'
    … …  
    3737XMAX: Real (0.0)
    3838YMAX: Real (0.0)
    39 
     39}}}
    4040If a blank character is entered into the WKT string (i.e. making is longer than 1023 characters) then ogrinfo works without any errors.
    41 
    42 
    43