Maintenance, especially GitHub issues

[Andreas B]

Hi everyone, especially Google people,

is this project still actively maintained? I just replied to someone who opened a new issue over on GitHub, and from a short survey it looks as if many of the currently open issues are actually resolved (or never were proper code issues to begin with) and can be closed.

Is there any way I could help with that, for example by tagging issues as "solved"?

[Bill S]

Hi Andreas, thanks for replying to that issue!

Folks from Google monitor this project and approve pull requests, but mainly rely on the community for changes, so you're definitely welcome and encouraged to tag resolved issues.

Cheers, Bill

[Andreas B]

Hi Bill,

thanks for the reply. For what it's worth, it's hard to tell from your username here if you are Google folk yourself - I assume you are because there's a similar username reviewing and merging over on GitHub. ;)

Can you suggest a good way to tag those issues? I'm obviously not allowed to add labels or anything, so it seems the only way would be to comment on (sometimes very outdated) issues - which could be considered rude or have the side effect of resurrecting off-topic discussions on those issues.

Here are some random issues that could, IMO, be closed - just the easy one's, not really having a detailed look when it comes to implementation requests:

#424 - off-topic, just mentioning some map POI

#399 - off-topic; potential bug on plus.codes website, not with OLC technology itself

#394 - seems as if I answered to OP's satisfaction last July

#387 - seems as if I answered to OP's satisfaction last March

#354 - problem with Google Map's implementation of choosing the proper reference location while shortening; not a problem with OLC itself

[Bill S]

Yup that's me :)

Thanks for the suggestions--I closed those issues. Feel free to comment on issues that look ready to close or flag them on this mailing list and I can do another pass. I see there are a couple feature requests out there for GitHub to support proposed labels, which seems like it would be pretty helpful here...

Cheers, Bill

[Andreas B]

There has been some recent activity over on GitHub, so here's another pass at issues that could probably be closed, or otherwise be dealt with:

#65 - oldest open issue. Someone offered code translation to TCL, but this ultimately went nowhere. User has since deleted his GitHub account, so it's likely impossible to work out proper attribution etc. for the code made available in a zip file
#126 - another issue with Google Maps or the plus.codes website, so can only be decided one way or the other by a Googler

#134 - replied to, not actually a bug/issue

#155 - replied to, not actually a bug/issue

#248 - replied to, seems outside of OLC scope; Doug explicitly stated that he doesn't see this progressing on your end

#358 - discussing the merits of OLC vs. other technologies; this comparison is already a part of the documentation, so no current issue; discussion seems to have run its course

#371 - Doug suggested rephrasing the Wiki, which has been accepted by creator of the issue. Apparently, the Wiki can only be edited by the repo owner(?), so please do and close this one as fixed.

[Bill Steinmetz (㌱)]

Done, thanks again!

--
Public site: http://www.openlocationcode.com/
Github project: https://github.com/google/open-location-code
Demo site: http://plus.codes/
---
You received this message because you are subscribed to a topic in the Google Groups "Plus Codes Community Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/open-location-code/5TuJ4rnc3bc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to open-location-c...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/open-location-code/8893a0e0-a990-4469-a047-cf03ce30969en%40googlegroups.com.

[Andreas B]

The following issues seem to be spam, or otherwise unrelated to the project, and can be closed:

https://github.com/google/open-location-code/issues/468

https://github.com/google/open-location-code/issues/484

https://github.com/google/open-location-code/issues/493

https://github.com/google/open-location-code/issues/494

https://github.com/google/open-location-code/issues/495

[Andreas B]

Another check reveals that

https://github.com/google/open-location-code/issues/442 - has been fixed in code, and can be closed

https://github.com/google/open-location-code/issues/466 - is another Google Maps issue, and can be closed as well.

Also, if I could get a comment if a PR as outlined in #500 would not be welcome, that would be appreciated. Otherwise, I'm getting to work in the next few days.

[Andreas B]

After #500 has been done, the following issues can be closed as "not planned":

https://github.com/google/open-location-code/issues/398

https://github.com/google/open-location-code/issues/461

https://github.com/google/open-location-code/issues/497

I suggest referencing https://github.com/google/open-location-code/wiki/FAQ#reference-location-dataset in the closing comment for each of these issues.

[Huroye Scott]

I am looking for some guidance on Plus Code implementation. If you can help please send me an email.

Thanks,

Roy

--

Public site: http://www.openlocationcode.com/
Github project: https://github.com/google/open-location-code
Demo site: http://plus.codes/
---

You received this message because you are subscribed to the Google Groups "Plus Codes Community Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-location-c...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/open-location-code/886cb9ef-afa2-47fc-97db-1172fcbf0657n%40googlegroups.com.

[Andreas B]

Hi Roy,

if it is something I can help you with, I'm happy to do that right here on the mailing list. Just open a new conversation with your questions. :)

[Andreas B]

https://github.com/google/open-location-code/issues/138 - relevant Q/A quoted from FAQ.txt should be added to the Wiki FAQ, then this issue be closed.

https://github.com/google/open-location-code/issues/161 - four years ago, a "Google-internal" discussion was supposedly started to find out where expanded functionality should go. If any progress has been made on that internal thread, please add the outcome to the issue. If none, the issue might as well be closed as "out of scope" for this project.

https://github.com/google/open-location-code/issues/278 - seems as if the original question has been answered; unsure if anything needs to be added based on the discussion; if not, close this issue - otherwise, let's discuss what exactly should be added where.

https://github.com/google/open-location-code/issues/343 - seems as if this could be closed, partially because it is out of scope insofar as it discusses Google Maps, and on top of that with a reference to the new FAQ addition, similar to https://github.com/google/open-location-code/issues/497 and other recently closed issues.

https://github.com/google/open-location-code/issues/483 - can be closed after accepting #502

[Pankaj Raina]

Is there a way to get distance between 2 plus codes in KM unit?

Regards

Pankaj Raina

To view this discussion on the web, visit https://groups.google.com/d/msgid/open-location-code/a1062369-5e0d-4c27-8a07-7807366f80e3n%40googlegroups.com.

[Andreas B]

Not directly. The best way to do this would be to convert both codes back to lat/long, and then implement the Haversine formula: https://en.wikipedia.org/wiki/Haversine_formula

[Rasťo Šrámek]

You can use the S2 geometry library, specifically the S2Earth class, to calculate the distance between two lat/longs.

To view this discussion on the web, visit https://groups.google.com/d/msgid/open-location-code/CACvUW_eLBjB7qs-j%3DpHXLEugyzoepdZggwCf4EZVpBqraDcvgg%40mail.gmail.com.