@hellblazer
You should be able to use things like "left outer joins" (&co) to do that. From Locality up to Country.
Or you could use hierarchic queries. Connect by level etc. (though most people find those more tricky to build)
@hellblazer
You should be able to use things like "left outer joins" (&co) to do that. From Locality up to Country.
Or you could use hierarchic queries. Connect by level etc. (though most people find those more tricky to build)
Thanks, @gio for your answer
I am trying joins at my end but not really getting through, since it is after all only one schema(table).
Can we not expose list out words? So, the problem I am facing is, if the locality value is empty, the town value is shifting to the locality column(shifting because the first element is district ).
@hellblazer
You can access one table multiple time with aliases. So that's not a limitation.
But we are not talking sql, I understand now.
Shifting because of non existing/missing/null attributes. Then you can replace null/missing/empty values with a (for instance) underscore prior to using the SpatialRelator.
SpatialRelator has no option to keep null or empty attributes (whilst some other transformers do have this option..)