search

curbmap / Open-Street-Parking-Restriction-Specification

An open standard for municipalities and private companies to correspond about and release information about parking restrictions for public consumption.
MIT License
7 stars 4 forks source link

Ability for city staff to input data #23

Open patwater opened 6 years ago

patwater commented 6 years ago

What's the current vision and operational practice for city staff (or others) to update the OSPRS (?) data? One idea would be to enable a javascript webform similar to what our team developed for our open water rate specification (OWRS). See http://survey.californiadatacollaborative.org/ for the live site and see here for the underlying GitHub repo https://github.com/California-Data-Collaborative/OWRScreator

That web form automatically submits a PR that can be reviewed prior to being merged into the master repo.

patwater commented 6 years ago

Oh is that what this tool is intended to do? https://github.com/curbmap/new.curbmap.com

eselkin commented 6 years ago

We have no input mechanism. OSPRS is a specification for communication and maybe to structure a municipality's data for storage themselves. When you're talking about inputting data, I expect you mean to our database. Our database collects all OSPRS data fields and some extra (but those are mainly user information and internal values). If anyone wants to modify the OSPRS, we welcome pull-requests. The site "new.curbmap.com" will be a way for users to decode, jointly decipher, signage and other objects related to parking. Adding data (and using that data for exploring parking around you) is left to the mobile apps (iOS and android).

patwater commented 6 years ago

@vr00n you would enjoy taking a look at this project again. In many ways an open source coord.co

eselkin commented 6 years ago

coord.co is a business to business approach. They are digitizing google's vast catalog of streetview data and combining municipality data. They will then provide this service at a cost to businesses. It is a very good model, but I'm not sure it is a sustainable model, since cities change their restrictions all the time and only document it most of the time. Who knows how long the process will be to go from a change in the physical world to its reflection in their database.

patwater commented 6 years ago

Maybe... note there's ample examples of businesses taking public data like land use information and commercial entity classifications from government and reselling it to businesses. See ParcelQuest, Dunn and Bradstreet, etc.

What's OWPRS's idea for how to keep the restrictions data more up to date? Won't this project have the same issue with cities only documenting some of the time?

eselkin commented 6 years ago

crowdsourcing... continually updating data.

vr00n commented 6 years ago

Could you perhaps?

  1. Use www.openstreetcam.org to survey street parking / curb signs
  2. Load images to www.zooniverse.org
  3. Conduct an epic Tag-a-Thon to digitize street sign imagery into OSPRS format.
  4. Repeat until you have encoded all streets signs FTW.
eselkin commented 6 years ago

Zooniverse has restrictions about what kind of data you can put on there (like published research etc. and it has to fit into one of their disciplines). I've just built a React classifying/labeling tool that would do a more detailed labeling job than Zooniverse anyway that's going to go up at curbmap.com shortly. Also openstreetcam has very little data. And the tag-a-thon is what we are going to try to do on user inputted photos.

patwater commented 6 years ago

Cool is there a link to the code for the classifying app you built? Also you're right openstreetcam has very little data in LA though that's a great reason to change that and add more! Note multiple benefits with openstreetcam beyond this parking restriction specification including improving open street map and measuring street quality.

eselkin commented 6 years ago

@patwater: There's no link yet, I'm going to put it up this weekend... it will be at curbmap.com