We upgraded our Python API to 2.0 recently and just discovered that when geocoding using the GeoSeries.from_df() function, the geometries are getting assigned to the wrong row. I have verified that it is an issue with both the world geocoding service and our own address locator. In the screenshot on the map 1328 Steinbeck Dr, Raleigh, NC 27609 is showing as at 603 W Morgan St, Raleigh, NC 27603, which is also in the list of addresses. It looks like it is getting out of order during the conversion.
Note: tried this in an ArcGIS Online Notebook (version 1.9.1. of the API) and see the same results. See the correct results at 1.8.2. After further testing on different version, looks like this is happening since 1.9.0, seeing correct results at 1.8.5.
We upgraded our Python API to 2.0 recently and just discovered that when geocoding using the GeoSeries.from_df() function, the geometries are getting assigned to the wrong row. I have verified that it is an issue with both the world geocoding service and our own address locator. In the screenshot on the map 1328 Steinbeck Dr, Raleigh, NC 27609 is showing as at 603 W Morgan St, Raleigh, NC 27603, which is also in the list of addresses. It looks like it is getting out of order during the conversion.
Note: tried this in an ArcGIS Online Notebook (version 1.9.1. of the API) and see the same results. See the correct results at 1.8.2. After further testing on different version, looks like this is happening since 1.9.0, seeing correct results at 1.8.5.