Drupal geofield auto resolve geocode from address

[joskar]

Drupal geofield auto resolve geocode form address field. So it doesn't let us to pass a value direct to the geofield. This seems to be a headache because in drupal administrator panel there isn't an "admin friendly" way to disable this kind of behavior. Any suggestions ?

[billtzim]

I am not sure if i am getting what you`re saying but why use the geofield which has geocoding enabled with data taken from the address field and not pass the information directly to the database tables. Also, what is it that you want to accomplish?

Στις 5:04 μ.μ. Παρασκευή, 7 Μαρτίου 2014, ο/η JosKar [email protected] έγραψε:

Drupal geofield auto resolve geocode form address field. So it doesn't let us to pass a value direct to the geofield. This seems to be a headache because in drupal administrator panel there isn't an "admin friendly" way to disable this kind of behavior. Any suggestions ?
—
Reply to this email directly or view it on GitHub.

[hypest]

OK, here's what the mobile needs to be able to do: post an article with the precise geocoordinates, (taken via the device GPS or from a map). So, we tried to understand how the current posting can accommodate this goal, and saw that it can't. We need to somehow understand how the Drupal plugins/modules can be combined to use the direct "Latitude/Longitude" geofield type from the xml-rpc service. So, any quick pointers towards that direction would be welcomed :)

[billtzim]

Yes i see the problem in what you are trying to do. From drupals perspective i dont know how internally worksthe thing but from the current setup i don't see any easy way to change the current setup. The only thing that comes in mind is to create a second content type (ct). The existing ct connects geofield with address_field and changing that will break the user experience of adding location via address.
I propose that we create a second ct where the geofield is setup to take coordinates directly and that ct will be used solely for the android app posting purpose. In the database as far as i have seen (and if memory serves right) the points are all together and have a column with the ct name in which they belong.

Problems that may occur: We will have to check that point listing, mapping and searching can be configured to seamlessly work with both content types.

This is a video about how to use services to post coordinates --> http://www.youtube.com/watch?v=mItU7eogjbU   It may give some ideas. I will research the problem  a bit and report any findings if any

Στις 2:57 π.μ. Κυριακή, 9 Μαρτίου 2014, ο/η Stefanos Togoulidis [email protected] έγραψε:

OK, here's what the mobile needs to be able to do: post an article with the precise geocoordinates, (taken via the device GPS or from a map). So, we tried to understand how the current posting can accommodate this goal, and saw that it can't. We need to somehow understand how the Drupal plugins/modules can be combined to use the direct "Latitude/Longitude" geofield type from the xml-rpc service. So, any quick pointers towards that direction would be welcomed :)
—
Reply to this email directly or view it on GitHub.

[alskia]

Love that you boys are working on a weekend :)

On Sun, Mar 9, 2014 at 10:21 AM, billtzim [email protected] wrote:

Yes i see the problem in what you are trying to do. From drupals
perspective i dont know how internally worksthe thing but from the current
setup i don't see any easy way to change the current setup. The only thing
that comes in mind is to create a second content type (ct). The existing ct
connects geofield with address_field and changing that will break the user
experience of adding location via address.
I propose that we create a second ct where the geofield is setup to take
coordinates directly and that ct will be used solely for the android app
posting purpose. In the database as far as i have seen (and if memory
serves right) the points are all together and have a column with the ct
name in which they belong.

Problems that may occur: We will have to check that point listing, mapping
and searching can be configured to seamlessly work with both content types.

This is a video about how to use services to post coordinates -->
http://www.youtube.com/watch?v=mItU7eogjbU It may give some ideas. I
will research the problem a bit and report any findings if any

Óôéò 2:57 ð.ì. ÊõñéáêÞ, 9 Ìáñôßïõ 2014, ï/ç Stefanos Togoulidis <
[email protected]> Ýãñáøå:

OK, here's what the mobile needs to be able to do: post an article with
the precise geocoordinates, (taken via the device GPS or from a map). So,
we tried to understand how the current posting can accommodate this goal,
and saw that it can't. We need to somehow understand how the Drupal
plugins/modules can be combined to use the direct "Latitude/Longitude"
geofield type from the xml-rpc service. So, any quick pointers towards that

direction would be welcomed :)

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-37121862
.

Alkisti Skiadopoulou
Architect, Msc
Twitter: @alskia http:/twitter.com/alskia
http://archinc.wordpress.com/
http://gr.linkedin.com/in/alkistiskiadopoulouhttp://about.me/alskia
http://gr.linkedin.com/in/alkistiskiadopoulou
https://www.elance.com/s/alskia/

[billtzim]

After the love given by alskia to us weekend working boys i have another proposition

What if you applied reverse geocoding on the android side converting thus the gps location to address (the same thing is what geofield does) and push the returned address for posting. The geocoding service used is the same (google's) so we won't have different results i believe.

Some sample code just for reference

http://stackoverflow.com/questions/6922312/get-location-name-from-fetched-coordinates

Στις 1:12 μ.μ. Κυριακή, 9 Μαρτίου 2014, ο/η alskia [email protected] έγραψε:

Love that you boys are working on a weekend :)

On Sun, Mar 9, 2014 at 10:21 AM, billtzim [email protected] wrote:

Yes i see the problem in what you are trying to do. From drupals
perspective i dont know how internally worksthe thing but from the current
setup i don't see any easy way to change the current setup. The only thing
that comes in mind is to create a second content type (ct). The existing ct
connects geofield with address_field and changing that will break the user
experience of adding location via address.
I propose that we create a second ct where the geofield is setup to take
coordinates directly and that ct will be used solely for the android app
posting purpose. In the database as far as i have seen (and if memory
serves right) the points are all together and have a column with the ct
name in which they belong.

Problems that may occur: We will have to check that point listing, mapping
and searching can be configured to seamlessly work with both content types.

This is a video about how to use services to post coordinates -->
http://www.youtube.com/watch?v=mItU7eogjbU It may give some ideas. I
will research the problem a bit and report any findings if any

Óôéò 2:57 ð.ì. ÊõñéáêÞ, 9 Ìáñôßïõ 2014, ï/ç Stefanos Togoulidis <
[email protected]> Ýãñáøå:

OK, here's what the mobile needs to be able to do: post an article with
the precise geocoordinates, (taken via the device GPS or from a map). So,
we tried to understand how the current posting can accommodate this goal,
and saw that it can't. We need to somehow understand how the Drupal
plugins/modules can be combined to use the direct "Latitude/Longitude"
geofield type from the xml-rpc service. So, any quick pointers towards that

direction would be welcomed :)

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-37121862
.

Alkisti Skiadopoulou
Architect, Msc
Twitter: @alskia http:/twitter.com/alskia
http://archinc.wordpress.com/
http://gr.linkedin.com/in/alkistiskiadopoulouhttp://about.me/alskia
http://gr.linkedin.com/in/alkistiskiadopoulou
https://www.elance.com/s/alskia/
—
Reply to this email directly or view it on GitHub.

[joskar]

hmm this sound like a good work around. I am going to make some tests.

[billtzim]

Workaround is my middle name :p ΚΑΨΙΜΟ (no good enough English word for this :D )

Στις 3:08 μ.μ. Κυριακή, 9 Μαρτίου 2014, ο/η JosKar [email protected] έγραψε:

hmm this sound like a good work around. I am going to make some tests.
—
Reply to this email directly or view it on GitHub.