Re: [OSM-talk] [Tagging] README tag with editor support
I’ll add my thoughts here.. Imagery: The issue of outdated imagery is complicated because: 1. In iD we don't really know the date range that the imagery was taken (Bing is the exception not the rule, and we can get from their API only a range not a hard date) 2. It depends on what zoom the user happens to be looking at, not just the location. And the imagery changes constantly, and can depend on caching and CDN issues. So I don’t see a way for us to provide an automatic solution for this issue. Notes Tag: Yes, notes as a tag do sort of work right now. A user can draw an area (closed way with `area=yes`) around the place where the imagery is known to be outdated and add a `note` tag, and iD will show it in the sidebar if someone happens to hover or select the area. Notes are a bit problematic because they only appear in the language that the user created them in, and they can obviously be used for abuse. The idea of having some arbitrary user entered README text popup automatically as the user scrolls around in iD (possibly containing naughty ascii pictures) - this just isn’t going to happen. OSM Notes: You could use OSM notes to warn users about imagery issues, though we don’t currently show them in iD.. But we plan to add this eventually, and it might be a better way to solve this issue rather than using a tag. I like that OSM notes expire and can be marked as resolved. New Tag: Maybe we should define an actual tag for localized situations where you want to warn a future editor about something. Like a `warning=*`, tag that would go on the surrounding area. We could standardize on this so that e.g. `warning=imagery` could display a message (translated for the user) like “Imagery in this area may be outdated. Please do not make changes without local knowledge.” `note=*` could provide more detail, and you could delete the warning eventually after Bing is up to date. Thanks, Bryan On Jun 11, 2015, at 8:45 PM, Ian Sergeant inas66+...@gmail.com wrote: Perhaps a nice objective tag, rather than README text. If a feature is new, add a start_date tag. The editor can then have options.. 1, Alert the user if the start date is more recent than the layers currently displayed. 2. Visually indicate if the start_date is within a configurable recency (say, draw a halo around objects constructed in the past two years, or so). There is also some scope for automated analysis, rather than depend on free text. Ian. ___ Tagging mailing list tagg...@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] [Tagging] README tag with editor support
I like the idea. Editors show the message prominently the first time you touch the object. It doesn't have to be imagery, it can be various messages to subsequent mappers. pet, 12. lip 2015. 00:20 David dban...@internode.on.net je napisao: Formalising readme is a good and have editing tools display it. But i would like to see the readme tag used very selectively. It could contain far more data than the rest if the object's tag. Bad if people saw it like comments in source code. Perhaps more emphasis is needed on good manners when editing existing data too. David . Richard Welty rwe...@averillpark.net wrote: this is a summary of previous discussion on newbies talk-us we have an ongoing, persistent problem with armchair mappers correcting the map to match out of date aerial imagery. i just had to repair the map in Rensselaer, NY; the street named Broadway was reconfigured in late 2012, and bing imagery is out of date. a couple of months ago someone realigned my edits to match the out of date bing imagery. others can and have described similar situations. i have started using the unofficial tag README whenever i make edits that differ from current bing imagery; i usually place the date of the note in ISO format at the beginning of the text. for example, here is the note i placed on the road in Rensselaer: 2013-01-15 - reconfiguration of road not yet fully reflected in aerial imagery. do not conform this road to current imagery. this has mostly worked, but in this specific case the armchair mapper chose not to read the note, or read it and dismissed it. so i have two things in mind here: 1) formalize the README tag as a way to caution future mappers 2) request editor support, when someone goes to change a README tagged entity, it would be nice if editors would popup a dialog saying something along the lines of Warning: read the following before making any changes to this object README text follows other suggestions that have been made have included trying to make the dates on which imagery was collected more obvious, adding warnings when edits are newer than available imagery (or newer than the imagery layer currently being displayed), and pressing to get more current imagery into place. does anyone have any thoughts on how to approach this? richard -- rwe...@averillpark.net Averill Park Networking - GIS IT Consulting OpenStreetMap - PostgreSQL - Linux Java - Web Applications - Search ___ Tagging mailing list tagg...@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list tagg...@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] [Tagging] README tag with editor support
Perhaps a nice objective tag, rather than README text. If a feature is new, add a start_date tag. The editor can then have options.. 1, Alert the user if the start date is more recent than the layers currently displayed. 2. Visually indicate if the start_date is within a configurable recency (say, draw a halo around objects constructed in the past two years, or so). There is also some scope for automated analysis, rather than depend on free text. Ian. ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
