Re-evaluate where NaN coordinates should be allowable for Places JsonDb Plugin

The implementation currently allows coordinates which have NaN values for the latitude and longitude data fields. It should be re-evaluated whether there should be specific checks to try prevent such data being written into the database (although the plugin should be robust enough to handle reading such data).