| Subject: | Truncated levels in Geo-Google-PolylineEncoder-0.04? |
| Date: | Sun, 24 May 2009 23:44:40 -0700 |
| To: | bug-Geo-Google-PolylineEncoder [...] rt.cpan.org |
| From: | Joe Navratil <joe [...] navratils.org> |
Package: Geo-Google-PolylineEncoder-0.04
Perl version: v5.8.9 built for darwin-2level
OS: Darwin Kernel Version 9.7.0 (Mac OS X 10.5.7 + Darwin Ports)
I'm not entirely sure what's going on, but it would appear that
generating a polyline encoding from many moderately complex sets of
data ends up with the wrong number of levels (as reported by Google's
Interactive Polyline Encoder Utility, http://code.google.com/apis/maps/documentation/polylineutility.html)
and also fails to display the last few points (in the attached
example, approximately three points are left off the end when the
encoded line is rendered).
The attached sample data gives the following output:
points: qrueF`zojVYD}BSs@?Lh@CZWb@oAbAiC^yAGgCDuBIAd@o@|
B
@hB
]tAyA
]sBeACGk
@De
@KUM
]Km
@]YWa
@g
@o
@_@_@K]SWg@o@g@uAbBSL}AiD]g@MEc@^W`@SJUEMWMAOLi@DMLILIf@A`BIr@_@xA}ARwB
\sAEaC`@
levels: PA@DB@DBD@@FAABFA@BA@?CA?A?@AAE@DA@F@@C@@CA@D@A@AE?ABP
...which, as mentioned, fails the IPEU check and displays incorrectly.
The same data plugged into the usnavguide.com generation code
(mentioned in Geo::Google::PolylineEncoder's "SEE ALSO" doc section)
results in the following output:
points: qrueFdzojVYB}BSq@?Jd@CZUb@qAbAiC`@yAGgCBs@CaAEAf@o@|
B
@fB
]tAyA
[sBeACIk
@Be
@KUK
]Mm
@[YWa
@g
@o
@a@_@I[SYi@o@e@sAbBUJ{AkD]e@MEc@^W^SLWEKYMAONi@BMNGJIh@C`BGr@_@xA}APwB
\sAGaC`@
levels: PA@D@CACD@@@FAAAFA@BB@@CA@A@@BAE@EA@F@@CA@C@@E@A@AE@AAP
...which passes the IPEU check and displays correctly.
I can provide more sample data that exhibits this behavior if it would
be helpful.
-Joe
Message body not shown because it is not plain text.