Incorrect Location Returned From /points/{point} Endpoint

[jmdelawder]

Describe the bug
/points/{point} endpoint returns incorrect city/state for a latitude/longitude coordinate.

To Reproduce

1. Use ArcGIS /suggest endpoint to suggest locations to an end user
   Suggest Endpoint

2. Using ArcGIS results, user selects "New York, NY, USA", which initiates an API request to the /findAddressCandidates endpoint using the result text and magicKey
   Find Address Endpoint

3. Lat/Lon returned is {"x":-74.007139999999936,"y":40.714550000000031}. Subsequently querying the NWS API with /points/40.714,-74.007 returns Hoboken, NJ as the city/state in the request, but should be New York, NY

Additional context
This can be replicated by simply executing step 3.

[scadergit]

It comes down to user expectation of where the center of a geo name actually is. While our presentation layers (Alerts, Radar, Forecast, etc.) use Esri geolocation services, the API uses imported census data. The census considers the entire boundary for "New York, NY," and not the common user's expectation somewhere within Manhattan. You can see on the map below the center of the entire boundary is out near Brooklyn (red circle/x). The blue "x" is where you queried the API, and the green circles are locations in NJ that are tecnincally closer than the census' center for "New York, NY."

This is a common problem even with Esri geoservices, and we won't be able to address this anytime soon. If that geo name precision is important, it would be better to use Esri for the names and ignore the API metadata.