
Google Maps Extractor
Pay $6.00 for 1,000 results

Google Maps Extractor
Pay $6.00 for 1,000 results
Extract data from hundreds of places fast. Scrape Google Maps by keyword, category, location, URLs & other filters. Get addresses, contact info, opening hours, popular times, prices, menus & more. Export scraped data, run the scraper via API, schedule and monitor runs, or integrate with other tools.
Some json fields and also categories are translated, what's the reason behind?
What's the reason of translating json fields names instead of using camel case convention, example here (Services disponibles, Accessibilité...):
1"additionalInfo": { 2 "Services disponibles": [ 3 { 4 "Services sur place": true 5 } 6 ], 7 "Accessibilité": [ 8 { 9 "Entrée accessible en fauteuil roulant": true 10 }, 11 { 12 "Parking accessible en fauteuil roulant": true 13 } 14 ] 15 }
Same for categories names (then how can I map categories from list here https://api.apify.com/v2/key-value-stores/epxZwNRgmnzzBpNJd/records/categories if they are translated in the response?)
1"categories": [ 2 "Mosquée", 3 "Site historique", 4 "Attraction touristique" 5 ]
Hi there!
Thank you for reaching out. The output reflects the data as it's provided by Google Maps API in the specified language and region. The Actor doesn't modify the field names or categories to maintain data integrity and accuracy as provided by Google Maps. This approach ensures that the extracted data closely matches what you would see on Google Maps in the local language and region.
For example, in the English output, you'll see fields like "Accessibility" with properties such as "Wheelchair accessible entrance". If you're seeing French terms like "Services disponibles" and "Accessibilité", it's because the search was performed in a French-speaking region or with French language settings.
If you need standardized field names across languages, you might need to post-process the data to convert it to a consistent format like camelCase.
As you mention, it can be challenging to map the translated categories. To get a standardized list, i’d suggest using the 'language' parameter: Set it to 'en' in your input to get categories in English, which will match the standard list. If you need results in multiple languages, you'll need to implement a post-processing step to map the translated categories to their English equivalents.
Hope this answers your questions!
Actor Metrics
5.2k monthly users
-
699 bookmarks
98% runs succeeded
2.9 days response time
Created in Feb 2024
Modified 5 hours ago