We've spent some time with this in the past, but don't currently have an
operational service. You can find more details at
http://wiki.open311.org/GeoWeb_DNS/
Ideally this would be done in away that's not specific to 311/Open311, but
can be applied to any common geographic boundary/jurisdiction specific API
endpoint. I'm involved with some similar work for looking up basic
government contact details for governments (http://docs.opencivicdata.org/)
and would probably want to try to merge Open311 location lookup services
with much of the same boundary-lookup infrastructure used there (
http://represent.poplus.org/)
We could treat the server endpoint list
<http://wiki.open311.org/GeoReport_v2/Servers/> (or a future incarnation of
it) as a canonical source of data with jurisdictions submitting their API
endpoint URLs along with whatever they consider their official boundary
polygon (as linked geojson or shapefile in WGS84), but allow multiple
lookup services to be offered based on that data.
Ideally this would evolve into a more robust network that could federate
and route to lower levels as necessary much like DNS so that a national
government might only need to manage a service that delegates to regional
governments and then each regional government could route to the city
government boundary lookup service for final endpoint resolution.
LoST is a similar concept that's been proposed in the context of 911
emergency services - http://tools.ietf.org/html/rfc5222
On Tue, Dec 15, 2015 at 4:06 PM, Milo van der Linden - Code Fellow
Eindhoven <<email obscured>> wrote:
> Open311 Lists <http://lists.open311.org>
> [image: Photo of Milo van der Linden - Code Fellow Eindhoven]
> <http://lists.open311.org/p/3gBy5lHo5oSYB3vbKvxM4d> *[open311 discuss]
> List of tools/companies supporting Open311?*
> <http://lists.open311.org/r/topic/6FkxUZDuGoUUGAyscmLReT> by *Milo van
> der Linden - Code Fellow Eindhoven*
> <http://lists.open311.org/p/3gBy5lHo5oSYB3vbKvxM4d> in *Open311 Discuss*
> <http://lists.open311.org/groups/discuss>
> ------------------------------
> "the main challenge is actually orchestrating the routing and delegation
> among
> agencies, not implementing the API."
>
> Interesting you bring this up as this has been occupying my mind the last
> couple of days. One thing I was thinking about is setting up a geographic
> boundary per jurisdiction and/or open311 endpoint. It would then be good to
> set up a central service of some kind that would respond to a geographic
> query narrowing down the set of possible organisations to handle a service
> request in a certain geographic location.
>
> At first we could pick administrative boundaries. For instance, from
> OpenStreetMap, and experiment with that. We might set up a whole new
> service or see if this can for instance find its way to http://
> *status.open311.org*/ <http://status.open311.org/> which can potentially
> be a good central source of available and active service and can combine
> the boundary for an organisation with the status of the open311 endpoints
> thus being able to further narrow down the potential 311 services to use.
> ------------------------------
> ⮪ Reply
>
<discuss@lists.open311.org?subject=Re%3A%20%5Bopen311%20discuss%5D%20List%20of%20tools/companies%20supporting%20Open311%3F>
> 🖂 New topic <discuss@lists.open311.org> View topic…
> <http://lists.open311.org/r/topic/6FkxUZDuGoUUGAyscmLReT> Unsubscribe
>
<discuss@lists.open311.org?subject=Unsubscribe&body=Hello%2C%0A%0APlease%20remove%20me%20from%20Open311%20Discuss%0A%3Chttp%3A//lists.open311.org/groups/discuss%3E%0A%0AThank%20you.>
> • Switch to a daily digest
>
<discuss@lists.open311.org?subject=Digest%20on&body=Hello%2C%0A%0APlease%20switch%20me%20from%20receiving%20one%20email%20per%20post%20to%20the%20daily%0Adigest%2C%20which%20summarises%20the%20all%20the%20posts%20made%20each%20day%20in%0AOpen311%20Discuss%0A%3Chttp%3A//lists.open311.org/groups/discuss%3E%0A%0AThank%20you.>
operational service. You can find more details at
http://wiki.open311.org/GeoWeb_DNS/
Ideally this would be done in away that's not specific to 311/Open311, but
can be applied to any common geographic boundary/jurisdiction specific API
endpoint. I'm involved with some similar work for looking up basic
government contact details for governments (http://docs.opencivicdata.org/)
and would probably want to try to merge Open311 location lookup services
with much of the same boundary-lookup infrastructure used there (
http://represent.poplus.org/)
We could treat the server endpoint list
<http://wiki.open311.org/GeoReport_v2/Servers/> (or a future incarnation of
it) as a canonical source of data with jurisdictions submitting their API
endpoint URLs along with whatever they consider their official boundary
polygon (as linked geojson or shapefile in WGS84), but allow multiple
lookup services to be offered based on that data.
Ideally this would evolve into a more robust network that could federate
and route to lower levels as necessary much like DNS so that a national
government might only need to manage a service that delegates to regional
governments and then each regional government could route to the city
government boundary lookup service for final endpoint resolution.
LoST is a similar concept that's been proposed in the context of 911
emergency services - http://tools.ietf.org/html/rfc5222
On Tue, Dec 15, 2015 at 4:06 PM, Milo van der Linden - Code Fellow
Eindhoven <<email obscured>> wrote:
> Open311 Lists <http://lists.open311.org>
> [image: Photo of Milo van der Linden - Code Fellow Eindhoven]
> <http://lists.open311.org/p/3gBy5lHo5oSYB3vbKvxM4d> *[open311 discuss]
> List of tools/companies supporting Open311?*
> <http://lists.open311.org/r/topic/6FkxUZDuGoUUGAyscmLReT> by *Milo van
> der Linden - Code Fellow Eindhoven*
> <http://lists.open311.org/p/3gBy5lHo5oSYB3vbKvxM4d> in *Open311 Discuss*
> <http://lists.open311.org/groups/discuss>
> ------------------------------
> "the main challenge is actually orchestrating the routing and delegation
> among
> agencies, not implementing the API."
>
> Interesting you bring this up as this has been occupying my mind the last
> couple of days. One thing I was thinking about is setting up a geographic
> boundary per jurisdiction and/or open311 endpoint. It would then be good to
> set up a central service of some kind that would respond to a geographic
> query narrowing down the set of possible organisations to handle a service
> request in a certain geographic location.
>
> At first we could pick administrative boundaries. For instance, from
> OpenStreetMap, and experiment with that. We might set up a whole new
> service or see if this can for instance find its way to http://
> *status.open311.org*/ <http://status.open311.org/> which can potentially
> be a good central source of available and active service and can combine
> the boundary for an organisation with the status of the open311 endpoints
> thus being able to further narrow down the potential 311 services to use.
> ------------------------------
> ⮪ Reply
>
<discuss@lists.open311.org?subject=Re%3A%20%5Bopen311%20discuss%5D%20List%20of%20tools/companies%20supporting%20Open311%3F>
> 🖂 New topic <discuss@lists.open311.org> View topic…
> <http://lists.open311.org/r/topic/6FkxUZDuGoUUGAyscmLReT> Unsubscribe
>
<discuss@lists.open311.org?subject=Unsubscribe&body=Hello%2C%0A%0APlease%20remove%20me%20from%20Open311%20Discuss%0A%3Chttp%3A//lists.open311.org/groups/discuss%3E%0A%0AThank%20you.>
> • Switch to a daily digest
>
<discuss@lists.open311.org?subject=Digest%20on&body=Hello%2C%0A%0APlease%20switch%20me%20from%20receiving%20one%20email%20per%20post%20to%20the%20daily%0Adigest%2C%20which%20summarises%20the%20all%20the%20posts%20made%20each%20day%20in%0AOpen311%20Discuss%0A%3Chttp%3A//lists.open311.org/groups/discuss%3E%0A%0AThank%20you.>