Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Full-history endpoints return wrong parameters in the response #191

Closed
bonaparten opened this issue May 12, 2021 · 0 comments · Fixed by #192
Closed

Full-history endpoints return wrong parameters in the response #191

bonaparten opened this issue May 12, 2021 · 0 comments · Fixed by #192
Labels
bug Something isn't working

Comments

@bonaparten
Copy link
Contributor

bonaparten commented May 12, 2021

Bug Description

A full-history extraction returns in the response the parameters @snapshotTimestamp and/or @lastEdit if the last edit of the OSM entity happened before the period of time requested.

General Information

  • ohsome API 1.4.1
  • API instances: remote instance https://api.ohsome.org/v1 and local instance with an h2 file
  • Affected endpoint(s) [e.g. /elementsfullhistory{geometryType}]
  • Request URL
  • HTTP method: GET
  • Utilized tool/library for the request: Swagger and cURL

Expected Behaviour

Since the full-history endpoints give the full history of the OSM entities at a given time, @snapshotTimestamp and @lastEdit should not be present in the response.

@bonaparten bonaparten added the bug Something isn't working label May 12, 2021
@bonaparten bonaparten changed the title Full-history endpoints returns wrong parameters in the response Full-history endpoints return wrong parameters in the response May 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant