Data Manager Documentation

To access Data Manager at any time, please sign in and click the green Manage AppKeys button or your user name, then choose Manage AppKeys. This will take you to your Application Keys page. Data Manager will be available from the dropdown menu in the column labeled Action.

 

Table of Contents

 

Additional Documentation

 


Staging Data vs. Production Data

Whenever you upload a .txt or an .acd batch file, your file is processed, meaning that locations are verified for required information and then geocoded if no lat/lng are provided. Geocoding is the process by which latitude and longitude coordinates are assigned to geographic locations. Once files are processed, data is loaded into a "staging" database.

 

Whenever you add, edit, move or delete individual locations with MapQuest Data Manager, you are editing the data that resides in your staging database.

 

In order to expose data, or changes to data, to your end-users, you must "push," or copy your staging data to a production database.


Creating Tables

MapQuest Data Manager allows you to create up to ten data tables. Each table contains required standard fields, as well as optional variable attributes. To create a table, click the Tables link in the left navigation.

 

Creating Tables

The first step in creating a table is to specify a suffix to be appended to your table name and to help you in differentiating multiple tables. Suffix names must use alpha-numeric characters and may be up to 25 characters in length.

 

The next step in creating a table is to specify your attributes. In addition to the standard fields listed, you may define up to 130 attributes by specifying a field name and field type for each attribute you plan to include in your location data file. Field names must use alpha-numeric characters and may be up to 25 characters in length. To specify a field type, select Integer, String, Boolean or Date from the Field Type pulldown menu. Please note that field names must be specified in the order in which they will appear in your data file. You may order the fields using Up and Down buttons. If desired, you may even delete any standard fields which are not marked as REQUIRED. You may re-add a deleted standard field by specifying the field type as Standard. When you are satisfied with your table schema, click the SUBMIT button.

 

Printing Table Schemas

Once you have created a table, you will note that the main Tables page displays a list of the tables you've created. To the right of each table name, you will see a Print Schema icon. When clicked, you will be provided with a page containing your entire schema, including both the required standard fields and the optional variable attributes you added in the order in which you have entered. To print, click your browser's PRINT option.

 

Editing Tables

Once you have created a table, you will note that the main Tables page displays a list of the tables you've created. To the right of each table name, you will see an Edit Table icon. Please note that editing a table schema will cause your staging database to be deleted and recreated. It is recommended that instead of editing a table, you create a new table and when satisfied with your new table, delete your original table. To edit a table, click the Edit Table icon and make the desired changes. Once you have uploaded data for your new table schema, you will need to push the changes to production in order to expose the new table to your end users.

 

Deleting Tables

Once you have created a table, you will note that the main Tables page displays a list of the tables you've created. To the right of each table name, you will see a DeleteTable icon. Please note that deleting a table schema will cause your staging data to be deleted. To delete the table from your production environment, you must push changes to production.

 

Changing Active Table

By default, the first table you create will be your active table upon login. You may change the active table in two ways. To switch to another active table during your session, visit the Tables section and select the desired table from the pulldown menu in the upper right corner. To change the default table so that it is your active table each time you login, visit the Preferences page.


Preparing & Uploading Files

MapQuest Data Manager allows you to upload batch files to be processed. Files may contain up to two million records.

 

The first time you upload a file to MapQuest, your file will have a .txt extension. When MapQuest Data Manager sees a .txt extension, it knows that the data you are providing is meant to completely overwrite your current staging data.

 

Once data resides in your staging database, you may choose to upload batch files containing only records to be added, changed or deleted. These incremental files have an .acd extension.

 

The file format for .txt files and .acd files are slightly different.

 

Preparing .txt Files

When MapQuest Data Manager sees a .txt extension, it knows that the data you are providing is meant to completely overwrite your current data.

 

Files may be, but do not have to be, compressed using zip or gzip compression. Your .txt file must, at a minimum, include placeholders for the fields in your table. Of course, the more information you are able to provide, the greater the quality of the geocoding. Please note that fields must be comma-, tab- or pipe-delimited and each record must be delimited with a carriage return. To view the list of fields and their order, click the 'Print Schema' icon in the Tables section.

 

Preparing .acd Files

When MapQuest Data Manager sees an .acd extension, it knows that you are providing a file containing only records to be added, changed or deleted. An .acd file is identical to a .txt file with two exceptions:

  • 1. The file extension is .acd instead of .txt
  • 2. An additional field is prepended to the beginning of each record

 

Your .acd file should begin with a processing code and contain a column for each of the fields you specified while creating your table (in the defined order). To view the list of fields and their order, click the 'Print Schema' icon in the Tables section.

 

Processing code:

  • A = Add Record
  • C = Change Record
  • D = Delete Record

 

Uploading Files

To upload a .txt or an .acd file, click the Upload File link in the left navigation.

 

Once you upload a file, MapQuest Data Manager will geocode and process your file. When processing is complete you will receive an email notification from MapQuest Data Manager with further information.


Data Summary

The Data Summary provides an overview of the geocoding quality of your locations hosted by MapQuest.

 

To view your Data Summary, click the Data Summary link in the left navigation. When you first click to view the Data Summary, you are looking at an overview of the locations in your Staging database. You may alternatively wish to see an overview of the locations in your Production database. To do so, click the "Production" link to the upper right of the page.

 

Understanding Geocode Quality

Geocode quality can be impacted by several factors, including the quality of your data, whether your locations are in metropolitan areas or rural areas, whether your locations are in established areas or newer subdivisions, etc. Files may be, but do not have to be, compressed using zip or gzip compression. If an address or intersection is provided, MapQuest will always attempt to match the address or intersection first. If a street number cannot be found, the geocoder will attempt to find the street name, in which case a Block Match might be returned. If an address is not provided or cannot be found, the geocoder will look for a ZIP or postal code. The geocoder will continue to "fall back" until it finds a match. If no match is found, the geocode quality will default to "Country Match" and a latitude and longitude representing the center of the United States will be assigned to your location.

 

Ambiguous Records

Ambiguous records are records for which multiple potential matches were found, or for which a match was found that does not exactly match the original input. We encourage you to "fix" ambiguous records prior to pushing data to production. If ambiguities are not fixed before data is pushed to production, the first ambiguous geocode is the geocode pushed to production. You may, however, opt to never push ambiguous records to production. Read about Preferences for additional information on the handing of ambiguities.

 

Records Not Geocoded

MapQuest Data Manager will not geocode records for which you provide valid latitude and longitude coordinates. These records are moved directly to your staging database using the coordinates you provided.

 

Records Not Processed (Errors)

Records for which errors exist are not stored by MapQuest. Therefore, it is a good idea to download the Errors file for additional information on why records were not processed. The Errors file may be downloaded in the Download Data section. You may correct errors and resubmit as an .acd file at any time. See Preparing & Uploading Files for additional information on submitting .acd files.

 

Viewing Records Based on Geocode Quality

Within the Data Summary, each listing for Geocode Quality is a link. When clicked, you are provided with a list of locations matching the specified Geocode Quality. From the list, you may select locations to edit or move by clicking on the desired Record ID.

 

Improving Geocode Quality

Here are some tips to assist you in improving the geocode quality of your locations:

 

Intersections - To map an intersection use the word "and" or the ampersand ("&") or the word "at". Examples: "First & Broadway" or "Interstate 25 and Colorado Blvd" or "Smith Road at Blake St."

 

Interstates & Highways - To map an interstate or highway, spell out the word "interstate" or "highway" completely. Abbreviations are not accepted.

 

North & South - Within addresses, north and south may be abbreviated "N" and "S." The abbreviations "No." and "So." are not accepted. Examples: "123 N Main St" or "456 Main St N"

 

City Names - Abbreviated city names are not accepted. For instance, New York should not be entered as NYC. In addition, cities like North Hampton should not be entered as N. Hampton.

 

Suites Numbers - MapQuest does not recognize suite numbers and apartment numbers so if you are having trouble geocoding a location, try omitting the suite number.

 

Address Ranges - When a building's address is represented as an address range (for example, 24-58 Elm Street), you should select a single address within that range (for example, 24 Elm Street). MapQuest does not accept address ranges.

 

Vanity Addresses - In most cases, MapQuest does not recognize vanity addresses (for example, #1 MapQuest Drive). Please use the alternative street address recognized by the United Postal Service.


Adding Individual Locations

To add locations individually, click the Add Locations link in the left navigation.

 

On the first screen you will be asked to provide a unique record ID, the location name, address and icon ID. If you do not wish to enter variable data for the location, you may click the DONE button to save the record. Otherwise, you will click the CONTINUE button to add user fields and search fields.


Editing Individual Locations

To edit locations individually, click the Edit Locations link in the left navigation.

 

The first screen is a query screen where you will be asked to provide information to assist MapQuest Data Manager in finding the location(s) you wish to edit. You may search by record ID, location name, address and/or geocoded quality. If locations are found which match your criteria, you will be provided with a list of those locations. To select a location to edit, click the EDIT icon to the right of the desired location. On the first screen you will be able to view and/or edit the unique record ID, the location name, address and icon ID. If you do not wish to edit the variable data for the location, you may click the DONE button to save the changes. Otherwise, you will click the CONTINUE button to edit the user fields and search fields.

 

When you are done editing the location, you will receive a page confirming that the record has been updated. From there, you may move the location of the record you just edited, you may return to the list of locations to select another record to edit, or you may push the change to your production data.


Move Individual Locations

To move locations individually, click the Edit Locations link in the left navigation.

 

The first screen is a query screen where you will be asked to provide information to assist MapQuest Data Manager in finding the location(s) you wish to move. You may search by record ID, location name, address and/or geocoded quality. If locations are found which match your criteria, you will be provided with a list of those locations. To select a location to move, click the MOVE icon to the right of the desired location. There are three ways to move a location:

 

Click To Map

When using this option, clicking on any spot on the map will redraw the page, centering your map on the point clicked and moving the original icon to the new map center-point. To assist you in finding where your location should be placed, panning frames surround the map and may be clicked to move your map in any direction. In addition, the zoom slider to the right of the map may be clicked to zoom the map to any of ten predefined zoom levels.

 

When you are satisfied with the new placement, click the UPDATE LOCATION button at the bottom of the page. You will receive a page confirming that the record has been updated in your staging data. From there, you may edit the location you just moved, you may return to the list of locations to select another record to move, or you may push the change to your production data.

 

Enter a Latitude and Longitude

To enter a latitude and longitude, click the "Enter a Latitude and Longitude" link to the upper right of the page. A pop-up will appear, providing an area for you to enter a latitude and longitude. When the new coordinate is submitted, the map will be updated. Notice that the Geocode Quality shows a "Manual" placement of the location.

 

When you are satisfied with the new placement, click the UPDATE LOCATION button at the bottom of the page. You will receive a page confirming that the record has been updated in your staging data. From there, you may edit the location you just moved, you may return to the list of locations to select another record to move, or you may push the change to your production data.

 

Re-Geocode with MapQuest

To have MapQuest Data Manager automatically generate a new geocoded, click the "Re-Geocode with MapQuest" link to the upper right of the page. When the new coordinate is determined, the map and Geocode Quality will be updated.

 

To submit the new geocoded, click the UPDATE LOCATION button at the bottom of the page. You will receive a page confirming that the record has been updated in your staging data. From there, you may edit the location you just moved, you may return to the list of locations to select another record to move, or you may push the change to your production data.


Deleting Individual Locations

To delete locations individually, click the Edit Locations link in the left navigation.

 

The first screen is a query screen where you will be asked to provide information to assist MapQuest Data Manager in finding the location(s) you wish to delete. You may search by record ID, location name, address and/or geocoded quality. If locations are found which match your criteria, you will be provided with a list of those locations. To select a location to delete, click the DELETE icon to the right of the desired location.

 

On the resulting page, you will be asked to verify that you would like to delete the selected record. To continue, click YES. Otherwise, click NO to return to the list of locations. When a location is deleted, you will receive a page confirming that the record was deleted from your staging data. From there, you may return to the list of locations to select another record to delete, or you may push the change to your production data.


Pushing Data to Production

Whenever you add, edit, move or delete individual locations with MapQuest Data Manager, you are editing data that resides in a staging database. In order to expose those changes to your end-users, you must "push" those changes to your production database.

 

In addition, when you upload a .txt or an .acd batch file, you will receive an email message notifying you when the processing of your file is complete. Once processing is completed, you will need to login to MapQuest Data Manager to push the new data to production, unless you have changed your MapQuest Data Manager Preferences to automatically push to production. Read about Preferences for additional information on automatically pushing data to production.

 

To manually push data to production, click the Production link in the left navigation.

 

On the resulting page, you will be asked to verify that you would like to push data to production. Note that pushing data to production will overwrite all data in your production database. To continue, click YES. Otherwise, click NO to return to the Data Manager Index page.

 

Please be aware that while data is being copied to your production database, you will be unable to utilize other MapQuest Data Manager features.


Downloading Data

To download data, click the Download Data link in the left navigation. On the resulting screen, you will have the option to download any of the following:

 

Ambiguities

Ambiguities are records for which multiple potential matches were found, or for which a match was found that does not exactly match the original input. If ambiguities are not fixed before data is pushed to production, the first ambiguous geocode is the geocode pushed to production. It is, however, possible to change MapQuest Data Manager Preferences to never push ambiguous records to production. Read about Preferences for additional information on the handing of ambiguities.

 

Errors

Records for which errors exist are not stored in the MapQuest database. Therefore, it is a good idea to download the file for additional information on why records were not processed. You may correct errors and resubmit as an .acd file. See Preparing & Uploading Files for additional information on submitting .acd files.

 

Staging Data

Records which currently reside in your staging database.

 

Production Data

Records which currently reside in your production database. This data is exposed to your end-users.

 

Note that while data is being downloaded, you will be unable to utilize other MapQuest Data Manager features.


Setting Preferences

MapQuest provides several preference settings to assist you in getting the most out of MapQuest Data Manager.

 

Automatic Push to Production

Typically, when MapQuest finishes processing your .txt and .acd batch files, you are notified by email and asked to return to MapQuest Data Manager in order to verify your data and push your new data to production. You may, however, choose to automatically push your data to production, without returning to MapQuest Data Manager and without verifying that the data is accurate. We do not recommend this setting for new users.

 

Ambiguities

Ambiguities are records for which multiple potential matches were found, or for which a match was found that does not exactly match the original input. If ambiguities are not fixed before data is pushed to production, the first ambiguous geocode is the geocode pushed to production. You may, however, opt to never push ambiguous records to production.

 

Email Notifications

MapQuest Data Manager email notifications are sent to the email address on file with MapQuest. You may however, specify an additional email address to which MapQuest Data Manager notifications will be sent.