Reference Guide

Reference Guide#

Introduction#

The Web Smart Street Search service matches a street name or just a partial street name and returns any valid addresses that match that pattern.

Used in conjunction with the Web Smart Address Verifier, Street Search can be used to match incorrect or misspelled street names, list possible ranges for a street or a highrise and generate probable suggestions for end users to select. For example, if 123 Main matches both 123 Main St and 123 Main Ave in the same ZIP Code, the Address Verifier would return a multiple match error. Street Search can return all records that match that pattern in the same ZIP Code, allowing you to correct a partial or inaccurate address record that would otherwise result in an undeliverable mail piece.

The records that Street Search returns describe ranges of delivery address, not necessarily specific individual addresses. Therefore, Street Search cannot be used to construct address records from partial data. It can be used to verify that a submitted address falls within a valid range of known addresses (and thus is probably a deliverable address). Alternately, it can used to suggest alternate spellings for a street name or possibly alternate ZIP codes within the same city when the Address Verifier service cannot verify a submitted address.

Service URLs#

Protocol

URL

SOAP

https://streetsearch.melissadata.net/v2/soap/service.svc

SOAP:WSDL

https://streetsearch.melissadata.net/v2/soap/service.svc?wsdl

SOAP:Flat WSDL

https://streetsearch.melissadata.net/v2/soap/service.wsdl

XML

https://streetsearch.melissadata.net/v2/xml/service.svc

REST

https://streetsearch.melissadata.net/v2/rest/service.svc

Sample Code#

Street Search Options#

The Web Smart Street Search service has two optional settings which control the extent of its search.

Adding Street Search to a Project#

If you are using the SOAP service with Visual Studio .NET, you need to add a web reference to the service to your project. Click on the Project menu and select Add Web Reference… Enter the following URL on the Add Web Reference dialog box:

https://streetsearch.melissadata.net/v2/SOAP/Service.svc

If you are not using Visual Studio .NET, see the documention for your SOAP interface for the procedure for adding the service to your project.

Submitting an XML Request#

After building your XML string from your data, an XML request to the web service is submitted using an HTTP POST operation to the following URL:

https://streetsearch.melissadata.net/v2/XML/Service.svc/doStreetSearch

Building a REST Request#

Query strings are sent to the webservice as part of the URL using an HTTP Get operation appended to following URL:

https://streetsearch.melissadata.net/v2/REST/Service.svc/doStreetSearch

Street Search Request Object#

At the minimum, a request to the WebSmart Street Search service will consist of a street address and either a ZIP Code or a combination of city and state. Only one record is allowed per request.

SOAP Request#

The following Visual Basic Code shows a simple order of operations for building and submitting a Request object, submitting it to the Web Service and retrieving a response object.

Step 1 – Create the Request and Response Objects

Dim ReqStreetSearch As New dqwsStreetSearch.Request
Dim ResStreetSearch As New dqwsStreetSearch.Response

Step 2 – Assign the General Request Values

There are three properties of the Request object that apply to the request as a whole. CustomerID is required.

ReqStreetSearch.CustomerID = strCustID
ReqStreetSearch.TransmissionReference = strTranRef
ReqStreetSearch.OptInRangeOnly = True

The Transmission Reference is a unique string value that identifies this request.

Step 3 – Build the Record

The exact method for building the array will depend on the exact database software in use, but you will need to assign the required values to the corresponding elements in the Request.

ReqStreetSearch.Address = "22382 Avenida Empresa"
ReqStreetSearch.Zip = "92688"
ReqStreetSearch.City = "Rancho Santa Margarita"
ReqStreetSearch.State = "CA"

Step 4 – Submit the Request

The final step is to create the Service Client Object and then submit the Request object doStreetSearch method. This sends the data to the web service and retrieves the Response object.

StreetSearchClient = New dqwsStreetSearch.Service
ResStreetSearch = StreetSearchClient.doStreetSearch(ReqStreetSearch)

XML Request#

The raw XML request is built using whatever XML tools are available via your development tools and submitted to the following URL using an HTTP POST request:

https://streetsearch.melissadata.net/v2/XML/Service.svc/doStreetSearch

The following XML Code contains the same request as the SOAP example above.

<?xml version="1.0" ?>
<Request xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <TransmissionReference xmlns="urn:mdWebServiceStreetSearch">Test
  </TransmissionReference>
  <CustomerID xmlns="urn:mdWebServiceStreetSearch">XXXXXXXX</CustomerID>
  <OptInRangeOnly xmlns="urn:mdWebServiceStreetSearch">false</OptInRangeOnly>
  <AddressLine xmlns="urn:mdWebServiceStreetSearch">22382 Avenida Empresa</AddressLine>
  <City xmlns="urn:mdWebServiceStreetSearch">Rancho Santa Margarita</City>
  <State xmlns="urn:mdWebServiceStreetSearch">CA</State>
  <Zip xmlns="urn:mdWebServiceStreetSearch">92688</Zip>
  <Country xmlns="urn:mdWebServiceStreetSearch" />
</Request>

REST Request#

A REST request can submit a single address record via an HTTP GET. The following example uses the same address as the SOAP and XML samples.

https://streetsearch.melissadata.net/v2/REST/Service.svc/doStreetSearch?id=12345678&opt=true&a=22382%20Avenida%20Empresa&city=Rancho%20Santa%20Margarita&state=CA&zip=92688

Request Elements#

The following section lists the elements that set the basic options for each and identify the user to the Web Service.

Customer ID#

This is a required string value containing the identifier number issued to the customer when signing up for Melissa Data Web Services.

You need a customer ID to access any Melissa Data Web Service. If this element is not populated, the web service will return an error. To receive a customer ID, call your Melissa Data sale representative.

SOAP#

Request.CustomerID = string

XML#

<Request>
  <CustomerID>String</CustomerID>
</Request>

REST#

id={CustomerID}

Transmission Reference#

This is an optional string value that may be passed with each Request to serve as a unique identifier for this set of records.

This value is returned as sent by the Response Array, allowing you to match the Response to the Request.

SOAP#

Request.TransmissionReference = string

XML#

<Request>
  <TransmissionReference>String</TransmissionReference>
</Request>

REST#

t={transMissionReference}

OptInRangeOnly#

This element enables the Street In Range search option of the WebSmart Street Search service.

Setting this option to True will cause StreetSearch to search for street data records within the submitted ZIP Code, that match the submitted street name and where the submitted street number falls within the primary range values.

For example, if the submitted address is 1234 Main St, in the ZIP Code 12345, assuming there is a Main St in that ZIP Code, Street Search will return any street data records in that ZIP Code that match the name Main St and where the submitted street number falls within the primary range values. Therefore, if the low range was 1200 and the high was 1299, and the Odd or Even indicator was either Even or Both, then the record would be a match.

If this element is set to False or left blank, StreetSearch will search for street data records within the submitted ZIP Code, that match the submitted street name.

Using the above example, Street Search would return any record that matched Main St. Note that Street Search only searches on the street name, independent of the suffix, so if there was a Main Ave and a Main Blvd in the same ZIP Code, Street Search would return those records as well.

SOAP#

Request.OptInRangeOnly = string

XML#

<Request>
  <OptInRangeOnly>String</OptInRangeOnly>
</Request>

REST#

opt={OptInRangeOnly}

AddressLine#

This element passes the street address to the Street Search service.

The AddressLine element is required with any request to the Street Search service. Attempting to submit a request without a populated AddressLine element will result in an error.

AddressLine must contain, at the very minimum, a street number and a full or partial street name. For example, 1234 M would match all street names beginning with the letter M in the submitted ZIP Code.

SOAP#

Request.AddressLine = string

XML#

<Request>
  <AddressLine>String</AddressLine>
</Request>

REST#

a={AddressLine}

City#

This element passes the city name to the Street Search service.

The city element is optional, as long as the ZIP Code is submitted with the request. However, if the ZIP Code is missing or not valid, Street Search will fall back on the city and state to determine the ZIP Code.

Also, if a search of the primary ZIP Code returns no results, Street Search will search the city and state combination for other ZIP codes and use those ZIP codes to expand the search.

SOAP#

Request.City = string

XML#

<Request>
  <City>String</City>
</Request>

REST#

city={City}

State#

This element passes the state abbreviation to the Street Search service.

The state element is optional, as long as the ZIP Code is submitted with the request. However, if the ZIP Code is missing or not valid, Street Search will fall back on the city and state to determine the ZIP Code.

Also, if a search of the primary ZIP Code returns no results, Street Search will search the city and state combination for other ZIP codes and use those ZIP codes to expand the search.

SOAP#

Request.State = string

XML#

<Request>
  <State>String</State>
</Request>

REST#

state={State}

Zip#

This element passes a five-digit ZIP Code to the Street Search service.

The ZIP element is required but, if missing or not valid, Street Search will fall back on the city and state to determine the ZIP Code.

Also, if a search of the primary ZIP Code returns no results, Street Search will search the city and state combination for other ZIP codes and use those ZIP codes to expand the search.

SOAP#

Request.Zip = string

XML#

<Request>
  <Zip>String</Zip>
</Request>

REST#

zip={Zip}

Country#

This element passes the two-characer country code to the Street Search service.

Currently, Street Search only works on addresses within the United States, so this element is optional and has no effect. It is included for future compatibility.

SOAP#

Request.Country = string

XML#

<Request>
  <Country>String</Country>
</Request>

REST#

ctry={Country}

Street Search Response Object#

Combining Street Record components into a full address line#

To display to the end user, you may want to combine the separate address elements of the street record into a full address. For your typical address line, the order you would combine the address components would be:

[Primary Range] [Pre-Direction] [Street Name] [Suffix] [Post-Direction] [Suite Name] [Suite Range]

Not all addresses will have all of these components, in which case they will be blank. However, there are exceptions. If the street record is a PO Box record or a Rural Route record, you will have to re-arrange the address components differently.

PO Boxes (Address Type P):

For PO Boxes, PO Box is stored in the street name while the box number is stored in the primary range. There are no directionals, suffixes, or suites for PO Boxes.

[Street Name] [Primary Range]
Rural Routes (Address Type R):

For Rural Routes, the street name contains the route information. Additionally, if the route has multiple mailboxes, the primary range will have the box range information. USPS specifications do not have a place to put the word Box for these types of addresses, so you must add it is manually if a box primary range exists. Like PO Boxes, Rural Routes do not have directionals, suffix, or suites.

[Street Name] Box [Primary Range]
Spanish Addresses

Suffixes are usually positioned after the street name. However, Spanish style streets have their suffixes before the street name. If the suffix is Avenida, Calle, Camino, Paseo, or Via, position the address components as such:

[Primary Range] [Pre-Direction] [Suffix] [Street Name] [Post-Direction]

All of these components are returned by each street record, except for the primary range which comes in the form of a number range with a primary range low and a primary range high. When doing an OptInRangeOnly search, you will assume the provided input range is correct, and use that for display. To do so, make sure to keep the parsed primary range from Address Object or the WebSmart AddressCheck Service.

Non-Deliverable Street Records

Sometimes an entire range on a street will be non-deliverable. In those cases, the street record still exists but the Plus4High and the Plus4High will both contain the string XXXX. It is recommended that you filter out these records as they cannot contain deliverable addresses.

Using StreetSearch with AddressCheck Error Result Codes#

StreetSearch can be combined with the results of an AddressCheck to find alternatives for addresses that have uncorrectable errors. Of high importance is the use of OptInRangeOnly, which should be turned on if the input primary range was not the source of the address error. Here are types of AddressCheck Result errors and how to use StreetSearch for each of them.

AE01 - Zip Code Error

Unfortunately, if the zip code and city/state are missing or incorrect, we cannot search for alternative addresses.

AE02 - Unknown Street

The input street was not found, so we should assume the input range is correct and turn on OptInRangeOnly to search for streets for which the input range is valid.

AE03 - Component Mismatch Error

This means the street name and range matched but other multiple address components did not match. Turn on OptInRangeOnly to find the correct street record and display the correct components.

AE04 - Non-deliverable Address

The physical address is correct but no mailbox exist there. Since the address is correct, there are no alternative to generate.

AE05 - Multiple Match

Most commonly, this is due to multiple suffixes for the same street name. Turn on OptInRangeOnly to isolate the possible records.

AE06 - Early Warning Address

Address does not exist in current database but the street is scheduled to be added to the next update. No alternative generation is recommended here.

AE07 - Empty Address Input

There was no data to generate an alternative for.

AE08, AE09 - Suite Range Error, Suite Range Missing

This means the primary range and street name were correct. Turn on OptInRangeOnly to isolate the records in the highrise. Additionally, USPS data often has one or two records without suites in the beginning to represent the entire building and/or building office. To list possible suites, exclude those records by making sure a street record has a suite range low and suite range high.

AE10, AE11 - Primary Range Invalid, Primary Range Missing

Here, the primary range is the incorrect piece of information, so we should not turn on OptInRangeOnly. Doing a Street search with OptInRangeOnly off will return all possible ranges for the input street.

AE12, AE13 - PO Box or Rural Route Number is invalid, missing

Here, the PO Box and Rural Route number is equivalent to the primary range, so we should NOT turn on OptInRangeOnly. Doing a Street search with OptInRangeOnly off will return all possible ranges for the input PO Box or Rural Route.

AE14 - CMRA private mailbox missing

The USPS does not possess data for CMRA (Commercial Mail Receiving Agencies) so alternatives cannot be generated.

Return Elements — General#

The SOAP interface for the Street Search service returns a Response Object. The primary component of this object is an array of StreetRecord objects, one for each street data record returned.

The XML and REST interfaces return XML documents containing a number of <StreetRecord> elements, one for each street record returned.

TransmissionReference#

Returns a string value containing the contents of the TransmissionReference element from the original Request.

If you passed any value to the TransmissionReference element when building your request, it is returned here. You can use this property to match the response to the request.

SOAP#

string = Response.TransmissionReference

XML#

<ResponseArray>
  <TransmissionReference>String</TransmissionReference>
</ResponseArray>

Total Records#

Returns a string value containing the number of street records returned with the current response.

This property returns the number of street records processed and returned by the response as a string value.

SOAP#

string = Response.TotalRecords

XML#

<ResponseArray>
  <TotalRecords>String</TotalRecords>
</ResponseArray>

Results#

Returns a string value containing the general error, system error, and search error messages from the most recent request sent to the service.

For a list of these codes, see StreetSearch - Result Codes.

SOAP#

string = Response.Results

XML#

<ResponseArray>
  <Results>String</Results>
</ResponseArray>

Version#

Returns a string value containing the current version number of the Street Search service.

SOAP#

string = Response.Version

XML#

<ResponseArray>
  <Version>String</Version>
</ResponseArray>

StreetRecord Elements#

The SOAP version of the Response object returns a property called StreetRecord which is an array of StreetRecord objects matching the input submitted with the Request with the original .

The XML and REST services may return one or more <StreetRecord> elements that match the original request.

The maximum number of records returned in both cases in 1,000.

The following section describes the elements returned by each record in the Repsonse Object.

Record ID#

For each record in the Response, this element returns a string value containing the sequential identifier for the current StreetRecord.

The RecordID is sequential number to aid in organizing the StreetRecords returned by the Street Search service.

SOAP#

string = Response.StreetRecord().RecordID

XML and REST#

<Response>
  <StreetRecord>
    <RecordID>String</RecordID>
  </StreetRecord>
</Response>

Company#

For each record in the StreetRecord array, this element returns the string value containing the contents of the Company element if a company is tied to a street record in the USPS Data.

SOAP#

string = Response.StreetRecord().Company

XML#

<Response>
  <StreetRecord>
    <Company>String</Company>
  </StreetRecord>
</Response>

FullAddressLine#

For each record in the StreetRecord array, this element returns a string value containing the complete address line.

This property returns the range high and low for both the street and the suite, as well as an indicator if it is odd or even.

Example

22342-22342 Even AVENIDA EMPRESA STE 225-225 Odd

SOAP#

string = Response.StreetRecord().FullAddressLine

XML#

<Response>
  <StreetRecord>
    <FullAddressLine>String</FullAddressLine>
  </StreetRecord>
</Response>

PrimaryRange#

For each record in the StreetRecord array, the PrimaryRange node returns three elements that indicate the high and low values of the range of street numbers, and indicates whether the numbers in the range are even, odd, or both.

The high and low elements return a 10-character maximum string containing the first and last street numbers in the range of streets address represented by the current StreetRecord. For example, if the address range is 100 to 200 Main Street, these elements will return the values 100 and 200, respectively.

A hyphen in front of the range element indicates a significant leading zero. That means that the leading zero is part of the range and is required. For example, -7 would indicate the range is 07 and cannot be just 7.

The OddEven element returns an E if the numbers in the range are all even, O if they are all odd, and B if there are both odd and even.

SOAP#

string = Response.StreetRecord().PrimaryRange.Low
string = Response.StreetRecord().PrimaryRange.High
string = Response.StreetRecord().PrimaryRange.OddEven

XML#

<Response>
  <StreetRecord>
    <PrimaryRange>
      <Low>String</Low>
      <High>String</High>
      <OddEven>String</OddEven>
    </PrimaryRange>
  </StreetRecord>
</Response>

Street#

These elements return the parsed components of the street name: the predirectional, the name, the suffix and the post-directional.

The Street elements return the following information:

PreDirection

The pre-direction is a geographical directional that precedes the street name. For example, in the address range of 100 N Main St, this element will hold the N. Directions such as North will be changed to N before they are returned by this function.

The directional can be one of the following: N, NE, E, SE, S, SW, W, NW.

Name

Returns the name of the street containing the current range.

Suffix

When street names are used more than once within a city or area, street suffixes are often used to distinguish them. For example, if there is a Main Street but also a Main Avenue, this element will hold either the St or Ave suffix, depending on which one is being referred to. Typical suffix values include ST, RD, AVE, BLVD, CIR, and PL.

PostDirection

The post-direction is a geographical directional that follows the street name. For example, in the address range of 100 N Main St E, this element will hold the E. The post direction can be one of the following: N, NE, E, SE, S, SW, W, NW.

Note About Spanish Street Names

For street names that begin with certain Spanish words, that first word will be returned by the Suffix element and the next word in the street name will be returned as the street name. This is because Spanish street names have the suffix at the front of the address. If the suffix was not returned by the Suffix element, it would appear that every street in some Puerto Rican ZIP codes began with the same letter. The Spanish words that would be returned by the Suffix element are: Avenida, Calle, Camino, Paseo, and Via.

SOAP#

string = Response.StreetRecord().Street.PreDirection
string = Response.StreetRecord().Street.Name
string = Response.StreetRecord().Street.Suffix
string = Response.StreetRecord().Street.PostDirection

XML#

<Response>
  <StreetRecord>
    <Street>
      <PreDirection>String</PreDirection>
      <Name>String</Name>
      <Suffix>String</Suffix>
      <PostDirection>String</PostDirection>
    </Street>
  </StreetRecord>
</Response>

Suite#

These elements return the secondary address information, if any, for the current Street record.

The Suite elements return the following information:

Name

If suite numbers exist in the address range, this element will indicate the proper suite name for addresses in that range.

Possible return values are: #, APT, BLDG, BOX, BSMT, DEPT, FL, FRNT, HNGR, LBBY, LOT, LOWR, OFC, PH (Penthouse), PIER, REAR, RM, SIDE, SLIP, SPC, STE, STOP, TRLR, UNIT, UPPR.

Low

This element returns the lowest suite number in the current range. For instance, if the range covered the suite numbers 1001 through 2001, this element would return 1001.

High

This element returns the lowest suite number in the current range. For instance, if the range covered the suite numbers 1001 through 2001, this element would return 2001.

OddEven

This element returns an O for Odd, an E for Even, or a B for Both. An O indicates that the suite range contains only odd numbers, an E indicates that only even numbers are present in the suite range, and a B indicates that both odd and even numbers are included in the suite range. For example, an O will indicate that, in the 1001 to 2001 suite range, only suite numbers 1001, 1003, 1005, 1007, and so on, exist.

SOAP#

string = Response.StreetRecord().Suite.Name
string = Response.StreetRecord().Suite.Low
string = Response.StreetRecord().Suite.High
string = Response.StreetRecord().Suite.OddEven

XML#

<Response>
  <StreetRecord>
    <Suite>
      <Name>String</Name>
      <High>String</High>
      <Low>String</Low>
      <OddEven>String</OddEven>
    </Suite>
  </StreetRecord>
</Response>

Zip#

The Zip elements return the five-digit ZIP Code, plus the high and low values of the four-digit ZIP + 4 extensions.

The Zip5 element returns the five-digit base ZIP Code for the street record. The return values of the Plus4Low and Plus4High elements define the range of ZIP + 4 codes for the street record. If the ZIP + 4 range is 1234 to 1334, Plus4Low will return the 1234 and Plus4High will return 1334.

The Plus4Low and Plus4High elements will usually contain the same value. In some instances, such as with PO Boxes, the Plus4Low and Plus4High elements will return different values as every PO Box has its own ZIP + 4 code.

In these cases, the lengths of the address range and the Plus4 High-Low range will be identical and the numbers can be paired up accordingly. For example, if the address range is PO Box 100 to 200 and the Plus4 High-Low range is 0100 to 0200, PO Box 110 will have a Plus4 of 0110.

SOAP#

string = Response.StreetRecord().Zip.Zip5
string = Response.StreetRecord().Zip.Plus4Low
string = Response.StreetRecord().Zip.Plus4High

XML#

<Response>
  <StreetRecord>
    <Zip>
      <Zip5>String</Zip5>
      <Plus4Low>String</Plus4Low>
      <Plus4High>String</Plus4High>
    </Zip>
  </StreetRecord>
</Response>

CarrierRoute#

For each record in the Street Record Array, CarrierRoute returns a string value containing the four-character code defining the carrier route for that record.

The first character of this property is always alphabetic, and the last three characters are numeric. The alphabetic letter indicates the type of delivery associated with this address.

For a list of these delivery type codes, see StreetSearch - Record Level Product Codes.

SOAP#

string = Response.StreetRecord().CarrierRoute

XML#

<Response>
  <StreetRecord>
    <CarrierRoute>String</CarrierRoute>
  </StreetRecord>
</Response>

Urbanization#

For each record in the StreetRecord array, Urbanization Code returns a string value containing the six-digit code number for the Urbanization connected with the current address. Urbanization Name returns a string value containing the name of the Urbanization.

Urbanizations will only be returned for addresses in Puerto Rico.

SOAP#

string = Response.StreetRecord().Urbanization.Code
string = Response.StreetRecord().Urbanization.Name

XML#

<Response>
  <StreetRecord>
    <Urbanization>
      <Name>String</Name>
      <Code>String</Code>
    </Urbanization>
  </StreetRecord>
</Response>

AddressType#

For each record in the StreetRecord array, this element returns the address type for the current streetrecord returned.

The Address Type function is a 1-character (maximum) string value, that indicates the type of address that was returned.

For a list of these address type codes, see StreetSearch - Record Level Product Codes.

SOAP#

string = Response.StreetRecord().AddressType

XML#

<Response>
  <StreetRecord>
    <AddressType>String</AddressType>
  </StreetRecord>
</Response>

LACSIndicator#

For each record in the StreetRecord array, this element returns the LACS indicator for each StreetRecord.

The LacsIndicator element returns a one-character which indicates whether or not the address returned by current StreetRecord element has undergone LACS conversion.

Some rural route addresses are modified to city-style addresses to allow emergency services (for example, ambulance, police, fire, and so on) to find these addresses more efficiently.

An empty space in the return value indicates that the address has not undergone a conversion. A value of L in the LACSIndicator return value indicates that the address has undergone a conversion. After a conversion, the old address is retained in the ZIP + 4 file for a period of one year. After the one year period, the old addresses will be dropped from the ZIP + 4 file and the address checking logic will not assign a ZIP + 4 for this address.

SOAP#

string = Response.StreetRecord().LACSIndicator

XML#

<Response>
  <StreetRecord>
    <LACSIndicator>String</LACSIndicator>
  </StreetRecord>
</Response>

BaseAlternateIndicator#

For each record in the StreetRecord array, this element returns the base alternate indicator for the current StreetRecord.

This element returns a 1-character maximum string value which specifies whether or not a record is a base (preferred) or alternate record. Base records (indicated by a B) can represent a range of addresses or an individual address, such as a firm record, while alternate records (indicated by an A) are individual delivery points. Base records are generally preferred over alternate records. The base record for an alternate record can be found by matching up the ZIP + 4 ranges.

SOAP#

string = Response.StreetRecord().BaseAlternateIndicator

XML#

<Response>
  <StreetRecord>
    <BaseAlternateIndicator>String</BaseAlternateIndicator>
  </StreetRecord>
</Response>

Response Object XML Format#

The following shows the structure of the XML document returned by the WebSmart StreetSearch Service.

<?xml version="1.0" ?>
<ResponseArray xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Version xmlns="urn:mdWebServiceStreetSearch">2.0.20</Version>
  <TransmissionReference xmlns="urn:mdWebServiceStreetSearch">Test
  </TransmissionReference>
  <Results xmlns="urn:mdWebServiceStreetSearch">SS02</Results>
  <TotalRecords xmlns="urn:mdWebServiceStreetSearch">30</TotalRecords>
  <StreetRecord xmlns="urn:mdWebServiceStreetSearch">
    <RecordID>1</RecordID>
    <Company />
    <PrimaryRange>
      <High>22398</High>
      <Low>22300</Low>
      <OddEven>E</OddEven>
    </PrimaryRange>
    <Street>
      <PreDirection />
      <Name>EMPRESA</Name>
      <Suffix>AVDA</Suffix>
      <PostDirection />
    </Street>
    <Suite>
      <Name />
      <High />
      <Low />
      <OddEven />
    </Suite>
    <FullAddressLine>22300-22398 Even AVENIDA EMPRESA</FullAddressLine>
    <Zip>
      <Zip5>92688</Zip5>
      <Plus4Low>2112</Plus4Low>
      <Plus4High>2112</Plus4High>
    </Zip>
    <CarrierRoute>C059</CarrierRoute>
    <Urbanization>
      <Code />
      <Name />
    </Urbanization>
    <AddressType>S</AddressType>
    <LACSIndicator />
    <BaseAlternateIndicator>B</BaseAlternateIndicator>
  </StreetRecord>
...
  <StreetRecord xmlns="urn:mdWebServiceStreetSearch">
    <RecordID>30</RecordID>
    <Company />
    <PrimaryRange>
      <High>22342A</High>
      <Low>22342A</Low>
      <OddEven>E</OddEven>
    </PrimaryRange>
    <Street>
      <PreDirection />
      <Name>EMPRESA</Name>
      <Suffix>AVDA</Suffix>
      <PostDirection />
    </Street>
    <Suite>
      <Name>STE</Name>
      <High>102A</High>
      <Low>100A</Low>
      <OddEven>B</OddEven>
    </Suite>
    <FullAddressLine>22342A-22342A Even AVENIDA EMPRESA STE 100A-102A</FullAddressLine>
    <Zip>
      <Zip5>92688</Zip5>
      <Plus4Low>2126</Plus4Low>
      <Plus4High>2126</Plus4High>
    </Zip>
    <CarrierRoute>C059</CarrierRoute>
    <Urbanization>
      <Code />
      <Name />
    </Urbanization>
    <AddressType>H</AddressType>
    <LACSIndicator />
    <BaseAlternateIndicator>B</BaseAlternateIndicator>
  </StreetRecord>
</ResponseArray>
Contents