P/R Lots (orig. 8/12/12)

[Dan Kaempff]

Hi all,

Mika's recent request for updated P/R lot info prompted me to look into this feature a bit more closely.

In my use of DLC, I'm not seeing the lots appearing on the map when I'm searching for an origin or destination. Since I know where most of them are, I can click on an area or a Google Transit icon on the map to select that area. THEN, a yellow "PR" logo appears to indicate that this location is a Park and Ride lot. Zooming out reveals other P/R lots in the vicinity.

Wouldn't it be better to have the PR icons appear automatically at a certain zoom level prior to the trip origin and destination being selected? That way, people could see where the lots are in proximity to their trip, particularly if they're not aware that a lot is nearby.

Also, the trip I created was from Terrebonne, Oregon to La Pine, Oregon. DLC found the La Pine lot and labeled it as a PR after I selected it, but it didn't find the Terrebonne lot, even though it's on the list that Mika sent around last week.

Am I the only one who's having this issue? Or is this something to look into further?

Thanks,

Dan

Comment by Amol B on August 17, 2012 at 2:55pm           Delete Comment

Hi Dan,

The current behavior is that the PNRs do not show up when a  pre-existing address in the user's profile is selected as the origin or destination. Interaction with the map control such as selecting or resolving an address via the map view shows the PNRs. There are a number of reasons historically why this was in place - one of the main being constraints with the older mapping technology.

The upcoming update does have some changes corresponding to the display of PNRs. One of the changes is specifically that PNR display does not require map control interaction - so for instance, even when selecting an existing address, the PNR should show up.

About the second issue you mentioned, there hasn't been an issue in finding lots - I'm not sure exactly the problem you ran into. Could it be because you selected an existing address - so its another occurrence of the same behavior described above? I would recommed you try it out your scenario once the update is in place.

Happy Friday,

Amol