Smartphone Design Thoughts
17 views
Skip to first unread message
Rick Dietz
Jul 30, 2013, 4:14:51 PM7/30/13
to open311...@googlegroups.com
I have been working with a group at IU on visual design suggestions for the mobile devices. I think there are a lot of good ideas. I just want to share what we have been discussing. WE are not devising a definitive interface, but I thought some of our ideas might inform your progress. I am posting this to open up a conversation.
By the way, all of the screen shots I have seen look very good so far.
Let me know what you think or if you have any questions or feedback.
-Rick
On the "Homepage" there are 3 main sections
Title Area
* includes Name of City/Jursidiction/Organization
* New Report Button goes to chooser page for all report types
My Reports Area
List of top 3 reports that a person makes
"All" button goes to complete reports list
"ReportName >" Button goes to reports page filtering only that report
"+" goes to new report page for that type of report
Settings Area
* Contact info - this should go to a chooser page or pop-up dialog with a pre-set option for Anonymous.
* Server Chooser
-------
~~~~~~~~~~~~~~~~~~~~~~~~~
Rick Dietz, Director
Information & Technology Services Dept.
City of Bloomington, Indiana
812.349.3485 (office) 812.340.7958 (cell)
die...@bloomington.in.gov
Peter Watkins
Jul 30, 2013, 5:22:31 PM7/30/13
to open311...@googlegroups.com
1) I really like "Report As" and the built-in Anonymous option.
2) How are you planning to get the "nearby" reports? Pass bounding box
coords to /requests.FMT? Or just grab all open tickets with that
service_type and mapping those found to be within the visible map
extent? (This goes beyond UI, but ISTM that the client could include
"extraneous" bounding box info and Open311 endpoints that don't support
bounding box queries would ignore the coordinates and at least not
behave any worse than if the client omitted info about the map extent.)
3) Any thoughts about how you might deal with open tickets that don't
have geocoordinates? We have a mid-range plan to batch geocode tickets
that don't have lat/lng, but currently a good portion of our tickets
have address strings but no coordinates. On our public website we
currently just list a table of street addresses for similar, open
tickets since so many cannot be mapped (yet).
-Peter
2) How are you planning to get the "nearby" reports? Pass bounding box
coords to /requests.FMT? Or just grab all open tickets with that
service_type and mapping those found to be within the visible map
extent? (This goes beyond UI, but ISTM that the client could include
"extraneous" bounding box info and Open311 endpoints that don't support
bounding box queries would ignore the coordinates and at least not
behave any worse than if the client omitted info about the map extent.)
3) Any thoughts about how you might deal with open tickets that don't
have geocoordinates? We have a mid-range plan to batch geocode tickets
that don't have lat/lng, but currently a good portion of our tickets
have address strings but no coordinates. On our public website we
currently just list a table of street addresses for similar, open
tickets since so many cannot be mapped (yet).
-Peter
Cliff Ingham
Jul 31, 2013, 8:54:47 AM7/31/13
to open311...@googlegroups.com
2) We will be passing bounding box coordinates as a parameter. We have
a Google Summer of Code project underway that is implementing the
bounding box search on the server side in uReport.
https://github.com/City-of-Bloomington/uReport/tree/mapping
The way we've written the mobile apps includes the AvailableServers
configuration file which tells the app what features the endpoint
supports. This file is created by hand. We already use settings in the
AvailableServers to toggle some other non-standard things, like the
Media upload via POST functionality. Once the server is ready, the
mobile apps would include a new setting to toggle display of existing
service_requests on a map depending on whether the endpoint supports the
bounding box parameter. That's still a little way off, but we'll see if
we can get it implemented by this fall.
For us, when doing a request using a bounding box parameter, we only
return tickets that have coordinates. Any service_requests that do not
have lat/long are essentially invisible to the map request.
3) We also a have a fair amount of tickets that do not have coordinates,
however these are usually for things that are not georeferenced (such as
complaints about the website). All of our tickets get geogeocoded at
creation time.
Our open311 clients only send in lat/long, which we use to reverse
geocode the address string. For internally generated tickets, city
employees provide a validated address string (we are integrated with our
master address system). From that string we add the lat/long for that
address.
a Google Summer of Code project underway that is implementing the
bounding box search on the server side in uReport.
https://github.com/City-of-Bloomington/uReport/tree/mapping
The way we've written the mobile apps includes the AvailableServers
configuration file which tells the app what features the endpoint
supports. This file is created by hand. We already use settings in the
AvailableServers to toggle some other non-standard things, like the
Media upload via POST functionality. Once the server is ready, the
mobile apps would include a new setting to toggle display of existing
service_requests on a map depending on whether the endpoint supports the
bounding box parameter. That's still a little way off, but we'll see if
we can get it implemented by this fall.
For us, when doing a request using a bounding box parameter, we only
return tickets that have coordinates. Any service_requests that do not
have lat/long are essentially invisible to the map request.
3) We also a have a fair amount of tickets that do not have coordinates,
however these are usually for things that are not georeferenced (such as
complaints about the website). All of our tickets get geogeocoded at
creation time.
Our open311 clients only send in lat/long, which we use to reverse
geocode the address string. For internally generated tickets, city
employees provide a validated address string (we are integrated with our
master address system). From that string we add the lat/long for that
address.
Rick Dietz
Aug 2, 2013, 1:09:10 PM8/2/13
to open311...@googlegroups.com
On Tue, Jul 30, 2013 at 5:22 PM, Peter Watkins <pet...@tux.org> wrote:
1) I really like "Report As" and the built-in Anonymous option.
Yes, we think this is important as well. This interaction makes it easy to toggle from contact info to anonymous fairly simply.
2) How are you planning to get the "nearby" reports? Pass bounding box coords to /requests.FMT? Or just grab all open tickets with that service_type and mapping those found to be within the visible map extent? (This goes beyond UI, but ISTM that the client could include "extraneous" bounding box info and Open311 endpoints that don't support bounding box queries would ignore the coordinates and at least not behave any worse than if the client omitted info about the map extent.)
3) Any thoughts about how you might deal with open tickets that don't have geocoordinates? We have a mid-range plan to batch geocode tickets that don't have lat/lng, but currently a good portion of our tickets have address strings but no coordinates. On our public website we currently just list a table of street addresses for similar, open tickets since so many cannot be mapped (yet).
One option is to display the records with geo-coordinates and above or below the map indicate the total records (10 Mappable records, 30 Total)
R
-Peter
On 2013-07-30 16:14, Rick Dietz wrote:
I have been working with a group at IU on visual design suggestions
for the mobile devices. I think there are a lot of good ideas. I
just want to share what we have been discussing. WE are not devising
a definitive interface, but I thought some of our ideas might inform
your progress. I am posting this to open up a conversation.
By the way, all of the screen shots I have seen look very good so far.
Let me know what you think or if you have any questions or feedback.
-Rick
On the "Homepage" there are 3 main sections
Title Area
* includes Name of City/Jursidiction/Organization
* New Report Button goes to chooser page for all report types
My Reports Area
List of top 3 reports that a person makes
"All" button goes to complete reports list
"ReportName >" Button goes to reports page filtering only that report
"+" goes to new report page for that type of report
Settings Area
* Contact info - this should go to a chooser page or pop-up dialog
with a pre-set option for Anonymous.
* Server Chooser
--
You received this message because you are subscribed to the Google Groups "open311-mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open311-mobile+unsubscribe@googlegroups.com.
To post to this group, send email to open311-mobile@googlegroups.com.
Visit this group at http://groups.google.com/group/open311-mobile.
For more options, visit https://groups.google.com/groups/opt_out.
Reply all
Reply to author
Forward
0 new messages