You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per a discussion with @Alexander-M-Waldman we might want to change everything to be stored in lat/lon natively so we don't have to rely on pre-transformed XYs in address_summary or transform on the fly. There seem to be some inconsistencies between pulling from the State Plane XYs in address_summary and pulling from the geom column of the geocode table.
The text was updated successfully, but these errors were encountered:
Per a discussion with @Alexander-M-Waldman we might want to change everything to be stored in lat/lon natively so we don't have to rely on pre-transformed XYs in
address_summary
or transform on the fly. There seem to be some inconsistencies between pulling from the State Plane XYs inaddress_summary
and pulling from thegeom
column of thegeocode
table.The text was updated successfully, but these errors were encountered: