MPLNAM(3NCARG)

πŸ“¦ version 6.6.2, in epel 9, fedora 43, fedora 44

πŸ’– MPLNAM β€” it's giving "read a map database, drop boundary lines into your area map" ✨

okay bestie, welcome to the NCAR GRAPHICS corner of the group chat, this one lives in section 3NCARG and it's literally called MPLNAM πŸ—ΊοΈ


🌸 NAME 🌸

MPLNAM β€” reads a specified EZMAP database and sends boundary lines from it to a specified area map. that's it, that's the whole vibe πŸ¦‹


✨ SYNOPSIS ✨

CALL MPLNAM (FLNM,ILVL,IAMA)

πŸŽ€ C-BINDING SYNOPSIS πŸŽ€

#include <ncarg/ncargC.h>

void c_mplnam (char *flnm, int ilvl, int *iama)

πŸ’… DESCRIPTION πŸ’…

  • FLNM β€” an input expression of type CHARACTER, and it's the name of the database you wanna use, periodt. here's the little hunt MPLNAM goes on: first it looks for the files of the database you named in the current working directory, and if they're not chillin' there, it goes looking in the NCAR Graphics database directory instead. the database that got created in 1998 and shipped as part of Version 4.1 of NCAR Graphics is named "Earth..1" 🫢
  • ILVL β€” an input expression of type INTEGER, and this is the level the database gets used at. the tea is:
    • value 1 β†’ only land/water boundaries 🌊
    • value 2 β†’ adds continental boundaries (like the one separating Africa from Eurasia, iconic honestly) 🌍
    • value 3 β†’ adds the boundaries of countries πŸ—Ύ
    • value 4 β†’ adds states πŸ“
    • (value 5 will eventually be used to add counties β€” not yet bestie, don't come for me)
  • IAMA β€” an input/output array of type INTEGER, and it's the area map array that the boundary lines get added to πŸ’–

πŸ¦‹ C-BINDING DESCRIPTION πŸ¦‹

the C-binding argument description is the same as the FORTRAN argument description. no notes, same energy, slay πŸ’…


πŸ”₯ USAGE πŸ”₯

calling MPLNAM adds boundary lines to the area map sitting in the array IAMA. now β€” important β€” that area map must have previously been initialized by calling the routine ARINAM, over in the package AREAS, with a statement like:

CALL ARINAM (IAMA,LAMA)

where LAMA is the length of the array IAMA. after that you can do all kinds of stuff with the area map; for example you could call the AREAS routine ARSCAM to draw a solid-filled map. cute right?? 🌈

one or two groups of boundary lines get added to the area map by a call to MPLNAM:

  • the first, having group identifier 'G1' (default value 1), consists of a perimeter (either rectangular or elliptical, depending on the value of the internal parameter 'EL') plus the set of projected boundary lines implied by your selection of a map database and level. and for certain projections, a limb line may also be included πŸ‘€
  • if the parameter 'VS' has a value greater than zero, the group 'G2' gets added to the area map; it consists of a copy of the perimeter and the limb line (if any) plus a set of vertical lines splitting the area inside the perimeter into 'VS' vertical strips. (by default, the value of 'VS' is 1.) the object of the group 'G2' is to split areas up, reducing the number of points required to define a typical area below the level at which some target hardware device begins to fail 😭 (this is more important when using MPLNAM than it was when using MAPBLA because the new database is at a higher resolution β€” glow up behaviour, fr fr)

the perimeter and the limb in the groups 'G1' and 'G2' have the following left and right area identifiers:

  • 0 β€” identifies the area inside the perimeter or limb
  • -1 β€” identifies the area outside the perimeter or limb

the vertical lines in the group 'G2' have left and right area identifiers of 0.

to set the values of 'G1', 'G2', and 'VS', call the EZMAP routine MAPSTI. to get the current values of 'G1', 'G2', and 'VS', call the EZMAP routine MAPGTI. see the man pages for MAPSTI and MAPGTI πŸ“š


πŸ’œ EXAMPLES πŸ’œ

use the ncargex command to see the following relevant examples: mpex11, tezmpb. go look, they ate πŸ’…


πŸ‘‘ ACCESS πŸ‘‘

to use MPLNAM or c_mplnam, load the NCAR Graphics libraries ncarg, ncarg_gks, and ncarg_c, preferably in that order. order matters bestie, don't play 🫢


🌈 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, mapitm, 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, mplndm, mplndr, mplnri, mpname, mprset, mpsetc, mpseti, mpsetl, mpsetr, supmap, supcon, ncarg_cbind β€” yes that's the whole list, we don't skip entries in this house πŸ’–


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

ok that's the whole page bestie, go forth and plot those boundaries πŸ—ΊοΈβœ¨ no cap, you're gonna eat

this was the UNIX flavour of the page, dated April 1998, and it's filed under MPLNAM(3NCARG) β€” mwah, bye πŸ’‹

πŸ“¦ where this page comes from