Google Earth roads mis-aligned
-
Does someone has experienced this kind of problem? The roads appears more or less above other parallel roads. I see the maps with the feeling of "If I can drag this road's layers 20 pixels left and up all will fit nice!".
For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.(John 3:16) :badger:
-
Does someone has experienced this kind of problem? The roads appears more or less above other parallel roads. I see the maps with the feeling of "If I can drag this road's layers 20 pixels left and up all will fit nice!".
For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.(John 3:16) :badger:
Clickok wrote: Does someone has experienced this kind of problem? The roads appears more or less above other parallel roads. I see the maps with the feeling of "If I can drag this road's layers 20 pixels left and up all will fit nice!". There are actually a couple of things that go into this. First there was a problem with USGS data the has been propagated through most of the US imagery and elevation files. Not really a problem until you get into the fine details, which few ever needed access to before. The cause was the difference between center pixel and corner pixel in the root calculations of core 100m/30m elevation files generated prior to about 2 years ago. It isn't something that is known by everyone. We pointed out the error to the USGS about 3 years ago at the beginning of the DRAPE project during an evaluation of digital elevation files vs. real terrain. Currently you are best off double checking the processing date of the elevation files (which are also used for alignment of image features on geospecific imagery (satellite imagery specific to any given location). The other issue is the way data is stored for roads and addresses. There is no direct correlation between latitude/longitude data and road data except at key-points (roads are stored as vectors of direction and length which tends to increase errors until another key-point). Although many of us complain over the inaccuracies, since the primary user of said data is road navigation, and GPS navigation devices use "lock-on-road" options, most people don't know, and don't care. :) Welcome to the real world. :) congratulations on seeing it, most people don't. :)
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Clickok wrote: Does someone has experienced this kind of problem? The roads appears more or less above other parallel roads. I see the maps with the feeling of "If I can drag this road's layers 20 pixels left and up all will fit nice!". There are actually a couple of things that go into this. First there was a problem with USGS data the has been propagated through most of the US imagery and elevation files. Not really a problem until you get into the fine details, which few ever needed access to before. The cause was the difference between center pixel and corner pixel in the root calculations of core 100m/30m elevation files generated prior to about 2 years ago. It isn't something that is known by everyone. We pointed out the error to the USGS about 3 years ago at the beginning of the DRAPE project during an evaluation of digital elevation files vs. real terrain. Currently you are best off double checking the processing date of the elevation files (which are also used for alignment of image features on geospecific imagery (satellite imagery specific to any given location). The other issue is the way data is stored for roads and addresses. There is no direct correlation between latitude/longitude data and road data except at key-points (roads are stored as vectors of direction and length which tends to increase errors until another key-point). Although many of us complain over the inaccuracies, since the primary user of said data is road navigation, and GPS navigation devices use "lock-on-road" options, most people don't know, and don't care. :) Welcome to the real world. :) congratulations on seeing it, most people don't. :)
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
Is this also why Google Earth puts a cross street through my living room? Or is that likely just bad road data...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
-
Is this also why Google Earth puts a cross street through my living room? Or is that likely just bad road data...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
Shog9 wrote:
Is this also why Google Earth puts a cross street through my living room? Or is that likely just bad road data...
probably a combination of both.... Don't sweat it, road data puts my home in the elderly care center across the street... think how that makes me feel. I just had my 42nd birthday, honest! :laugh:
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Is this also why Google Earth puts a cross street through my living room? Or is that likely just bad road data...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
Shog9 wrote:
a cross street through my living room?
see also: easement, eminent domain, parallel reality
image processing toolkits | batch image processing | blogging
-
Shog9 wrote:
a cross street through my living room?
see also: easement, eminent domain, parallel reality
image processing toolkits | batch image processing | blogging
Chris Losinger wrote:
easement, eminent domain
you know, they could be building a highway bypass through his house.... The bulldozers could be on the way now....
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Is this also why Google Earth puts a cross street through my living room? Or is that likely just bad road data...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
Ummm - didn't you get the letter from your council? Sorry to be the bearer of bad news, but...
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Is this also why Google Earth puts a cross street through my living room? Or is that likely just bad road data...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
You remind me of Arthur Dent...
-- Raaaaaaaaaaaaaaaaaaaaa!
-
You remind me of Arthur Dent...
-- Raaaaaaaaaaaaaaaaaaaaa!
Heh... Well, shucks. I'm gonna go have a beer and check on my downstairs neighbors... :rolleyes:
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
-
Is this also why Google Earth puts a cross street through my living room? Or is that likely just bad road data...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
I finished the four Hitch Hiker books this month, so it's no wonder I was reminded of Arthur Dent. :laugh:
Cheers, Vikram.
"But nowadays, it means nothing. Features are never frozen, development keeps happening, bugs never get fixed, and documentation is something you might find on wikipedia." - Marc Clifton on betas.
Join the CP group at NationStates. Password:
byalmightybob -
Is this also why Google Earth puts a cross street through my living room? Or is that likely just bad road data...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
[lil out of context] Google Earth uses Google Map API ??? some one to please update. btw, try this Google Map Application , its cool... 1) Go to maps.google.com 2) "Get Directions" 3) "London" in first text box and "New York" in second. 4) Read Step # 37. Lemme quote it: "Swim across the Atlantic Ocean 3,462 mi" :-D Can you try it ;P
-
Is this also why Google Earth puts a cross street through my living room? Or is that likely just bad road data...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
Nah, they just know about new roads that you don't....yet :laugh:
-
[lil out of context] Google Earth uses Google Map API ??? some one to please update. btw, try this Google Map Application , its cool... 1) Go to maps.google.com 2) "Get Directions" 3) "London" in first text box and "New York" in second. 4) Read Step # 37. Lemme quote it: "Swim across the Atlantic Ocean 3,462 mi" :-D Can you try it ;P
Brilliant. Being from this side of the pond, I can also tell you that steps #21 + #22 also involve getting a little damp (unless you use the ferry of course).
-
Does someone has experienced this kind of problem? The roads appears more or less above other parallel roads. I see the maps with the feeling of "If I can drag this road's layers 20 pixels left and up all will fit nice!".
For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.(John 3:16) :badger:
Clickok wrote:
Does someone has experienced this kind of problem?
yes :cool:
[VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]
-
I finished the four Hitch Hiker books this month, so it's no wonder I was reminded of Arthur Dent. :laugh:
Cheers, Vikram.
"But nowadays, it means nothing. Features are never frozen, development keeps happening, bugs never get fixed, and documentation is something you might find on wikipedia." - Marc Clifton on betas.
Join the CP group at NationStates. Password:
byalmightybobThere are five books... ;P
-
There are five books... ;P
Uh, I never said there were only four. I just happened to read four.
Cheers, Vikram.
"But nowadays, it means nothing. Features are never frozen, development keeps happening, bugs never get fixed, and documentation is something you might find on wikipedia." - Marc Clifton on betas.
Join the CP group at NationStates. Password:
byalmightybob -
Clickok wrote: Does someone has experienced this kind of problem? The roads appears more or less above other parallel roads. I see the maps with the feeling of "If I can drag this road's layers 20 pixels left and up all will fit nice!". There are actually a couple of things that go into this. First there was a problem with USGS data the has been propagated through most of the US imagery and elevation files. Not really a problem until you get into the fine details, which few ever needed access to before. The cause was the difference between center pixel and corner pixel in the root calculations of core 100m/30m elevation files generated prior to about 2 years ago. It isn't something that is known by everyone. We pointed out the error to the USGS about 3 years ago at the beginning of the DRAPE project during an evaluation of digital elevation files vs. real terrain. Currently you are best off double checking the processing date of the elevation files (which are also used for alignment of image features on geospecific imagery (satellite imagery specific to any given location). The other issue is the way data is stored for roads and addresses. There is no direct correlation between latitude/longitude data and road data except at key-points (roads are stored as vectors of direction and length which tends to increase errors until another key-point). Although many of us complain over the inaccuracies, since the primary user of said data is road navigation, and GPS navigation devices use "lock-on-road" options, most people don't know, and don't care. :) Welcome to the real world. :) congratulations on seeing it, most people don't. :)
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
Jeffry J. Brickley wrote:
The other issue is the way data is stored for roads and addresses. There is no direct correlation between latitude/longitude data and road data except at key-points (roads are stored as vectors of direction and length which tends to increase errors until another key-point). Although many of us complain over the inaccuracies, since the primary user of said data is road navigation, and GPS navigation devices use "lock-on-road" options, most people don't know, and don't care. Welcome to the real world. congratulations on seeing it, most people don't.
I would like to thank you, I just thought I was getting a little more blind. LOL :laugh: No actually I understand what you are talking about due to the fact that I was a USCG licensed Oceans Master for 20 Yr. and we fought with the DMA for the same reasons, as we were more heavily relying on Loran (long ago), and then GPS (in my industry we also used the differental correction module). This really pointed out the difference between chart and reality. Anyway, thanks for pointing that out, as you obviously, know a lot more about the reasons for the errors than I do but it sure clarified allot of unanswered questions for me. :-D
DB_Cooper1950 Either enjoy life, Or Hate Life, Just quit SITTING ON THE FENCE!