Fast Solution with ArcGIS Create a Project (untitled.mxd) set the projection to Geographic WGS84
Load your shapefiles in - a 'warning' that your source data is not in that project - ignore this. Will 'project on the fly' save the project .mxd Then use Export to KML in ArcToolBox [Conversion Tools > MapToKML or LayerToKML] Load in Google Earth - to check alignment To use in Google Maps API use the GeoXML as http://code.google.com/apis/maps/documentation/services.html#XML_Overlays Or if have ArcInfo either use project tool [Data Management >Projections and Tranformations> Project] no .prj file then use [Data Management >Projections and Tranformations> Define Projection] Many other ways in ArcGIS As John mentions PostGIS is a very powerful and free solution. Highly Recommended. Don't worry too much about the accuracy for small scale mapping as Rossko details [Google Maps and Google Earth has varying scales and sources so some inaccuracy occurs] Mapperz http://mapperz.blogspot.com/ On Apr 23, 7:29 pm, mapcoder817 <[email protected]> wrote: > Candegrl, > > The X/Y coordinates you are dealing with are "State Plane > Coordinates." According to the information you have provided, you're > in the Florida East Zone, NAD83. The coordinates in your file appear > to be written, Easting, Northing (X,Y) which is unusual (typically > northing comes first). There are a couple of things you can do to > convert state plane to lat/long. > > 1) Use the NGS geodetic toolkit,http://www.ngs.noaa.gov/cgi-bin/spc_getgp.prl > but that only does one point at a time. They have a link to a > download for SPCS 83, which may do batch, but I've never used this > tool. Note, your zone number is 901. > > 2) Use CorpsConhttp://crunch.tec.army.mil/software/corpscon/corpscon.html > It may be a little difficult to install and use, but it can process > batch files, and it gets the job done. > > 3) See if any of the ESRI products (i.e. ARCGIS) in your office can do > it. > > Dealing with state plane coordinates is VERY tricky. Even experienced > land surveyors make major mistakes. Here are a couple of things to > watch out for: > > 1) The coordinates for your current project are apparently in U.S. > Survey Feet (1ft = 0.304800609601), NOT International feet (1 ft = > 0.3048m). It may not seem like much of a difference, but it can lead > to 15 ft errors. > > 2) *ALWAYS* stick a couple of converted points into google maps or > google earth and make sure they fall where they're supposed to on the > aerial photos. You'd be surprised how often your field person has > blown a measurement, or you have made a careless mistake. > > I've converted your point number 7354 (from your file) into lat/long, > and get: 29.7577585,-81.2490777 > > Here is a link to it in google maps Street View. You can even see the > hydrant!:http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=29.757758... > > Good Luck! > > Jeff > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps API" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/google-maps-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
