Add chronology relation preset #178
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced May 28, 2023
|
@danrademacher - is this our first non-Greeninfo/DevSeed PR?!? |
This was referenced Aug 18, 2023
This was referenced Mar 22, 2024
Merged
Open
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a Chronology preset for
chronologyrelations. As in #145, this comes with a mechanism for extending the standard set of presets and default presets that come with id-tagging-schema.I’ve also tweaked the ℹ️ button to look for documentation from OpenHistoricalMap-related data items on the OSM Wiki, not just OSM-related data items. The data item must have a sitelink to an article titled “Open Historical Map/Tags/Key/key” for keys, “Open Historical Map/Tags/Relation/Tag/key=value” for tag values, or “Open Historical Map/Tags/Relation/type” for relation types.
Fixes OpenHistoricalMap/issues#540.