Is there somewhere I can find information about these 3D file formats or other ones? I am particularly interested in seeing which file formats can hold PMI data?
Product Manufacturing Information (PMI) is usually defined by the following components:
GD&T (geometrical dimensioning and tolerancing).
3D annotations / symbols.
Captured views.
These might be also represented in two ways in format:
Graphical representation (how to actually display information in 3D viewer - usually in form of pre-tessellated geometry).
Semantic representation (just marks / annotates real geometry with extra information; it is up to the application how to use / display this information to user).
There are two key ISO standardized file formats that mentions PMI explicitly:
STEP (most noticeably AP242). Here is a live example of GD&T in STEP.
JT (mostly promoted by a single vendor).
Proprietary and native file formats (specific to one product) might also support PMI (like Catia V5 / SOLIDWORKS), but they are not expected to be used for data exchange. I don't think that FBX has anything directly related to PMI.
There are might be more formats supporting PMI (3D PDF?), but I haven't seen much information about that.
Related
I dont't have any experience with the geographics databases so I hope that you be patiente with me, the thing is: I know that the datatype geography is used if all you care about is measuring distances and lengths and you have data from all over the world and the datatype geometry is used is best if you are pretty comfortable with spatial reference systems or you are dealing with localized data where
all your data fits in a single spatial reference system (SRID), or you need to do a lot of spatial processing (that's what I read in chapter 3 of the documentation of postgis) and I saw on the link https://www.tutorialspoint.com/postgresql/postgresql_data_types.htm the following datatypes: point, line, lseg, box, path, path, polygon and circle. And then I saw the documentation again of the postgis on the section 4.1.3 SQL-MM Part 3 about the following types with the extension well-know text: circularString, compoundCurve, curvePolygon, multiCurve, multiSurface. What I don't understand is: what is the difference between these datatypes?
I am new with using NVIDIA DIGITS. My train dataset has following structure and its format is .hdf5 .
crops Dataset {27482, 3, 128, 192}
labels Dataset {27482, 12}
mean Dataset {3, 128, 192}
pids Dataset {27482}
I know how to feed model with simpler formats like .txt or .jpg. My question is how can i feed my model with .hdf5 format in NVIDIA DIGITS
HDF5 datasets are only used for image classification datasets in DIGITS, and even then the support isn't very full-featured.
Why?
Caffe doesn't support HDF5 nearly as well as it supports LMDBs:
For large datasets, you have to break them up into separate files (see here)
Data is not prefetched - the whole dataset is read into memory at once (see here)
Data transformations are not supported with the HDF5Data layer (see here)
Since DIGITS is primarily Caffe-based for now, our main dataset format is LMDB. If/when we support more backend frameworks, we may decide to standardize on a more generic format like HDF5 or zipfiles.
There appears to be geospatial-query support under Java (https://cloud.google.com/appengine/docs/java/datastore/geosearch) but there appears to be absolutely no documentation for doing the same under Go. Grepping google.golang.org/appengine for "geo" renders nothing but construction and validation of GeoPoint values.
Since Java supports this the API support must obviously be there. Does anyone have any experience with this or advice? Thanks.
Edit:
It looks like what limited support there is is only offered for Java:
http://startup-with-gae.blogspot.com/2016/01/geospatial-queries-with-google-cloud.html
It's, officially, completely unsupported in Datastore at this time. Use geohashes: https://github.com/gansidui/geohash/blob/master/geohash.go . It reduces this fro ma geospatial-storage/RTREE support problem to a string prefix-search.
It allows you derive a hash that describes a particular location, and then you can take this string and successively remove characters from the right side (and do string prefix-searches against your list of places and their geohashes with what remains) to find places near your principal location and expanding outward.
There is a predictable amount of geographic precision between each adjacent character of a geohash string, so you can either use this or the common prefix bytes between the principal point and the corner latitude/longitude of the map window to identify all places that should appear within it.
Recently I started to work on some internationalization aspects of my project, and I need to build a user preference to display numbers (arabic numbers) in their accustomed format.
I did some research online and despite a surprisingly lack of reliant standard documentation I found this article which outlines 7 formats out there. Which is a good starting point.
The question is, how do I represent/store those formats internally?
Formatting numbers should be done at the view level only, so simply store them as regular integers (or floats, depending on your need).
Then only when you need to display them, format them per the current locale.
To store them in the database, since the format is defined by the decimal separator (either "," or ".") and the thousand separator (" ", "," or nothing), I'd just use two simple varchar columns, eg. format_dec_seprator and format_thousand_separator to represent the format.
If some formats don't separate thousands, you can use an empty string separator.
As from what the subject says do anyone know the dimensions of a shipping label for domestic and international shipping?. I have read that labels are printed as 4x6" in 8.5x11" self adhesive paper. Is 4x6" the standard of the shipping labels?
Thank you and more power.
AFAIK, there is no standard label size, that you are forced to use. I have used several combinations of sizes. I primarily use Avery labels and print onto them. You can open up MS Word, go to Envelopes/Labels or similar option and it will given you a list of sizes of the various labels.