Do not traverse relations when attaching GeoJSON

[literarymachine]

See #1953

[literarymachine]

The query to migrate the data is as follows:

INSERT {
  ?entry <http://schema.org/location> ?inherit .
}
WHERE {
  ?entry a ?clazz .
  FILTER NOT EXISTS { ?entry <http://schema.org/location> ?location }
  ?entry ?traverse ?target .
  ?target <http://schema.org/location> ?inherit .
  FILTER (
    ?traverse = <http://schema.org/mentions> ||
    ?traverse = <http://schema.org/member> ||
    ?traverse = <http://schema.org/agent> ||
    ?traverse = <http://schema.org/participant> ||
    ?traverse = <http://schema.org/provider> ||
    ?traverse = <http://schema.org/publisher> ||
    ?traverse = <http://schema.org/creator> ||
    ?traverse = <http://schema.org/isRelatedTo>
  )
  FILTER (
    ?clazz = <http://schema.org/Article> ||
    ?clazz = <http://schema.org/Person> ||
    ?clazz = <http://schema.org/Organization> ||
    ?clazz = <http://schema.org/Service> ||
    ?clazz = <http://schema.org/Action> ||
    ?clazz = <http://schema.org/Event> ||
    ?clazz = <http://schema.org/WebPage> ||
    ?clazz = <http://schema.org/Product> ||
    ?clazz = <http://schema.org/Policy>
  )
}

This will effectively add the corresponding locations to all entries that don't have an explicit one according to our current inheritance rules.