GML Import/Export #24
Labels
No Label
backlog
bug
duplicate
enhancement
feature
help wanted
invalid
question
wontfix
bug
duplicate
enhancement
help wanted
in discussion
invalid
priority
1
priority
2
priority
3
priority
4
priority
5
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: IT-Naturschutz/konova#24
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Status quo
Menu buttons exist. No functionality so far.
ToDo
GML import and export need to be implemented the same way the old system already provides it. The import handler is mainly being used by Kaiserslautern where they export GML files from their CAIGOS system for importing into KSP.
The following objects and all of their related data objects (payments, ...) need to be supported:
Update
As discussed with the only users of the import/export function in the current system, we will no longer focus on a gml based import and needed export functionalities.
Instead the users dev was happy to hear about the option of syncing their data using an API. Therefore this issue will no longer be pursuied. Instead we need to focus on a proper and well documented API.
This issue will not be closed (for now).