You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
A slight change of plans: as all addresses are now in the database, geocoding will not be needed in Linkedevents, so #318 is closed. Helsinki has no use case for this at the moment (since we import all the addresses already), but the functionality should still be included for other cities.
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 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.
The text was updated successfully, but these errors were encountered: