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

Refactor Northeastern Arizona boundaries #9

Closed
evansiroky opened this issue Mar 17, 2017 · 4 comments
Closed

Refactor Northeastern Arizona boundaries #9

evansiroky opened this issue Mar 17, 2017 · 4 comments

Comments

@evansiroky
Copy link
Owner

There's been a report at https://github.com/darkskyapp/tz-lookup/issues/7 that the town of Page, AZ is resolving to America/Denver when it should be America/Phoenix.

As of right now, it appears that the area around Page, AZ relies on data that was imported into OpenStreetMap from the efele.net shapefile. The shaded area is America/Phoenix.

screen shot 2017-03-17 at 9 43 09 am

I've read a few online articles here and there that suggest that Page, AZ and surrounding areas should be in America/Phoenix. So, I'm creating this issue to try and figure out the best way to draw the boundaries in Northeastern Arizona. Shown below are the current boundaries:

screen shot 2017-03-17 at 10 14 54 am

All of the shaded area is America/Phoenix and the unshaded is America/Denver. In OSM, the boundary appears to be an import of the efele.net shapefile outlining the boundary of the Navajo Nation enclaving the Hopi Reservation. Unfortunately, I'm not sure if an OSM relation exists for either the Navajo Nation or Hopi Reservation.

@jamesd8
Copy link

jamesd8 commented Oct 6, 2017

The problem appears to be an obsolete outline for the Navajo Nation. The land that Page, AZ is on used to be part of the reservation, but was transferred in a land exchange in 1957 as part of the Glen Canyon Dam project. See https://en.wikipedia.org/wiki/Page,_Arizona#History for details.

It is now just part of AZ and as such should be on the America/Phoenix time zone. I'm not 100%, but I believe the census has up-to-date shapefiles for the Native American reservations, so perhaps that would be a way to fix this.

@evansiroky
Copy link
Owner Author

I'm attaching a picture below to illustrate the issue with the current OSM data:

screen shot 2017-10-06 at 11 19 19 am

In this picture there are three lines to pay attention to and they are as follows:

  • Blue with white inner dashes: this is the efele.net timezone boundary that was imported. As you can see it is not very accurate.
  • Green with white inner dashes: this is the outline of the Glen Canyon Nation Recreation Area
  • White dashed line: This appears to be an import from TIGER of the city boundary for the City of Page.

Unfortunately, all of these lines don't share the same points and aren't all contiguous for the lengths needed to represent the full boundary of the Navajo Nation within Arizona. Furthermore, the relation and boundaries of the Navajo Nation are missing entirely from OSM. If someone could import that into OSM, that would be very helpful. Until then, I think the best solution would be to intersect the America/Phoenix polygon with the City of Page polygon and then also difference the America/Denver polygon with the City of Page polygon and call it good.

@keith-lafortune
Copy link

Commenting to echo what jamesd8 has written above. Any solution that places Page Municipal Airport (PGA) in the correct timezone would be most welcome. The geo point we have for PGA is LAT 36.9260833 and LONG -111.4483611.

Thanks in advance for your help.

@evansiroky
Copy link
Owner Author

This is the current OSM Boundary for Page:

screen shot 2017-10-06 at 11 52 44 am

Looks like the airport would be fully included.

pirxpilot added a commit to pirxpilot/tz-lookup that referenced this issue Jan 24, 2018
pirxpilot added a commit to pirxpilot/tz-lookup that referenced this issue Jan 25, 2018
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

No branches or pull requests

3 participants