Minh Nguyễn
Minh Nguyễn
> However, this is also a good opportunity to double-check whether the construction has already completed, since many of these tags were added years ago. Per https://github.com/Project-OSRM/osrm-backend/pull/4258#issuecomment-313906383, there are quite...
The [Silicon Valley POI import](https://maproulette.org/browse/projects/42122) currently hosts 59 challenges, divided by editor preset. Combining challenges further would make it difficult to communicate tagging instructions to mappers and increase the likelihood...
Thank you for clarifying the intended limits. Those limits would comfortably accommodate a project like the Silicon Valley POI import and similar projects at a county level. I agree that...
> You are right to call out that the popup / callout behavior needs to be addressed. Another way to do this is to not show properties in a callout...
Without either a task or challenge URL, individual participants in MapRoulette challenges can get called out for things that are already explained well in the task description, such as in...
> This results in wiki pages being trimmed when someone enters a non-supported character As a workaround, the user can invoke [this Scribunto module](https://wiki.openstreetmap.org/wiki/Module:Char) with Unicode codepoints. (So that others...
For the time being, I’ve customized [all the interface messages I could find](https://translatewiki.net/wiki/Special:Search/insource:WBREPONAME_intitle:en) to say “data items” instead of “OpenStreetMap Wiki”, but that only affects the English interface and I’m...
A more structured attribution syntax like the one described in https://github.com/mapbox/mapbox-gl-js/issues/1804#issuecomment-162717387 is being tracked in mapbox/tilejson-spec/issues/20.
It would also be great if objects could contain expressions. For example, the `collator` expression’s first argument is an object rather than an array. Historically, the iOS and macOS SDKs...
> the `"match"` expression in the style spec is specifically designed for this case. Ideally, I think we'd want `"match"` (the NSExpression representation of it) to be the most natural...