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

Historic Mountain View boundaries #33

Open
1ec5 opened this issue Sep 29, 2022 · 2 comments
Open

Historic Mountain View boundaries #33

1ec5 opened this issue Sep 29, 2022 · 2 comments

Comments

@1ec5
Copy link
Member

1ec5 commented Sep 29, 2022

The City of Mountain View maintains a GIS layer of annexation areas. This dataset is in the public domain as a work of a California government agency. Each area comes with two dates: the date on which the annexation ordinance was filed by the city, and the date on which it was enrolled into the county’s resolution book. For OpenHistoricalMap, we can create boundary relations based on these areas, similar to San José in #28, and tag them with one of the dates. Mountain View doesn’t border San José, so boundary conflation won’t be necessary just yet.

@1ec5
Copy link
Member Author

1ec5 commented May 23, 2024

@jeffreyameyer imported this dataset last August. However, some of the features need to be retagged. For example, way 199,589,446 has lots of junk tags autogenerated from ArcGIS. All the ways need to be converted into boundary relations with inner and outer rings and added to a chronology relation.

@jeffreyameyer
Copy link
Collaborator

Yes - some of those tags are junk (not sure why I left the ShapeST* - I can clean those up. Some of the other metadata may be useful. I'll do a quick cleanup.

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

No branches or pull requests

2 participants