Create org location error should remain on screen & prevent progression

[alexelash]

If I enter a location that does not have climate data, the relevant input gets the error message for a moment, but it disappears. This made me think that the error message showed up accidentally, so I kept creating my org.

At step 3, however, the app takes me back to step 1 and the error message is now correctly placed under the input + the next button is disabled.

Expected, option 1:

• Enter location without climate data
• Error message appears and stays
• User can't proceed past step 1, next button is disabled

Expected, option 2 (maybe better?):

• Enter location that has no climate data
• Dropdown list shows it as disabled
• User can hover on the disabled item to see a hover that explains: "No climate data for this location. Contact us using the link below."
• User can't proceed past step 1, next button is disabled.

[maurizi]

The blink and you'll miss it flash of the "No climate data" error is in fact unintentional - we have no way of knowing if there is climate data until we check the server results.

We intentionally decided not to check for climate data until the form is posted when originally added the geocoder on this page. Staging is misleading because we don't have much climate data ingested on the staging database, however on the production database we believe we can cover most of the populated portions of the continental united states, and so the "No climate data" error should be rather rare.