cityofaustin / cityofaustin/techstack
Locations beyond MVP
- Dominant language
- No language data
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
# What's next for Locations?
### Features we've identified that we might want to add at some point, but haven't prioritized.
**Accessibility features**
- [ ] Language access: translation services available on-site, or can be arranged upon request, braille
- [ ] Physical access: ramps, elevators, handicap parking spaces; ability to add photos
- [ ] Transportation access: accessible by city bus routes, bike, scooter, sidewalk, transit centers, bus stops, rail stops
**Hours**
- [ ] Availability: appointment-only, or walk-ins accepted
- [ ] Anticipated closures: Holidays observed, major events, seasonal hours, construction
- [ ] Unanticipated closures: emergencies, weather
**Other location types**
- [ ] Mobile services
- [ ] Temporary and seasonal services
- [ ] Co-located services, locations within larger locations
**Amenities**
- [ ] Recreation: tennis courts, pools, parks, community gardens, golf courses,
- [ ] Programs and classes: one-time, recurring, seasonal
- [ ] Cost: free, fee, financial assistance, payment types accepted
**Parking**
- [ ] Type: street, garage, residential, lot
- [ ] Cost: free, fee
- [ ] Payment types accepted
- [ ] Accessibility: handicap parking available, curb cutouts
- [ ] Status: special events
**Events**
- [ ]
## UX/Dev stuff
- [ ] ironing out our address validation, checking for duplicate address entries
- [ ] automatically getting a google streetview photo of a location based on its lat/lng instead of the user having to upload a photo
- [ ] (longer term) providing export functionality so we can easily send the data to google and other data partners
- [ ] automatically getting bus stops within a set radius
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.