Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update attribution string for au/qld/statewide #7241

Merged
merged 3 commits into from
May 19, 2024

Conversation

andrewharvey
Copy link
Contributor

No description provided.

@data-please
Copy link

data-please bot commented May 19, 2024

@data-please
Copy link

data-please bot commented May 19, 2024

@iandees iandees merged commit a48d336 into openaddresses:master May 19, 2024
2 of 3 checks passed
"unit": "UNIT_NUMBER",
"layer": "QLD_LOCATION_ADDRESS",
"unit": [
"UNIT_TYPE",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's probably better to leave out the unit type, as the type is not as important and more likely to confuse data consumers. In a future OA schema it could go into its own field.

image

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "unit" is meant for sub-address stuff like this. We want to get "APT 1" or "SHED" in this field.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes but I'd just expect ["UNIT_NUMBER", "UNIT_SUFFIX"] here, otherwise data consumers need to parse out the unit type field and need to implement rules specific to each OA source since what these prefixes mean is specific to the source. For a map, you'd likely want to omit the prefix and label like "1A" but for a full postal address you'd want the prefix, eg. "Unit 1A", expanding the "U" into "Unit".

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's still useful to include UNIT_TYPE here, otherwise you can't tell the difference between "APT 1 A" and "U 1 A" or "VLLA 1 A". I agree that the data source's encoding/shortening in "UNIT_TYPE" isn't ideal, but it's still useful and important information to include in our output.

If we know what the encodings are via documentation, we could use a conform function to expand them, I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants