Current implementation is dependent on the existence of a field '4' in destination. I found artifacts that has this field empty, leading to exception throwing, even with the field '1' filed with an descriptive address, and the destination coordinates.
I guess that when the source/destination is a named place, the name is informed in field 4. When it is an address, not named, the field '4' is empty and the descriptive address is informed in field '1'. But this need more samples to validate.
Current implementation is dependent on the existence of a field '4' in destination. I found artifacts that has this field empty, leading to exception throwing, even with the field '1' filed with an descriptive address, and the destination coordinates.
I guess that when the source/destination is a named place, the name is informed in field 4. When it is an address, not named, the field '4' is empty and the descriptive address is informed in field '1'. But this need more samples to validate.