elevated road poi

I don't believe the the Custom POI specification allows for elevation data.

I tested this in GeePeeEx Editor and you can add elevations to your POI.

I created two identical POI using the same coordinates, but one with 0 elevation and the other with 80ft elevation. Both POI were saved to a csv file and I confirmed the csv file showed an elavations column with the data. I then uploaded the POIs to my 750 and both were shown under Custom POIs.

It appears that it can be done. But I haven't tested them yet in a real-world situation.

I'll give that a shot. I haven't used the GeePeeEx Editor before so I made some files, hope they are wright.
>
Does the NUVI 760 know the elevation that it is at!

If you go to Tools, Where Am I, it shows elevation under your location.

If you are going to create POIs with elevation, remember that elevation means the height above sea level, and not the height above the ground. I live near the ocean so elevations in my area are 10-100 feet. If you live in Colorado, your elevation is something like 3,000 feet!

Thanks For the help.

I am going to try it out tomorow.
I set elevation at what I thought it might be. When get to the eleavated road I'll check for the right elevation.

Ok, I guess I should clarify what I meant. It might be possible to put the information in there, but I don't believe that the alerts function based upon this data.

Yes, they all do. Touch the vehicle pointer and the Where Am I screen that pops up will show the elevation.

I highly doubt that the routing and alerting engine pays any attention to this, though. I just can't think of any real world examples where a road that was E/W or N/S would have the lanes separated by a significant height and were directly one above the other so that the GPS would have to rely on elevation to know which one you were driving on. They obviously must exist, but not in such numbers to require programming to handle that situation.

Are you sure you can't set POI's on the far right or left side of the roadway so that they would only trigger for northbound vs southbound?

While the nuvi's know their elevation I am not sure if they would be that accurate. I have an E-trex Vista that uses a barometer to fix altitude. The advances in GPS might have made a sat fix more accurate though I will have to start checking that out.

I think that this is very interesting to play out. But my assumption is going to be that the height bubble to get an alert will be too great for you to see any difference.

Just like we found when making custom poi files, for them to alert you have to make the close to your route. Most of us make them near the road entrance instead of at the store to be safe.

If your nuvi really pays attention to elevation, I would bet that the margin of error is greater than 20 feet - may be more like a hundred or more.

Let us know what you find.

Daniel

This subject had me do a little investigation. In Los Angeles The Museum of Contemporary Art (MOCA) is located on S. Grand Ave. There is an upper and lower Grand Ave. and you have to get to them by different routes. If I look up the address with my 760 it only shows one S. Grand Ave. However with the map view of the area you can see two different streets, beside each other, even though they are above each other. So you can set a waypoint with different coordinates and it will route you to the correct coordinates. But because the coordinates would in reality be the same I am not sure how the gps would know which street you were on unless is was routing you to the waypoint. .BTW The gps reception might be compromised on lower Grand Ave

A peculiarity, while checking this I made a route from 1st and Grand Ave to MOCA, which is a little over a block down Grand Ave and MapSource made a route which was about 8 ½ blocks long… Grand Ave is not a one way street, but it is divided, so it seems as if the routing was trying to get you on the correct side of the street, which you couldn’t do without a U-turn…. It did continue the route to lower Grand Ave correctly.

You can - but I think this should probably be considered a readonly field (The unit records information here, but I'm not convinced that either it, or POILoader will make any use of it as input).

GeePeeEx's .csv output is not intended for input to POILoader (which only looks at the first four 'columns' and ignores headers).

You should save the data as .gpx for use with POILoader. (The .csv export is there to allow further data manipulations, using a tool such as Excel).

It still gives the alarm for both POI files.
I am thinking that the lower would need the elevation on the file also.
>
As for as to the elevation showing on the GPS it is very unstable. It would show -2 ft to 30 ft above my actual elevation. I would contribe that to the ( + , - ) error of about (10 ft +,- )for the GPS.
Will try making the lower road with elevations of a lower elevation to see.

What would the file look like using excel ( ie: lon., lan., road name, @ 45 ?

The easiest way to find out, is to try it ... download the Trial version of GeePeeEx Editor, enter some data, (or import your Favourites) - then 'File | Export as .csv' (the trial has a 5 waypoint limit on this function, so you may need to de-select some entries).

Basically, a header is written for every gpx field, then the data for each record - speed is one thing that is separated out from its 'usual' location (appended to the name).

See also: http://geepeeex.googlepages.com/importingmulti-columncsvfile...

(It's not easy to describe in words!)