That makes more sense to me. This particular case might not work
properly. Let's see if I can fix it :-)
Cheers
Victor
2011/7/7 Antonio Falciano <afalci...@yahoo.it>:
> Il 07/07/2011 17.03, Nacho Uve ha scritto:
>>
>>
>> 2011/7/7 Victor Olaya
>>
>> Nacho,
>>
>> I am afraid I need more information to reproduce the errors. This is
>> what I have tried.
>>
>> 1)I create a model which takes a DEM and calculates slope twice. I am
>> able to configure both executions of slope separately...
>>
>>
>> I realize that only happens when save and re-open the new model. Then
>> both algs share the same parameters when editing.
>>
>> 2)I creted a model that taes a vector layer and a field. Autoincrement
>> works fine. Then I remove the field and enter a fixed field name that
>> exists in the input layer and it also works fine.
>>
>>
>> Hummm... I test with the followed model:
>>
>> 1.- Create aleatory vector layer
>> 2.- Add Field ("ID", Numeric, 5, Integer)
>> 3.- Autoincrement with "ID"
>>
>> And I get the following message:
>>
>> java.util.concurrent.ExecutionException:
>> es.unex.sextante.exceptions.GeoAlgorithmExecutionException: ERROR: Field
>> ID not found in layer Result
>> at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
>
> Hi all,
> I confirm the ExecutionException reported by Nacho obtained with the
> recent nightly build. The model is in attachment. ;)
> It seems that the fields of random layers are not recognized by the
> following procedures.
>
> Cheers,
> Antonio
>
> --
> Antonio Falciano
> http://www.linkedin.com/in/antoniofalciano
>
> _______________________________________________
> Sextante-users mailing list
> Sextante-users@lists.forge.osor.eu
> https://lists.forge.osor.eu/listinfo/sextante-users
>
>
_______________________________________________
Sextante-users mailing list
Sextante-users@lists.forge.osor.eu
https://lists.forge.osor.eu/listinfo/sextante-users
