a) We could accept an additional optional parameter 'country' for the neighbour service. This could be done easily. Is there anything else you would require?
me, i would welcome that functionality from a) to make my userland code simpler, shorter, faster. as it is now i either generate useless traffic to your geo servers and spend more time for fetching the data i want, or must implement a bit more caching logic.
>> Is there anything else you would require?
since i'm just getting started with your api i don't know ... maybe all other users need to look up the internal geo id anyway for all the other services. i would like it if i could just work with existing 3166 or fips or nuts codes wherever they exist.