Programming with Microsoft MapPoint Location Server, Version

Chandu Thota takes a first look at Microsoft MapPoint Location Server and demonstrates how to develop powerful location-based applications and services using MapPoint Location Server and MapPoint Web Service

Read the full article here:
http://www.mp2kmag.com/a110--location.server.programming.mappoint.html

We look forward to this long awaited platform being announced on MArch 22nd, We too have been anxoius to see what the future has in store for Developers and customers in this new mobile device world for location in which the carrier will release location data on the handset and the platform will manage all aspects of mangement of this data to feed into developers and customer applications. Like any product when first introduced, awareness must be created, this will take 6-12 months for Developers TO AGAIN sign on to A platform that can/may/will change overnight or over time , right now the carriers have got high expectations on what they can charge for location in relation to a black box which has a one time charge but will spit out location for 0$ over a wireless network that can be had for 5-15 dollars per month, In the end customers will rebuff the carierrs pricing model for any application that requires higher granularity. Emergency applications will be the first sticky apps , as the value of location in these segments will be MNO (money no object for ROI) in about 12-18 months a few winning aplciations will emerge, carriers will lower their per locate revenue expectations and from awareness we will move to acceptance when a couple of big customers Deploy and with real ROI apps. From this acceptance stage the market will evolve again and Adaption will take place and critical mass the fourth stage will follow if the applications and customers determine a high ROI to handset location.

We this would beg the next question" Which Enterpise segments and Individual customers PLACE A HIGH VALUE on location of a handset.


these are the first customers to seek out and handhold through the NATURAL STAGES OF ANY PRODUCT CYCLE.

I very much enjoyed the articles and your recent first wave offering on MLS

Please keep an eye on BAKA TRAKIT as we are hopefully again going to go down a devlopement path with MSFT and our customers that will answer the question

"Is location in the handset the next big thing....for some enterprise customers we firmly believe their is some very definable and measurable applications" and we are going to SPEND AGAIN and go down another road with Microsoft, lets hope the rules of hte engagement/ licensing dont change this time and we can all just "get along"


Guy Annable

Dear Guy,

I read your post and agree with everything you said. Especially the last line " lets hope the rules of hte engagement/ licensing dont change this time and we can all just "get along""

Which begs a few common sense questions:

1) You acknowledge that Microsoft has in the past changed the License rules for MapPoint. (if enforced, would have a detrimental impact on fleet applications such as BAKA) Why would you not try to avoid this risk a second time?

2) If Microsofts new MLS allows any IT guy to access lat/longs from handsets and display them on maps with MapPoint.NET, why do I need Baka as an additional third party expense? Microsoft provides all the tools?

3) Have you read the threads in the Fleet EULA forum? http://www.mp2kmag.com/mappoint/discussion/viewtopic.asp?t=3523 If not, maybe you should.