Roy--
My objection was to the last sentence, as I made clear in my first post:
"Other methods typically take days if
not weeks and requires extensive user-involvement."
in the last quoted paragraph seems clearly false to me.
Why not simply remove that sentence and leave the package otherwise unchanged?
And yes, someone should be able to request a correction of an author.
More reasonable requests may be honored, slightly less reasonable
requests may be politely refused, and unreasonable requests may be
ignored, at the discretion of the author, of course.
Evidently we have a deep and abiding disagreement as to what
constitutes "reasonable" (possibly along several dimensions).
I certainly find you quoting me as having validated your package as an
unreasonable statement, and a gross misrepresentation. I did nothing
of the sort.
On Sun, Sep 13, 2009 at 3:43 PM, Roy Wada <[email protected]> wrote:
> Should someone be able to publicly request a correction in someone else's package
> when it clearly does not affect that person? Is there a gross scientific falsehood
> not consistent with good research? Have I caused an unconscionable loss or damages
> to someone as a result of my package? Did I steal codes out of someone's programs
> and misrepresented myself as the author?
>
> I am trying to understand Austin's position here.
>
> What it says in the help file is not important to me.
>
> If Austin thinks it will greatly improve the package, then I am open to a revision.
> He can post a revised version help file here or send it to me privately.
>
> The current version says the following:
>
> distmatch provides a fast and easy way to perform distance matching based
> on latitudes and longitudes. It mathces location identifiers, attributes,
> or distances from one to another. It also counts the number of
> neighboring locations within a given area, either in circles or bands of
> concentric circles.
>
> Outputs produced by distmatch are typically used in studies of geocoded
> data. These outputs can also be produced by non-Stata softwares such as
> ArcGIS and ArcView.
>
> distmatch implements haversine formula for distance. The default is in
> miles.
>
> Distance matching is computationally intensive. Observations of 3,000 may
> take several minutes to complete. Other methods typically take days if
> not weeks and requires extensive user-involvement.
>
> Roy
>
*
* For searches and help try:
* http://www.stata.com/help.cgi?search
* http://www.stata.com/support/statalist/faq
* http://www.ats.ucla.edu/stat/stata/
