Unfortunately, the answer to this is "no" – the two bridge methods provide more secure ways of entering the tor network and fundamentally work differently. Obfs4proxy is designed to make traffic look like encrypted web traffic, known as SSL, and alters the statistical properties of the traffic as a result. The path your data takes when using obfsproxy looks a bit like this (sorry for the awful diagram!)
OBFSPROXY CASE
+--------------------------------------------------------------+
| +----------| |
| Your Computer |Tor node+--------->Internet|
| + +--------> | |
| | +v-----| | |
| | | |----> | |
| v +----------+ |
| Obfs4proxy server+-----------> Tor node |
| |
+--------------------------------------------------------------+
In other words, the obfs4proxy server just acts as a bridge to the tor network. That's why they're called bridges – the network itself does its onion routing thing, and then directs your data to its destination, be that an onion site within the network or an external webserver.
Meek works differently, using a technique called domain fronting to make it appear that you are connecting to one website in particular -- nowadays, Microsoft Azure alone. So, the diagram looks a bit different but the concept is the same:
MEEK-AZURE CASE
+--------------------------------------------------------------+
| |
| Your Computer +----------| |
| + |Tor node+--------->Internet|
| | +------>+ +--------> | |
| | | | +v-----| | |
| v + | | |----> | |
| Microsoft Azure | +----------+ |
| +------------->Tor guard |
+--------------------------------------------------------------+
Note that the difference is with meek you don't actually connect to Azure, really, unlike with obfs4proxy. So it's much more censorship resistant, but because of these single links, unfortunately is really quite slow. They are very hard to block though. Signal uses this technique in China, and there's a good explanation of how it works here: https://securityaffairs.co/wordpress/54659/digital-id/signal-domain-fronting.html