You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only relying on the user's current location isn't too helpful if they aren't currently where they have their car or want to get fuel. Until maps are supported, being able to search by suburb or postcode will be very handy!
There are two main things to consider with this, getting the data and how to display it, here are some starting suggestions.
Getting the data
The dataset needs to contain not just all suburbs and their postcodes, also, their latitude and longitude as all our calculations come down to that, where two main options arise as I want to keep it mostly free of cost where possible.
Google Maps Geocoding API:Geocoding API overview | Google for Developers seems to be the normal approach others go, well documented, good coverage and for the realistic user load should stay within the free tier. There are other alternatives like https://www.mapbox.com/ but I'm keen to more explore the common Google API if this route is taken.
Matthew Proctor's Australian Suburb and Postcode Dataset:Australian Post Codes - Matthew Proctor is a fantastic resource made by @matthewproctor which is fairly up-to-date, is free and would allow experimentation with storing a large dataset and how to quickly retrieve values, likely utilising something like Redis.
Displaying the input and results
I'm thinking this could replace the home page main CTA with an input instead which, when selected, takes to the search page:
And then on the seach page, we already have these inputs which take up a good amount of space:
Desktop
Mobile
Perhaps we would make each input smaller on mobile or have an expand view, more experimentation would need to be done there.
The text was updated successfully, but these errors were encountered:
Only relying on the user's current location isn't too helpful if they aren't currently where they have their car or want to get fuel. Until maps are supported, being able to search by suburb or postcode will be very handy!
There are two main things to consider with this, getting the data and how to display it, here are some starting suggestions.
Getting the data
The dataset needs to contain not just all suburbs and their postcodes, also, their latitude and longitude as all our calculations come down to that, where two main options arise as I want to keep it mostly free of cost where possible.
Displaying the input and results
I'm thinking this could replace the home page main CTA with an input instead which, when selected, takes to the search page:
And then on the seach page, we already have these inputs which take up a good amount of space:
Desktop
![image](https://private-user-images.githubusercontent.com/19419349/296417646-bab9b0df-706f-44af-9666-fb0b7b3efde2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwMDAyNDksIm5iZiI6MTczODk5OTk0OSwicGF0aCI6Ii8xOTQxOTM0OS8yOTY0MTc2NDYtYmFiOWIwZGYtNzA2Zi00NGFmLTk2NjYtZmIwYjdiM2VmZGUyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA4VDA3MzIyOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNlZmEzMDNmN2ZiZDk1Y2E2OTIxOWRmMWMwZjRkZTIyMWFjNGYxYTgyMTYyZDM4MjdmMmUxNDJkYjNhZWFlYjMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ZuXN6cXvG_u0X_N42CW3GSDNOKUeVnEyn2h7DNcgGik)
Mobile
![image](https://private-user-images.githubusercontent.com/19419349/296417658-5fa8fc32-70fe-463f-8055-fbd8769580f1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwMDAyNDksIm5iZiI6MTczODk5OTk0OSwicGF0aCI6Ii8xOTQxOTM0OS8yOTY0MTc2NTgtNWZhOGZjMzItNzBmZS00NjNmLTgwNTUtZmJkODc2OTU4MGYxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA4VDA3MzIyOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBiYzU5ZWMzOTVjNmNhNTZkODlmYTk3Nzg5MWRiNmMxNmYwNWJjNjllZjViYjhjZDEzODJiOWM0ZWExNmZkOTQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.QiWvK1hcBhuvc31HiBPDe1yGRe-X5hg_2LCCXPADA7o)
Perhaps we would make each input smaller on mobile or have an expand view, more experimentation would need to be done there.
The text was updated successfully, but these errors were encountered: