-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KML Placemark/Point Meta Data Not Displaying Correctly #1475
Comments
Additional debugging. After more probing it appears conclusive that something is breaking in the markup related to comment. Crown marked "all" their records with the comment "Previously Lightower" and none work NTT FRA 2 has comments, truncated meta data Seems like a pattern. |
I see this. Also, when I look at https://www.peeringdb.com/fac/3152 I just see the comment but not the rest of the entry. |
+1 this should be checked out. |
+1 we should fix this |
Thanks Martin for linking, I had missed this one when checking issues for duplicate before submitting, my apologies. As noted in #1501, I was able to confirm that the notes being added as the "Description" are hiding the rest of the meta data. Verified this by manually deleting the notes text from the Description in Google Earth and the meta data shows up properly. Can do the same in reverse and go to properties of a placemark and add any text in the Description, once you do that you can't see any of the other meta data, only the text in the description. Seems that the solution is likely to just not export the Notes field in to the Description since the Notes are also in the regular meta data table and shows up there. Thanks all! |
Anthony, yep. Confirmed. I couldn't figure out why removing the notes had
an impact, but I think 20c did.
The notes are valuable IMHO. Not critical of peeringDB, but they've enabled
work-around to deficiencies. They're also good to monitor to see where PDB
can make improvements (such as
#1131) since if you have to
put it in notes to get attention and more than a few are doing it perhaps
there's an enhancement to be made. Even if Lumen did tag you in PDB, that
doesn't tell the real story of Lumen (Qwest, Level(3), Centurylink,
$acquisition). A lot of people still think in terms of footprint. And
because of how messy long haul provisioning is the extra information can be
useful to guide provisioning while they try and find everything.
Example attached. The other great thing about notes is it supports markdown
language so you can make it "look" nice in the record.
Hope it's not too difficult of a fix!
…On Mon, Jan 8, 2024 at 12:57 PM Anthony Steller ***@***.***> wrote:
Thanks Martin for linking, I had missed this one when checking issues for
duplicate before submitting, my apologies.
As noted in #1501 <#1501>, I
was able to confirm that the notes being added as the "Description" are
hiding the rest of the meta data. Verified this by manually deleting the
notes text from the Description in Google Earth and the meta data shows up
properly. Can do the same in reverse and go to properties of a placemark
and add any text in the Description, once you do that you can't see any of
the other meta data, only the text in the description.
Seems that the solution is likely to just not export the Notes field in to
the Description since the Notes are also in the regular meta data table and
shows up there.
Thanks all!
—
Reply to this email directly, view it on GitHub
<#1475 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFA2YQV3VIGJT5IQZSPTH4DYNQXQNAVCNFSM6AAAAAA76JLZEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBRGU3DSMZZGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Will be fixed with #1489 |
Describe the bug
When clicking on pin for KML meta data? Some display, and some have truncated data.
To Reproduce
To easily fly to the bad pin, use the GE app to go to 1 Summer, Boston, MA
This is happening to more than a few placemarks. Or points. I thought I saw some inconsistency in the KML but the file was too big to easily diff the bad vs. good. HTH.
Expected behavior
Meta data display entirely when requested
Who is affected by the problem?
Users of the KMZ file
What is the impact?
Incomplete data
Are there security concerns?
No.
Are there privacy concerns?
No.
What are the proposed actions?
Evaluate, repair.
What is the proposed priority?
Not urgent
Provide a rationale for any/all of the above
Accuracy, consistency.
Additional context
Considered adding to enhancements list, but this bug has a different class so I didn't.
The text was updated successfully, but these errors were encountered: