Essentially, this means finishing the almost-finished PR #236 .
Required for City-of-Helsinki/linkedevents-ui#420
On the API side, we do not want to limit the coordinates and addresses the users POST, since not all cities using Linkedevents have a comprehensive address and geocoding service that would allow us to ascertain the addresses and coordinates.
Therefore, locations with any addresses and coordinates should be POSTable (with the system data source), and if a data source has is_user_editable set to True, its locations should be editable via the API.
In the Helsinki use case, the UI will check the validity of the coordinate-address pairs using the #318 address endpoint.
Essentially, this means finishing the almost-finished PR #236 .
Required for City-of-Helsinki/linkedevents-ui#420
On the API side, we do not want to limit the coordinates and addresses the users POST, since not all cities using Linkedevents have a comprehensive address and geocoding service that would allow us to ascertain the addresses and coordinates.
Therefore, locations with any addresses and coordinates should be POSTable (with the system data source), and if a data source has
is_user_editableset toTrue, its locations should be editable via the API.In the Helsinki use case, the UI will check the validity of the coordinate-address pairs using the #318 address endpoint.