Linked data service (SPARQL) - Receiving modified addresses

[Lucca Kaiser]

Hi,

we've been using the following SPARQL request to get recently modified addresses by modification date:

```

curl 'https://geo.ld.admin.ch/query' \
-H 'accept: application/sparql-results+json' \
-H 'content-type: application/x-www-form-urlencoded; charset=UTF-8' \
-H 'origin: https://geo.ld.admin.ch' \
--data-raw 'query=prefix+xsd%3A+%3Chttp%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema%23%3E%0Aprefix+schema%3A+%3Chttp%3A%2F%2Fschema.org%2F%3E%0A%0ASelect+%3Fid+where+%7B%0A+GRAPH+%3Curn%3Abgdi%3Alocation%3Aaddresses%3E+%7B%0A+++%3Fs+a+schema%3APostalAddress+.%0A+++%3Fs+schema%3AdateModified+%3Fdate+.%0A+++%3Fs+schema%3Aidentifier+%3Fid+.%0A++++++++FILTER(%3Fdate+%3D+%222023-09-05%22%5E%5Exsd%3Adate)+%0A++%7D+%0A%7D'

```

Same as screenshot:

On certain days (i.e. 2022-09-05) we receive all addresses (~3'100'00), on other days (i.e. 2022-09-06) we get 0. Is there a problem with the data, are all addresses modified on the same day now, or is there a problem with our request? We've been using the same request for a quite some time and it worked fine with a steady amount of modified addresses per day.

Thanks for your help.

Best regards,

Lucca

[Pasquale Di Donato]

Dear Lucca,

many thanks for highlighting this.

There is actually a problem with the source data and we are on it to understand where exactly the issue happens in the data production/integration pipeline.

We'll be back to you as soon as the issue will be fixed.

Sincerely,

Pasquale