I am polling an external website for XML data that will then update a hosted feature service with point data for stream gauges. One of the issues with the XML data is that the lat and long are in DMS as strings. To solve this I am using field calculators to extract the degrees, minutes, and second values, convert them to double type values, and perform simple math to convert them to decimal degrees. That all works well. The issue I am having is figuring out how to write those converted latitude and longitude values out to the hosted feature service as geometries. I am curious if the fact that the latitude and longitude values are being calculated on the fly, and so is the geometry, that when I go to build my geometry those calculated latitude and longitude values only exist in memory and are not available to the "toPoint()" function. I have even tried breaking out the latitude, longitude, and geometry calculations to their own field calculator processors, but no luck. It's really hard to explain what issue I am encountering, so I appreciate it if you have read this far, and maybe you have some suggestions?