- Option: Always show parcels
Probably not advisable. Unless we rasterize the parcel layer, this will mean sending a lot of data to the client. It also means that the client has to manipulate that data. There are 13,541 shapes in the Somerville parcel data
- Option: Only show parcels at a high zoom level, a la the ArcGIS web viewer
- Option: Only show parcels for the ‘relevant’ properties
The definition of ‘relevant will vary by the active view type. If we want to show historical zoning data, this would mean showing only parcels for which data is available. Other views and filters would work as expected.
- Option: Hybrid
Show all parcel shapes, but only enable interaction with relevant properties. We could achieve this by serving the parcels as a raster image.
- View the history of a parcel
- View an ‘activity overlay’ of the city. Divide the city into smaller regions (need a strategy for doing this), group markers by region,
Eventually, it would be great to show site plans directly on the site. They could be presented as popups, or if we can massage the data into a machine-readable format, as overlaps.
- Set up the server to periodically scrape the Reports and Decisions page for permits
- Determine which permits are “stale” (where “stale” has some reasonable definition)
- Record the observation (raw data?)
- Save updates to the relevant cases
- Record user notification preferences and contact information.
- Create an interface for users to access and change their preferences
- Get the latest changes
- Send email/SMS/push notifications
This is an option for users who do not want to provide us with registration details. The RSS feed URL endpoint should accept all the same filters we use elsewhere.