Requisitions with geo-coordinates with city geolocation data with 7 decimal places are truncated to 5 decimal places in the node's asset location and on the regional status map. E.g. 44.4182376, -110.5830235 gets converted to a longitude of -110.58613 and latitude of 44.41949. The city value remains unchanged. While this is close enough for regions, it's way off for adjacent buildings or antenna locations which would be really helpful in a scenario I'm working on. Requisitions continue to hold the correct value after saving and syncing, only the asset information seems to be affected by rounding.
I'm told it's defined as DOUBLE PRECISION in the assets table.
Even if we could get the map to read the city value for location and ignore the latitude and longitude values, that would be a nice improvement.