Do not display Coordinates Resolved for nonsense coordinates

[ojalaquellueva]

Current, hyperlinked values for Coordinates Resolved are displayed for nonsense coordinates with values outside the allowed range of -90:90 for latitude and -180:180 for latitude (Coordinate Status="Coordinate values out of bounds"). Nothing should be displayed in column Coordinates Resolved for coordinates with Coordinate Status="Coordinate values out of bounds" or Coordinate Status="Coordinates non-numeric". Values should only be displayed for coordinates which appear on the map.

[ojalaquellueva]

I have reopened this issue as out-of-bounds coordinates were still displaying. However, the main solution was with the API. I have updated the API to remove out-of-bounds coordinates from field latitude and longitude. However, there is still an additional problem on web app end: a single comma now displays for nonsense coordinates (both "out of bounds" and "non-numeric"). This is no doubt the result of concatenating the empty latitude and longitude columns with a comma delimiter. Please correct this behavior so that column Coordinates Resolved is completely blank for "out of bounds" and "non-numeric" coordinates.

[ojalaquellueva]

See ojalaquellueva/gvs#8 (completed).