Conversation
add [ts] linkages
# Conflicts: # README.md
Merging this to the feature branch so we can look at it holistically, make edits and suggestions, and incorporate other related issues/PRs before we agree on the spec and merge to dev.
|
To do: Need to review the definitions and add to MDS schema. |
|
Added 5 examples and associated files. Each example has 2 files, one is the MDS JSON, and the other is the GeoJSON part of those files so that Github can make a preview of it in the browser. I pulled them all from a real world city, Louisville, KY because 1) we needed a real city, 2) all of these GIS files are documented and available online as open data here and here, 3) many different geography_types are represented in the available files, and 4) I am familiar with this city and these files. I'd like to add one more example file which is the location of Stops when it's available from the city online. |
|
I've added an example for 'stop' which uses Point instead of MultiPolygon. Are points allowed, or do all geographies have to be MultiPolygons? Points would seem to affect the ability for some policy actions and policy driven events if used. |
4 participants
Explain pull request
This PR is to see what changes between the Geography feature branch and the dev branch, and prepare it for merger once it's ready.
Is this a breaking change
Impacted Spec
agencypolicyproviderAdditional context
PR #499 is merged to a 'feature branch' in the MDS repo so we can see how it fits into the larger spec, allow the community and staff to do PRs against it, merge other related PRs into it, and see how it will fit into dev when it's ready with this PR.