Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> Andrea Aime wrote:
>>> Justin Deoliveira ha scritto:
Unfortunately I have run into this issue in a few places, and the
only time the answer is to do a full lookup. I always to try to set
fullScan to false, but it seems to only w
Justin Deoliveira ha scritto:
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Unfortunately I have run into this issue in a few places, and the
only time the answer is to do a full lookup. I always to try to set
fullScan to false, but it seems to only work some of the time. I
understand the
Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> Unfortunately I have run into this issue in a few places, and the only
>> time the answer is to do a full lookup. I always to try to set
>> fullScan to false, but it seems to only work some of the time. I
>> understand the cost of the lookup
Justin Deoliveira ha scritto:
> Unfortunately I have run into this issue in a few places, and the only
> time the answer is to do a full lookup. I always to try to set fullScan
> to false, but it seems to only work some of the time. I understand the
> cost of the lookup but I see no other altern
Unfortunately I have run into this issue in a few places, and the only
time the answer is to do a full lookup. I always to try to set fullScan
to false, but it seems to only work some of the time. I understand the
cost of the lookup but I see no other alternative in a case where you
*need* an S
Hi,
investigating why saving a feature type was taking so long
on trunk I found out this code:
@Override
public String toString(Object obj) {
CoordinateReferenceSystem crs = (CoordinateReferenceSystem) obj;
try {
return "EPSG:" + CRS.lookupEpsgCode(crs, true);
}
catch
