search

maphew / arcmapbook

Automatically exported from code.google.com/p/arcmapbook
Other
3 stars 2 forks source link

Local Indicator #87

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create Mapbook Series
2. Add Local Indicator to Layout View
3. Click on Interior Section number (any Section or Quarter Section # 8-
11,14-17,20-23,26-29) - Looks ok, section is shaded where it needs to be 
and shows the whole Township surrounding
4. Click on an Exterior Section number (1-7, 12-13, 18-19, 30-36) - Does 
not look ok, section is shaded but sits in center of view with too many 
sections outside of township surrounding it.

What is the expected output? - Hoped for each section to display where it 
sits within a single township.
What do you see instead? - too much space surrounding exterior sections of 
single township.

What version of the product are you using? - Mapbook for ArcMap 9.3 R 2009 
Feb 11
On what operating system? XP

Please provide any additional information below.
- Attached is our dataset that we are using for this project. We use the 
Maptile field for creating the Map Series. I have added the screenshots I 
had posted on the ESRI Forums. I received a reply Matt Wilkie. This is for 
you Matt! :) Thanks!!!

Original issue reported on code.google.com by lochhav...@aol.com on 27 May 2010 at 12:22

Attachments:

GoogleCodeExporter commented 9 years ago 
Please reply to bconces@kcgov.us, not the betty@ytabizcom.com
Thanks!

Original comment by lochhav...@aol.com on 27 May 2010 at 12:23

GoogleCodeExporter commented 9 years ago 
Hi Betty, the first issue is that the MapTile feature class does not have a
projection associated with it
(http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=Identifying_an_un
known_coordinate_system).

I need help interpreting your dataset. What are the "Interior Section" and 
"Exterior
Section" numbers you refer to? I don't see any attributes containing numbers 
other
than MapScale and Scale. Perhaps upload your map composition also (the .mxd).

A bigger issue is that MapTile consists of nested polygons: squares inside 
squares,
and yet more squares inside those squares. Do you really want to create of 
mapbook
with more than 7,300 pages? That's the result using this index as is. What I 
think
you need to do is create a new index layer using the appropriate nesting level.

In the attached example I used the Dissolve tool to merge all polygons with a 
common
TR value, deleted the one remaining polygon with a null TR, then calculated TR 
to
equal TR & ObjectID (a quick & dirty method to guarantee unique values).

Original comment by map...@gmail.com on 27 May 2010 at 4:53

Attachments:

GoogleCodeExporter commented 9 years ago 
Interpreting the dataset: In the layout view, we use the Mapbook to select our 
area 
for creating maps and it is by section or quarter section. The Mapbook is built 
off 
of the 'Maptile' field in the KC_Maptile dataset. When you see the township 
grid on 
our template in the layout view, you will see sections 1 thru 36. Any 'Maptile' 
that 
hits the edge of the township boundaries (exterior sections) will center in 
that 
grid. Any 'Maptile' that does not hit the edge of the township boundary will 
place 
correctly (not exactly but correctly)within our grid (which has the Local 
Indicator 
data view over it). If you open KC_Mapping.mxd, it should open with the layout 
view 
acctive and zoomed into the grid I spoke of. Any Maptile starting with 50N04W 
will 
include our parcels. If you select the Mapbook tab and scroll down to 50N04W18 
you 
will see the difference between Sections 17 & 18 (an interior & exterior 
section). I 
hope this helps you understand what we're trying to do. I truly appreciate your 
time 
with this! ~betty P.S. I did not include the the KC_Maptile because I sent that 
to 
you yesterday and this file was getting rather large.

Original comment by lochhav...@aol.com on 1 Jun 2010 at 8:38

Attachments:

GoogleCodeExporter commented 9 years ago 
I begin to see your problem more clearly. In the local indicator area of the 
page,
the grid of squares numbered 1-36 are just "dumb graphics", meaning they have no
attributes which tell them where they are in the world. They're stuck in 
page-space,
only knowing "I'm 3.7 inches leftwards and 13.8 inches high from the bottom 
left of
the page".

Underneath the 36grid is the Local Indicator data frame. It *does* have 
intelligence.
The frame knows where it is in page-space (3.7",13.8" from bottom left) AND in 
the
world (2,537,600m west & 2,191,649m north of projection origin; called the 
Spatial
Reference System [SRS]). 

When the viewpoint inside the data frame changes, moving from one quarter 
section to
another, the SRS coordinates change while the page coordinates do not. 
Therefore as
far as the 36grid graphics are concerned nothing has changed and it stays put.

Imagine you're in a space shuttle orbiting the earth, watching the scene below
through a porthole. With a grease pencil draw a grid on the glass and number the
tiles. Relative to you the grid stays put and the landscape beneath forever 
changes.
If you want tile#17 to refer to a quarter section in Kootenai County, Idaho you 
need
to figure out how to extend your grease pencil through the porthole and draw on 
the
ground. Thankfully we have computers for this job. ;)    This is an exercise I 
don't
have time to describe. The general outline is: Create or obtain a feature class 
of
the quarter sections (the grid of tiles 1-36) and put them *inside* your Local
Indicator dataframe. 

Another suggestion: if you're only interested in Maptiles starting with 50N04W,
create a new feature class of only those entities (Select > by attributes; 
Create
layer from selected features; Export to new FC).

Original comment by map...@gmail.com on 2 Jun 2010 at 5:24

GoogleCodeExporter commented 9 years ago 
Matt, thank you.  Your  effort in addressing the questions we have posed to 
this point is much appreciated.  If you would please consider one more 
submission regarding the circumstances we are trying to communicate, then we 
will be done.  Yes, the grid is a dumb graphic and the Local Indicator is a 
data frame above/below the dumb graphic.  According to your analogy I am 
sitting in my office chair on the space shuttle, looking at our map-Layout View 
which has a data frame that is the glass portal.  I have a ‘dumb’ 36 
section grid graphic on my map layout in the local indicator area.  I add my 
MapTile dataset containing 144 records (4 townships containing 36 records each- 
one record for each section [1-36] in each township).  I build a Map Book 
specifying the MapTile dataset and specifying a field in the data called 
Maptile that contains a unique string comprised of the township, range, and 
section numbers for each record.  Thus, each of the 144 records is unique in 
name as well as being a polygon in its proper spatial location in the county.  
I then click the tool button ‘Add Identifier Frame’ and select ‘Local’ 
to create a Local Indicator data frame above the ‘dumb’ 36 section grid 
graphic.  When I choose from the MapBook the page named 50N04W16 the map data 
view brings up Section 16 in 50N04W and the local indicator data frame 
correctly depicts the boundary of section 16 above the ‘dumb’ grid space 
for Section 16.  All is well.  When I choose Mapbook page 51N05W22 (different 
township/range and section) the map data view brings up Section 22 in 51N05W 
and the local indicator data frame correctly depicts the boundary of Section 22 
above the ‘dumb’ grid space for Section 22.  All is well.  But if I choose 
any page in the MapBook pertaining to Sections 1 thru 7, 12,13,18,19,24,25,30 
thru 36 (township border sections) in any of the Townships, the 
‘intelligent’ local indicator data frame fails to depict the boundary of 
the chosen section above the correct ‘dumb’ grid space graphic for the 
section.  The scale of the section polygons within the local indicator data 
frame on the map layout view appear to change and their positioning shifts – 
as though the space shuttle instantly went from an ordinary orbit of around 200 
miles above the Earth to an orbit 800 miles above the Earth!  The Earth 
hasn’t changed position and the position of both the ‘dumb’ graphic grid 
the local indicator data frame is unchanged in the map layout view.

Items to be included: 
KC_Data1.zip:   Stripped down geodatabase containing Section Map only records in 
50N05W,51N04W,51N05W.
See second comment for KC_Data2.zip: Stripped down geodatabase containing 
Section Map only records in 50N04W and KC_Mapping.mxd containing MapBook built 
using item #1 and the subject area taxparcels.

Original comment by lochhav...@aol.com on 8 Jun 2010 at 5:17

Attachments:

GoogleCodeExporter commented 9 years ago 
KC_Data2.zip: Stripped down geodatabase containing Section Map only records in 
50N04W and KC_Mapping.mxd containing MapBook built using item #1 and the 
subject area taxparcels.

Thanks again Matt! We sincerely appreciate your time.
~betty

Original comment by lochhav...@aol.com on 8 Jun 2010 at 5:18

Attachments: