New Enhancements to MAR 2 API
Hello District Developers and Data Users,
We are excited to announce we’ve made enhancements to the MAR 2 API, as well as updates to the Data Developers Portal for MAR 2 API.
The latest version of MAR 2 API is packed with more enhancements including better scoring for address verification and location-based analysis, security features, usage tracking, and better communication opportunities with our developer community.
Here's what's new:
-
Additional Zones: We often need to know the zones (geographic boundaries) a location falls within. The MAR 2 API now offers zonal outputs for Commission of Fine Arts Boundaries, Historic Districts, Comprehensive Plan Planning Areas, and Single Member District. This point-to-zone feature allows users to aggregate data for displaying in charts, understand the distribution of data across DC, or simply validate a location within a boundary. Have you ever found a point to fall on the borderline of a zone? The MAR 2 API handles this by providing results as an array of multiple zones. View the full list of available zones.
-
Batch Geocoding: With this update, batch geocoding (location mapping) outputs are expanded to give users the Ward, Census Tract, ANC, and whether the location has a condo or residential unit (HasCondoUnit or HasResUnit). Quickly answer how many of your thousands of data points fall within each DC Ward or other boundaries. These are commonly requested outputs when processing large numbers of addresses, or any location. Look for more updates in our next releases and learn how to configure parameters for batch geocoding.
-
Reverse Geocoding: The MAR 2 API allows for reverse geocoding, using geographic coordinates, to find an address nearby. The functionality was expanded so that users can identify the number of addresses that fall within a specified distance, in addition to the nearest single address. This provides you with a proximity-based match with the ability to adjust the search distance. Explore more ways to reverse geocode.
-
Portal Updates: The Data Developer’s Portal continues to be a source for documentation and guides to using the MAR 2 API. We have added references for batch geocode using Python and the option to view API references in previous versions of the MAR 2 API. Have you found an error with an address or perhaps unable to validate? Use the new easy-to-use online form to report missing or invalid addresses.
Build with MAR 2 API for Application Developers
The MAR 2 API web service is publicly available to individuals and organizations needing to verify addresses, place names, blocks, and intersections, and develop applications and build systems using Washington, D.C. addressing data across all platforms. It is developed with a modern code framework that provides output in modern data exchange formats. Using newer technology such as .NET Core and ElasticSearch, MAR 2 API’s dynamic responses allow for the return of objects and results with or without associated zones (geographic boundaries).
The Data Developers Portal for MAR 2 API is the developer guide to building new applications that need authoritative District government addressing components and obtaining location data that will enhance your location-based analysis within the District of Columbia. Check out our available resources — guides, sample viewers, future plans and more. Please note, if you have not already done so, you will need to register to use this portal.
What will happen with Legacy MAR?
We encourage you to begin testing your current applications with the MAR 2 API and start to migrate off the Legacy MAR Web Services, previously known as MAR 1. We know how important this toolset is to everyone, as the Legacy MAR has been around for many years. It is stable and has reached its maturity where OCTO is no longer developing with it. Although Legacy MAR will not be going away anytime soon, we are asking developers to start migrating their applications to the MAR 2 API. Our goal is to continuously improve MAR 2 API with new features and functionality. Learn more about the differences between Legacy MAR and MAR 2 API.
Contact us at data.dev@dc.gov with questions or feedback.
|
