RoadFlaw.com
Matt Paulin
As I talked about last night, we are putting together a hands on
activity for mapping enthusiast. The details are here
http://docs.google.com/View?docid=dd9th8k2_14g85qp5hp
Over the next month we will hammer out more of the specifics. If you
are interested in planning or contributing to the idea you can talk to
me in irc here. irc://freenode/cugos, or at this email address. I
am pretty swamped right now so I might take some time to get back to
you, but I will respond :)
Our current plan is to get together Saturday Sept 27 from 1pm - 7pm.
This may be subject to change but I will send out more emails as we
get closer.
Some of the things I could use help with at this point is gathering
resources. If anyone can provide the following resource that would be
wonderful.
1) A server that can handle web hosting for Django and Postgres with
PostGIS installed
2) SVN hosting
3) Task management/Bug tracking (Tracs, Mantis, Bugzilla, Whatever...)
Cheers,
-Matt Paulin
Michael Gerlek
* is this a Seattle-only thing? (I'm specifically interested in
adding Bainbridge to the project's bounding box)
* it says "classify the flaw as either for cars or bikes" -- I'd
suggest adding pedestrians and boaters/kayakers too.
* one feature I'd like to see is an RSS feed of flaws in my area.
Could be done by zipcode, but bbox (GeoRSS) would even better (since I
don't care about flaws on the south side of the Island)
* flaws might want some sort of expiry date on them, to preserve
freshness (since, ideally, potholes will get fixed eventually...)
* as a helpful side feature, keeping a list of Contacts might be nice
-- local authorities, utility departments, etc, who can be contacted
with Flaw Reports
I've got Saturday marked off on my calender...
-mpg
--
-mpg
Roger André
I'd like to participate, but that's the weekend I'm flying my mom up from Sucramento to visit. Is there some prep work I could help with?
Roger
--
Matt Paulin
On Fri, Aug 22, 2008 at 8:24 AM, Michael Gerlek <m...@flaxen.com> wrote:
> A few thoughts while reading your document on the way in this morning:
>
> * is this a Seattle-only thing? (I'm specifically interested in
> adding Bainbridge to the project's bounding box)
No, there isn't any reason to limit this to Seattle.
> * it says "classify the flaw as either for cars or bikes" -- I'd
> suggest adding pedestrians and boaters/kayakers too.
I think I will change that in the document. We had talked about a way
to tag flaws thus making the system open to showing any classification
structure. For instance, we can have tags for kayaker, boater, cars,
bike, trails, and then just attach these tags to the flaw.
> * one feature I'd like to see is an RSS feed of flaws in my area.
> Could be done by zipcode, but bbox (GeoRSS) would even better (since I
> don't care about flaws on the south side of the Island)
Cool! I will add that to the doc
> * flaws might want some sort of expiry date on them, to preserve
> freshness (since, ideally, potholes will get fixed eventually...)
Good point
> * as a helpful side feature, keeping a list of Contacts might be nice
> -- local authorities, utility departments, etc, who can be contacted
> with Flaw Reports
I will add this also to the doc