Opened 10 years ago
Closed 10 years ago
#5736 closed defect (invalid)
Non-ascii characters in data files
Reported by: | Kurt Schwehr | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | default | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: |
Description
In 1.11-svn and trunk:
source:trunk/gdal/data/ellipsoid.csv#L9
7007,Clarke 1858,20926348,9005,,20855233,1,"Clarke's 1858/II solution. Derived parameters: a = 6378293.645m using his 1865 ratio of 0.3047972654 feet per metre; 1/f = 294.26068
And then something that is likely a period.
source:trunk/gdal/data/ellipsoid.csv#L50
7055,Clarke 1880 (international foot),20926202,9002,,20854895,1,Clark'es 1880 definition in feet assumed for the purposes of metric conversion to be international foot. a = 6378306.370
Then I'm not sure what that is supposed to be.
source:trunk/gdal/data/unit_of_measure.csv#L58
logarithmic relationship (10^0.48401603 exactly). 1 ft = 0.3048007491
Then junk.
Also, the line right after looks like a bad line break.
9095,British foot (1936),length,9001,0.3048007491,1,For the 1936 [snip] 2. ""The Irish Grid - A Description of the Co-ordinate Reference System"" [snip]
Change History (2)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I think all you mention is OK. All the EPSG derived files have valid ASCII or UTF-8 content. The character you mention is a single UTF-8 character whose closest ASCII representations is 3 dots '...' And the line break is OK. The OGR CSV driver can deal with it nicely.