streetlives / yourpeer.nyc

The open source repository behind the yourpeer.nyc web application
https://yourpeer.nyc
MIT License
0 stars 0 forks source link

Standardize addresses #245

Open doobneek1 opened 3 weeks ago

doobneek1 commented 3 weeks ago

We should have a standard that is enforced in order to save the filed, like instead of typing 125 West 25 St Nicholas Street, 1 suite, New York, NY, it would prevent CIS from duplicating New York, NY as it will be filled automatically and will suggest typing: 125 W 25th St. Nicholas St, Ste 1 It should make CIS explicitly indicate whether there is a Floor, Suite, custom directions, or no room number.

it will also ask whether you need: 1) an ID (if so, what type) and /or an appointment, or 2) you cannot walk in as it is a confidential address

the outputs will look like: 1) You will need any sort of ID (even a school ID will work) to enter the building, an appointment is required. 2) This is a confidential location/corporate office not accepting any clients, please read about how you can access their services below: (referring to services, where we would describe whether it is a shelter/online service, etc, of course, the pin on the front end should be moved automatically to the closest middle of the road and get directions hyperlink would not be shown) That would standardized the input and eliminate the need of typing this from scratch in red lettering, some services can have different or no info on entry and others will but it will vary from CIS to CIS, when an update is needed it can be hard to edit.

adambard1 commented 1 day ago

"instead of typing 125 West 25 St Nicholas Street, 1 suite, New York, NY,..." Not sure I understand. We don't enter the city or state anyway. Are you suggesting an automatic address match from a series of options like those in sign up forms for some kinds of services?

adambard1 commented 1 day ago

Generating ID requirements to enter a location from its address sounds like we need to make sure we gather that info in the first place and have a data field to put it. Hopefully we have it in the Documents required section of services at these locations.

Identifying confidential locations sounds very helpful, but if it is confidential then I expect we wouldn't want to show it at all. Perhaps we can use a neighborhood boundary to signal the area rather than a pin? We'd have to have a way to signal to the DB in the first instance on GoGetta that we are creating a confidential location - maybe a checkmark or radio button, before the tool can identify it subsequently. We'd also need to be able to override the confidentiality if it changes. So there are afew things to think about in designing it.

An icon for confidential locations in the list view might be interesting, and we could put some thought toward how anyone browsing the map could know there are confidential locations in the area they're searching.