Feature #1595
closed
API: Subunits for Ariadne and THANADOS
Description
API output for Ariadne.
Maybe they need it in Open Archive format: http://www.openarchives.org/, but they are not so sure either. However, the format should be XML.
Ariadne requires each entity in a single XML tag. How these tags are called are not significant for them, as long as they are clear.
Stefan and Bernhard decided to an abstraction from the THANADOS GeoJSON format, which will then transformed into XML. (#1603)
Implementation
Endpoint: /api/0.3/subunits/<id> (has to be a place ID)
Parameters: count <bool>, download <bool>, format <xml>
Result: List of the place with all its subunits. The format is based on the Thanados GeoJSON standard.
Updated by Bernhard Koschiček-Krombholz over 1 year ago
- Blocked by Feature #1603: API: Specialized GeoJSON format for subunits added
Updated by Bernhard Koschiček-Krombholz over 1 year ago
- Description updated (diff)
- Assignee set to Bernhard Koschiček-Krombholz
Updated by Bernhard Koschiček-Krombholz over 1 year ago
- Status changed from Acknowledged to Resolved
Right now, the Ariadne team tests the output, but it looks very promising. This ticket will stay open, until the Ariadne tests are complete.
Updated by Alexander Watzinger 12 months ago
Just wanted to ask if there is any progress with this issue because last update was half a year ago.
Updated by Bernhard Koschiček-Krombholz 12 months ago
I will close it, and we also can give it to the roadmap.
As far as I know, is everything done from OpenAtlas point of view. I will open a new ticket, if major changes are demanded.
Updated by Bernhard Koschiček-Krombholz 12 months ago
- Subject changed from API: Ariadne to API: Subunits for Ariadne and Thanados
- Description updated (diff)
- Status changed from Resolved to Closed
- Target version changed from 208 to 7.4.0
Updated by Alexander Watzinger 12 months ago
- Subject changed from API: Subunits for Ariadne and Thanados to API: Subunits for Ariadne and THANADOS
- Description updated (diff)