Spatial field validation in DCAT-US

[avdata99]

In Catalog classic (with CKAN 2.3) we skip the validation of the spatial field.
When we moved to CKAN 2.8 this validation started working and we realize we use this field without this validation.
At Catalog#55 and #319 we skip this validation again

We need to define if this is the expected behaviour or we want to use spatial field considering this validation.

One example of a CKAN-CKAN harvest source containing spatial datasets is https://datos.gob.ar/

[kimwdavidson]

let's treat as two separate fields - spatial field in DCAT-US shouldn't map to the validated field.

DCAT-US accepts text or geographic format. In the future, we may want to translate that information to the CKAN field