- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 181
django address Model Notes
- Consider allowing storage of short and long form of this as per geocoding response from google maps
- Consider allowing storage of neighborhood, which Mapbox can return
- Consider allowing storage of administrative area_level_x
As noted by @explody here, it may make sense for postal code or a model PostalCode with its own components to be fk'd from Address. For example, google maps treats postal_code as a component of address.
If you've already geocoded an address string into an Address object, you may want to avoid performing the same geocoding operation again on the same query string.
The raw field can be used as a comparison for this purpose, but it isn't clear that this is the intent. Ensure it is, and if so document the use case. Or offer derived_search_query
or similar that inbound geocoding requests can be compared to prior to processing / overwriting an Address and its related models unnecessarily.
#67 explains that doing so may cause the same country to be represented by multiple objects.
- If you set fields on Address and want to generate a new raw from them this assembles it
- This does not appear to be the correct way to declare a custom model field. Originally pointed out in #49.
Possibly blamed for problems migrating scaled django site Listen at 35:24