From my buddies at the airport to this newsgroup, there is a lot of interest
in the Garming 396. No doubt it is a fine system with great features.

Why don't I hear anyone talking about the AnywhereMap WX, which seems to
have a roughly equivalent feature set for $800-$1,000 less up front cost?

Thoughts?

Anyone own (or borrow) an AnywhereMap WX and care to comment?

KB

In article >,
"Kyle Boatright" > wrote:

> From my buddies at the airport to this newsgroup, there is a lot of interest
> in the Garming 396. No doubt it is a fine system with great features.
>
> Why don't I hear anyone talking about the AnywhereMap WX, which seems to
> have a roughly equivalent feature set for $800-$1,000 less up front cost?
>
> Thoughts?
>
> Anyone own (or borrow) an AnywhereMap WX and care to comment?
>
> KB


I would recommend a Google search, but here's my quick opinion:

For weather display, AWM is decent but not complete. For navigation,
AWM is decent by not complete. For portability, reliability, and ease
of use, AWM is fair to poor.

The Garmin 396 isn't perfect (can't stand that horizontal screen
orientation), but its features are much more complete and very well
implemented. Garmin's support is also outstanding. AWM support was
always very responsive, but the end result was usually, "I don't know
when that bug will be fixed," or "We don't know anything about that
problem," even though AWM staff would specifically respond to posts
about the problem on their own forums. I don't think that I have ever
seen more over-promising and under-delivering in my life than from the
AWM folks.

AWM also does not include auto-route street mapping, marine
capabilities, or XM audio capabilities, if any of that matters to you.



JKG

I've owned AnywhereMap for about four years and am quite satisfied with
it. It's been reliable and the newest version is tight on all the most
important features. I do not currently have weather on it but would
like to add that soon.

Did you know that the 28-day update subscription on database changes is
only $95 per year for AnywhereMap? Nobody I know comes anywhere near
that. If I owned a Garmin or Lowrance, I might not be willing to pay
the three or four times that amount per year to keep the database up to
date.

Kyle Boatright wrote:
> From my buddies at the airport to this newsgroup, there is a lot of interest
> in the Garming 396. No doubt it is a fine system with great features.
>
> Why don't I hear anyone talking about the AnywhereMap WX, which seems to
> have a roughly equivalent feature set for $800-$1,000 less up front cost?
>
> Thoughts?
>
> Anyone own (or borrow) an AnywhereMap WX and care to comment?
>
> KB

In article . com>,
"Grumman 236" > wrote:
> Did you know that the 28-day update subscription on database changes is
> only $95 per year for AnywhereMap? Nobody I know comes anywhere near
> that. If I owned a Garmin or Lowrance, I might not be willing to pay


Ddid you know that the quality of the AWM database is poor compared with
the Jeppesen database that Garmin and Lowrance use?

You aren't saving money, you're simply paying less, and getting less.



JKG

Well the PocketFMS database update every don't know how often is free. To
be come a donor is US$60. This is about as good as it gets and it's a great
package. They don't have wx (yet).

I looked at the Anywhere product, but couldn't get a response from the
company to a couple of simple questions. The PFMS team get back right away.

YMMV,
Cheers,
Kevin

"Grumman 236" > wrote in message
oups.com...
> I've owned AnywhereMap for about four years and am quite satisfied with
> it. It's been reliable and the newest version is tight on all the most
> important features. I do not currently have weather on it but would
> like to add that soon.
>
> Did you know that the 28-day update subscription on database changes is
> only $95 per year for AnywhereMap? Nobody I know comes anywhere near
> that. If I owned a Garmin or Lowrance, I might not be willing to pay
> the three or four times that amount per year to keep the database up to
> date.
>
> Kyle Boatright wrote:
>> From my buddies at the airport to this newsgroup, there is a lot of
>> interest
>> in the Garming 396. No doubt it is a fine system with great features.
>>
>> Why don't I hear anyone talking about the AnywhereMap WX, which seems to
>> have a roughly equivalent feature set for $800-$1,000 less up front cost?
>>
>> Thoughts?
>>
>> Anyone own (or borrow) an AnywhereMap WX and care to comment?
>>
>> KB
>

Can you cite an example of erroneous or missing data, Jonathan? I'm
sure we'd all be very interested to see the validity of this claim
demonstrated!

=Jonathan Goodish wrote:
=Ddid you know that the quality of the AWM database is poor compared
with
= the Jeppesen database that Garmin and Lowrance use?
=
= You aren't saving money, you're simply paying less, and getting less.

In article . com>,
"Grumman 236" > wrote:

> Can you cite an example of erroneous or missing data, Jonathan? I'm
> sure we'd all be very interested to see the validity of this claim
> demonstrated!

Yes. Go to KPIT and look within 200 miles to find numerous airports
with missing or incorrect frequencies, runway information, incorrect
MEAs on airways, missing obstacles (used to be everything under 400AGL,
not sure whether they fixed this), and mislabeled roads. Need I go on?



JKG

Jonathan Goodish wrote:
> In article . com>,
> "Grumman 236" > wrote:
>
> > Can you cite an example of erroneous or missing data, Jonathan? I'm
> > sure we'd all be very interested to see the validity of this claim
> > demonstrated!
>
> Yes. Go to KPIT and look within 200 miles to find numerous airports
> with missing or incorrect frequencies, runway information, incorrect
> MEAs on airways, missing obstacles (used to be everything under 400AGL,
> not sure whether they fixed this), and mislabeled roads. Need I go on?
>
Yes, if you would be so kind as to list an airport, nav-aid, fix or
obstacle that is correct in the Jeppesen database and incorrect in
AnywhereMap's FAA database, it would help immensely!

Grumman,

> Yes, if you would be so kind as to list an airport, nav-aid, fix or
> obstacle that is correct in the Jeppesen database and incorrect in
> AnywhereMap's FAA database, it would help immensely!
>

Oh, you want facts? ;-)

--
Thomas Borchert (EDDH)

I've had the AWM system for 2-3 years with Wx. There have been some
problems with software, and I consider Control Vision to be somewhat
sloppy, although in their defence I recognize the difficulty of making
all their features work with the big variety of PDAs that people use.

They have many extended features (gliding range circles to passing
airports) but most of the fancy stuff is just that to me - I don't
really need the built-in logbook, for example.

I do like having a single PDA that I can use both for flying and other
purposes.

On the other hand, my experience with Garmin has been that the
equipment is much more reliable.

I made a recent IFR trip in rain and found the Wx display on the Ipaq
to be accurate and wonderfully helpful.

In article . com>,
"Grumman 236" > wrote:
> > Yes. Go to KPIT and look within 200 miles to find numerous airports
> > with missing or incorrect frequencies, runway information, incorrect
> > MEAs on airways, missing obstacles (used to be everything under 400AGL,
> > not sure whether they fixed this), and mislabeled roads. Need I go on?
> >
> Yes, if you would be so kind as to list an airport, nav-aid, fix or
> obstacle that is correct in the Jeppesen database and incorrect in
> AnywhereMap's FAA database, it would help immensely!

You'll have to do your own legwork on this since I no longer own my AWM
system. Look, you'll find them. And, by the way, Control Vision has
NEVER to my knowledge disputed the poor data. I believe that CV and
Jepp get their data from the same source (government), but Jepp corrects
it and CV does not. CV has had plans for quite a while to start
correcting the data, but it hasn't happened yet. It's just one of their
many promises on which they have not delivered.



JKG

In article >,
Thomas Borchert > wrote:

> Grumman,
>
> > Yes, if you would be so kind as to list an airport, nav-aid, fix or
> > obstacle that is correct in the Jeppesen database and incorrect in
> > AnywhereMap's FAA database, it would help immensely!
> >
>
> Oh, you want facts? ;-)

Which I graciously provided, thank you.


JKG

I've actually done quite a bit of legwork (wing-work?) with AnywhereMap
and found their aviation data to be quite reliable, accurate and
complete. It served me well getting to 1S0 (Pierce County Airport, WA)
when the Jeppesen Data (September 2005 edition - $545 per year
subscription) in my Northstar panel mount was missing that airport.

Your aspersions would have credibility if you could cite at least one
specific example that could be verified...

Jonathan Goodish wrote:
> In article . com>,
> "Grumman 236" > wrote:
> > > Yes. Go to KPIT and look within 200 miles to find numerous airports
> > > with missing or incorrect frequencies, runway information, incorrect
> > > MEAs on airways, missing obstacles (used to be everything under 400AGL,
> > > not sure whether they fixed this), and mislabeled roads. Need I go on?
> > >
> > Yes, if you would be so kind as to list an airport, nav-aid, fix or
> > obstacle that is correct in the Jeppesen database and incorrect in
> > AnywhereMap's FAA database, it would help immensely!
>
> You'll have to do your own legwork on this since I no longer own my AWM
> system. Look, you'll find them. And, by the way, Control Vision has
> NEVER to my knowledge disputed the poor data. I believe that CV and
> Jepp get their data from the same source (government), but Jepp corrects
> it and CV does not. CV has had plans for quite a while to start
> correcting the data, but it hasn't happened yet. It's just one of their
> many promises on which they have not delivered.
>
>
>
> JKG

In article . com>,
"Grumman 236" > wrote:
> I've actually done quite a bit of legwork (wing-work?) with AnywhereMap
> and found their aviation data to be quite reliable, accurate and
> complete. It served me well getting to 1S0 (Pierce County Airport, WA)
> when the Jeppesen Data (September 2005 edition - $545 per year
> subscription) in my Northstar panel mount was missing that airport.
>
> Your aspersions would have credibility if you could cite at least one
> specific example that could be verified...

I already pointed you in the right direction, but if you don't believe
me, Google for the many others who have noticed the same problems.
Better yet, do a search on the AWM forums (now closed to the public).
It didn't take me 15 minutes with AWM and a low-altitude chart and
Detroit sectional to find several errors within close proximity to KPIT.
I would be happy to point out more specifics (one that I remember was
incorrect runways at KWAY), but I sold my AWM system, so I can't look.

I'm not sure why your Jepp data didn't have that airport, unless it
wasn't up to date or the field is a private airport. I don't believe
that Jepp data contains private airports.



JKG

AnywhereMap info for KWAY shows runway 08/26 at 3,500'X75' Left traffic
and 1,065' elevation. 082-degrees magnetic heading.

Airnav shows the runways as 09/27 and NACO shows a helicopter GPS090
approach.

This substantiates your claim that AnywhereMap data is incorrect. Does
anyone have a current Jepp database handy and can confirm that it shows
the correct runways for KWAY?

Jonathan Goodish wrote:
> In article . com>,
> "Grumman 236" > wrote:
> > I've actually done quite a bit of legwork (wing-work?) with AnywhereMap
> > and found their aviation data to be quite reliable, accurate and
> > complete. It served me well getting to 1S0 (Pierce County Airport, WA)
> > when the Jeppesen Data (September 2005 edition - $545 per year
> > subscription) in my Northstar panel mount was missing that airport.
> >
> > Your aspersions would have credibility if you could cite at least one
> > specific example that could be verified...
>
> I already pointed you in the right direction, but if you don't believe
> me, Google for the many others who have noticed the same problems.
> Better yet, do a search on the AWM forums (now closed to the public).
> It didn't take me 15 minutes with AWM and a low-altitude chart and
> Detroit sectional to find several errors within close proximity to KPIT.
> I would be happy to point out more specifics (one that I remember was
> incorrect runways at KWAY), but I sold my AWM system, so I can't look.
>
> I'm not sure why your Jepp data didn't have that airport, unless it
> wasn't up to date or the field is a private airport. I don't believe
> that Jepp data contains private airports.
>
>
>
> JKG

My 296 shows runways 09-27 alt 1070' and a GPS90 approach if that helps

Grumman 236 wrote:
> AnywhereMap info for KWAY shows runway 08/26 at 3,500'X75' Left traffic
> and 1,065' elevation. 082-degrees magnetic heading.
>
> Airnav shows the runways as 09/27 and NACO shows a helicopter GPS090
> approach.
>
> This substantiates your claim that AnywhereMap data is incorrect. Does
> anyone have a current Jepp database handy and can confirm that it shows
> the correct runways for KWAY?
>
> Jonathan Goodish wrote:
>
>>In article . com>,
>> "Grumman 236" > wrote:
>>
>>>I've actually done quite a bit of legwork (wing-work?) with AnywhereMap
>>>and found their aviation data to be quite reliable, accurate and
>>>complete. It served me well getting to 1S0 (Pierce County Airport, WA)
>>>when the Jeppesen Data (September 2005 edition - $545 per year
>>>subscription) in my Northstar panel mount was missing that airport.
>>>
>>>Your aspersions would have credibility if you could cite at least one
>>>specific example that could be verified...
>>
>>I already pointed you in the right direction, but if you don't believe
>>me, Google for the many others who have noticed the same problems.
>>Better yet, do a search on the AWM forums (now closed to the public).
>>It didn't take me 15 minutes with AWM and a low-altitude chart and
>>Detroit sectional to find several errors within close proximity to KPIT.
>>I would be happy to point out more specifics (one that I remember was
>>incorrect runways at KWAY), but I sold my AWM system, so I can't look.
>>
>>I'm not sure why your Jepp data didn't have that airport, unless it
>>wasn't up to date or the field is a private airport. I don't believe
>>that Jepp data contains private airports.
>>
>>
>>
>>JKG
>
>

Grumman 236 wrote:
> AnywhereMap info for KWAY shows runway 08/26 at 3,500'X75' Left traffic
> and 1,065' elevation. 082-degrees magnetic heading.
>
> Airnav shows the runways as 09/27 and NACO shows a helicopter GPS090
> approach.
>
> This substantiates your claim that AnywhereMap data is incorrect. Does
> anyone have a current Jepp database handy and can confirm that it shows
> the correct runways for KWAY?

Can't verify Jepp, but the FAA's ATA100 files with an effective date of 08/03
confirm runway 09/27, 3500x75, left traffic and elevation 1065.

The runway magnetic alignment data is blank, as are the fields for lat/lon of
the runway ends (from which the alignment could be calculated).

Pretty sure the ATA100 files are the source documents for airnav.com, currently
displaying the 06/08 effective date version.

Dave

In a previous article, "Grumman 236" > said:
>AnywhereMap info for KWAY shows runway 08/26 at 3,500'X75' Left traffic
>and 1,065' elevation. 082-degrees magnetic heading.
>
>Airnav shows the runways as 09/27 and NACO shows a helicopter GPS090
>approach.

My FAA data has the runway as 9/27, but my DAFIF data has it as 8/26. I
guess that shows where AnywhereMap is getting their data. In my
experience, DAFIF data is not as good as FAA data, but it's the only
solution for outside the US if you don't want to pay Jeppesen fees.

--
Paul Tomblin > http://xcski.com/blogs/pt/
Compared to system administration, being cursed forever is a step up.
-- Paul Tomko

In article . com>,
"Grumman 236" > wrote:
> AnywhereMap info for KWAY shows runway 08/26 at 3,500'X75' Left traffic
> and 1,065' elevation. 082-degrees magnetic heading.
>
> Airnav shows the runways as 09/27 and NACO shows a helicopter GPS090
> approach.
>
> This substantiates your claim that AnywhereMap data is incorrect. Does
> anyone have a current Jepp database handy and can confirm that it shows
> the correct runways for KWAY?

The Jepp data has been correct for a while, as the runway numbering
change is a few years old. It was correct in the database of my Garmin
195 before I sold it (and the database wasn't up to date at the time.)

I wish that I could remember some of the MEA and frequency errors, as
I'm sure that they are still present as well. The Control Vision
explanation was that the data contained numerous errors, but that their
present database format did not permit them to correct the errors. I
know for a fact that the Control Vision forums had numerous reports of
errors all across the country during the time that I was an AWM user.
If you have access to the forums, you may want to search there for other
errors (and I may have posted some), assuming that CV hasn't purged
those threads.

CV promised to rework the database and make it changeable with v2.0 of
the software, which was supposed to be released in 2005. Still hasn't
happened. Even when they make the database changeable, someone will
have to change it--that takes labor, which equates to expense.



JKG