addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobe--smallglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1launch-new-window--smalllight-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Fwd: Geoclient v1 - Bug Fix Notification

From: Noel Hidalgo | B.
Sent on: Wednesday, December 18, 2013 2:28 PM
FYI for those of you who use NYC's GeoClient API. 

N

--
Sent from my TI–85

Begin forwarded message:

Date: 18 December[masked]:36:43 EST
Subject: Geoclient v1 - Bug Fix Notification

Hello Registered Geoclient User,

A bug was recently discovered in the Geoclient service in which values for the lat/long-related coordinates are reversed. Specifically, this bug affects the following fields:

latitude/longitude
latitudeInternalLabel/longitudeInternalLabel

Please note that the following fields are correct and will not change: xCoordinate, yCoordinate, internalLabelXCoordinate, internalLabelYCoordinate

On January 8th, 2014, DoITT GIS will be releasing a patch to the Geoclient service which corrects this bug. Depending on your current use of these values, this change may impact your application.

If you have any questions, please contact Matthew Lipper ([address removed]) at (718) 403-8094.

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy