10.12.2012 Views

Oracle Spatial User's Guide and Reference - InfoLab

Oracle Spatial User's Guide and Reference - InfoLab

Oracle Spatial User's Guide and Reference - InfoLab

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Table 5–3 (Cont.) Match Codes for Geocoding Operations<br />

Match<br />

Code Description<br />

5.1.4 Error Messages for Output Geocoded Addresses<br />

Concepts for Geocoding<br />

11 The postal code matches the data used for geocoding, but the city name does not<br />

match.<br />

For an output geocoded address, the ErrorMessage attribute of the SDO_GEO_<br />

ADDR object (described in Section 5.2.1) contains a string that indicates which<br />

address attributes have been matched against the data used for geocoding. Before<br />

the geocoding operation begins, the string is set to the value ???????????281C??;<br />

<strong>and</strong> the value is modified to reflect which attributes have been matched.<br />

Table 5–4 lists the character positions in the string <strong>and</strong> the address attribute<br />

corresponding to each position. It also lists the character value that the position is<br />

set to if the attribute is matched.<br />

Table 5–4 Geocoded Address Error Message Interpretation<br />

Position Attribute Value If Matched<br />

1-4 (Reserved for future<br />

use.)<br />

????<br />

5 House or building<br />

number<br />

#<br />

6 Street prefix E<br />

7 Street base name N<br />

8 Street suffix U<br />

9 Street type T<br />

10 Secondary unit S<br />

11 Built-up area or city B<br />

14 Region 1<br />

15 Country C<br />

16 Postal code P<br />

17 Postal add-on code A<br />

Geocoding Address Data 5-5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!