Open GoogleCodeExporter opened 9 years ago
Using points alone could be problematic as the resulting extent could be very
small. A work around would be buffering the points and using those buffers as
your
index layer. I would think any enhancement in this area would essentially work
off
a buffer of the points, whether temporary or permanent.
Original comment by jason.eb...@modot.mo.gov
on 24 Jul 2008 at 2:07
thanks for the pointer towards a possible solution Jason.
Original comment by map...@gmail.com
on 24 Jul 2008 at 3:48
I would also like this feature added - creating buffer polygons is not ideal
because
you end up with an additional, new polygon layer that you then need to maintain
and
keep synchronized with your point layer. It should be fairly easy to modify the
extension to handle points (and lines). The only difference would be for
points,
where you'd have to gray out the option to zoom to the extent of each feature,
and
force the user to choose either a single set scale or take a data-based scale
from
the attribute table. Lines wouldn't be any different from polygons. I am not
intimately familiar with the code (I've done a little bit of tinkering:
http://forums.esri.com/Thread.asp?c=93&f=989&t=64703&mc=410#611025 ) but I
imagine
there would only need to be a few changes.
Original comment by davidfki...@gmail.com
on 17 Jul 2009 at 2:41
Issue 59 has been merged into this issue.
Original comment by map...@gmail.com
on 6 Aug 2009 at 3:56
Original issue reported on code.google.com by
simon.ro...@gmail.com
on 4 Jul 2008 at 12:32