Discomap is a website for developers and gis experts to allow re-use of our map-services.
Any map services here is exposed for public users by EEA or any other website who might be interested to do so.
Cloud APIs are all about the endpoints: some services follow the current trend of providing a RESTful end point, others use older protocols such as RPC or SOAP, some use newer - push focused - endpoints like WebSockets or HTTP Streaming, others may offer a number of different endpoints to meet different requirements and some just use what seems to be best for a specific job which might mean not strictly following protocol rules. But is providing an endpoint to a service alone good enough? Should a developer really have to care about how a service is built or accessed when they can use a client library?
Earlier this week Google announced a new feature for its Maps Data API (check out our Maps Data API Profile) that will have a significant impact on how developers upload, and subsequently access, geospatial data in the cloud: data can now be uploaded to Google's infrastructure in either KML or CSV format.