Terraserver is down - so are all programs that use it

[+quakemap]

I have already posted this message in another thread - http://ubbx.Groundspeak.com/6/ubb.x?a=tpc&s=5726007311&f=7116058331&m=88060006 - but I suggest that this thread with distinct topic name should be used for terraserver-related messages. Please post your observations here while Microsoft is restoring services.

 

Microsoft is moving Terraserver to a different location.

http://terraserver-usa.com/About.aspx?n=AboutMoving

As of now, TerraServer web services seem to be down.

 

As part of this move, we will modify QuakeMap to reflect the change. An updated version of QuakeMap will be made available as soon as Microsoft restores web services.

 

Here is how to test if web services are up:

-- go to http://terraserver-usa.com/webservices.aspx

-- click on "Access the TerraService WSDL file" link in the middle

-- when the service is up, a complex XML file appears. Currently error message is displayed.

 

I guess, every software using Terraserver will need to be updated when the services are brought back up. This is because the domain name is changing.

 

Happy updating, :-)

 

http://www.quakemap.com - redefining Easy...

[+quakemap]

Terraservices are still down as of now - seems strange, as Microsoft team promised to keep things up using the "mini-cluster". Yesterday I sent them email describing the problem, which probably ended up in a bottomless pit.

 

Am I missing something? Ideas and discoveries are greatly appreciated!

 

http://www.quakemap.com - redefining Easy...

 

[This message was edited by quakemap.com on May 27, 2003 at 09:33 AM.]

[+parkrrrr]

My imagery script - which doesn't use the dot-net/dot-not/dot-nyet/not-yet service - seems to be working flawlessly. Presumably this is because they're redirecting the URLs that I'm using, but I haven't taken the time to look this particular gift horse in the mouth.

 

[+quakemap]

That's right, programs which do not rely on .NET service (which was part of old Terraserver installation) work ok. QuakeMap is at disadvantage now, it uses the web service for framing of the topo/arial and for getting landmarks. I guess with the way things go there we just need to wait a couple of days till the new hardware is in place, and the full TerraServer software suite is functional. I will explore the options of using different framing technique, but with the advantages the web service gives it will be unwise of me to completely abandon it.

 

Sorry for inconvenience, QuakeMap will be fully functional when the terraserver move completes.

 

http://www.quakemap.com - redefining Easy...

[+quakemap]

Terraserver Web services are back on line and an updated version of QuakeMap is posted at http://www.quakemap.com

 

Please use download link there or regular Update process of QuakeMap.

 

Waypoints manager is improved to show Pocket Queries detail and sort waypoints by distance.

 

CR, you will like better handling of popups.

 

Thank you all for your patience.

 

http://www.quakemap.com - redefining Easy...

[+quakemap]

Terraserver remains a moving target, Microsoft engineers made substantial changes to the web services definitions in the middle of the day. It will turn good at the end of the road, but currently it means making updates to QuakeMap every time they choose to change their end.

 

Build 20030529 is placed in download area; please install - or just take a vacation till the dust settles down, hopefully at the end of the week :-)

 

Thank you for your patience and support.

 

http://www.quakemap.com - redefining Easy...

[+parkrrrr]

Meanwhile, things that don't use Web Services are still working like they used to. What's the .NET advantage again? Does Microsoft know that one division is shooting at the other's feet again?

 

Note that this is not a criticism of anyone who's actually using web services, but of the people who are trying to sell it to you with the one hand, and then using the other hand to slap you in the face for actually using it.

 

[+quakemap]

In Terraserver case, Web services deliver tiles boundaries based on lonlat - this is easily computed locally. What can't be computed - is exact information about availability of requested tiles (results in "this area is not covered by Terraserver"), nearest known point name ("2345 miles West of Los Angeles") and the date when picture was taken (displayed in QuakeMap title). All at the expense of a roundtrip to the server, and therefore 1-2 sec delay (when things work well). This has little to do with .NET, but all with Web Services.

 

The .NET/C# advantage is programming ease - for less than $1000 you have lots of power on your fingertips, can almost forget about memory leaks and ride on the front of the wave. Programming is about managing complexity, and the complexity treshold is the highest for .NET among the programming environments now.

 

Microsoft does what it is supposed to do - improves the service. On the large scale of things a weeks outage is nothing compared to another 3 years of uninterrupted service. I am being foolish trying to deliver updates while they are moving - but on the other hand QuakeMap's update notification and relative convenience of updating makes it less painful to you.

 

I am more worried about the fact that Microsoft and HP were not bragging about substantially upgrading the hardware - they are moving 3-years-old boxes between the datacenters. Three years is all the useful life for servers. What happens next?

 

http://www.quakemap.com - redefining Easy...