Skip to content

New geoconvert api changes#886

Merged
Blodir merged 3 commits intodevelopmentfrom
new-geoconvert-23000-vir
Jan 14, 2026
Merged

New geoconvert api changes#886
Blodir merged 3 commits intodevelopmentfrom
new-geoconvert-23000-vir

Conversation

@aorin
Copy link
Contributor

@aorin aorin commented Jan 12, 2026

https://23000.viranomaiset-dev.laji.fi/

Can be tested by selecting a file download and downloading it in a gis format here https://23000.viranomaiset-dev.laji.fi/en/usage/my-downloads (if you don't have any file downloads you can make one here https://23000.viranomaiset-dev.laji.fi/en/observation).

The new geoconvert api has some changes compared to the old one, for example the person token needs to be included in all the requests and the format query parameter is not used.

queryParams['personToken'] = personToken;
}
const params = new HttpParams({fromObject: queryParams});
return this.httpClient.get<GeoConversionStatusApiResponse>('/api/geo-convert/status/' + conversionId, {params});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could this be converted to use laji-api-client-b at the same time?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Geoconvert api swagger is not correct at the moment so the typings are wrong, I would wait for it to get fixed first. It might not make it to this release if the release is going to be soon

@Blodir Blodir added this to the Release 88 milestone Jan 14, 2026
@Blodir Blodir merged commit 8d230b4 into development Jan 14, 2026
1 check passed
@Blodir Blodir deleted the new-geoconvert-23000-vir branch January 14, 2026 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants