I used Tomtom to send me an email from the route planning option on my iPhone. In that email is a tomtomhome:geo link which I used. To test I clicked on the link on my Mac in Safari, and obviously nothing happened. Then I saved the link as a bookmark, which immediately is synced to my iPhone using MobileMe. I clicked on the bookmark on my iPhone Safari browser and viola Tomtom opens with a map centred to the location in the link. It pops up with a balloon with the links name, and an right arrow allows me to choose first option "Navigate there"
I got a bag of tomatillos one week with the intention of making salsa for steak, because tomatillo salsa on steak is like peanut butter on jelly. That first bag of toms sat in the fridge, dejected, for a week before I decided to attempt a salsa of some sort. My guilt over wasting food finally got the better of me. This is what happened-
What is going on here? PayPal can see perfectly well what happened in February so it is perfectly obvious that the debits are not authorised and TomTom will refund each one, assuming that I have the patience to contact them every month.
IANAL, but I think that the GPL license is related to the Samsung *source* code copyright; instead the patent is related to the /copyright/ of *ideas/algorithms* implementation; the last "copyright" word has to be intended in a more general meaning.
What I mean is that even if the source code is released under GPL, that doesn't affect any Microsoft rights of the exFAT patents.
So if you want to ship the Samsung *compiled* code you have to respect the GPL requirements, and you have to ship the source too; moreover you must have a license from Microsoft for selling/distributing the *compiled* code.
The GPL is *another* requirements to the Samsung exFAT code other than the Microsoft patents obligations.
May be that shipping the code, is legal; but for sure you need a Microsoft license for shipping the compiled code or you are in risk to be sued.
That happened in TomTom vs Microsoft court case, related to the FAT32 patents. ( _v._TomTom). It must to be noted that Microsoft never prohibit Linus to ship the source code of the FAT32 in the linux kernel. But sued TomTom when it tried to ship the compiled code.
But I don't know what happens if you ship (like Samsung does) the source code and an user
a) download the exFAT source code
b) compile it and execute it on its own computer
Because nobdy ships nor sells the *compiled* code.
To me it seems a way too simple to circumvent the patents obligations.
GB
(Log in to post comments) Samsung releases exFAT filesystem source Posted Aug 17, 2013 19:29 UTC (Sat) by SLi (subscriber, #53131) [Link]
I'm Ruanna, a content writer for TomTom Developers. This article originally appeared on developer.tomtom.com. The original author is Jose Rojas. Check out our Developer Portal for more articles, tutorials, code samples, toolkits, and more!
One of the questions in the survey was asking people if they verified the location of the crash information. So if your crash report form doesn't have enough detail, how do you know that the crash actually happened in a work zone? And further, are there specific information from your crash report form that will tell you exactly where in the work zone it happened?
So this work zone was a long project, about I think at least 30 miles of continuous work zone with barrier on both sides. It was a heavy widening project. And so the crashes were way up across the board. So this gives you an idea of how it looked previous to the work zone and then also how it's behaving as it goes across the year, and if you see a spike in a certain month, then you can investigate what might have caused that spike-- whether it was a different phase that will happened to be in, or different operation that they were doing during that month.
So the purpose of this report is to kind of try to find those impacts that we didn't expect. And then also because we're not in on the weekends and that district work zone person most likely is not in on the weekends, to kind of give them a heads up if something happened that they were not aware of.
We also with that fused information from 75 weather stations in Virginia that were located near the interstate system. And essentially what happened is our research office, in concert with our operations division, developed Matlab code that combined all these data sets together and then we use Tableau for visualization in order to generate these delay estimates.
We're also able to take this and break it down by interstate corridor and region. So again, just another example here. This is the contribution that happened in Hampton Roads due to that major capacity expansion project on I-64. We had another bridge project on a rural section of I-95 that was out there that also caused this large jump in congestion. So this is being used in concert with the other things in this congestion pie to help make some decisions about how we're investing and how we're trying to mitigate some of these problems that we see at our sites.
Now in this minute, what happened is it dynamically generated three different sub XD segments that were substantially different from this 43 miles an hour. And so essentially what we're seeing here is that starting at the link for the first 0.13 miles, we have a speed of 36 miles an hour. Then we've got a gap between 0.13 and 0.26 that has this 43 mile an hour speed. And then we have a 48 mile an hour speed and a 51 mile an hour speed.
aa06259810