Modeling IT Systems Modeling is the foundation for successful development and implementation of new IT systems. A correct and complete model ensures that, in the end, users get the IT system they need. Figure 4.1 Different views of a system In this chapter, we show how a conceptual model of an IT system can be developed with the help of UML. The IT system model consists of four different views, each of which emphasizes certain aspects and which are closely related to each other. Figure 4.2 Different views of an IT system External View—Use case diagram and use case sequence diagram Structural View—Class diagram Interaction View—Sequence diagram and communication diagram Behavioral View—Statechart diagram Each of these views emphasizes certain aspects, and thus, disregards all others. The external view shows the use cases of the IT system in the form of UML use case diagrams and an interface prototype. Events are the real links that hold the different views together.
Map of the Week In this guest blog post, we hear from Adam Ratana, a hobbyist photographer and software engineer by day, and developer of the Android and iOS Sun Surveyor apps by night. In this tutorial, Adam talks about his creative implementation of custom polylines on Street View panoramas in the Google Maps SDK for iOS. When I set out to build Sun Surveyor, I knew I wanted to give users an easy way of visualizing the location of the sun and the moon. Visualizing the sun and moon paths in augmented reality and map views When Street View launched in the Google Maps SDK for iOS in v1.4.0 (July, 2013), I couldn’t wait to visualize the sun and moon paths within an interactive panorama. Sun and moon paths with Street View panoramas Implementing a sun path Overlay on Street View I took a creative approach to working with the Google Maps SDK for iOs. I. Representing Overlay Items We represent the overlay items with a protocol having two methods: updateWithPanoramaView and draw. II. III.
Google Maps API v3 tutorial - how to make a simple local business map I’ve grown a little tired recently of seeing the same old Google Maps embedded onto the contact webpage of small businesses. In this tutorial I’m going to walk through some of the basic features of the Google Maps API (V3) and create a custom map for a local business. I first tried out the Google Maps API when creating a mini map embed for our contact page. Dissatisfied with the clutter of the default Google Places embed, I managed to achieve a much more usable map whilst maintaining it’s mini size. The types of Map Embeds Available At present, there are three different ways to add Google Maps to your website. As you can see, particularly when used small, the classic map embed is barely usable. In this tutorial I’m going to explain the basics of creating your own local business Google Map embed using the API. This is not a complete tutorial to show you all of the possible features of the API, however I am going to cover the basics of creating your own map with a custom marker and controls.
CodeIgniter Google Maps V3 API Library | BIOSTALL Looking for a Laravel implementation of this library? You’re in luck. Click here. In early May 2010 I wrote a Google Maps API library for CodeIgniter. This used Version 2 of the Google API and was pretty limited. Well, I’ve been working tirelessly over the past weeks to get a new version wrote that uses Version 3 of the API instead and I am very pleased to announce that it is now avalaible for download. The library enables you to create a map and overlay multiple markers, polylines, polygons, rectangles, ground overlays and/or circles, all of which are fully customisable. To get a copy, read the documentation or to view a demo simply follow the links below: Download Library (Last updated 1st February 2013) View GitHub Repository View Documentation PDF (185kb) View Demonstrations The demonstrations above are basic examples of what can be achieved by using the library. An Introduction to using the Library (Watch on YouTube) Library Features Upcoming Features
Cassandra vs MongoDB vs CouchDB vs Redis vs Riak vs HBase vs Couchbase vs Hypertable vs ElasticSearch vs Accumulo vs VoltDB vs Scalaris comparison :: Software architect Kristof Kovacs While SQL databases are insanely useful tools, their monopoly in the last decades is coming to an end. And it's just time: I can't even count the things that were forced into relational databases, but never really fitted them. (That being said, relational databases will always be the best for the stuff that has relations.) But, the differences between NoSQL databases are much bigger than ever was between one SQL database and another. This means that it is a bigger responsibility on software architects to choose the appropriate one for a project right at the beginning. In this light, here is a comparison of Open Source NOSQL databases: The most popular ones # Redis # Best used: For rapidly changing data with a foreseeable database size (should fit mostly in memory). For example: To store real-time stock prices. Cassandra # Best used: When you need to store data so huge that it doesn't fit on server, but still want a friendly familiar interface to it. MongoDB # ElasticSearch # CouchDB # Accumulo #
Getting Creative With the Google Maps API You’ve designed a shiny new website; carefully selecting the colors, typography and photographs to perfectly reflect the company's branding. Then your client asks you to add a map. Sure, you could use a map building ‘wizard’, such as the one that comes with every google account. But, let’s face it, their functionality is limited and they look pretty generic! The Google maps API, on the other hand, gives you the freedom to create completely customized maps, which can do all sorts of cool things. This series of tutorials will show you how to create customized maps using the Google maps API. The tutorials will cover all sorts of things. These tutorials use the scenario of a UK company promoting music festivals. Note: Only the Glastonbury marker is 'active' in this example. Before starting, you may like to download the files associated with this tutorial. An API, or Application Programming Interface, is a fancy way of saying a set of commands (e.g. functions) a company (e.g.
API Google Maps API Google Earth Webmapping Cartograhie exemples et tutoriels The Google Geocoding API - Google Maps API Web Services This document discusses the Geocoding API v3. Note that the Geocoding API v2 has been turned down and is no longer available. Users of the Geocoding API v2 service should upgrade to v3. Looking to use this service in a JavaScript application? What is Geocoding? Geocoding is the process of converting addresses (like "1600 Amphitheatre Parkway, Mountain View, CA") into geographic coordinates (like latitude 37.423021 and longitude -122.083739), which you can use to place markers or position the map. Reverse geocoding is the process of converting geographic coordinates into a human-readable address. The Google Geocoding API provides a direct way to access a these services via an HTTP request. Before You Begin This document is intended for website and mobile developers who want to use geocoding data within maps provided by one of the Google Maps APIs. Geocoding is a time and resource intensive task. API Key All Geocoding API applications should use an API key. Usage Limits Users of the free API:
How to Style Google Maps Google Maps is one of the best services you can get from Google. It’s a free tool that allows you to easily embed interactive and information-rich maps on your website. However, one disadvantage that comes from using free services is that eventually they all look the same. The good news is Google launched the API that controls the map styles. View Demo Google Maps Library The first thing that we need to do is to include the Google Maps JavaScript library inside the document’s <head> tag, so that we can use the API. Google Maps Components There are three components to style the Google Maps: the feautureTypes, the elementTypes, and the Sytlers. featureTypes is used to select the geographical objects on the map, such as the road, the water, and the parks, so it basically works like the CSS selectors. For more, you can head over to the following API reference: Google Maps feature type specification. stylers is an array of properties to adjust the object colors and its visibility. Basic Usage
dafont.com