-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add a Street schema to Physical Address eXchange Schema Standard #254
Comments
Here is the proposed definition of the Street Schema. It includes spoken versions of the street and locality in .wav format. If this proposal is acceptable, streetNamePhonetic and localityNamePhonetic can be taken out of the civic address schema.
|
Here is the proposed Locality Schema:
There should be one record for every locality with civic addresses. This schema would be used for place name data coming from the toponomy authority (e.g., BCGNIS), not from the address authority. |
In the PAX schema, streetNamePhonetic is a fact about a Street. Do we need a separate street schema to provide the proper home for this field? localityNamePhonetic is a fact about a locality so is best left as a proposed addition to BCGNIS.
A street schema can also be used to validate street fields in the new-civic-addresses file. For example, let's say the Salmon Arm address authority provides the following street records:
If they also provide the following civic addresses:
this address will be rejected by the geocoder data integration process because there is no 10 Ave N in Salmon Arm according to their street schema.
The street schema can also be used to validate streets in submitted road segment files . This allows for checking for mispelled streetNames between blocks of a street in the same locality, and unknown streetTypes, streetDirections, and streetQualifiers
The text was updated successfully, but these errors were encountered: