Hello,
First i want to say thank you for Clavin wich works very well.
We integrate it into a service that take one String as input and return a country code as respons.
We use it mainly on small string containing most of the time location information.
String like : "Montmartre Paris, France" The webApp responds FR
It has been some month now that we use Clavin, and we have encountered some cases that didnt work as expected.
Here are 4 examples of such cases:
Norfolk, VA
Baltimore & Scotland
Chelsea, Québec; CANADA
Greenwich, CT USA
Our integration of Clavin return GB or nothing for these cases.
I tried to update the version of Clavin we use to 1.0 but that didnt change the result.
After some investigation, the problem seems to come from the LocationExtractor (we use the ApacheExtractor implementation) that didnt recognize some part of the string as location name.
So i was wondering what is making the web demo working so well.
Does it use another LocationExtractor ?
Does it do some work on the string before calling the GeoParser?