bad lat/lon specifications causing editor hangups

[scott2b]

Users who are interpreting the helper text to mean that their lat/lon values should be enclosed in angle brackets <>, are having editor hangups due to the inability to interpret the resulting bracketed values.

In general, we should probably clean out non-numeric characters when we parse lat/lon from the input here https://github.com/NUKnightLab/StoryMapJS/blob/master/templates/edit.html#L1621

[scott2b]

An additional bug has surfaced which seems to indicate that the parser is not cleanly extracting lat and lon values in the case of extraneous symbols. In this case, it appeared that the user may have included a comma after the lat value, which was being propagated to the StoryMap data.

[scott2b]

I am unable to reproduce this latter issue with respect to commas leaking into the data. The relevant parsing code is here:

StoryMapJS/templates/edit.html

Line 1621 in b0cf5f1

function parseLatLon(s) {

I see no indication that a comma should be captured nor that the values for lat and lon should end up being stored as strings rather than decimal values. I do see that there is a token split that is not utilized which seems to probably be an artifact of an attempt at a different approach, but seems like a benign no-op effectively.