addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1light-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Location Analytics by Placed

  • Nov 13, 2012 · 6:30 PM
  • F5 Networks

Hello everyone!

Acquiring location data can introduce a slew of issues for the developer - anything from cleaning the data for analytics, to dealing with battery and privacy issues. Placed is very familiar with these problems, and I expect they will be presenting a fascinating look at how you can solve them for your applications!

There will be dinner and drinks provided, and I look forward to seeing everyone there!



Join or login to comment.

  • Brad B.

    Thanks for the feedback everyone! The Placed team had a great time at the meetup. Here is a link to the slides from the presentation. If you find any errors or have any questions let me know! My email is [masked].

    November 19, 2012

  • Jim

    Very much enjoyed Placed, Inc. Speakers.

    November 18, 2012

  • Mitch

    I just noticed that with the new Android 4.2, the following is true regarding location permissions:

    "Compared to previous versions of Android, user location results may be less accurate if your app requests the ACCESS_COARSE_LOCATION permission but does not request the ACCESS_FINE_LOCATION permission.
    To meet the privacy expectations of users when your app requests permission for coarse location (and not fine location), the system will not provide a user location estimate that’s more accurate than a city block."

    This makes sense, I suppose. But that means that even if there is fine location known on the device, they will falsely decrease the accuracy of the location by about a city block. I wonder if that will be done with simple rounding off. Interesting!

    November 16, 2012

  • Margaret M.

    Excellent presentation! Informative topics on location detection accuracy, battery performance monitoring, location data analytics & dealing with user privacy issues.

    November 14, 2012

  • Zhong


    November 13, 2012

  • Eric S.

    Great host, great presentation by Placed

    November 13, 2012

  • Max M.

    Where can we park?

    November 13, 2012

    • Benn

      There's a variety of street parking options, including some free streets one block up from Elliot, and several lots in the area.

      November 13, 2012

    • Max M.

      Thanks for the info!

      November 13, 2012

  • A former member
    A former member

    Does anyone know if this presentation is going to be focused on coding or if it is on best practices?

    November 12, 2012

    • Andrea

      Hi Jason - It's a little bit of both. Our Android dev will be showing some code as well as walking through some things we have learned in our experiences with location data. We'll also have our Principal Scientist talking about how his team works with the data that we collect. Hope to see you there!

      November 12, 2012

    • A former member
      A former member

      Thank you Andrea, As a UX Designer, I get lost when it comes to anything more then the most basic coding. :-)

      November 13, 2012

  • John A. H.

    Looks like another good topic. Wish I could be there. I have a conflicting meeting.

    October 7, 2012

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy