Here you can find the most frequently asked questions for Proximity
What does Hopewiser Proximity software do?
Proximity builds up a relational geographic database using client data. The resulting database then facilitates a 'find your nearest...' search as seen commonly on websites, for example. There are two stages to Proximity; the building of the reference datafiles (from client's own data supplied in a recognised format), then the querying of this data using a comparative location, for example, a postcode.
Am I limited in what data I can have in my Proximity database?
No. The Proximity build process has only one real operational requirement; the provision of a current and valid postcode. Any other data items can be 'carried over' with the postcode to figure in the final reference dataset.
What does 'Error opening files: 1/1/3/proxindx' mean?
This error usually denotes an invalid directory passed a parameter when calling the Proximity lookup module. The directory required is the one that contains 'proxindx' and 'proxdata' files. You should also check that this same directory allows full access to the system trying to utilise the data.
What does 'ERROR: Record nn -No gridref: <> -status: 3.5.0.atlpzonc' mean?
When this is reported within the 'proxload' process log file 'proxload.log', it means that the record concerned (represented here by nn) does not have a valid and current postcode. If this is corrected, the error should disappear from the log file when the process is rerun using the new datafile.
Why do my Proximity datafiles contain duplicate entries?
This is because the Proximity build process allows for the appending of data to an existing file. If you are looking to perform a complete and comprehensive rebuild of the reference dataset, you should delete (or move elsewhere) the files 'proxindx' and 'proxdata' so that they are built afresh, not appended to.
Why do I have no entries in my Proximity reference dataset?
This is likely down to the fact that you have not specified the location of the raw data postcode correctly in the 'proxload' job parameters. See the documentation for the correct syntax to be used, and ensure that your datafile has the postcode in the field referenced by number in the 'proxload' job submission command (p=n).
Why are my associated data fields in places I don't expect them to be?
This could be due to an inconsistent format in the raw datafile used in the 'proxload' step. It could also be due to field delimiters in the data fields being submitted at this step too.
For further details on Proximity and how to best utilise it, please refer to the PDF documentation within the application installation directory. If you have any questions not covered by this document, please contact Hopewiser technical support department on 0161 924 2801.