Closed aalexandrasilva closed 1 year ago
Why you renamed the property ngeo:geometry
and considered its value as a string?
Why you renamed the property
ngeo:geometry
and considered its value as a string?
This configuration file was shared with me by Sherif, the metrics were changed to also include a string similarity in exactmatch(s.strGeo,t.StrGeo)
.
Are you able to get result with this configuration?
Yes, if I feed this configuration to limes I get:
15:47:43.242 [main] [] INFO org.aksw.limes.core.controller.Controller:226 - Mapping size: 134 (accepted) + 4070 (need verification) = 4204 (total)
I see if you replace MINUS(geo_hausdorff(s.GEOMETRY,t.GEOMETRY)|0.5,exactmatch(s.strGeo,t.StrGeo)|0.5)
with geo_hausdorff(s.GEOMETRY,t.GEOMETRY)|0.5
are you still able to generate results?
Yes.
15:54:56.889 [main] [] INFO org.aksw.limes.core.controller.Controller:226 - Mapping size: 424 (accepted) + 4070 (need verification) = 4494 (total)
Why you renamed the property
ngeo:geometry
and considered its value as a string?
The old geometry url is not working any more. i.e., the LGD changed the used ontology, that is why it was working but with no results.
the second parameters of the MINUS operator is just to make sure not to get instances ner by itself
As requested, changed the LGD example configuration to: