To be honest, Location Maps don't really get much use which means they don't get much development time/money allocated to them. It has been on the potential feature list for years but there are ALWAYS higher priority items for our development team.
Post
FollowReferencing manually trimmed maps in Locations
Your excellent manual trimming tool allows me to exclude private property from my field maps. Once trimmed, my map shows up correctly in both public and private views of the map. The one place that I can't see it is in the location map selector. That is, the map identity is correct, but the reference points to the untrimmed (or automatically trimmed) map. All I need is for that selector to reference the same manually trimmed map that you present to me and others elsewhere. This should be easy to do, and it would be of huge benefit for those of us who have neighbors who hate and fear drones and the pictures that they make. Please!
Please sign in to leave a comment.
4 comments
I get it. But it is very disappointing because it is literally the only way forward for me. Wildlife conservation has similar issues, way too much to do with completely insufficient resources. One of the biggest obstacles is that it takes a LONG time for many conservation efforts to show benefits. With your location map option, it's a snap to show layers of the same area, separated by time, that clearly show the gradual changes (improvements :-)) that are occurring. The first of these will be added to our village hall website in a week or two because they have a field without my "neighbor problem", therefore no manual trimming requirement. I have a half-dozen other fields that we would be adding to our East Keswick Wildlife Trust website but most of them do have the "neighbor problem." I just published our newsletter with an article showing the first increment of change since we acquired a new field. It is nicely trimmed and does not violate our neighbors' sense of privacy, but I cannot put that comparison on the website because I would violate that promise and print simply does not do the comparison justice.
The trimmed map has an objectGUID. I just need for the selector on the location map editing page to refer to that objectGUID. If I were working for you, I'd offer to do it on my coffee break. And yeah, I know that testing takes longer than that. I'd test it on my lunch break.
Please.
May I send you a copy of the newsletter? You're on page 5.
The trimmed map does not have an objectGUID. The untrimmed map does. And then the single map gets trimmed with an annotation. The source imagery is still present, it is just not being displayed. This is done with a third party library that does not support having multiple trim layers or boundary sources. This is why we haven't added it.
Thank you for that explanation, Zane. I'll look for another approach.