To view data errors in your map, click on the ladybug icon in the map toolbar (hovering over the ladybug icon will show the text: 'Reported Bugs') and if there are errors close by, they will be illustrated by the red ladybug icons. Click on the icon(s) displayed on the map to activate a popup window which contains the logged data error information. Also within that popup window, are links to correct the error in Potlatch 2 or JOSM.
We're showing these map and route errors to make the data even better in the U.S. and throughout the world - but we need your help with improving and fixing the underlying OSM data! If you'd like a quick read on how to choose the right editor for you or find out more about editing OpenStreetMap data, click on: http://developer.mapquest.com/web/products/open/tools.
L1AAAas the quality code and "
ntus_strpt" as the vendor name for Enterprise Edition versions 5.* and older,
P1AAAfor the new geocoding service SDK's and two sets of latitude/longitude pairs that show the parcel center and snap-to-street latitude/longitude. You can read more about APG in a blog post we did last year: "APG now in Beta Geocoding Service." Here are a couple samples using the APG data - red star is interpolated location, blue star is center of parcel and green star is using APG:
2k9a" as your new map style. If you're already using the default map style - you've already been upgraded, nothing to do on your side! If your business model includes printing static maps - we suggest using a high DPI raster image setting in order to capture the lakes/terrain data with the new map styles. Want to know more? Read: "MapQuest Introduces our New Map Styles and More!" A sample new static (dynamic) map: