Location field and geocode duplication

Answered

Comments

8 comments

  • Casper Fabricius

    We don't geocode the locations. We just save the address, and then we let Google Maps do the geocoding on the fly client-side. So we don't have the lat/long stored to share through the API.

    0
    Comment actions Permalink
  • James Trusler

    When you put the address through into google maps, an address is returned in the geocoder. Is there any possibilities that this can be shared through the api in the future :) ?

    0
    Comment actions Permalink
  • James Trusler

    a lat long is returned in the geocoder*

    0
    Comment actions Permalink
  • Christian Holm

    We always wanted to do more with the location field, but haven't found the time for it yet. I think it is very likely that we will do geocoding and reverse geocoding in the API at some point next year, but when that is I have no idea.

    0
    Comment actions Permalink
  • James Trusler

    Hi guys, just stirring up this old post because i'm wondering how many people will benefit from this.

    In Podio, when you see a google map embedded, it has come originally from someone typing in a location: "England, Peper Harow Park"

    That string is then sent to Google to Geocode by you guys. The longitude and latitude that is returned from google you use to iterate over and display on the map.

    Considering you have gone to the effort of getting the latlong, i wonder if you could possibly store it as part of the map object you send to us through the API.

    Why?

     If we wanted to display a selection of app items on a map we create, we will need to geocode the location your Podio API sends us... and geocoding is slow and has limits. While you only need to geocode once per map added, if we are trying to display lots, we have to geocode lots... and regardless of caching, at some point, those locations do have to be geocoded. It would make life much much easier if we could just used the lat longs stored in Podio. 

    If you are worried about that data going out of date, whenever the item is looked at... just refresh the data stored as the latlong which I assume you are doing any way?

    What are your thoughts? 

    0
    Comment actions Permalink
  • Andreas Haugstrup Pedersen

    Hi James,

    As Christian mentioned above we would like to do more with the location field than we are currently doing. Unfortunately, we haven't found the time yet.

    We don't store any lat/long data at the moment as all geocoding happens on the fly in your browser. Believe me, if we had them available we would expose them to you. We see clear advantages in doing so, but we have not had time to improve the location field yet.

    All the best,

    Andreas 

    0
    Comment actions Permalink
  • Stefan Falkboman
    • 1 here. Populating a map using the API would be so much easier with Long/Lat values rather than just an address.
    0
    Comment actions Permalink
  • Andreas Forstinger

    Just stumbled upon this thread and wanted to share what we did. We needed this functionality too and what we did is the following: we did not use the "location" field, but fields for street, city etc. Then we have a combined "full address" field. Behind this we have PHP API hook sitting and waiting for changes to the full address (actually the seperate fields because hooks on calculated fields are not allowed) - we then do the Google Geocoding ourselves and store the coordinates. We have another PHP script showing a map with all the items, based on our Podio coordinates.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk