Hello,
finally i got two profiles working with JOSM, now i would like to know if there are some suggested plugins especially for OHM.
Also there might be some map-stypes that makes sense or presets (i found “historical objects”).
OpenHistoricalMap/JOSM - OpenStreetMap Wiki is kind of what i’m asking here with the additional config for utilsplugin2
In some time maybe the “OpenHistoricalMap date filter for JOSM” GitHub - OpenHistoricalMap/ohm-date-filter that i found through Make time filtering even easier in JOSM · Issue #771 · OpenHistoricalMap/issues · GitHub
Maybe there is more out there (in some Slack-Channel probably) and we can make a place to collect it.
1 Like
We desperately need some OHM-specific validator rules for JOSM. The good news is that some of them might be simple enough to implement in MapCSS without requiring programming skills:
opened 06:56PM - 17 Jan 25 UTC
josm
JOSM is a major source of mapping errors, in part because its users are unaware … that they’re following OpenStreetMap tagging standards rather than OHM tagging standards. For example, most of the 11,000 elements with malformed `start_date=*` and `end_date=*` tags were authored in JOSM. This sort of error can cause data consumers to choke: https://github.com/OpenHistoricalMap/issues/issues/144#issuecomment-681945615 OpenHistoricalMap/issues#944.
JOSM comes with standard validator rules that are appropriate for OSM but not OHM. We should publish an alternative set of [validator rules](https://josm.openstreetmap.de/wiki/Rules) that conform to OHM tagging standards. The custom validator rules we’ve implemented for iD can serve as a starting point. Here’s a running list of errors and warnings we should add, modify, or replace:
* [ ] Warn about a malformed `start_date=*` or `end_date=*`
* [ ] Warn about a malformed `start_date:edtf=*` or `end_date:edtf=*`
* [ ] Warn about a `start_date=*` or `end_date=*` that falls outside `start_date:edtf=*` or `end_date:edtf=*`, respectively
* [ ] Warn about an element’s end date preceding its start date
* [ ] Warn about the deprecated practice of appending a date range to `name=*`: #793
* [ ] Warn about an artificial feature missing `start_date=*`
* [ ] Warn about a date range that falls outside of the parent chronology relation’s date range
* [ ] Silence the warning about [`source:name=*` without `name=*`](https://github.com/JOSM/josm/blob/a8bd279219c55315d74f94b87499451135636131/resources/data/validator/combinations.mapcss#L57)
* [ ] Silence the [crossing ways](https://github.com/JOSM/josm/blob/a8bd279219c55315d74f94b87499451135636131/src/org/openstreetmap/josm/data/validation/tests/CrossingWays.java) warning if the ways don’t overlap temporally
A simple [MapCSS](https://josm.openstreetmap.de/wiki/Help/Validator/MapCSSTagChecker) stylesheet should be capable of implementing most rules about tags. However, more complex rules or rules related to geometry will require Java code, either as a plugin or as part of the core software (special-cased to only activate when editing OHM, if that’s possible).
/ref https://github.com/OpenHistoricalMap/issues/issues/684#issuecomment-2148221884
1 Like
I’m using the Admin Boundaries map paint when mapping boundaries. It has some pretty nice features, such as showing where a line is broken or ended. Also when you select a relation it shows the whole area filled.