Daniel, sorry for the late reply. It's not that quiet moment of the year!

I'll try to answer inline

>
>1) The applications we run are sensitive and will have to work standalone with zero http connectivity at desktop.
>
>Do you think we could and (may legally) split the applications in two parts. One at server-level, for pre-fetching the bulk of the required mapping information into a local application directory - a bit in the way Maperitive does it - and the one at workstation level working disconnected with the downloaded pre-fetched material. I expect and anticipate that the answer may be no since the Here company certainly has a server-centric business model. But you certainly have the full detailed answer,

I don't think your approach will break the Here licensing (https://developer.here.com/terms-and-conditions). Of course, you can't recreate the services to others, but if you want to proxy and cache data and services, and your application is built using these architectural elements, then I believe it will be ok.

If still in doubt, you may contact the Here people, they are responsive and helpful.

>2) You mention that the overhere project is still "In development. Unsuited for production". Do you expect that using a limited subset - I am looking into very, very basic GIS functionality here - is possibly within the reach of the current code base?

Well, basically since I'm not using overHere in production, this warning just means that it has not yet been tested in real life.

What specifically do you require right now? The limit of what can be done is, of course, set by https://developer.here.com/documentation (most of the REST apis can be wrapped by the project, if they are not yet), but I expect that expanding the Here API coverage will not be difficult and will not diminish the project's orthogonality.