Enable .KMZ export for Advanced Search results

[leovegoda]

Is your feature request related to a problem? Please describe.
The Advanced Search provides geographic results for Campuses, Exchanges, Facilities and Organizations. These can be exported as JSON or CSV. We should add .KMZ as an export option now we share all facility data in .KMZ format.

Who is affected by the problem?
Anyone who wants to look at data on a map.

What is the impact?
Improved service offering.

Are there security concerns?
No. This is the same data in a new format.

Are there privacy concerns?
No.

Describe the solution you'd like
Add a .KMZ export option.

Do you think this feature will require a formal design?
Possibly.

Describe alternatives you've considered
Do nothing.

Could this feature request need support from the Admin Committee?
It should not.

What is the proposed priority?
Implement in a .KMZ focused release early in 2024

[mcmanuss8]

+1

[martinhannigan]

How much resource is this going to use? I would suggest we at least put this function behind a login account. I could see this being used widely and by many with no direct affiliations to PDB. Since it's only fasciitis data the parsing regionally is slick if approved.

…

On Wed, Dec 13, 2023 at 11:18 AM mcmanuss8 ***@***.***> wrote: +1 — Reply to this email directly, view it on GitHub <#1495 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFA2YQT3RCMZ4IFQDSHLM4LYJHINDAVCNFSM6AAAAABATLDDTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJUGI2DIOBYGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[leovegoda]

How much resource is this going to use?

Probably very similar to what we use now.

I would suggest we at least put this function behind a login account.

All the geographic use of Advanced Search already requires users to be logged in. This is just a new way to package the same results they are already getting.

[martinhannigan]

Resource wise I was asking about how much CPU do we burn with each output to KML if any and we should consider moving the KML itself "inside" the login. The data is valuable and the least we can require is for a user to be a bonafide PDB user. We ought to think more about how we can use this feature.

…

On Wed, Dec 13, 2023 at 12:55 PM Leo Vegoda ***@***.***> wrote: How much resource is this going to use? Probably very similar to what we use now. I would suggest we at least put this function behind a login account. All the geographic use of Advanced Search already requires users to be logged in. This is just a new way to package the same results they are already getting. — Reply to this email directly, view it on GitHub <#1495 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFA2YQVHCELNG47NHPXPHLTYJHTXPAVCNFSM6AAAAABATLDDTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJUGQ2TCNRSGM> . You are receiving this because you commented.Message ID: ***@***.***>

[leovegoda]

The @peeringdb/oc can comment on the CPU requirements to generate a .KMZ file versus JSON.

All our data, except for contact data marked as private, is already available in other formats. You can sync PeeringDB to your laptop with https://github.com/peeringdb/peeringdb-py. We could add a login requirement but that would a policy change.

[martinhannigan]

So moving the kmz from the main page/www without auth to a page that requires auth is a policy change?

…

On Wed, Dec 13, 2023 at 16:00 Leo Vegoda ***@***.***> wrote: The @peeringdb/oc <https://github.com/orgs/peeringdb/teams/oc> can comment on the CPU requirements to generate a .KMZ file versus JSON. All our data, except for contact data marked as private, is already available in other formats. You can sync PeeringDB to your laptop with https://github.com/peeringdb/peeringdb-py. We could add a login requirement but that would a policy change. — Reply to this email directly, view it on GitHub <#1495 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFA2YQRZEPDYGX4ZWXOQKFDYJIJQPAVCNFSM6AAAAABATLDDTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJUGY4TGNJWHA> . You are receiving this because you commented.Message ID: ***@***.***>

[grizz]

+1

[leovegoda]

So moving the kmz from the main page/www without auth to a page that requires auth is a policy change?

Requiring a login for data that does not require a login now sounds like a policy change to me. What is the advantage we get from making them login?

[martinhannigan]

I don’t recall any suggestions that it should’ve been in the public space anyhow. Was there? I’ll send some policy suggestions to the PC. Then we can communicate that to the board. thanks leo!

…

On Thu, Dec 14, 2023 at 10:54 Leo Vegoda ***@***.***> wrote: So moving the kmz from the main page/www without auth to a page that requires auth is a policy change? Requiring a login for data that does not require a login now sounds like a policy change to me. What is the advantage we get from making them login? — Reply to this email directly, view it on GitHub <#1495 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFA2YQXLBPZ4XR7PPZATHSTYJMOLVAVCNFSM6AAAAABATLDDTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJWGEYDIMBWGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[leovegoda]

I think the decision to put it in the footer was taken by me and 20C. We chose that because it just repackaged existing content that was already available anonymously.

[martinhannigan]

I didn't know anyone else had a KMZ. Doable vs API - buy then why would we if someone else did it? (hint: authoritative +enterprise value)

…

On Thu, Dec 14, 2023 at 12:54 Leo Vegoda ***@***.***> wrote: I think the decision to put it in the footer was taken by me and 20C. We chose that because it just repackaged existing content that was already available anonymously. — Reply to this email directly, view it on GitHub <#1495 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFA2YQVJJBRSSXSFH3UXC7DYJM4MHAVCNFSM6AAAAABATLDDTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJWGMZDKNBTGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[martinhannigan]

This isn't a bad idea overall. I'd suggest we do a cost analysis. I'm also skeptical that outputting advanced search results into a KML will be worth the cost to produce it e.g. "all facilities in Boston, MA". While the cost may be small, it's not negligible or zero.

…

On Thu, Dec 14, 2023 at 12:54 PM Leo Vegoda ***@***.***> wrote: I think the decision to put it in the footer was taken by me and 20C. We chose that because it just repackaged existing content that was already available anonymously. — Reply to this email directly, view it on GitHub <#1495 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFA2YQVJJBRSSXSFH3UXC7DYJM4MHAVCNFSM6AAAAABATLDDTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJWGMZDKNBTGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[grizz]

outputting to KML is going to be very similar to CSV. KMZ is compressed, so it would be a bit more.

[martinhannigan]

-1

[martinhannigan]

+1

[jackcarrozzo]

+1