Gabriel Cardona

In addition to the above, we would like to show the walking time to the destination. As a possible option to calculate this, we could use this API: https://developers.arcgis.com/javascript/3/jssamples/analysis_connectoriginstodestinations.html

This could be presented similar to GoPhillyGo, where an icon is used to indicate the type of directions presented and the walking distance/time are separated by a small element: https://gophillygo.org/?origin=39.952545%2C-75.1625599&originText=City%20Hall%2C%20Philadelphia%2C%20Pennsylvania%2C%2019107&mode=BICYCLE&maxWalk=482802&wheelchair=false&bikeOptimize=GREENWAYS&arriveBy=false&dateTime=&destination=39.958162%2C-75.1783254&destinationText=Race%20Street%20Crossing%20(SRT)&tourMode=false

@waltribeiro - Could you test this again on the beta site(https://beta.phlask.me)? I believe we may have fixed this when moving to the new info panels.

Closing as this has been resolved ✅

@cjfit is correct, the environment variables will be resolved during the build phase, so the time to set it would be in GitHub actions. The resolved value would be preserved...

For anyone reading this in the future, we are exploring this update after a dev circle poll to explore alternative options for our imports: https://codeforphilly.slack.com/archives/C03F02LUDJQ/p1725144372740349

This will be made easier by work @RNR1 is doing to switch us over from create-react-app to vite-js 🎉

In a sense, we're asserting that the form can be completed by reaching the end state where all pages of the form are interacted with and all relevant data fields...

These are awesome notes, thanks for putting them together @ravicodelabs ! I'm looking through the scenarios and PR 👀 As for the note about the default location being city hall...

Closing this as it has been addressed, thanks again @ravicodelabs !