Geo Coding
GoMaps.GeoCoding History
Hide minor edits - Show changes to output
Changed lines 3-4 from:
Nope. GoMaps will do it for you.
to:
Nope. GoMaps/ProMaps will do it for you.
Added lines 9-13:
!! When does ProMaps geocode my address
-> This is done in the script "GeoCodeAddress (address, tempObjectName, resultFieldName)" which is currently called from script triggers on the address fields on the "Properties Detail" layout. You can do the same in your file. We also include a script called "GeoCodeAddress For ProMaps" that will manually geocode the address for the record you are on. This script references the address fields in ProMaps so if you have different address fields make sure and edit the script to reference those new fields.
-> Be sure you give your copy of the "gm_GeoLocation" field an object name of "field_geoLocation" so our script can properly reference that field. For more, see step 5 (Add Geo Code Lookup To Your File) in our [[integration]] instructions.
-> This is done in the script "GeoCodeAddress (address, tempObjectName, resultFieldName)" which is currently called from script triggers on the address fields on the "Properties Detail" layout. You can do the same in your file. We also include a script called "GeoCodeAddress For ProMaps" that will manually geocode the address for the record you are on. This script references the address fields in ProMaps so if you have different address fields make sure and edit the script to reference those new fields.
-> Be sure you give your copy of the "gm_GeoLocation" field an object name of "field_geoLocation" so our script can properly reference that field. For more, see step 5 (Add Geo Code Lookup To Your File) in our [[integration]] instructions.
Changed line 48 from:
)
to:
)
Changed lines 29-33 from:
1. You'll still create a field called "gm_GeoLocation" field and give it an object name of "field_geoLocation". (See step 5 "Add Geo Code Lookup To Your File" in our [[integration]] instrucions.)
2. Make sure your Lat/Long is in the form Map expects, like: "47.6821060,-122.3085170" without the quotes.
3. Turn off the geocoding script by editing the script "GeoCodeAddress (address, tempObjectName, resultFieldName)" and placing an ExitScript step as the first line. Also disable the script "Check Property Integrity" the same way and now it's up to you to make sure you have a Lat/Long for every record =)
2. Make sure your Lat/Long is in the form Map expects, like: "47.6821060,-122.3085170" without the quotes.
3. Turn off the geocoding script by editing the script "GeoCodeAddress (address, tempObjectName, resultFieldName)" and placing an ExitScript step as the first line. Also disable the script "Check Property Integrity" the same way and now it's up to you to make sure you have a Lat/Long for every record =)
to:
-> 1. You'll still create a field called "gm_GeoLocation" field and give it an object name of "field_geoLocation". (See step 5 "Add Geo Code Lookup To Your File" in our [[integration]] instrucions.)
-> 2. Make sure your Lat/Long is in the form Map expects, like: "47.6821060,-122.3085170" without the quotes.
-> 3. Turn off the geocoding script by editing the script "GeoCodeAddress (address, tempObjectName, resultFieldName)" and placing an ExitScript step as the first line. Also disable the script "Check Property Integrity" the same way and now it's up to you to make sure you have a Lat/Long for every record =)
If your Lat and Long are in two separate fields, change the "gm_geoCode" field in the properties table to an auto enter calc. The contents of the calc should be text and would look like this...
Substitute (
List (
YourLat;
YourLong
);
"¶" ; ","
)
-> 2. Make sure your Lat/Long is in the form Map expects, like: "47.6821060,-122.3085170" without the quotes.
-> 3. Turn off the geocoding script by editing the script "GeoCodeAddress (address, tempObjectName, resultFieldName)" and placing an ExitScript step as the first line. Also disable the script "Check Property Integrity" the same way and now it's up to you to make sure you have a Lat/Long for every record =)
If your Lat and Long are in two separate fields, change the "gm_geoCode" field in the properties table to an auto enter calc. The contents of the calc should be text and would look like this...
Substitute (
List (
YourLat;
YourLong
);
"¶" ; ","
)
Changed lines 23-33 from:
Please note: The Google geocoding service is limited to 2500 geocode requests per day from your device. You can increase this limit by signing up for Google Maps API for Business. This is a paid service from Google that is used for customers with large user bases and heavy traffic. This should not be needed in most situations.
to:
Please note: The Google geocoding service is limited to 2500 geocode requests per day from your device. You can increase this limit by signing up for Google Maps API for Business. This is a paid service from Google that is used for customers with large user bases and heavy traffic. This should not be needed in most situations.
!! What if I already have a Latitude and Longitude for my records?
In that case you don't need our script to geocode them. Just do three things:
1. You'll still create a field called "gm_GeoLocation" field and give it an object name of "field_geoLocation". (See step 5 "Add Geo Code Lookup To Your File" in our [[integration]] instrucions.)
2. Make sure your Lat/Long is in the form Map expects, like: "47.6821060,-122.3085170" without the quotes.
3. Turn off the geocoding script by editing the script "GeoCodeAddress (address, tempObjectName, resultFieldName)" and placing an ExitScript step as the first line. Also disable the script "Check Property Integrity" the same way and now it's up to you to make sure you have a Lat/Long for every record =)
!! What if I already have a Latitude and Longitude for my records?
In that case you don't need our script to geocode them. Just do three things:
1. You'll still create a field called "gm_GeoLocation" field and give it an object name of "field_geoLocation". (See step 5 "Add Geo Code Lookup To Your File" in our [[integration]] instrucions.)
2. Make sure your Lat/Long is in the form Map expects, like: "47.6821060,-122.3085170" without the quotes.
3. Turn off the geocoding script by editing the script "GeoCodeAddress (address, tempObjectName, resultFieldName)" and placing an ExitScript step as the first line. Also disable the script "Check Property Integrity" the same way and now it's up to you to make sure you have a Lat/Long for every record =)
Changed lines 15-16 from:
Be sure you give your copy of the "gm_GeoLocation" field an object name of "field_geoLocation" so our script can properly reference that field.
to:
-> Be sure you give your copy of the "gm_GeoLocation" field an object name of "field_geoLocation" so our script can properly reference that field. For more, see step 5 (Add Geo Code Lookup To Your File) in our [[integration]] instructions.
Added lines 15-16:
Be sure you give your copy of the "gm_GeoLocation" field an object name of "field_geoLocation" so our script can properly reference that field.
Changed line 23 from:
Please note: The Google geocoding service is limited to 2500 geocode requests per day from your device. You can increase this limit by signing up for Google Maps API for Business. This is a paid service from Google that is used for customers with large user bases and heavy traffic. This should not be needed in most situations.
to:
Please note: The Google geocoding service is limited to 2500 geocode requests per day from your device. You can increase this limit by signing up for Google Maps API for Business. This is a paid service from Google that is used for customers with large user bases and heavy traffic. This should not be needed in most situations.
Changed lines 11-12 from:
We start on the hosted file, when events are created or edited.
to:
We start on the hosted file, when events are created or edited...
Changed lines 15-16 from:
Then we do it on the mobile file if we have to.
to:
Then we do it on the mobile file if we have to...
Changed line 21 from:
to:
Please note: The Google geocoding service is limited to 2500 geocode requests per day from your device. You can increase this limit by signing up for Google Maps API for Business. This is a paid service from Google that is used for customers with large user bases and heavy traffic. This should not be needed in most situations.
Changed lines 3-4 from:
to:
Nope. GoMaps will do it for you.
!! What the heck is a geocode?
Under the hood, Google Maps uses Lat/Long for plotting addresses, so GoMaps converts your addresses into Lat/Long. This process is called geocoding. GoMaps uses the Google Maps geocoding API: [[https://developers.google.com/maps/documentation/geocoding/ | https://developers.google.com/maps/documentation/geocoding/]]
!! What the heck is a geocode?
Under the hood, Google Maps uses Lat/Long for plotting addresses, so GoMaps converts your addresses into Lat/Long. This process is called geocoding. GoMaps uses the Google Maps geocoding API: [[https://developers.google.com/maps/documentation/geocoding/ | https://developers.google.com/maps/documentation/geocoding/]]
Changed lines 11-15 from:
!! What the heck is a geocode?
Under the hood, Google Maps uses Lat/Long for plotting addresses
to:
We start on the hosted file, when events are created or edited.
-> This is done in the script "GeoCodeAddress (address, tempObjectName, resultFieldName)" which is currently called from script triggers on the address fields in GoMapsHosted. You can do the same in your file, or periodically run the script "Re-GeoCode All Properties", perhaps from a server-side script.
Then we do it on the mobile file if we have to.
-> Every time we compile the map using the script "Compile Map Data And Settings" we check to see if the event has been geocoded as part of the script "Check Property Integrity". So if something goes wrong on your hosted file, we'll try and correct the geocoding. This "Compile Map Data And Settings" script runs as part of the sync, which is one reason we like to run GoMaps synced instead of live. (This is also the script run from the buttons at the bottom of the "setup" layouts in GoMaps.)
-> We'll also re-geocode an address if you've edited the record, as part of the script "Property On Record Commit", which we have running on commit as part of the layout level script triggers.
-> This is done in the script "GeoCodeAddress (address, tempObjectName, resultFieldName)" which is currently called from script triggers on the address fields in GoMapsHosted. You can do the same in your file, or periodically run the script "Re-GeoCode All Properties", perhaps from a server-side script.
Then we do it on the mobile file if we have to.
-> Every time we compile the map using the script "Compile Map Data And Settings" we check to see if the event has been geocoded as part of the script "Check Property Integrity". So if something goes wrong on your hosted file, we'll try and correct the geocoding. This "Compile Map Data And Settings" script runs as part of the sync, which is one reason we like to run GoMaps synced instead of live. (This is also the script run from the buttons at the bottom of the "setup" layouts in GoMaps.)
-> We'll also re-geocode an address if you've edited the record, as part of the script "Property On Record Commit", which we have running on commit as part of the layout level script triggers.
Added lines 1-11:
!! Do I have to GeoCode my addresses to use GoMaps?
No. GoMaps will do it for you.
!! When does GoMaps geocode my address
> > Good question
!! What the heck is a geocode?
Under the hood, Google Maps uses Lat/Long for plotting addresses, so GoMaps converts your addresses into Lat/Long. This process is called geocoding. GoMaps uses the Google Maps geocoding API: [[https://developers.google.com/maps/documentation/geocoding/ | https://developers.google.com/maps/documentation/geocoding/]]
No. GoMaps will do it for you.
!! When does GoMaps geocode my address
> > Good question
!! What the heck is a geocode?
Under the hood, Google Maps uses Lat/Long for plotting addresses, so GoMaps converts your addresses into Lat/Long. This process is called geocoding. GoMaps uses the Google Maps geocoding API: [[https://developers.google.com/maps/documentation/geocoding/ | https://developers.google.com/maps/documentation/geocoding/]]
