Add to your parse file somewher appropriate (eg footer)
Page ID is <MySource_PRINT id_name="global" var="assetid" />
This prints out the asset id on all pages 
go to System Configuration > Global Preferences >Protocol Templates and add "Page ID" with a value of ./?a=%%link%%
Now in the WYSIWYG users can select the Page ID protocol and simply type in the number of the page they need to link to (that they see on the front end), saves them navigating the java tree.
We also have a "Google Map Australia" protocol with a value of http://maps.google.com.au/maps?f=q&hl=en&geocode=&time=&date=&ttype=&q=%%link%%: select this and type in an address and voila! Google maps launches with the address.
Nifty.
I like this idea, but I think if you setup the link to point at a matrix asset, eg ./?a=<id of maps asset>&<address here> it should be easier to maintain.
If google changes their format for the url or you decide to change mapping service (or even implement your own) it would be a one off change, instead of having to search the site.
Having a redirect asset to google would also let you generate stats on how many people are linking to a map for x on your site.
The only downfall I can think of is that there is slightly more overhead and thus the link will take slightly longer to load.