Changes in 1559f0b: FIXED: more links in wiki pages referencing other wiki pages fixed

				configuration/backup.sh
			
          @@ -8,7 +8,7 @@

           # only the same root directories are associated to that name. It is NOT possible

           # to backup different root directories to the same backup name.

           #

          -# Documentation: http://wiki.sapsailing.com/wiki/amazon-ec2-backup-strategy

          +# Documentation: https://wiki.sapsailing.com/wiki/info/landscape/amazon-ec2-backup-strategy

           #

           # Maintainer: simon.marcel.pamies@sap.com

				configuration/releaseAndroidApps.sh
			
          @@ -46,7 +46,7 @@ if [ $# -eq 0 ]; then

               echo "Request a new Java Correction Workbench (JCWB) Correction Request ID at:"

               echo "  https://css.wdf.sap.corp/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/jcwb/default.htm?newCMForProject=sapsailingcapture#"

               echo "See more usage details in the sapsailing.com wiki at:"

          -    echo "  https://wiki.sapsailing.com/wiki/building-and-deploying#building-deploying-stopping-and-starting-server-instances_app-build-process-for-ios-and-android_xmake-build-for-android-apps"

          +    echo "  https://wiki.sapsailing.com/wiki/info/landscape/building-and-deploying#building-deploying-stopping-and-starting-server-instances"

               echo "-m Disable upgrading the AndroidManifest.xml versionCode and versionName"

               echo "-p Disable upgrading the pom.xml and MANIFEST.MF versions"

               echo "-g Disable the final git push operation to refs/for/$RELEASE_BRANCH"

				ios/SAPTracker/src/xcode/SAPTracker/RegattaViewController.swift
			
          @@ -282,7 +282,7 @@ class RegattaViewController : UIViewController, UIActionSheetDelegate, UINavigat

                   APIManager.sharedManager.postTeamImage(DataManager.sharedManager.selectedCheckIn!.competitorId,

                       imageData: jpegData,

                       success: { (responseObject) -> Void in

          -                // http://wiki.sapsailing.com/wiki/tracking-app/api-v1#Competitor-Information-%28in-general%29

          +                // https://wiki.sapsailing.com/wiki/info/api/api-v1#tracking-app-api-v1_check-in-information_competitor-information-in-general

                           // "Additional Notes: Competitor profile image left out for now."

                           let responseDictionary = responseObject as![String: AnyObject]

                           let imageUrl = (responseDictionary["teamImageUri"]) as! String;

				wiki/events/Charleston-Race-Week-2016.md
			
          @@ -17,7 +17,7 @@ The VPN setup can be easily expanded to further regions like APJ.

           ### Load balancers and Route53

           This setup requires two ELB's; one in each region. Put instances behind the according ELB in your region as usual.

          -The only difference here is, that Route53 entries differ a little bit from the usual standard. There are event subdomain entries (crw2016) for different geo-based locations set, which will handle and forward requests to the "best" load balancer which is set up in each region. See [here](https://wiki.sapsailing.com/wiki/amazon-ec2#amazon-ec2-for-sap-sailing-analytics_howto_using-latency-based-dns-across-regions) for the basic setup of latency-based or geo-based Route53 entries.

          +The only difference here is, that Route53 entries differ a little bit from the usual standard. There are event subdomain entries (crw2016) for different geo-based locations set, which will handle and forward requests to the "best" load balancer which is set up in each region. See [here](https://wiki.sapsailing.com/wiki/info/landscape/amazon-ec2#amazon-ec2-for-sap-sailing-analytics_howto_using-latency-based-dns-across-regions) for the basic setup of latency-based or geo-based Route53 entries.

           ### Technical event meta information

           ```

				wiki/info/api/training-api-v1-draft.md
			
          @@ -20,7 +20,7 @@ Use cases include:

               * Analyze sessions

               * View history

          -Please note that this interface is independent of the race tracking API described here: http://wiki.sapsailing.com/wiki/tracking-app-api-v1-draft

          +Please note that this interface is independent of the race tracking API described here: https://wiki.sapsailing.com/wiki/info/api/training-api-v1-draft

           ## Endpoint

          @@ -652,7 +652,7 @@ Sets wind speed and direction.

           ## Tracking

          -The tracking interface is identical to that of the race tracking API http://wiki.sapsailing.com/wiki/tracking-app-api-v1-draft#Send-Measurements-%28to-the-Fix-Store%29

          +The tracking interface is identical to that of the race tracking API https://wiki.sapsailing.com/wiki/info/api/tracking-app-api#tracking-app-api_send-geolocation

           **Path:** ``gps_fixes``

				wiki/info/landscape/building-and-deploying.md
			
          @@ -65,7 +65,7 @@ Stopping a running server has---for your convenience---been wrapped into the `st

           ## Automatic Java Instance Start-Up After Boot

          -When firing up an EC2 instance it can be convenient to not having to log on to have the EC2 instance run a Java instance automatically after it has completed its boot process. This is possible using so-called _user data_. The process of firing up an instance that either builds a certain git commit, installs and starts it after server boot or that downloads and installs a release and starts it is explained [here](http://wiki.sapsailing.com/wiki/amazon-ec2#HowTo).

          +When firing up an EC2 instance it can be convenient to not having to log on to have the EC2 instance run a Java instance automatically after it has completed its boot process. This is possible using so-called _user data_. The process of firing up an instance that either builds a certain git commit, installs and starts it after server boot or that downloads and installs a release and starts it is explained [here](https://wiki.sapsailing.com/wiki/info/landscape/amazon-ec2#amazon-ec2-for-sap-sailing-analytics_howto).

           ## App Build Process for iOS and Android

				wiki/info/landscape/creating-ec2-image-from-scratch.md
			
          @@ -125,4 +125,4 @@ VNCSERVERARGS[2]="-geometry 1600x900"

           ```

           ## Mail Relaying

          -For setting up mail relaying towards central postfix server, have a look [here](https://wiki.sapsailing.com/wiki/mail-relaying)

          \ No newline at end of file

          +For setting up mail relaying towards central postfix server, have a look [here](https://wiki.sapsailing.com/wiki/info/landscape/mail-relaying)

          \ No newline at end of file

				wiki/planning/businesscases/smartphonetracking.md
			
          @@ -5,7 +5,7 @@ There are several million active sailors around the world. STG claims there are 

           In comparison, only a small share of them is actively participating in large regattas that are sufficiently prestigious to be supported by professionally-managed tracking infrastructure. Therefore, this large share of sailing events is not currently able to use the SAP Sailing Analytics to understand, analyze and also promote their hobby.

          -For a good introduction to the topic of smartphone tracking see [[Jan Bross' Bachelor thesis|doc/theses/20130913_Bross_Tracking_Sailing_Races_with_Mobile_Devices.pdf]]. For a technical description of what has been implemented in a second iteration see [[RaceLog Tracking|wiki/racelog-tracking]]. There is also a [[specification of a tracking app|http://wiki.sapsailing.com/wiki/racelog-tracking/app-spec/app-spec]].

          +For a good introduction to the topic of smartphone tracking see [[Jan Bross' Bachelor thesis|doc/theses/20130913_Bross_Tracking_Sailing_Races_with_Mobile_Devices.pdf]]. For a technical description of what has been implemented in a second iteration see [[RaceLog Tracking|wiki/racelog-tracking]]. There is also a [[specification of a tracking app|https://wiki.sapsailing.com/wiki/info/mobile/app-spec/app-spec]].

           ## Purpose

				wiki/planning/offseason-2014-2015.md
			
          @@ -42,7 +42,7 @@ Reaching a broader audience with the SAP Sailing Analytics will mainly happen th

           ## Data Quality (Christopher)

          -See [http://wiki.sapsailing.com/wiki/data-quality](http://wiki.sapsailing.com/wiki/data-quality). We think that transparency needs to be the first step. Therefore, we should start working on internal analyses, probably with the help of the DataMining framework (see below), to produce reports that show us all the facts about the data quality so far. Only then can we decide how much to invest into cleansing and outlier detection and how much to spend on advanced aggregation techniques that live with sparse and lossy data.

          +See [https://wiki.sapsailing.com/wiki/info/misc/data-quality](https://wiki.sapsailing.com/wiki/info/misc/data-quality). We think that transparency needs to be the first step. Therefore, we should start working on internal analyses, probably with the help of the DataMining framework (see below), to produce reports that show us all the facts about the data quality so far. Only then can we decide how much to invest into cleansing and outlier detection and how much to spend on advanced aggregation techniques that live with sparse and lossy data.

           ## Data Mining and Polar Sheets (Lennart, Frederik)

           We have made good progress with the DataMining framework and corresponding branch. The PolarSheet calculations are to be migrated to the DataMining framework. We want to implement a first set of analysis "models" with a prototypical UI that allows us to test the DataMining framework's maturity. Only if this works out well can we continue with UI/UX design.

...	...	@@ -282,7 +282,7 @@ class RegattaViewController : UIViewController, UIActionSheetDelegate, UINavigat
282	282	APIManager.sharedManager.postTeamImage(DataManager.sharedManager.selectedCheckIn!.competitorId,
283	283	imageData: jpegData,
284	284	success: { (responseObject) -> Void in
285		- // http://wiki.sapsailing.com/wiki/tracking-app/api-v1#Competitor-Information-%28in-general%29
	285	+ // https://wiki.sapsailing.com/wiki/info/api/api-v1#tracking-app-api-v1_check-in-information_competitor-information-in-general
286	286	// "Additional Notes: Competitor profile image left out for now."
287	287	let responseDictionary = responseObject as![String: AnyObject]
288	288	let imageUrl = (responseDictionary["teamImageUri"]) as! String;

...	...	@@ -17,7 +17,7 @@ The VPN setup can be easily expanded to further regions like APJ.
17	17	### Load balancers and Route53
18	18
19	19	This setup requires two ELB's; one in each region. Put instances behind the according ELB in your region as usual.
20		-The only difference here is, that Route53 entries differ a little bit from the usual standard. There are event subdomain entries (crw2016) for different geo-based locations set, which will handle and forward requests to the "best" load balancer which is set up in each region. See [here](https://wiki.sapsailing.com/wiki/amazon-ec2#amazon-ec2-for-sap-sailing-analytics_howto_using-latency-based-dns-across-regions) for the basic setup of latency-based or geo-based Route53 entries.
	20	+The only difference here is, that Route53 entries differ a little bit from the usual standard. There are event subdomain entries (crw2016) for different geo-based locations set, which will handle and forward requests to the "best" load balancer which is set up in each region. See [here](https://wiki.sapsailing.com/wiki/info/landscape/amazon-ec2#amazon-ec2-for-sap-sailing-analytics_howto_using-latency-based-dns-across-regions) for the basic setup of latency-based or geo-based Route53 entries.
21	21
22	22	### Technical event meta information
23	23	```

...	...	@@ -20,7 +20,7 @@ Use cases include:
20	20	* Analyze sessions
21	21	* View history
22	22
23		-Please note that this interface is independent of the race tracking API described here: http://wiki.sapsailing.com/wiki/tracking-app-api-v1-draft
	23	+Please note that this interface is independent of the race tracking API described here: https://wiki.sapsailing.com/wiki/info/api/training-api-v1-draft
24	24
25	25	## Endpoint
26	26
...	...	@@ -652,7 +652,7 @@ Sets wind speed and direction.
652	652
653	653	## Tracking
654	654
655		-The tracking interface is identical to that of the race tracking API http://wiki.sapsailing.com/wiki/tracking-app-api-v1-draft#Send-Measurements-%28to-the-Fix-Store%29
	655	+The tracking interface is identical to that of the race tracking API https://wiki.sapsailing.com/wiki/info/api/tracking-app-api#tracking-app-api_send-geolocation
656	656
657	657	Path: ``gps_fixes``
658	658

...	...	@@ -65,7 +65,7 @@ Stopping a running server has---for your convenience---been wrapped into the `st
65	65
66	66	## Automatic Java Instance Start-Up After Boot
67	67
68		-When firing up an EC2 instance it can be convenient to not having to log on to have the EC2 instance run a Java instance automatically after it has completed its boot process. This is possible using so-called _user data_. The process of firing up an instance that either builds a certain git commit, installs and starts it after server boot or that downloads and installs a release and starts it is explained [here](http://wiki.sapsailing.com/wiki/amazon-ec2#HowTo).
	68	+When firing up an EC2 instance it can be convenient to not having to log on to have the EC2 instance run a Java instance automatically after it has completed its boot process. This is possible using so-called _user data_. The process of firing up an instance that either builds a certain git commit, installs and starts it after server boot or that downloads and installs a release and starts it is explained [here](https://wiki.sapsailing.com/wiki/info/landscape/amazon-ec2#amazon-ec2-for-sap-sailing-analytics_howto).
69	69
70	70	## App Build Process for iOS and Android
71	71

...	...	@@ -125,4 +125,4 @@ VNCSERVERARGS[2]="-geometry 1600x900"
125	125	```
126	126
127	127	## Mail Relaying
128		-For setting up mail relaying towards central postfix server, have a look [here](https://wiki.sapsailing.com/wiki/mail-relaying)
...	...	\ No newline at end of file
	0	+For setting up mail relaying towards central postfix server, have a look [here](https://wiki.sapsailing.com/wiki/info/landscape/mail-relaying)
...	...	\ No newline at end of file

...	...	@@ -8,7 +8,7 @@
8	8	# only the same root directories are associated to that name. It is NOT possible
9	9	# to backup different root directories to the same backup name.
10	10	#
11		-# Documentation: http://wiki.sapsailing.com/wiki/amazon-ec2-backup-strategy
	11	+# Documentation: https://wiki.sapsailing.com/wiki/info/landscape/amazon-ec2-backup-strategy
12	12	#
13	13	# Maintainer: simon.marcel.pamies@sap.com
14	14

...	...	@@ -46,7 +46,7 @@ if [ $# -eq 0 ]; then
46	46	echo "Request a new Java Correction Workbench (JCWB) Correction Request ID at:"
47	47	echo " https://css.wdf.sap.corp/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/jcwb/default.htm?newCMForProject=sapsailingcapture#"
48	48	echo "See more usage details in the sapsailing.com wiki at:"
49		- echo " https://wiki.sapsailing.com/wiki/building-and-deploying#building-deploying-stopping-and-starting-server-instances_app-build-process-for-ios-and-android_xmake-build-for-android-apps"
	49	+ echo " https://wiki.sapsailing.com/wiki/info/landscape/building-and-deploying#building-deploying-stopping-and-starting-server-instances"
50	50	echo "-m Disable upgrading the AndroidManifest.xml versionCode and versionName"
51	51	echo "-p Disable upgrading the pom.xml and MANIFEST.MF versions"
52	52	echo "-g Disable the final git push operation to refs/for/$RELEASE_BRANCH"

...	...	@@ -5,7 +5,7 @@ There are several million active sailors around the world. STG claims there are
5	5
6	6	In comparison, only a small share of them is actively participating in large regattas that are sufficiently prestigious to be supported by professionally-managed tracking infrastructure. Therefore, this large share of sailing events is not currently able to use the SAP Sailing Analytics to understand, analyze and also promote their hobby.
7	7
8		-For a good introduction to the topic of smartphone tracking see [[Jan Bross' Bachelor thesis\|doc/theses/20130913_Bross_Tracking_Sailing_Races_with_Mobile_Devices.pdf]]. For a technical description of what has been implemented in a second iteration see [[RaceLog Tracking\|wiki/racelog-tracking]]. There is also a [[specification of a tracking app\|http://wiki.sapsailing.com/wiki/racelog-tracking/app-spec/app-spec]].
	8	+For a good introduction to the topic of smartphone tracking see [[Jan Bross' Bachelor thesis\|doc/theses/20130913_Bross_Tracking_Sailing_Races_with_Mobile_Devices.pdf]]. For a technical description of what has been implemented in a second iteration see [[RaceLog Tracking\|wiki/racelog-tracking]]. There is also a [[specification of a tracking app\|https://wiki.sapsailing.com/wiki/info/mobile/app-spec/app-spec]].
9	9
10	10	## Purpose
11	11

...	...	@@ -42,7 +42,7 @@ Reaching a broader audience with the SAP Sailing Analytics will mainly happen th
42	42
43	43	## Data Quality (Christopher)
44	44
45		-See [http://wiki.sapsailing.com/wiki/data-quality](http://wiki.sapsailing.com/wiki/data-quality). We think that transparency needs to be the first step. Therefore, we should start working on internal analyses, probably with the help of the DataMining framework (see below), to produce reports that show us all the facts about the data quality so far. Only then can we decide how much to invest into cleansing and outlier detection and how much to spend on advanced aggregation techniques that live with sparse and lossy data.
	45	+See [https://wiki.sapsailing.com/wiki/info/misc/data-quality](https://wiki.sapsailing.com/wiki/info/misc/data-quality). We think that transparency needs to be the first step. Therefore, we should start working on internal analyses, probably with the help of the DataMining framework (see below), to produce reports that show us all the facts about the data quality so far. Only then can we decide how much to invest into cleansing and outlier detection and how much to spend on advanced aggregation techniques that live with sparse and lossy data.
46	46
47	47	## Data Mining and Polar Sheets (Lennart, Frederik)
48	48	We have made good progress with the DataMining framework and corresponding branch. The PolarSheet calculations are to be migrated to the DataMining framework. We want to implement a first set of analysis "models" with a prototypical UI that allows us to test the DataMining framework's maturity. Only if this works out well can we continue with UI/UX design.