[GRASS-dev] Location EPSG code storage

[Martin Landa]

Hi,

2011/9/8 Markus Neteler <neteler at osgeo.org>:
>> Options:
>> a) add a new key-value pair to PROJ_INFO
>> + all information is stored in single place
>> + projection information reading/writing code is already inplace
>> - it needs to be changed to deal with a new key-value pair
>> - breaks backwards compatibility
>
> For sure it breaks it? I didn't look at the routines.

I am not sure in which sense it could break the backwards
compatibility. The Key_Value structure for PROJ_INFO will have one
more item called "epsg" (or not if not defined). The scripts which
would depend on number of items in PROJ_INFO, etc. are just badly
written.

Martin

-- 
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa