Yahoo! Placemaker is a freely available geoparsing Web service. It helps developers make their applications location-aware by identifying places in unstructured and atomic content – feeds, web pages, news, status updates – and returning geographic metadata for geographic indexing and markup.
Placemaker provides geo-enrichment for the hugely significant proportion of Web content that is geographically relevant but not geographically discoverable. Provided with free-form text, the service identifies places mentioned in text, disambiguates those places, and returns unique identifiers (WOEIDs) for each, as well as information about how many times the place was found in the text, and where in the text it was found. The WOEIDs returned by the service can be passed to Yahoo!'s GeoPlanet™ API for further geographic enrichment and discovery.
Placemaker is not a geocoder and does not perform street-level address recognition; it is however a geo-extraction and indexing tool designed to help determine the 'whereness' of a document or atomic unit of text. It provides the geographic developer community with the means to mark-up and index their content geographically in a globally-aware, locally-relevant, and language-neutral manner, and assists with geographic discovery and aggregation across the Internet.
I checked this out, and it reminded me of a pet peeve of mine with APIs.
I know this is hacker news and all, but it's annoying when a neat-looking new api is released like this and the documentation doesn't have any obvious cut-and-paste examples of Get calls to play around with. They offer up two examples, but the "examples" don't resemble anything that I can play with or take action with, I see two code snippets and not much in the way of explanation.
I find enough APIs like this that I have a text file with sample api calls for different services that I get out when I go to play around with them as I can't find cut-and-paste examples of their calls in their documentation.
If anyone can steer me to a URL I can try out (I have an api key), I'd be appreciative. It's just not clear to me, as a somewhat novice developer how to use this service without a blunt example.
Use either documentContent or documentURL to specify what you want to use. I quite enjoyed trying War and Peace (from Gutenberg) although the whole book is a bit big for a single request.
Also this my personal API key. So please don't be jerks with it. Enjoy!
you know i once saw you at the yahoo coffee bar wearing a shirt with a giant hammer and sickle on it. my immediate conclusion was that you were a hipster who skipped history. in case you need a little refresher on how cool the soviets were, read this: http://en.wikipedia.org/wiki/Holodomor
I wasn't able to find any viewport biasing, that would be very useful for disambiguation. For example, "Im in the Mission right now" is pretty vague unless I could viewport bias the analysis to 37/-122. Google Geo API offers this, but last time I tried it it didn't work very well.
I was impressed by this api from Yahoo a lot. It worked really well. I'd already written my own but this works super fast and reliably. I just need more control over disambiguation.
this is very cool, and the beginning of a trend, it seems to me. the whole semantic web depends on structured information, but it's a pain to structure information. it makes a lot of sense that the services to structure plain text will be made available as APIs - eg to extract geo information, date and time information, contact information, etc.
13 comments
[ 4.2 ms ] story [ 40.3 ms ] threadHere's some other info though: http://blog.programmableweb.com/2009/05/20/yahoo-releases-pl...
Yahoo! Placemaker is a freely available geoparsing Web service. It helps developers make their applications location-aware by identifying places in unstructured and atomic content – feeds, web pages, news, status updates – and returning geographic metadata for geographic indexing and markup.
Placemaker provides geo-enrichment for the hugely significant proportion of Web content that is geographically relevant but not geographically discoverable. Provided with free-form text, the service identifies places mentioned in text, disambiguates those places, and returns unique identifiers (WOEIDs) for each, as well as information about how many times the place was found in the text, and where in the text it was found. The WOEIDs returned by the service can be passed to Yahoo!'s GeoPlanet™ API for further geographic enrichment and discovery.
Placemaker is not a geocoder and does not perform street-level address recognition; it is however a geo-extraction and indexing tool designed to help determine the 'whereness' of a document or atomic unit of text. It provides the geographic developer community with the means to mark-up and index their content geographically in a globally-aware, locally-relevant, and language-neutral manner, and assists with geographic discovery and aggregation across the Internet.
(This is awesome.)
It is the "unstructured" plain text input that people will appreciate about this service.
I know this is hacker news and all, but it's annoying when a neat-looking new api is released like this and the documentation doesn't have any obvious cut-and-paste examples of Get calls to play around with. They offer up two examples, but the "examples" don't resemble anything that I can play with or take action with, I see two code snippets and not much in the way of explanation.
I find enough APIs like this that I have a text file with sample api calls for different services that I get out when I go to play around with them as I can't find cut-and-paste examples of their calls in their documentation.
If anyone can steer me to a URL I can try out (I have an api key), I'd be appreciative. It's just not clear to me, as a somewhat novice developer how to use this service without a blunt example.
Use either documentContent or documentURL to specify what you want to use. I quite enjoyed trying War and Peace (from Gutenberg) although the whole book is a bit big for a single request.
Also this my personal API key. So please don't be jerks with it. Enjoy!
Disclaimer: I work for Y!
I was impressed by this api from Yahoo a lot. It worked really well. I'd already written my own but this works super fast and reliably. I just need more control over disambiguation.