7,612
edits
Changes
Jump to navigation
Jump to search
no edit summary
Note that all code, including ranking code was run before backup.
==Fix the Geocoding==
The longitudes and latitudes were stored as numeric, rather than real, but this doesn't seem to the source of the problem as it has suitable precision[https://www.postgresql.org/docs/current/datatype-numeric.html].
There are some notes on [[VentureXpert_Data#GeoCoding_Companies.2C_Firms.2C_and_Branch_Offices]] and the SQL appears to be in:
E:\mcnair\Projects\VentureXpert Database\vcdb3\LoadingScripts\GeoLoad.sql
The company process began with a load of oldgeocords 44740 from companybasegeomaster.txt (which came from vcdb2). The problem is that companybasegeomaster has low precision data in it. This was documented in [[VC_Database_Rebuild#Re-Fixing_erroneous_geo-coordinates]]. There's good data, but keyed solely by companyname, in vcdb2:
*Geocore 43628 (with nulls)
*Geoallcoords 44999 (with nulls)
*Geoallcoords1 44999 (with nulls)
The next step in the company geo process was to load remaining from RemainingLatLong.txt. This is high precision data.
