Regarding the boundary between Costa Rica and Nicaragua

Update (11/8/10): For those interested in reading more about the history of this dispute, consider checking out Stefan Geens’ thorough post over at Ogle Earth.

Yesterday we became aware of a dispute that referenced the border between Costa Rica and Nicaragua as depicted on Google Maps. This morning, after a discussion with the data supplier for this particular border (the U.S. Department of State), we determined that there was indeed an error in the compilation of the source data, by up to 2.7 kilometers. The U.S. Department of State has provided a corrected version and we are now working to update our maps.

Current, incorrect depiction of the San Juan River boundary

Unlike the image above of our current depiction, the corrected version will follow the east bank of the San Juan River going northward, nearly to the Caribbean. It will then turn eastward and follow the southern shoreline of a large lagoon, Laguna los Portillos. This depiction follows the demarcation laid out in the First Award of Arbitration of 1897, which affirmed the Cañas-Jerez Treaty of 1858.

It is our goal to provide the most accurate, up-to-date maps possible. Maps are created using a variety of data sources, and there are inevitably going to be errors in that data. We work hard to correct any errors as soon as we discover them.

Given the complexity of the issue, I thought that I’d take this opportunity to provide some additional historical context.

The dispute in this area goes back to at least the mid-19th century, and both the International Court of Justice and the United Nations have weighed in. The dispute mainly centers around control of the mouth of the San Juan River, and was recently reignited because of dredging activity in this location.

In 1888, U.S. President Grover Cleveland was called upon by Nicaragua and Costa Rica to arbitrate the dispute. That year, the New York Times published President Cleveland’s decision. The 1888 Arbitration upheld the 1858 treaty and its terms.

The New York Times, 25 March, 1888

Then, in 1897, Cleveland sent Edward P. Alexander to do a more detailed Arbitration Award for this region. Alexander went into great detail on the San Juan river boundary and drew the map depicted below:

Map attached to the Sept. 30, 1897 Arbitration Award

Once our updates go live in Google Earth and Maps we will be depicting the border according to the most recent and definitive records available. But as we know, cartography is a complex undertaking, and borders are always changing. We remain committed to updating our maps as needed.

Posted by Charlie Hale, Geo Policy Analyst

A Place for everything, and everything in its Place

If someone asked you where you are right now, how would you answer? Would you say that you are at home, or at work? Maybe you are in a foreign country, in the park, or at your favourite coffee shop. These are just a few of the many places by which we navigate through our daily lives. Maps applications may see the world in terms of latitudes and longitudes, but we think in terms of ‘Places’.

In September of last year Google launched Place Pages on Google Maps. Each Place Page consolidates together everything we know about a single Place, be it a business, point of interest, or geographical feature such as a city or neighbourhood. We believe that this unified concept of Places more accurately reflects the way that Maps users see the world, and are working to bring an awareness of Places to the Google Maps API. At Google I/O today we offered a preview of the first Place related features that that are coming to the Google Maps API in the near future.

The Nearby Places widget is a user interface element that will launch in the Google Maps API v3. It combines the W3C Geolocation API with location based Place search to present the user with a list of Places in their immediate vicinity. The user can select a Place which the Maps API application can use as a check-in, or to tag content supplied by the user about that place. The application can also obtain more detailed information about the Place, such as the address, telephone number, and Place Page URL.

The Nearby Places widget is built on top of the Places Web Service, a new addition to the family of Google Maps API Web Services. The Places Web service offers search for nearby places to native mobile applications through an XML/JSON REST interface. In order for us to manage demand and ensure that the Places Web Service is used appropriately, applications will be required to authenticate their requests. If you are interested in using the service, check out the Places Web Service documentation which outlines the usage guidelines and application process. We expect to begin processing applications when the service launches in July.

We are also very excited to be working with Booyah, developers of the hugely popular MyTown iPhone application. The broad international coverage and superior performance of the Places Web Service made it the logical choice to serve the growing community of over two million active MyTown users. We were delighted to invite David Wang, Vice President of Business Development at Booyah, to speak at Google I/O about the ways in which they are integrating the Places Web Service into the MyTown application.

The Nearby Places widget and Places Web Service are our first steps towards tightly integrated and powerful support for discovering and understanding Places using the Google Maps API. Keep an eye on this blog for more information about the availability of these services, and other Place related launches in future.