Geo-coding for new node-maps requires unnecessary assets
Description
At present, five assets are required before a node will be geo-coded and drawn on the node-map: address1, city, state, zip, country.
In the UK at least, most of this information is unnecessary - the 7-character postcode is sufficient to narrow the pin to within typically 100 metres of the expected destination - more than adequate for a country-wide map of hundreds of nodes!
Presently, this means I must fill the address1, state and city fields with a single period (image attached) in order that the field is non-empty, causing great wastage and unnecessary bulk in the provisioning requisition.
I recommend that the data required for geocoding should be reduced to 'zip + country.'
Acceptance / Success Criteria
None
Attachments
1
Lucidchart Diagrams
Activity
Show:
Benjamin Reed April 3, 2013 at 8:54 AM
Definitely a thinko in the address-string logic. It was basically never appending any data, if the address1 field was empty.
At present, five assets are required before a node will be geo-coded and drawn on the node-map: address1, city, state, zip, country.
In the UK at least, most of this information is unnecessary - the 7-character postcode is sufficient to narrow the pin to within typically 100 metres of the expected destination - more than adequate for a country-wide map of hundreds of nodes!
Presently, this means I must fill the address1, state and city fields with a single period (image attached) in order that the field is non-empty, causing great wastage and unnecessary bulk in the provisioning requisition.
I recommend that the data required for geocoding should be reduced to 'zip + country.'