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

Feature/issue 384 52 revision #386

Closed
wants to merge 14 commits into from
Closed

Conversation

afsmythe
Copy link

@afsmythe afsmythe commented Aug 16, 2019

This PR references the following open Issues:
#351
#162
#377
#367

This is a first pass at the 5.2 revision. Comments and suggestions are welcomed and encouraged.

@afsmythe afsmythe requested a review from jdmgoogle August 16, 2019 19:09
id,name,address_line,directions,hours,photo_uri,hours_open_id,is_drop_box,is_early_voting,latitude,longitude,latlng_source
poll001,ALBERMARLE HIGH SCHOOL","2775 Hydraulic Rd Charlottesville, VA 22901,Use back door,7am-8pm,www.picture.com,ho001,false,true,38.0754627,78.5014875,Google Maps
id,name,address_line,structured_location_name,structured_line_1,structured_city,structured_state,structured_zip,directions,hours,photo_uri,hours_open_id,is_drop_box,is_early_voting,latitude,longitude,latlng_source
poll001,ALBERMARLE HIGH SCHOOL","2775 Hydraulic Rd Charlottesville, VA 22901,ALBERMARLE HIGH SCHOOL,2775 Hydraulic Rd,Charlottesville,VA,22901,Use back door,7am-8pm,www.picture.com,ho001,false,true,38.0754627,78.5014875,Google Maps
Copy link
Contributor

Choose a reason for hiding this comment

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

This doesn't seem to be a valid example. It has both address_line and the structured address. Plus I'm not sure what the quotations are doing here.

Copy link
Author

Choose a reason for hiding this comment

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

Will clean this up. It is a bad example.

@@ -67,6 +67,14 @@ are equal.
| | | | | **IncludesAllStreets** are true, this | |
| | | | | value is ignored. | |
+------------------------+---------------------------+--------------+--------------+------------------------------------------+------------------------------------------+
| house_number_prefix | ``xs:string`` | Optional | Single | Part of a street address. It may contain | If the field is not present of invalid, |
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd like to discuss these more before adding them.

@@ -57,6 +57,14 @@
| | | | | **IncludesAllStreets** are true, this | |
| | | | | value is ignored. | |
+----------------------+---------------------------+--------------+--------------+------------------------------------------+------------------------------------------+
| HouseNumberPrefix | ``xs:string`` | Optional | Single | Part of a street address. It may contain | If the field is not present of invalid, |
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here. We need guidance on what these mean before adding them. See my comments/requests on #162.

@@ -3,23 +3,6 @@ csv-header-name: lat_long
description: |-
The latitude and longitude of a polling location in `WGS 84`_ format. Both
latitude and longitude values are measured in decimal degrees.
post: |-
Copy link
Contributor

Choose a reason for hiding this comment

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

Why was this block removed?

Copy link
Author

@afsmythe afsmythe Sep 4, 2019

Choose a reason for hiding this comment

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

This PollingLocation XML example post was relocated from the lat_long.yaml to the polling_location.yaml file.

@@ -112,6 +112,22 @@ tags:
**StartHouseNumber**, the implementation should ignore the element containing
it.
type: xs:integer
- _name: HouseNumberPrefix
Copy link
Contributor

Choose a reason for hiding this comment

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

See other comments about needing to resolve issues around #162 before adding this to the spec.

@afsmythe afsmythe closed this Oct 23, 2019
@afsmythe afsmythe deleted the feature/issue-384-52-revision branch May 13, 2021 15:36
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.

2 participants