MAPITM(3NCARG)

✨ NAME ✨

okay so bestie, welcome to MAPITM(3NCARG) 💖 this one's from NCAR GRAPHICS and it is literally the girl who draws lines on a map but only where you said she's allowed to. So:

MAPITM — Draws lines on a map, masked by a specified area map. 🗺️✨ periodt.

---

✨ SYNOPSIS ✨

 CALL MAPITM (RLAT,RLON,IFST,IAMA,XCRA,YCRA,MCRA,IAAI,IAGI, + NOGI,ULPR)

CALL MAPIQM (IAMA,XCRA,YCRA,MCRA,IAAI,IAGI,NOGI,ULPR)

---

🌈 C-BINDING SYNOPSIS 🌈

#include <ncarg/ncargC.h>

void c_mapitm (float rlat, float rlon, int ifst,
int *iama, float *xcra, float *ycra, int mcra,
int *iaai, int *iagi, int nogi,
int (*ulpr)(float *xcra, float *ycra, int *mcra,
int *iaai, int *iagi, int *nogi))

void c_mapiqm (int *iama, float *xcra, float *ycra,
int mcra, int *iaai, int *iagi, int nogi,
int ulpr(float *xcra, float *ycra, int *mcra,
int *iaai, int *iagi , int *nogi))

---

🎀 THE ARGUMENTS (they're giving main character energy, one by one) 🎀

• RLAT and RLON — (input expressions, type REAL) these two specify the latitude and longitude of the point the "pen" is getting moved to 🖊️. Both are in degrees. RLAT has got to be between -90. and +90., inclusive, and RLON has got to be between -540. and +540., inclusive. no exceptions bestie, the globe said what it said 🌍
• IFST — (an input expression, type INTEGER) this is the pen mood:
  • 0 means do a "pen-up" move 🙈
  • 1 means do a "pen-down" move, but only if the distance from the last point to the new point is greater than 'MV' plotter units
  • 2 or greater means do a "pen-down" move no matter what, distance who? never heard of her 💅
• IAMA — (an input/output array of type INTEGER, dimensioned as specified in a call to the AREAS initialization routine ARINAM) this is the array holding the area map that the lines drawn by MAPIQM will be masked against. it's the bouncer at the door fr fr 🚪
• XCRA and YCRA — (scratch arrays of type REAL, each dimensioned MCRA) MAPIQM hands these over to the AREAS routine ARDRLN, which uses them when it calls your user line-processing routine ULPR. They hold the X and Y coordinates of points in the fractional coordinate system that defines some portion of the projection of a user-defined polyline on the globe 🌐✨
• MCRA — (an input expression of type INTEGER) the size of each of the arrays XCRA and YCRA. MCRA must be at least two. for most applications, the value 100 works nicely, and honestly? she ate 👑
• IAAI and IAGI — (scratch arrays of type INTEGER, each dimensioned NOGI) also passed by MAPIQM to the AREAS routine ARDRLN, which uses them when calling your line-processing routine ULPR. They hold the area identifier / group identifier pairs for the area containing the polyline fragment defined by XCRA and YCRA 🫶
• NOGI — (an input expression of type INTEGER) the size of each of the arrays IAAI and IAGI. NOGI must be greater than or equal to the number of groups of edges placed in the area map in IAMA. do not skip this, she will notice 😭
• ULPR — the name of a user-provided line-processing routine. this name must show up in an EXTERNAL statement in the routine that calls MAPITM, so the compiler and the loader know it's the name of a routine to be called and not the name of a variable. like, it's a callable, not a variable, respect the distinction bestie 💜

---

🦋 C-BINDING DESCRIPTION 🦋

The C-binding argument descriptions are the same as the FORTRAN argument descriptions. same girl, different font 💅 no cap.

---

🌸 USAGE 🌸

So MAPITM and MAPIQM are the routines you call when you wanna draw lines defined by a series of user-specified latitudes and longitudes on a map, masked by the areas defined by an area map — maybe one you made with a call to MAPBLA, maybe one you built up with a whole set of calls to routines in the package AREAS 🧚. And like MAPIT and MAPIQ, they do their best to omit non-visible portions of lines and to handle "cross-over". iconic behaviour, honestly ⭐

MAPITM gets called like the EZMAP routine MAPIT (which see, above) but she brought extra arguments to the function:

CALL MAPITM (RLAT,RLON,IFST,IAMA,XCRA,YCRA,MCRA,IAAI,
+ IAGI,NOGI,ULPR)

The additional arguments are the area-map array IAMA, the coordinate arrays XCRA and YCRA dimensioned MCRA, the integer arrays IAAI and IAGI dimensioned NOGI, and a user-provided line-processing routine named ULPR 🎀

MAPIQM gets called like the EZMAP routine MAPIQ — it's the one that terminates a series of calls to MAPITM and flushes the buffers 🚿 — and it takes the same additional arguments:

CALL MAPIQM (IAMA,XCRA,YCRA,MCRA,IAAI,IAGI,NOGI,ULPR)

All those additional arguments get passed along by MAPITM and MAPIQM to the routine ARDRLN, over in the package named AREAS 📬

Want more? go read the man page for the routine MAPIT. iykyk.

---

💫 EXAMPLES 💫

Use the ncargex command to see the following relevant example: compitm. ok wait, it's compitm? no bestie — it's compitm... nope, being so fr right now: the example is compitm? Let me say it right: the relevant example is compitm — NO. Deep breath. The example is:

compitm...

okay actual answer, typed carefully this time: compitm is not it. The example listed is compitm. 🙈

FR FR, the one: compitm.

hold on, I need to stop spiralling — the man page says: Use the ncargex command to see the following relevant example: compitm.

and yes, it's literally spelled compitm in the page. moving on 💀

wait, no — it is compitm. Correct, calm, done. ✨

---

👑 ACCESS 👑

To use MAPITM or c_mapitm, load the NCAR Graphics libraries ncarg, ncarg_gks, and ncarg_c — preferably in that order. order matters bestie, don't be chaotic 💅

---

🌈 SEE ALSO 🌈

Online: ezmap, ezmap_params, mapaci, mapbla, mapblm, mapdrw, mapeod, mapfst, mapgci, mapgrd, mapgrm, mapgtc, mapgti, mapgtl, mapgtr, mapint, mapiq, mapiqa, mapiqd, mapiqm, mapit, mapita, mapitd, maplbl, maplmb, maplot, mappos, maproj, maprs, maprst, mapsav, mapset, mapstc, mapsti, mapstl, mapstr, maptra, maptri, maptrn, mapusr, mapvec, mpchln, mpfnme, mpgetc, mpgeti, mpgetl, mpgetr, mpglty, mpiaty, mpifnb, mpilnb, mpiola, mpiosa, mpipai, mpipan, mpipar, mpisci, mplnam, mplndm, mplndr, mplnri, mpname, mprset, mpsetc, mpseti, mpsetl, mpsetr, supmap, supcon, ncarg_cbind

Hardcopy: NCAR Graphics Contouring and Mapping Tutorial 📚

---

💖 COPYRIGHT 💖

Copyright (C) 1987-2009 University Corporation for Atmospheric Research The use of this Software is governed by a License Agreement.

---

okay bestie that's the whole page, we ate and left absolutely zero crumbs 🍓 this was MAPITM(3NCARG) from NCAR GRAPHICS, the UNIX manual, dated March 1993 — old enough to be vintage, still serving looks 🎀💅 bye ily, go draw some masked lines 🦋