Have integrated it into a new application as a sort of store locator with various locations. At the minute, as part of my DocumentType, I have a separate property for users to enter an address (purely for display and not tied to Terratype). This means when a user uses Terratype to define the map location they are entering/ searching for the address a second time.
Is there any way to access the full structured data returned by the Google Places Autocomplete - similar to the Terratype.Lookup property - so that I can format/ display this location data on the front end?
Great question. This functionality is on the road map, but not there yet.
[Boring text alert]
Reverse geocoding (The functionality you are asking for) has been asked for a few times, Google for example have very strict limits on how many you can do per day before charging lots of money.
Currently I'm writing an indexer and list view control for Terratype, this will allow for a future where Reversed Geocoded location could be searched for quickly, and the results displayed to both front-end and content editors in the back-end. You search for Texas and it would return all the Terratype maps located within Texas on a single combined map. But to keep the Reverse Geocoding free, I plan to allow use of Open Street Map, to enhance the capabilities. The database for Reverse Geocoding using OSM data is around 75gb.
All this code is taking time to write, and is likely to include elements that I will be charging for. So some elements will be free, other will cost money. My current idea is that a bog standard indexer will be free, but a faster load-balanced version will cost money, but the actual what will be and what won't be charged for is still in debate. The charging is really aimed at those that use Umbraco with 1000s of maps, so might never be relevant to you.
Structured location data
Hi Jonathan,
Loving the Terratype plugin!
Have integrated it into a new application as a sort of store locator with various locations. At the minute, as part of my DocumentType, I have a separate property for users to enter an address (purely for display and not tied to Terratype). This means when a user uses Terratype to define the map location they are entering/ searching for the address a second time.
Is there any way to access the full structured data returned by the Google Places Autocomplete - similar to the Terratype.Lookup property - so that I can format/ display this location data on the front end?
Thanks!
Hey Neil,
Great question. This functionality is on the road map, but not there yet.
[Boring text alert]
Reverse geocoding (The functionality you are asking for) has been asked for a few times, Google for example have very strict limits on how many you can do per day before charging lots of money.
Currently I'm writing an indexer and list view control for Terratype, this will allow for a future where Reversed Geocoded location could be searched for quickly, and the results displayed to both front-end and content editors in the back-end. You search for Texas and it would return all the Terratype maps located within Texas on a single combined map. But to keep the Reverse Geocoding free, I plan to allow use of Open Street Map, to enhance the capabilities. The database for Reverse Geocoding using OSM data is around 75gb.
All this code is taking time to write, and is likely to include elements that I will be charging for. So some elements will be free, other will cost money. My current idea is that a bog standard indexer will be free, but a faster load-balanced version will cost money, but the actual what will be and what won't be charged for is still in debate. The charging is really aimed at those that use Umbraco with 1000s of maps, so might never be relevant to you.
[End boring text alert]
tl;dr No you can't do this currently, sorry.
Cheers
Jonathan
Thanks for your prompt response Jonathan.
Knew this wasn't currently possible, was more to see if it was in the road map. Good to hear it is! :-)
Look forward to seeing what you produce on this front.
Thanks,
Neil
is working on a reply...