Your method is fine, but here's how I would first approach this problem. It's based on some assumptions about how the coordinate data looks, so it may not be usable for you. However, I think the process of developing it is simpler, and perhaps it's even a little more robust.
if ($kmlfile =~ m{<coordinates>(.*?)</coordinates>}) {
my @triples = split(' ', $1);
for (@triples) {
my ($lat, $long) = split(',', $_);
push(@coords, [$lat, $long]); # or whatever
}
}
It's a little more robust in that if there is non-conforming data it will be obvious (like one of your coordinates will be undef or contain junk.) Regex approaches have a tendency to just stop giving you results without any hint that there's a problem. That is, when they stop matching you're not sure if it's because there's nothing more to match or if there's a problem with your regex.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.