Changes between Initial Version and Version 9 of Ticket #372


Ignore:
Timestamp:
Apr 9, 2007, 9:55:31 AM (17 years ago)
Author:
Mateusz Łoskot
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #372 – Description

    initial v9  
    1 {{{
    21Frank,
    32
    4 after digging around with the extraction of political boundaries from
    5 VMAP0, I discovered, that the column length are not correct.
     3after digging around with the extraction of political boundaries from VMAP0, I discovered, that the column length are not correct.
    64
     5{{{
    76id: Integer (10.0)
    87f_code: String (5.0)
    … …  
    1211tile_id: Integer (5.0)
    1312fac_id: Integer (10.0)
     13}}}
    1414
    1515At least the column 'na2' is one character too short.
    1616
    1717This works however (extraction of Botswana):
     18
     19{{{
    1820ogrinfo -ro -where "na2 = ' BC'"
    1921gltp:/vrf/grass0/warmerdam/v0soa/vmaplv0/soamafr 'polbnda@bnd(*)_area'
    … …  
    2729GEOGCS["NAD83",
    2830[...]
     31}}}
    2932
    3033while this fails:
     34
     35{{{
    3136ogrinfo -ro -where "na2 = ' B'" gltp:/vrf/grass0/warmerdam/v0soa/vmaplv0/soamafr
    3237'polbnda@bnd(*)_area'
    … …  
    3944Layer SRS WKT:
    4045[...]
     46}}}
    4147
    4248It should be a 3 chars string just to be able to store
    … …  
    4753
    4854To fetch the USA from NOAMER, I have to run
     55
     56{{{
    4957ogrinfo -ro -where "na2 = ' US'"
    5058gltp:/vrf/grass0/warmerdam/v0noa/vmaplv0/noamer 'polbnda@bnd(*)_area'
     59}}}
    5160
    5261The bug may also be related to the fact, that the columns
    53 f_code, nam, na2, na3
    54 start with a white space. Maybe the reading of the string is shifted
    55 by one character.
     62f_code, nam, na2, na3 start with a white space. Maybe the reading of the string is shifted by one character.
    5663
    5764Hope it is easy to fix.
    … …  
    5966Thanks,
    6067
    61  Markus
    62 }}}
     68Markus