Are you sure your lat/longs are correct? What are your lat/longs referenced to? If they are WGS84, then your points are in the Lake, offshore from NavSta GL. The only reason I think you would need to be in the Lake would be to analyze or use bathymetry data. If that's the case, you'd need elevation and your csv doesn't have z-values.
BTW, if you want to perform a query, you don't necessarily need an ODBC because there are other ways to query without using an ODBC. However, if you really do, then you'll need to get the ODBC set up which means you'll need to download and install a Microsoft Access Database Engine that allows your dwg to connect to, and communicate with, a csv, xlsx or txt file. There are several MS DB Engines, your selection depends on your Acad version, your MS Office version, and your Operating System version. Picking the correct one is critical. Installing it can be an absolute beast. Make it easy on yourself, put in a ticket and let IT do it.
You can even bypass M3D and import your points to Google Earth Pro without any additional formatting to your csv. In GE Pro, go to File=>Import=>Change files of type to Generic Text=>Browse to your csv=>Open. Then, in the Places Panel on the left, scroll down to Temporary Places Section and check the box that has the same name as your csv file.
If you still want to perform a query, fix your lat/longs and post again.
Chicagolooper
@АлексЮстасу wrote:In my opinion, the points are not in the water, but in the snow - in Antarctica. 🙂
Latitude -87°.
LOL! No, no. This is a joke, right?
They are not in the snow. You are mixing up longitude and latitude. Latitude is not -87, that's longitude. Latitude is 42.
Map 3D refuses to convert to a cartesian coordinate system (UTM83-16F) from latitude-longitude (ll84):
"Can't transform point from Lat Long."
This is probably somehow related to the mathematics of Map 3D.
(For example, the Vincenty algorithm has a limit for latitudes from -80° to 84°).
Can't transform in Map 3D?? Are you sure? I know I can. And I'm sure there's a few other who can too.
Chicagolooper
You can load points with any number of characteristics. I will consider the example of dwg.
1. Remove the point numbers at the beginning in csv. Or drag them after the coordinates.
2. In dwg install ll84.
3. In dwg create a point block with attributes, the number of attributes is equal to the number of characteristics.
4. In dwg, create an Object Data description with fields of the same names as block attributes.
5. Download lisp Point Manager / PTM. APPLOAD it to AutoCAD. Call the PTM command.
6. Load points in dwg in the form of blocks with attributes. The option Current Point Format - Change allows you to set the reading order of coordinates:
7. Use the ADEGENLINK command to attach the Object Data to the points, loading the contents of the attributes into the OD fields:
8. Save, close dwg.
9. Create a new dwg, install the UTM83-16F.
10. MAPWSPACE, ON, Map Explorer tab. Drawings, Attach - dwg with dots.
11. Current Query, Define, Property all Layer, Execute Query:
12. Drawings, Detach - disconnect the dwg source.
Items 4, 7 about Object Data can be omitted. It is possible to select according to attribute values. But more convenient by OD.
An example is attached for Antarctica. 🙂
The block, attributes, OD, fields - all just for an example.
I could write this right away, but I hoped that someone would know a simpler way...
I, and I'm sure many others, don't care how it's written or displayed in other programs. Map 3D, Civil 3D as well as other GIS programs conveniently provide an option to designate whether it's X/Y or Y/X, whether it's northing/easting or easting/northing. This is why the formats such as PNEZD and PENZD exists in the first place. Because those programs, and more importantly, the users of those programs need to hit from both-sides-of-the-plate in order to optimize baserunning and scoring situations, not to mention improve batting average.
Since the OP already alluded to his points being offshore from Navel Station Great Lakes and in the water, Lake Michigan (the 4th largest freshwater 'pond' on the planet), deductive reasoning would position his points at a positive latitude north of the equator, and a negative longitude or beginning from the prime meridian then traversing westerly across the Atlantic.
Any navigator, geographer or cartographer, whether dead or alive, historical or modern, brilliant or not, would ascertain that given the north pole and equator, the the numbers noted above would mean a positive lat and a negative long. Or should it be a negative long and a positive lat?😊
Chicagolooper
You can try converting your points file into two files - mif/mid.
Using Excel and a text editor is quite simple.
These are text files: mif - table description and geometry, mid - table contents, characteristics.
And MAPIMPORT immediately with the conversion of coordinates, with the loading of characteristics in Object Data, into the attributes of the desired block:
Here is something from years ago. https://map3d.wordpress.com/2008/01/02/bring-a-csv-file-into-map-3d-with-data/
Another option is using the Map Task Pane and set up a survey data store. Then import ASSCI file.
Jonatan,
I can't see any easy way to do what you want in Map 3D. In the free QGIS you can import that CSV and export it as a Shapefile in about 30 seconds. QGIS will even allow you to export your Shapefile in UTM83-16F. With a Shapefile you can Query and Label those points easily.
Dave
Dave Stoll
Las Vegas, Nevada
This is not a comprehensive exercise that covers the details and nuances of performing a query. This is merely the down-n-dirty way. Of course there are other, more elegant ways that use sophisticated workflows and achieve a narrower focus. This post, however, serves to demonstrate some of the basic options available using your specific csv file.
Given the the rudimentary composition of your csv and the absence of a specific goal you would like to achieve, no ODBC connection was used in this workflow. Since Map 3D's query parameters provide enough horsepower to query your lake points, other add-ons to the drawing would only constitute extra baggage and provide only fluff without any meaningful utility beyond Kardashsian-esque glamour.
You can do it. Warning: Combining this workflow with other instructions may (and I don't care where they came from or who uttered them), or may not, derail this entire workflow. Use caution when deviating from the prescribed steps. Here's the down-n-dirty that you can use to do the deed:
Format your csv like this. Do it now. Notice the column headings are preceded with '#.' It's critical to insert it before each heading because if not used, M3D will be confused and treat the headings as data when they're not. You may also delete the first row altogether and avoid any potential confusion the headings may cause. Your csv will need exactly 5 columns. Column E, the 5th column, contains 7 columns from your original csv. The 7 columns have been combined in excel using an excel formula. The formula was then copied and applied to all rows to efficiently generate the results. Implementation of the formula will not be covered in this exercise since you can do that on your own. Save this newly reformatted csv and close it. In the next step, you'll use MAPIMPORT command. The command won't work if your csv is open.
Use MAPIMPORT command (Insert tab=>Import panel=>Map Import icon). Browse to your csv and choose PENZD (comma delimited) from the dropdown. You are specifically choosing PENZD because that's how you formatted your csv.
Make the import settings exactly like shown. When done, click OK to import your points.
Zoom extents to see your points. Your points will likely overlap because the block, Map_Survey_Point, will be too big. You'll need to rescale the blocks. Select all the points and rescale in the Prop Palette. Use the same number for scale-x, -y and -z. The scale should be smaller, e.g. 2000, than what's shown in the Prop Palette for the overlap to go away.
Because you've assigned UTM83-16F to modelspace and have indicated LL84-WGS84 was the CS used in the csv, your points will transform from lat/long degrees to UTM zone 16 feet. Turn on Bing aerial imagery to view the points with an aerial photo basemap. Since you stated in Post 3 of this thread that your are identifying Lake Coordinates, then yes, they're all wet because they're in the Lake! Haha! Save this dwg. Give it the name SETUP.dwg then close it. In the next step, you'll perform the query and the query can't happen if SETUP.dwg open.
Go to The Task Pane=>Map Explorer Tab=>Right click Drawings=>Attach=>Browse to SETUP=>Select SETUP=>Add=>OK. SETUP will now be displayed int the drawing tree under Drawings like shown below.
You will now begin building your query. (You can use your imagination to build your query, I’m obviously building an oversimplified one.) Still on Map Explorer tab, right click Current Query=>Define. Next, Location=>All=>OK
Continuing with the build, Click Data=>Attribute=>Map_Survey_Point=>Operator ‘=’ sign=>Then manually enter ‘*red*’ (without the quotes & include asteriks)=>OK. Then Execute Query to view results.
Up to this point, your query will consider all objects (I say all but really mean most because M3D will not really consider all objects, there are exceptions where objects are not considered, i.e. Civil 3D objects are not recognized in this type of query) in modelspace and evaluate whether red appears under the attribute DESC in any of the Map Survey Blocks. If red is not in the DESC attribute, then that block will be ignored. BTW, the * is a wildcard and is used to match red to any part of the DESC string.
When you build your query, you may get a pop-up message asking whether you want to save changes back to SETUP.dwg. Do not save back! You want to keep SETUP in its original condition. Decline any offers to save back because if you do, you’ll overwrite and essentially end up replacing the file.
You have successfully isolated all instances where the word red has appeared in the attribute DESC. If you wish, you may select the results of the red query and put them on a dedicated layer name RED.
You could have also chosen a different attribute or a different attribute value. You could have also used an operator other than the ‘=’ sign. You could have also queried Object Data as opposed to a block Attribute. As you can see, the permutations are mind boggling.
If you have put the result on a dedicated layer named RED, freeze that layer.Continuing with building a query, delete all lines below ‘Locations: ALL.’
In this next example, you will query all rows that satisfy three conditions: 1) Green, 2) Left and 3) Heavy. From Define Query dialog. There are exactly 7 points, that satisfy all 3 conditions, they are Points No's 16 through 22, see the orange highlighted rows.
Define the query, it should look like this.
When you execute the query, the results will look like this. The 7 points are shown with Bing aerial as a basemap. Points where the 3 conditions are NOT met are ignored and are not included in the 'Results.'
This concludes the Down-N-Dirty way. For a more elegant way, describe in detail, what you are trying to achieve then repost with a new Subject Line.
Chicagolooper
Type a product name
