wrote
It is an error in the design of the procedure. I have no way of knowing I can
"bust" the 2.5 DME altitude unless there is a procedural data note to tell me
that. Some Air Force guy's response on this forum hardly fills that bill!

But it does tell us what the intent of the procedure was.

A charting error occurs when NACO or Jeppesen does not correctly chart what is on
the source 8260-3 or -5. That is not the case here.

By that definition, I concur.

This is what the 8260.19C has to say about it,

(2) Where radar is the only method for procedure entry from the en route
environment, enter the following: "Chart planview note: RADAR REQUIRED."

The fact you can find a procedure that doesn't comply with that requirement only
speaks to the fact the feds do make mistakes.

Is that the ONLY time the note is added? I've seen an awful lot of
approaches where one could easily navigate to the IAF from the enroute
enviroment that were "RADAR REQUIRED" and I doubt they were all
errors. They tended to be approaches where an error on the part of
the pilot would cause him to penetrate airspace - in the case of the
VOR-B at LVJ, the airspace in question is the Class B surface area at
HOU, but I've seen it done for restricted areas as well.

Michael