You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1.Load feed
2.Check line 3 for example
3.
What is the expected output? What do you see instead?
The shape files do not match the roads on the map
What version of the product are you using? On what operating system?
Please provide any additional information below.
I have had nothing but frustrations and difficulties trying to get this feed to
work and the response time on this forum has been a minimum of at least a month
before I hear anything back. We would like to go live but it is taking an
unreasonable amount of time for support.
Original issue reported on code.google.com by CulverCi...@gmail.com on 23 Dec 2010 at 3:12
Hi,
I'm sorry this forum has not been responsive for you.
I grabbed your test file, converted it to a .kml file and loaded it up in
Earth. Most of it looks sane, but I suspect what you're talking about are
shapes as shown in the attached image.
Looking through your datafiles, it looks like the shapes are being represented
correctly as they appear in your shape file. I see that
(34.00482985,-118.3886011) occurs in many places in the shape file, and seems
to be consistently out of place:
$ grep -n 34.00482985 feed2/shapes.txt
202:3S_shp,34.00482985,-118.3886011,201
228:3SATN_B7AM_shp,34.00482985,-118.3886011,227
272:3SATN_A7AM_shp,34.00482985,-118.3886011,271
307:3SATN_A7PM_shp,34.00482985,-118.3886011,306
366:3SATS_A7AM_shp,34.00482985,-118.3886011,365
415:3SATS_A7PM_shp,34.00482985,-118.3886011,414
622:4E_shp,34.00482985,-118.3886011,621
645:4W_shp,34.00482985,-118.3886011,644
So can you be more specific about how you generated this particular shape file?
Is this being generated by the transxchange converter utilities? I'm happy to
go bug-hunting, but I need more context to know where to look.
Cheers,
-J
Original comment by justinca...@google.com on 11 Mar 2011 at 7:42
Original issue reported on code.google.com by
CulverCi...@gmail.com
on 23 Dec 2010 at 3:12Attachments:
The text was updated successfully, but these errors were encountered: